Nest Thermostat Wifi Connectivity Issues?

I’ve been seeing more Wifi issues recently with my Nest thermostats. I don’t see a pattern to the problem, and it seems to randomly affect all of them (sometimes at the same time, but often just one).


I’ve got a supported Wifi router (Apple Airport Express), and it’s within reasonable range to all of the thermostats in our house (no more than 20 foot from any thermostat). While it’s unfortunately overlapping with a similar band/frequency in our house, the router is dedicated to only the Thermostats right now (a unique SSID).

It doesn’t have any settings that seem necessary to change:



Any ideas?


  1. I’ve been seeing this recently with mine as well. A couple of times in the last month I’ve ended up with the “?” status. In general, I’ve found that I can (a) wait, and they’ll come back eventually or I can (b) reboot the thermostat and that fixes the problem. I suppose it’s inevitable that once a thermostat became a computer it would have to be rebooted every once in a while.

  2. I’m seeing the same thing. I have two Nests – one on the first floor and one on the second. My wifi access point (an Astaro AP30) is on top of kitchen cabinets on the first floor (so roughly equidistant to both Nests, and with a similar number of walls and other obstructions in between). Both are hooked up via a 24V common wire so power shouldn’t be an issue. My Astaro gateway reports 96% signal strength for my first floor Nest, and 100% for the second floor. Both had been working fine (barring known Nest system outages) since I got them a year ago, but in the last month or two I’ve noticed the second floor Nest losing connectivity intermittently, and at one point had completely forgotten about my network (I had to rejoin my WiFi network via the config screens on the Nest itself). When my second floor nest is unavailable, it normally comes back online within a few minutes without my having to do anything. I’m assuming the 3.0.4 Nest software has some WiFi issues of some kind – the software update history page on mentions “improved remote control availability” as the only update in that release, so there must have been some bugs in that area, apparently some of which are still there.

  3. I have noticed a similar issue with my 2nd Gen Nest and Airport Express. I have the 802.11g Express. It seems like every few days the network will become unconnectable. It shows up in the wireless network list of my various computers, but any attempt to connect to it ends with “A Connection Timeout Occurred”. This happens with all clients connected to this Express. Simply unplugging the express clears the issue for a few days, but it always comes back.

    I hadn’t thought that this could be Nest related. I have another 802.11n Express that runs a different SSID. I will join the Nest to that network and see if the problem stays with the old Express or moves to the new Express.

    I’d estimate that this started around Christmas, but seems to be happening with increasing frequency.

  4. I noticed 3.0.5 was rolled out last week. My second floor Nest had gone from intermittent wifi access to none at all – it was staying disconnected all the time, despite my first floor Nest and other wifi devices having no issues. Even when trying to coax it into joining my wifi network manually via the thermostat itself, it kept reporting a failure to connect. After some experimentation, I was able to get it to connect to a separate, temporary wifi network long enough for it to download 3.0.5, after which it was able to rejoin my main wifi network without issue, and has stayed connected to it since (this was two days ago). So it appears in my case that 3.0.5 fixed a problem, although nothing wifi-related is mentioned in the change log. Also, it’s odd that my identical first floor Nest had no connectivity issues at all when on 3.0.4.

  5. For what it’s worth, here are my Nest wifi experiences:

    I bought 2 nest thermostats and installed them yesterday. I quickly discovered that they dropped off the network regularly. Whenever one was off the network, all I had to do was walk up to it. The screen would turn on, and it would rejoin wifi. Sometimes only one would drop off, and sometimes both would drop off. They’d eventually come back, then drop off again, in an endless cycle.

    My home network uses two e3000 dual-channel access points (not acting as routers) running DD-WRT. I use a linux system that I run myself as a router. When the Nests would drop off the wireless, it was easy for me to do a packet capture and see what was going on. What I saw was the router ARPing for the Nests, but no answer back.

    I have lots of hardware lying around, so I pulled out an E2000 running stock firmware and set it up real quick to create a new wifi network just for my Nests. I put it on the same channel, same encryption, but a new SSID and WPA2 personal password. The Nests joined this new network and have been completely stable ever since.

    So, it does appear that the bouncing wifi connectivity is specific to wireless AP hardware/firmware, and the way they seem to recover when I’m using them but break when they’re mostly idle seems in line with it being related to power saving.

    Nest may be right about it being the wireless router’s fault for not properly supporting the power saving feature, but I still find that to be a terrible argument. My Nests have a C wire so there is plenty of power. If the extreme power saving mode they are using breaks with many common routers (or router firmwares), Nest should obviously have an option to disable that feature (or even automatically only use that feature when power isn’t plentiful). Saying it is someone else’s fault and leaving their customers to suffer is terrible customer service on their part. No matter whose fault it is, they can fix this trivially and seem to resist doing so for no good reason.

  6. I’m having similar WiFi dropout issues with Nest. Two nest thermostats both with C-Wire and both are randomly dropping off of WiFi. Sometimes they reconnect. Sometimes not. Sometimes when they don’t a simple forced (at the thermostat) reconnect works, often not and have to do it twice to get it to re-connect.

    After solving the c-wire issue (didn’t initially have) I’m much happier with my nests, however this latest issue adds to the disappointment. Apart from that, and lack of Windows Phone app, I love them :)

Comments are closed.