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.
Cts is 2347.
I cant move the rbs any closer, otherwise it’s going to be in my hallway...
I cant move the rbs any closer, otherwise it’s going to be in my hallway...
Lets try setting the CTS valued to 64 and set the power out put on the RBR to 50% from 100%. Lets see if we can help keep the NEST near the RBS connected at the RBS.
After you do this, I would disconnect the NEST from the RBS, reboot the NEST, the after it's back online, re-connect it to the RBS signal. Lets see if this helps any.
Also if you don't think the NEST is fully charged, please put a 30 minute charge on it then reconnect it.
I have this exact same issue. Installed FM v32 and moved the satalite as close as possible, but my nest thermostat still keeps dying.
Any updates or solutions anyone has found that worked for them?
- This is clearly a bug with netgear’s hardware/software. Standard users should not need to jump through hoops to get other devices connected and working properly.
At the rbr850’s price point, it should just work. So can we presume that your still having problems with the suggestions given?
If so, please file a support ticket with NG support.
brandobot wrote:
This is clearly a bug with netgear’s hardware/software. Standard users should not need to jump through hoops to get other devices connected and working properly.
At the rbr850’s price point, it should just work.What is the distance between the RBR and RBS? 30 feet or more is recommended.
What is the distance between the NEST controller and the RBR and RBS? How close is the Nest to either unit.
What CTS value are you using on the RBR? 64?
Is 20/40 Coexistence enabled?
Under Advanced Tab/Advanced Settings/Wireless Settings
I'm currently using manual channel 11 and 48 on my RBR. Seems to be working Ok for me. I did see a couple fo disconnects the other day and I had to manually re-connect the NEST.
CTS is 64
20/40Mhz is enabled.
My 3rd gen NEST is 5 feet away from the RBR. This one has been most problematic controller.
My 1st gen NEST is 10-12 feet away from the RBS downstairs, one wall in between.
Make sure you are charging the NESTs fully.
NG believes as I do that the NESTs are failing to re-connect after what ever reason they disconnect. Is this faulure to reconnect to the wifi singal that the NEST keeps ping and trying to connect, thus running the battery down. Also the NEST seems to keep ping ponging back and forth bvetween signals from the RBR and RBS. Then the NEST won't connect at all until it's re-charged. If you don't notice the NEST disconnected in time, then this runs the battery down. I agree, there seems to be issues with NG FW on Orbi. I wish NEST would also change the behavior of the controller to where if it can't get re-connected after a short period of time, it stop's trying and goes into idle or low power mode to save the battery until the user can get it re-connected. Something NEST should also review with NG.
Historically Orbi AX has only been problematic with NEST. My Orbi AC system and other routers I have tried over the years have not seen this issue.
orbi-adan wrote:I have this exact same issue. Installed FM v32 and moved the satalite as close as possible, but my nest thermostat still keeps dying.
Any updates or solutions anyone has found that worked for them?
FURRYe38 wrote:I'm currently using manual channel 11 and 48 on my RBR. Seems to be working Ok for me. I did see a couple fo disconnects the other day and I had to manually re-connect the NEST.
Doesn't sound like it is really working for you either if you have to watch for disconnects or have to manually reconnect.
Several of us have reported issues with our Nest thermostats and the Orbi AX system. No selection of channel or CTS/RTS fixes the problem. We are all running an older router for now to provide compatibility. My nest thermostats worked fine with my Orbi AC system, so Netgear should look more at what could be different between their AX and AC systems. This would be more fruitful than waiting for Nest to do something in their firmware, especially since the Nest is working fine with virtually all other routers right now (including Netgear's other ones). This is going to drive the Orbi AX system away from customers if they are not willing to workaround the problem as the few of us here have.
Telling people to fully charge their Nest, fine tune distances between their satellites, or lower power settings are interesting diagnosis or workaround steps but not solutions. There are many other devices in our home leveraging the wired access point capabilities of these satellites, in their existing locations, and thermostats usually cannot be moved around. We are supposed to benefit from the capabilities of these fancy new mesh routers, not redesign our homes and device locations to fit their quirks,
I'm not trying to tell users to redesign the homes or NEST placements. Trying to help users to see if some of the suggestions and configurations may help the behavior and then get some results and feedback from users having this problem so we can forward this info to NG so they and or NEST can help make changes to either NG Orbi FW and or NEST FW to help both work better and fix these problems.
So far I haven't changed my NEST placement or configuration since v32. What is working is keeping default CTS values and wifi setttings which for me, is working and keeping my NESTs online and not loosing batter life. It's the side effect from what I've seen with my NEST is that the NEST will not reconnect if the connection is lost with Orbi AX and the NEST continues to reconnect causing a battery loss over time if I don't catch the disonnect sooner then later. This seems to be a odd or bad NEST behavior on there part.
Ya, I agree NEST should work with out hassle with Orbi AX. Its been ongoing since I got mine and been working with NG on this as best as I can.
So, Aside from what we already know, any good feedback on results from suggestions given is appreciated so we can pass this on to NG for review. Hopefully they can get it all figured out. There seems to be differences in AX wifi vs AC wifi systems and how things are handled. There needs to be some tuning I presume at some level to get it working well with NEST controllers.
FURRYe38 wrote:I'm not trying to tell users to redesign the homes or NEST placements. Trying to help users to see if some of the suggestions and configurations may help the behavior and then get some results and feedback from users having this problem so we can forward this info to NG so they and or NEST can help make changes to either NG Orbi FW and or NEST FW to help both work better and fix these problems.
So far I haven't changed my NEST placement or configuration since v32. What is working is keeping default CTS values and wifi setttings which for me, is working and keeping my NESTs online and not loosing batter life. It's the side effect from what I've seen with my NEST is that the NEST will not reconnect if the connection is lost with Orbi AX and the NEST continues to reconnect causing a battery loss over time if I don't catch the disonnect sooner then later. This seems to be a odd or bad NEST behavior on there part.
Ya, I agree NEST should work with out hassle with Orbi AX. Its been ongoing since I got mine and been working with NG on this as best as I can.
So, Aside from what we already know, any good feedback on results from suggestions given is appreciated so we can pass this on to NG for review. Hopefully they can get it all figured out. There seems to be differences in AX wifi vs AC wifi systems and how things are handled. There needs to be some tuning I presume at some level to get it working well with NEST controllers.
Those settings didn't work for me. Default setup out of the box, and within hours my thermostats are offline. Honestly, who has time to mess with this nonsense when do any other routers have this issue with the Nest thermstats? None that I know of.
- NEST work out the issues? Seems like the issue is with Netgear.
Then return the Orbi AX system and find something that does.
Good Luck.
WilliamGr wrote:Those settings didn't work for me. Default setup out of the box, and within hours my thermostats are offline. Honestly, who has time to mess with this nonsense when do any other routers have this issue with the Nest thermstats? None that I know of.
- Experiencing the same issue. Have router and two satellites - all three Nest gen. 3 thermostats in my home have low power warnings and are disconnected from wifi.
Can you turne OFF 1 of your RBS and leave the other one online.
What is the distances from the NEST controllers to the RBR and to the RBS?
Inimical wrote:
Experiencing the same issue. Have router and two satellites - all three Nest gen. 3 thermostats in my home have low power warnings and are disconnected from wifi.- I can't disable anything as people are actively using the network. The distance is about 10 ft. from each one.
I recently added the 2nd satellite, the same issue was happening with one satellite. Everyone,
I just got off a online chat support with NEST themselves. I had the idea that to help with some of this, it would be nice that there NEST app gave notification of any kind of wifi disconnection with the controller, so users would be allowed to investigate the problem with there contorllers during any kind of abmornal condition. Normally the controllers will re-connect, however for odd issues, this would be helpful to users so they can take a look and gether contollers back online. The main issue is that when the controllers disconnect, they fail to get re-connected, for what ever reason they don't, thisi drains the battery thus everyone sees this as the end result. If users had early notification, then users can take action and get the controller reconnected thus help prevent battery drain.I presented this idea to NEST chat support this morning and it seemed to be well recieved and they said they would definately review this idea for there app. No idea if or when it will happen. Hoping it will be at some point in the future.
https://nest.com/support/contact-us/?from-chooser=true
They gave me some links for users to check out and if users are so inclined, can post about this and other things about there NEST products here:
https://support.google.com/googlenest/community?hl=en
I see this atricle as well though Orbi AX hasn't made this list: :smileyfrustrated:
https://support.google.com/googlenest/answer/9233444?hl=en&ref_topic=9361783
NG is aware of the problem with Orbi AX and NEST controllers and is working on it.
I'm seeing same thing, if I don't notice the controller disconnected for a long period of time, the battery will drain and has to be re-charged. If I catch the controller much sooner and get it re-connected, it's ok.
Hoping for a fix soon as well. :smileywink:
