NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi Firmware update 2.5.0.38 problems
Have a 2 year old RBR50 with 2 satellites - have had no problems until recent update to 2.5.0.38. Everything is working howerever the GUI now has issues when attempting to display devices. The web ...
The reset and setup from scratch on the RBR will probably fix the issues your seeing. Try then when your ready.
RonRolfsen wrote:After several reboots still have the problems (no Main page, no devices attached). I wanted to downgrade to 2.5.0.30 but now when I go to the Advanced-Administration-Firmware Update in the web gui get the:
400 Bad Request
This server does not support the operation requested by your client.
Mobile app does not allow a firmware downgrade as far as I can tell.
Is there a way to telnet into the router and downgrade the firmware?
(have not yet tried reset - saving as last resort since things are 'working')
Sometimes a factory reset is needed. Some users have had not to reset. Some have and has helped get there systems working. For these problems, a factory reset and setup from scratch should be tried as a last resort. I had no issues after manually updating FW to v38. Asided the device naming problem found, v38 is stable on my RBK50.
Good Luck.
Retired_Member wrote:I didn't pay 400+ bucks to have to factory reset my equipment each time there is a patch or upgrade. That would make this product (or any other) worthless in my opinion.
2.5.0.38 was installed after alert appeared on my ORBI app. I have 3 satellites . Installation went fine . All devices working , speeds are good BUT the new enhanced device recognition is a joke. The names and types of my 30+ devices are scrambled e.g: Thermostat showing up as a Door Bell, Garage Door as a camera, Laptop as a smart speaker etc. That would be a minor inconvenience IF i were able to manually edit but the changes made via the UI do not always stick. Some do . Seems to be more succesful when editing the details on a computer that is attached to the satellite where the device is incorrect. But not consistent. Like others in this community I also view being asked to rest to install incremental firmware as unreasonable.
There does seem to be a new device recogniction system in place in new FW. The naming of devices is a known issue. Since the behavior of this new system seems to be giving odd problems, I would try a factory reset on the RBR and set up the system from scratch. See if the behavior changes.
Various issues seen with other router mfrs so NG isn't the only one with FW issues. Maybe done differently however problem abound throughtout the router communities. Been like this for years. I do wish there was more in house testing before release to public.
texjones wrote:2.5.0.38 was installed after alert appeared on my ORBI app. I have 3 satellites . Installation went fine . All devices working , speeds are good BUT the new enhanced device recognition is a joke. The names and types of my 30+ devices are scrambled e.g: Thermostat showing up as a Door Bell, Garage Door as a camera, Laptop as a smart speaker etc. That would be a minor inconvenience IF i were able to manually edit but the changes made via the UI do not always stick. Some do . Seems to be more succesful when editing the details on a computer that is attached to the satellite where the device is incorrect. But not consistent. Like others in this community I also view being asked to rest to install incremental firmware as unreasonable.
I don't know your setup, but the advice to do a factory reset after every FW update is very weird. A factory reset will cost me a day to get every thing setup as before. During that time, all my camera's and other security devices won't be operational. That should not be necessary with an expensive system like this. In fact, if i really had to factory reset every time an update was issued, i would certainly dump the whole system.
A factory reset is a last resort method to check for problems and resolution. Though I and a few others use this in our normal manual FW updates methods, I understand that users shouldn't have too. However, again when problems appear or appear after FW updates, and all other troubleshooting has been exhausted, then a reset and setup from scratch should be performed. Seen many problems resolved after a reset. Lingering prior FW code or user mis-configurations with newer versions of FW code seem to cause problems. Resets allow the FW to be cleared out and start fresh.
To save time on factory resets and configurations, you should already be using Backup Configuration files. These save time. Do you not know about this feature?
v38 is working for me and others. You don't have to use it as well. Use what works for you.
PetervdK65 wrote:I don't know your setup, but the advice to do a factory reset after every FW update is very weird. A factory reset will cost me a day to get every thing setup as before. During that time, all my camera's and other security devices won't be operational. That should not be necessary with an expensive system like this. In fact, if i really had to factory reset every time an update was issued, i would certainly dump the whole system.
texjones wrote:2.5.0.38 was installed after alert appeared on my ORBI app.
This doesn't mean you have to upgrade.
I have the same naming problem, and I have 40 devices. I do not want to reset and start all over. I even downloaded v.40 thinking that would be a fix, but it was not. Does anyone know if this problem will be fixed by Netgear and when? Thanks.
A factory reset and setup from scratch should be performed as a last resort to see if this resolves what your seeing.
If you reset and setup and it fixes your problem besure to do a backup configuration to file for safe keeping. Saves time when resets maybe needed.
You can down grade FW as well.
dancar wrote:I have the same naming problem, and I have 40 devices. I do not want to reset and start all over. I even downloaded v.40 thinking that would be a fix, but it was not. Does anyone know if this problem will be fixed by Netgear and when? Thanks.
I also downloaded v.40, and no change in the names of the devices. Please let me know if you get an answer about a fix from NG. Thanks.
Try power cycling the Obbi rather than a reboot.
Solve my issue after that.