NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi RBR50 Device Names not Saving
I'm using the RBR50 through my Verizon Router as an AP and I'm trying to change the device names of my connected devices to know which device is which. Initially, when I was setting up the first few...
THe naming of devcies is confirmed and known and NG is aware of it. The impact of naming devices is really not a show stopper and more of an inconveience to users. Doesn't really impact operation or cause the system to fail, thus no reason to pull it.
Users will need to be patient, I presume the next FW update will have a fix.
Tizmasel wrote:Same problem here. I updated today then realised something was wrong. Subsequently found this thread. There's clearly a significant bug in this update so why wasn't it pulled earlier?
While it may be working for some folks on .30, devices is broken for me as well. Hit and miss whether or not the device type and/or name stick. I have no idea how Netgear can get away with this issue for as long as they have. If Netgear was deploying software for Apple or Microsoft, they would have been fired for releasing such a release. Or, at the very least, they would have fixed the issue the day of. But, they don't care about the paying consumer that actually keeps them in business. They have a glorified Executive Team that probably know nothing about ALL of the frustrating issues that their very products cause for us but it gives them a pretty good livelihood - as is mostly the case in the corporate world.
Some have said v40 works for them:
If you choose to update, manually download the FW files for the RBS and RBR. Install them then factory reset the RBR and setup from scratch. See if this helps your system. I would factory reset the RBR and setup from scratch to remove any lingering older code.
NG is aware of the problem found in v38 and is working on it:
This isn't a show stopper problem, though a inconvienence for some, and it's only been a month since it was discovered.
migsta wrote:While it may be working for some folks on .30, devices is broken for me as well. Hit and miss whether or not the device type and/or name stick. I have no idea how Netgear can get away with this issue for as long as they have. If Netgear was deploying software for Apple or Microsoft, they would have been fired for releasing such a release. Or, at the very least, they would have fixed the issue the day of. But, they don't care about the paying consumer that actually keeps them in business. They have a glorified Executive Team that probably know nothing about ALL of the frustrating issues that their very products cause for us but it gives them a pretty good livelihood - as is mostly the case in the corporate world.
It doesn't work. It's broken. I have used a brand new router (because i needed a satellite had the spare useless router) and i have factory reset including loading the firmwre using tftp command but it does not work. Devices is broken. And, as I've said countless times, devices works just as crappy on the RAX series routers. Devices has been broken with Netgear for months. This is issue is evident with the iOS app and GUI app and with all of your most popular routers. Maybe, it works for Android folks?
Something to contact NG about or wait for the next FW update. Someone already said NG was planning a FW update this next month.