NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Nest Protect with Orbi RBR850
Recently upgraded to the new Wifi 6 Orbi System (RBR850) after being very happy with the original. Ever since upgrading, my Nest Protects have had connection issues. First it was just one that was no...
What Firmware version is currently loaded? if v15.25, then there seems to be a problem with this version of FW and Nest products. My Nest controllers fail to keep connected if AX mode is enabled. So Ive disabled AX mode. Prior version v11.2 released FW worked well with NEST.
If changing CTS and AX modes doesn't seem to resolve this you may need to revert back FW versions.
JerBear81 wrote:Hello,
I also recentely got an RBR850 and matching sattelite and am having problems with my Nest thermostat battery draining. I had some troubles with my Nest Protects at first and, to be honest, can't remember how I resolved it...I think I had to factory reset and start from scratch. I couldn't just update the settings. However, Nest is telling me the problem with my battery is the WiFi signal and not the battery. From what I'm reading here, that may be accurate. They gave me a link that has settings to change. One is to enable 802.11 b/g/n which is enabled on my router. I have also checked off the box to enable AX functions and I have a lot of IoT devices and so AX was one of the main reasons for upgrading to this system. Next it tells me to increase the DHCP lease time to at least two hours. I cannot find anywhere to change this setting and from reading other posts there seems to be some disagreement whether this is default to 1 hour or 1 day. I did assign it an "address reservation" in the Advanced Tab -> Setup -> LAN Setup menu. I hope this helps. I decided to change the CTS/RTS threshold to 2347 based on the suggestions contained in here. Otherwise, most of Nest's troubleshooting suggestions on the provided link do me no good. They also want me to use my phone as a hot spot for the thermostat to "isolate the issue". If you all have any suggestions, I highly appreciate them. This is my first time posting.
FURRYe38,
Thank you for such a swift response. I do have the most current 15.25 FW loaded on both the router and satellite. I’ll go a step at a time. I really don’t want to disable AX options. So I’ll see if I lose battery thru the rest of today/tomorrow after changing CTS settings. If I do, then I’ll disable AX. Lastly, I’ll try downgrading the FW. Still open to any other suggestions you or anybody else have. Again, thanks for responding so quickly.
Thank you for such a swift response. I do have the most current 15.25 FW loaded on both the router and satellite. I’ll go a step at a time. I really don’t want to disable AX options. So I’ll see if I lose battery thru the rest of today/tomorrow after changing CTS settings. If I do, then I’ll disable AX. Lastly, I’ll try downgrading the FW. Still open to any other suggestions you or anybody else have. Again, thanks for responding so quickly.
Let us know how it goes. I'm finding my NEST contollers are staying connected with AX mode disabled and CTS set for 2347.
FURRYe38,
Well, the problem is still to be solved but have had some interesting (by interesting I mean incredibly frustrating) developments. At first my A/C was running and I kept checking the app and the thermostat remained online. This morning, the A/C had just kicked on and I checked the App and it said the thermostat had gone offline an hour ago when the A/C wasn't even running. It seems odd, since when the A/C/Furnace isnt running, the thermostat should be receiving power. At any rate, I decided to disable the AX mode. It applied the settings and I was just going to let it go to see what the thermostat did. Then I noticed my phone was no longer connected to WiFi. My SSID was visible so I tried to join and it told me I had the incorrect password. Even though nothing had changed, I typed my password back in and was again told it was not correct. Then I noticed one of my Google Home Hubs was also not connected. It seems sometimes when you change a setting, a hard reboot is needed to fully get everything going again so I tried that...and again the same problem. So I decided to turn AX mode back on. Again....I kept getting told I had the wrong password. At this point I finally decided to log back into my router and look at the password, somehow, some characters got removed or replaced and the string 35; was present twice in my password when it should not have been. I changed my password back to what it should be, applied the settings and everything connected again. I disabled AX mode, applied the settings and my password was once again changed with the string 35; added in once this time. So I put my correct password in, applied the settings and now everything is working.
I'm completely mystified as to how changing this setting also randomly changes my password. What a frustrating experience. But now that it is sorted out, I'm going to take my thermostat off the base and charge it directly for about an hour then reattach to the base and see what happens.
I also don't think consumers should have to jump through hoops to make these products work together. I'm not sure if it's a Netgear problem, Nest problem or both...but I hope they release an update or patch to fix it soon.
Very interesting that chaning AX mode is chaning the SSID password. Something I have not seen.
Has a factory reset been performed on the RBS and RBR since last update?
What browser are you using? I use Opera to configure my system most of the time.
Be sure to clear out any browser caches before entering the RBRs web page.
Is the CTS values at default 64 or did you change them to 2347?