New - RBR750 / RBS750 Firmware Version 4.6.7.13 Released

Unfortunately, that is the only surefire way to make sure that things/memory/stuck stuff get cleared out and the new be really be new. 10/10 times if you use a backup, which I admit to doing, you could bring back over problematic things that developed that is putting you in this place. And a Power Cycle of each device after wouldn't hurt either. Start with unplugging the Orbi, then Sat 1, then Sat 2 and so on. Then Plug the RBR back in and let it come back up all the way. The Sat 1, then Sat 2, rinse and repeat.

Having to reinput the settings is a pain, I use to use PDFs of each page that needed changes to follow. Now I have done this so many times I have memorized many of the settings.

As far as the Orbi App, it should show you a selection saying that you want to do it manually. That should take you out of that App wanting to it. I have to use PPPoE login with a Tagged 201 VLAN that the app doesn't support. So I always have to do it manually. If it still acts up, I'd uninstall it, then reinstall. Yes, I too hate the way this sometimes doesn't mesh when trying to set thing up when you're in a bad mood as it is . . . .

---

MNChuck wrote:

I did end up doing a factory reset of the router and both satellites, and set the system back up from scratch using the orbilogin website on a pc connected to the router via ethernet cable.  That all went smoothly, and so far the system is stable.   Interestingly, my wifi connected devices seem to be working much better with no freezing of web pages, etc.

The only issue now is that the Orbi app on my phone does not recognize the system as being set up and is trying to get me to set it all up again.  Is there a way to get the Orbi app to see the system as set up?

---

After the last update I am having issues with devices connected to the Satellite dropping offline, in particular my thermostat. If I shut the satellite off and the thermostat jumps over to the router it immediately comes back on line and I can see it via its app or the web page. I performed a factory reset and am hoping this resolves the issue.  So far the thermostat is staying connected to the router instead of the satellite. I'd have to try 'forcing' it to the satellite to test whether the factory reset helped. 

Glad you got it working. Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System

There seems to be a odd issue with Orbi app. We've passed this on to NG for review.

---

MNChuck wrote:

I did end up doing a factory reset of the router and both satellites, and set the system back up from scratch using the orbilogin website on a pc connected to the router via ethernet cable.  That all went smoothly, and so far the system is stable.   Interestingly, my wifi connected devices seem to be working much better with no freezing of web pages, etc.

The only issue now is that the Orbi app on my phone does not recognize the system as being set up and is trying to get me to set it all up again.  Is there a way to get the Orbi app to see the system as set up?

---

The algorithms behind the "assignment" of individual devices to a satellite or the router is a continuing mystery because it seems a) unpredictable and b) dynamic/changeable. Superficially, common sense does not always reign here, in that a device close to a satellite will connect to the router, or will connect to the close-by satellite and then later jump to the router, or vice versa, sometimes permanently and sometimes not. It is entertaining!

My experience is that the firmware's bias is toward the router so as to sidestep the satellite's middleman function when desirable, which does make some sense. The only solution I've so far found to "correct the assignments" is to reduce the transmit power of the router (in my case to 50 percent, doable only through the desktop interface) so that the satellites are more likely to reliably latch on to their nearby devices. I note this "reduced router power bias balancing strategy" as the assignment of individual devices to routers vs. satellites seems to be a pain point for some Orbi owners. I suspect that most don't care what connects where as long as the in-use performance of the connected device meets expectations. Please correct me if you have a better interpretation and good luck to all.   

My issue does't really lie with whether the device connects to the satellite or the router.  My issue is why when its connected to the satellite does it go offline and immediately come back to life when the satellite is removed from the picture and it jumps over to the router.  My satellite is about 30 or so feet from the router however the thermostat is pretty much halfway between the router and the satellite.

Saw same thing with NEST controllers couple of years ago. I found that with mine, one NEST controller being 4-5 feet away from the RBR. Would still ping pong back and forth thus causing the NEST to drain it's battery. I found last year that after I moved the RBR to a different location, 25 feet away the NEST stopped ping ponging back and forth. Also reduction in transmit power helps as well. 

What the distance between this one device and the RBR and RBS? 

