NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
oliverfelix
Dec 30, 2019Aspirant
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...
Mikey94025
May 24, 2020Hero
I would follow FURRYe38's recommendation to check and set your CTS/RTS values to 2347. The firmware defaults cause various wireless compatibility issues.
I have 2 Nest thermostats and 3 Nest Protects and they have been working fine with my Orbi AX system. Did your Nest devices successfully connect to wifi after you upgraded your router? It's important to verify the connectivity of your devices and reset/reconnect them if they are not connected. Not all devices will simply reconnect just because you kept the same SSID and password. If they could not connect to your new wireless SSID and kept retrying then that would explain why the surprise battery drain.
iNexxFear
May 24, 2020Apprentice
I was using an ASUS AX11000 prior to this, AX enabled on that device and no issues. And I’m no expert but if those setting are going to cause wireless issues they should be changed from the default for something that ranges from $600-$1000 with the 2 satellites like I bought. After seeing this configuration fully drain 2 smart thermostats within a matter of hours I have determined it’s not worth the cost, aggravation or setup especially when NG support isn’t able to fully help and ask about MU-MIMO in sections that do not exist for this device and in my opinion those default values should be good out of the box! I wouldn’t have known what settings. This is poor and I’m sincerely disappointed especially with the latest firmware and changes that have made it to market. But no more NETGEAR for me. I’ll stay with other vendors moving forward
- FURRYe38May 24, 2020Guru - Experienced User
2347 was the default value historically, however for unknown reasons NG change the CTS values to 64 which seems to cause problems in last few versions of FW. I also noticed this with my two NEST controllers. After chaning them back to 2347, my controllers are working again. Something you should try.
iNexxFear wrote:
I was using an ASUS AX11000 prior to this, AX enabled on that device and no issues. And I’m no expert but if those setting are going to cause wireless issues they should be changed from the default for something that ranges from $600-$1000 with the 2 satellites like I bought. After seeing this configuration fully drain 2 smart thermostats within a matter of hours I have determined it’s not worth the cost, aggravation or setup especially when NG support isn’t able to fully help and ask about MU-MIMO in sections that do not exist for this device and in my opinion those default values should be good out of the box! I wouldn’t have known what settings. This is poor and I’m sincerely disappointed especially with the latest firmware and changes that have made it to market. But no more NETGEAR for me. I’ll stay with other vendors moving forward