Firmware 2.3.5.30 valid for RBR50/RBS50?

rjantigua
Guide
Jul 16, 2019
Thanks for the update. I think pushing the update before updating the site can cause confusion if the site doesn't document support of the version with the model in question.

I work from home (read long hours), so I'll have to try it late in the night. I'm just realizing as well that with houses and devices becoming more and more connected, any network downtime has to be scheduled as if I'm upgrading a production server. Sigh. I'll try it again within the next couple days.
- FURRYe38
  Guru - Experienced User
  Jul 16, 2019
  The push to users system are for users to try if they wish to. NG isn't forcing updates anymore. So users dont' have to do FW udpates if there systems are working. If the files are not on the download site then it means FW is still being tested to ensure good operation before NG posts them.
  
  Let us know how it goes.
  - rjantigua
    Guide
    Jul 19, 2019
    I ran the update following the suggestion of starting with the satellites first. They updated fint with no issues. The router started fine but wouldn't come back, staying on the screen indicating that the update was in progress for over 20min (I didn't want to reset the router thinking it might still be updating the firmware for some reason). My laptop is hardwired to the router, so thinking it might be my stack, I reset my ethernet connection (no luck), then rebooted with no luck either. Then I tried going in via wireless, and lo and behold the login prompt popped up and I was able to get in. Both satellites showed up fine. I eventually went back to an ethernet connection with no issues.
    
    Then as I'm about to log off, I noticed that one satellite (Sat1) disconnected. Configuration is: Router in the basement, Sat1 on 1st floor, and Sat2 on second. Sat1 (closest physically to the router) was the one offline. Tried sync, power switch, unplug for 30sec...no luck. I also noticed that neither the blue or magenta lights displayed. Tired of running the stairs in the middle of the night (morning) I switched to my laptop on the first floor which normally connects wireless to Sat1. No internet, but it was connected. When I powered down Sat1, it connected to the router and I could log into the console and verify I was on the router and Sat2 was up. Then I hit the reset button on Sat1 (no luck), then I tried one more time holding it down to get a factory reset (flashing amber light, right?), and it eventually came up with the eventual blue light. I debate if it got to factory reset, because the node name and IP came up as before (Does it get that info automatically from the router??).
    
    Anyway, All three nodes are up for now and will monitor to see if anything happens over the next week or so. My apologies for being verbose, but I wanted all my trials and tribulations here in case it helps someone else.
    
    Just one other thing: When I previously updated to 2.2.1.212, then, 2.3.0.32, then 2.3.1.44, and then to 2.3.1.60 I had zero issues with either the router or satellites. This v2.3.5.30 was a different animal. Even when I had the initial issues with 5.30 and rolled back to 1.60, it went without a hitch, other than warning me that I was installing an older version.

Forum Discussion

Firmware 2.3.5.30 valid for RBR50/RBS50?