It's probably about the same distance from both, I'd say maybe 12-15 feet.  The thermostat having the problem is on the same floor as the router, the satellite is upstairs. The path may be a little less obstructed to the satellite as it only has to go through the floor and not a wall. I'm not sure how much the signal from the orbi radiates downward? But this issue is new since the most recent firmware.  

So ya, being about equal distance from the device to the RBR and RBS, seems that it can't make up it's mind on which signal source to lock on. Turn the transmit power and see if this helps. You may need to move the RBS and or RBR around to see if you can get the device to lock on better. 

---

Timothy88 wrote:

It's probably about the same distance from both, I'd say maybe 12-15 feet.  The thermostat having the problem is on the same floor as the router, the satellite is upstairs. The path may be a little less obstructed to the satellite as it only has to go through the floor and not a wall. I'm not sure how much the signal from the orbi radiates downward? But this issue is new since the most recent firmware.  

---

I can give it a try.  It's very befuddling how it decides which to use. My wife's office is directly above the router and her laptop would be closest to the router but it chose the satellite which is on the opposite side of the house. 

Yep. It's up to devices to pick and choose where they connect too. 

This will be problematic for the controller if it's in between the RBR and RBS and the distance is about the same from the controller to the RBR or RBS. You'll need to move the RBS closer to the RBS then turn down the RBRs transmit power in hopes that the controller connects to the RBS. Again this is a controller issue with it handling different signals and preferring to connect to the RBS. 

Another possibility is that the RBS is not in a good state. Thus something on the RBS maybe wrong. A full re-load of the RBS firmware, factory reset, remove the RBS from the RBS web page and setup and resync of the RBS while in same room may help with this, then place back in remote location. 

Why not revert back to FW that was working for you as well. 

Can you draw up a floor diagram of where you have the RBR, RBS and these controllers at and give the distances? 

How big is your home? Sq Ft? 

---

Timothy88 wrote:

My issue does't really lie with whether the device connects to the satellite or the router.  My issue is why when its connected to the satellite does it go offline and immediately come back to life when the satellite is removed from the picture and it jumps over to the router.  My satellite is about 30 or so feet from the router however the thermostat is pretty much halfway between the router and the satellite.

---

This will be problematic for the controller if it's in between the RBR and RBS and the distance is about the same from the controller to the RBR or RBS. You'll need to move the RBS closer to the RBS then turn down the RBRs transmit power in hopes that the controller connects to the RBS. Again this is a controller issue with it handling different signals and preferring to connect to the RBS. 

Why has it worked for all this time and then after a firmware update its now a problem?

Another possibility is that the RBS is not in a good state. Thus something on the RBS maybe wrong. A full re-load of the RBS firmware, factory reset, remove the RBS from the RBS web page and setup and resync of the RBS while in same room may help with this, then place back in remote location. 

Already tried this. 

Why not revert back to FW that was working for you as well. 

I mentioned that as well.

Can you draw up a floor diagram of where you have the RBR, RBS and these controllers at and give the distances? 

Already gave approximate distances in previous post.

How big is your home? Sq Ft? 

Approximately 2000 SqFt.

I've given up on the issue. I've lost way too much time in my life on this. It's extremely frustrating to pay the kind of money that is being charged for these devices to have the amount of problems they do.  Look at this entire forum its all about problems that people are having with these devices.  I surely don't see many positive posts regarding these products.  

For now I've decommissioned the satellite and am only running the router.

I am curious about one other thing:

What does Netgear give you that you defend them so much?

And again I reiterate how can you trust what's being released when they can't even catch a blatant bug in the app with a totally missing device icon. It probably does't affect functionality but it sure doesn't promote confidence in their abilites.

---

Timothy88 wrote:

This will be problematic for the controller if it's in between the RBR and RBS and the distance is about the same from the controller to the RBR or RBS. You'll need to move the RBS closer to the RBS then turn down the RBRs transmit power in hopes that the controller connects to the RBS. Again this is a controller issue with it handling different signals and preferring to connect to the RBS. 

Why has it worked for all this time and then after a firmware update its now a problem?

Possible NEST could have changed something on there side as well. 

 

Another possibility is that the RBS is not in a good state. Thus something on the RBS maybe wrong. A full re-load of the RBS firmware, factory reset, remove the RBS from the RBS web page and setup and resync of the RBS while in same room may help with this, then place back in remote location. 

