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.
A short term work around appears able to extend the battery life on NEST. Put a tape (I use painter tape) to cover the NEST motion sensor. This help me to sustain the battery level at 3.7v (better than at 3.6v but not ideal to be at 3.8v) Yes covering the sensor lose the farsight function, but at least in my case help keeping the sensor connected to Wifi
You can turn off the sensor function to sense motion so you don't have to use tape on the controller. If motion and sensor is causing the battery to drain, then you need to contact NEST about that. Thats NOT a NG problem.
Something I've never seen ith my 3rd gen controller.
samnt650 wrote:A short term work around appears able to extend the battery life on NEST. Put a tape (I use painter tape) to cover the NEST motion sensor. This help me to sustain the battery level at 3.7v (better than at 3.6v but not ideal to be at 3.8v) Yes covering the sensor lose the farsight function, but at least in my case help keeping the sensor connected to Wifi
I've tried the motion detect shutdown function within the NEST control. However that did not help sustain the battery life in my case.
Hmmm...seems kinda fishy though. Something I would bring up to NEST support. I've left my 1 3rd gen wide open, walk by it several times a day. No tape.
Anyone with a 8 series Orbi AX wanna try this new version of FW?
samnt650 wrote:I've tried the motion detect shutdown function within the NEST control. However that did not help sustain the battery life in my case.
Per support ticket I have with Netgear, Firmware v3.2.17.12 supposed to fix the NEST battery drain problem. Will be loading on Jan 22 evening for testing...
Please keep us updated about this. Would be interested to see if it fixes the issue (I'm not optimistic).
Mine are online since grading yesterday...no NEST disconnects so far.
samnt650 wrote:Per support ticket I have with Netgear, Firmware v3.2.17.12 supposed to fix the NEST battery drain problem. Will be loading on Jan 22 evening for testing...
How did it go for you?
I am another of the Orbi AX subset that experienced Nest thermostat low battery problems (and have been connecting to an older router because of it). I have 2 Nest Gen 3 thermostats and both would not work correctly with my Orbi RBR850 system.
I've been running V3.2.17.12_1.4.14 for a couple days and when I read that this firmware was supposed to fix my Nest issues, yesterday afternoon I reset the network on both thermostats and connected to my Orbi AX. Unfortunately this morning I found that both thermostats report low battery and disconnected from the network. Therefore it doesn't appear (for me) that this firmware has resolved the Nest thermostat issue.
I did not do a complete reset after this FW upgrade, and generally never do. I cannot waste more time trying a full reset so in another hope (guess) that it will makes any difference for this Nest issue, sorry. I'll wait until another Nest thermostat owner tries that and determines it's successful.
Please escalate the issue to Netgear support (assume your device warrant/support not expire) This is the only way keep the issue hot with Netgear. Somehow my Orbit would not load the new firmware zip file (escalated back to support...)
Did you unpack the .zip file before trying to manually load the FW?
samnt650 wrote:Please escalate the issue to Netgear support (assume your device warrant/support not expire) This is the only way keep the issue hot with Netgear. Somehow my Orbit would not load the new firmware zip file (escalated back to support...)
I updated the firmware to V3.2.17.12_1.4.14 and it is still not working for me. I have a ticket open with tier 2 support. I am asking that it be escalated.
I honestly have no idea why most of us here are even bothering. Netgear is unlikely to ever fix this. I'm so glad I returned my set, and if you still have the ability to do so - DO SO!
I have also made contact about this to NG as well.
rbernstein wrote:I updated the firmware to V3.2.17.12_1.4.14 and it is still not working for me. I have a ticket open with tier 2 support. I am asking that it be escalated.
Firmware 3.2.17.12 did the trick. NEST has been holding the charge for a week.
- What did you do to keep it working? I’m going to double check as I just manually updated the firmware on my rbk850s a couple days ago and it seems to drain faster.
- So both rbs850 and rbr850 are using v3.2.17.12 and it’s barely holding a charge to stay on the WiFi for half a day now. It’ll charge up to v3.82 and within 5 hours of putting it back on the base it’s back “offline”. I did notice that after rebooting everything is either connected to the rbr or the rbs, it’s not split it’s all or nothing.
I manually updated as well to the latest firmware and it is still not holding a charge. Did you do anything else beside updating?
What is the size of your home? Sq Ft?
What is the distance between the router and satellite(s)? 30 feet or more is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected.
https://kb.netgear.com/31029/Where-should-I-place-my-Orbi-satelliteDid you factory reset and set up the system from scratch?
What channels are you using? I'm using 1 and 40. 40Mhz only and CTS at 64 AX enabled and sometimes disabled since I only have a couple of AX supporting devices.
rbernstein wrote:I manually updated as well to the latest firmware and it is still not holding a charge. Did you do anything else beside updating?
From all the troubleshooting w/ Netgear Tech Support. There are few things you can help to minimize the NEST jumping between the Orbi device, one key way to drain the battery. Yes, you need to make enough of the distance differences between Orbi(s), as in 10 fts or more between the closest and the next unit. I know Orbi uses secondary Wifi for the backbone between devices for uplink. I dont know how that play into the NEST battery drain (aka, behaviour of the Orbi) My Orbi backbones are hardwired RJ45. As far as I can tell, the firmware helps my NEST stay connects to one specific Orbi device and that how it save from battery drain.
Agreed. My RBS are ethernet connected as well.
Another thing to try turn down the power output of the RBR as well. Mines at 50% though my 3rd gen NEST still likes to connect to the RBS downstairs in the dinning room. My 3rd gen NEST has been stable on v12. Was stable even on v16 FW as well.
I feel this is getting better.
Same issue here. Nest Thermostat Gen 3 started dying as soon as I installed this system.
Upgraded the firmware to V3.2.17.12_1.4.14, tried reducing power, and other things in this thread but it is still not resolved.The Orbi router is only about 10 feet and in direct line with the Nest Thermostat. The app shows connected to the RBR750 on 5ghz with good signal. The RBS750 is about 25 feet and a floor down from the RBR750.
I configured another wireless network on the ISP modem/router,connected the Nest to the ISP wifi, and I no longer have battery drain on the Nest. Hopefully there is a resolution and I can turn off the other network.
"The RBS750 is about 25 feet and a floor down from the RBR750." 25 feet is too close. This wil cause a pinging effect on the NEST in connecting to signals. 30 feet or more is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected.
What channels are you using on 2.4 and 5Ghz?
Also try changing CTS values from 64 to 2347.
Has a factory reset and setup from scratch been performed since last FW update?
ironmikel wrote:Same issue here. Nest Thermostat Gen 3 started dying as soon as I installed this system.
Upgraded the firmware to V3.2.17.12_1.4.14, tried reducing power, and other things in this thread but it is still not resolved.The Orbi router is only about 10 feet and in direct line with the Nest Thermostat. The app shows connected to the RBR750 on 5ghz with good signal. The RBS750 is about 25 feet and a floor down from the RBR750.
I configured another wireless network on the ISP modem/router,connected the Nest to the ISP wifi, and I no longer have battery drain on the Nest. Hopefully there is a resolution and I can turn off the other network.
Poor-man troubleshoot.... Shutdown the RBS and see if your NEST battery situation imrpove..
FURRYe38 wrote:"The RBS750 is about 25 feet and a floor down from the RBR750." 25 feet is too close. This wil cause a pinging effect on the NEST in connecting to signals. 30 feet or more is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected.
What channels are you using on 2.4 and 5Ghz?
Also try changing CTS values from 64 to 2347.
Has a factory reset and setup from scratch been performed since last FW update?
Appreciate the response FURRYe38 . I measured the actual distance and it is 39 feet between the router and satellite.
2.4 ghz is on auto channels and 64 CTS. 5ghz is on channel 48 and 64 CTS. I will change both CTS to 2347.
I did not do a factory reset and setup from scratch after the FW update. If this is necessary I will have to wait a few days as my family is frustrated. Over the last 2 weeks I have been dealing with issues from a google wifi network, replaced all with new Nest wifi with multiple resets, and finally to the Orbi. Other than this issue very happy with the Orbi system and the speeds throughout my house are excellent.
OK, I'm using channel 1 and 40 here. I haven't changed CTS. I'm trying to ensure that default CTS values work with NEST. It has been. However for yours change CTS values and check.
I'm also using 50% on the power output on the RBR. Since my next door neighbor has a Orbi system as well, I didn't want them to be causing problems.
What is the distance betewen the RBR/RBR and your NEST?
ironmikel wrote:
FURRYe38 wrote:"The RBS750 is about 25 feet and a floor down from the RBR750." 25 feet is too close. This wil cause a pinging effect on the NEST in connecting to signals. 30 feet or more is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected.
What channels are you using on 2.4 and 5Ghz?
Also try changing CTS values from 64 to 2347.
Has a factory reset and setup from scratch been performed since last FW update?
Appreciate the response FURRYe38 . I measured the actual distance and it is 39 feet between the router and satellite.
2.4 ghz is on auto channels and 64 CTS. 5ghz is on channel 48 and 64 CTS. I will change both CTS to 2347.
I did not do a factory reset and setup from scratch after the FW update. If this is necessary I will have to wait a few days as my family is frustrated. Over the last 2 weeks I have been dealing with issues from a google wifi network, replaced all with new Nest wifi with multiple resets, and finally to the Orbi. Other than this issue very happy with the Orbi system and the speeds throughout my house are excellent.
Yikes, Netgear or Nest needs to fix this. I installed a new RBR750 with 2 RBS750s and immediately started losing power on 1 of 2 Nest thermostats. Banged my head against everything in sight before finding this thread. I've just re-added one of my previous wifi access points (Netgear EX6120) and given it a different SSID and channel just for the Nest thermostats. I'm fairly confident that will work around the problem, but I should not have to do that!
