NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Nest Thermostat Batteries LOW on a new ORBI AX setup
I have a brand new ORBI AX wifi setup (RBR850 and 2 satellites) that i got configured and updated to the latest firmware (V3.2.15.25) about 10:00 last night with all nodes up to the version with a bi...
No.
Only thing I found was that with mine, being so close to the RBR, 5 feet, was having problems with the NEST. I found that when I moved the RBR away from the one NEST controller, 20-25 feet, the NEST controller started working with out draining the battery. Also was said that this is also a NEST controller issue as well that NEST needs to fix it on there side as these controllers ping pong back and forth on there own when there is more than 1 signal source in play, i.e. RBR and 1 or 2 RBS. Its also recommemeded to install the C power wire to your NEST from the main central AC system to help avoid the battery draining. You'll need to consult your systems mfr wiring diagram to find out which connection that is.
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 haven't had any of the issues you describe. Were they 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. Also, the Nest thermostats are very sensitive to battery power if you only have them connected via trickle charging and don't have a "C" wire providing continuous power.
Trickle charging is thier setup as they have been for 2 years. They connected and had the right up address, no issues so I thought all was good.
I’m done playing around with a $1000 setup for something I have never had to do with the 3 years I’ve owned the thermostat devices and the various other routers which have never made this occur. I’ll just disconnect them and USB charge them soon if they don’t recoup with the trickle charge since the old setup is back into place
I’m done playing around with a $1000 setup for something I have never had to do with the 3 years I’ve owned the thermostat devices and the various other routers which have never made this occur. I’ll just disconnect them and USB charge them soon if they don’t recoup with the trickle charge since the old setup is back into place
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.
- As far as I’m concerned when I contacted NG support and they can’t help me anywhere near what I’m getting from some of the folks here. AND if it truly is that setting a technical news letter should have been sent out or included in the last firmware.
For the cost to not get support and have it impact some core technologies in a home setting are truly poor. With my prior technology since factory resetting the Orbi and pulling it out my primary best has come to the level where it’s back on the network with the trickle charge and expect the second one to also appear soon (or I will disconnect it to manually run a charge.
This is poor, service is crazy and while it’s possibly a great product with some stunning speeds if I were to ever return to NG at this point I would think it would have to be with a RAX (night hawk single setup design). However once bitten twice shy.
I used to love linksys when owned by Cisco but when sold to belkin patches and firmware are almost not existent. Apple dissolving thier network series was my second hit and additional liked product. I’m happy with ASUS as firmware and technology is there, just having an issue with a client limitation it seems but nothing that has any ways introduced such explicit impacts like this.
So in all, I’m done tinkering. I’m not a network engineer, while i support technology I can’t endorse this or use it if they don’t advise and get things in a status where it’s kind of easy for end users. A lot was smooth but I’m just glad I didn’t hit this in the middle of winter when heating is essential where I live
So it’s on it’s way back to netgear via the vendor I purchasedGood Luck in you endeavours.