Already tried this. 

 

Why not revert back to FW that was working for you as well. 

I mentioned that as well.

 

Can you draw up a floor diagram of where you have the RBR, RBS and these controllers at and give the distances? 

Already gave approximate distances in previous post. More accurate distanced would be preferred. 

 

How big is your home? Sq Ft? 

Approximately 2000 SqFt.

For this size of home, just the RBR is enough to cover so having the RBS and such in this size of home and the controller in between will be problematic at best. The RBS would not really be needed. This is NOT the first time NEST controllers have causes problems with Orbi. Again this is a handling on the devices side. 

 

I've given up on the issue. I've lost way too much time in my life on this. It's extremely frustrating to pay the kind of money that is being charged for these devices to have the amount of problems they do.  Look at this entire forum its all about problems that people are having with these devices.  I surely don't see many positive posts regarding these products.  

For now I've decommissioned the satellite and am only running the router.

I am curious about one other thing:

What does Netgear give you that you defend them so much? This is not a defensive thing. I've already troubleshot this with a NG engineer two years ago and spent time with collecting logs and trying different configurations. Some of this was dealt with by NG and also GOOGLE/NEST was involved as well possible NEST has done something as well on there side. 

 

And again I reiterate how can you trust what's being released when they can't even catch a blatant bug in the app with a totally missing device icon. It probably does't affect functionality but it sure doesn't promote confidence in their abilites. IMO, this isn't a FW bug, rather a environment and configuration issue. Again your size of home and placement of the controllers and RBS is playing a roll in what your having problems with. I see others are not having issues with there NEST controllers. So this mostly pointed to your environment and conditions and not being a bug.  

 

 

---

Sounds defensive and deflecting from Netgear again.

 Examples:

1. Possible NEST could have changed something on there side as well. 

2. This is NOT the first time NEST controllers have causes problems with Orbi

3.IMO, this isn't a FW bug, rather a environment and configuration issue. Again your size of home and placement of the controllers and RBS is playing a roll in what your having problems with. I see others are not having issues with there NEST controllers. So this mostly pointed to your environment and conditions and not being a bug.

Number 1.  How did Nest change something? Last firmware update was 11/2/2021?

Number 2. How about this in not the first time we have seen problems with Nest thermostats on an Orbi system?

Number 3.  My environment hasn't changed. I've seen one or two posts in this thread doesn't mean others aren't having a problem and just haven't noticed it or haven't upgraded firmware. Are you a Wifi engineer?  

Agreed that the satellite may be overkill for the square footage but it is a two story house. It's sold as a "Whole home mesh system" with coverage up to 5000 sq ft. Well I am in the up to 5000 sq. ft. so that really shouldn't be a problem. And if it is then Netgear should let you purchase just the router.  

Try to take off the Netgear glasses and look at this logically to what has changed most recently and that is the Netgear firmware. 

The last firmware update on for the thermostat was 11/2/2021.  So Nest put a 5 month  orbi wifi bug in their firmware? 

There have been NO changes in my environment other than upgrading firmware. 

How can you without a doubt guarantee that there is possibly not an issue introduced?  Netgear does not have a great track record with their releases?

I am truly not trying to be confrontational ,demeaning or belittling and I know that Furry is trying to be helpful but I just see the same genertic responses; reboot, reload defaults and reload setup.

It has to be something on your end there's no way it could be Netgear's problem. It's as bad as dealing with Comcast, while I understand that in a few cases that a reboot may resolve the issue they are not generally the answer.  Restoring factory defaults to me is somewhat of a catastrophic process and should not be an acceptable solution after a firmware update.  If it is then it should be detailed as the process and there should not be an automated firmware update process.

I got the same initial response when I reported the issue with the missing icon in the app. Luckily I was able to get reconnected after I deleted and reinstalled the app. This is a little off topic but I'm trying to point out the generic responses.  

I would say that most people come to the forum for answers because most are tech savvy enough to have tried the initial steps.

Jimbo84 

Is it connected to the satellite or the router?

What instructions should be necessary for an automated update process, shouldn't this be autonomous? 

If there is a problem with the automated update process then it should be removed until it is fixed.