Is anyone on the 6.2-22 Software version and having issues? My Nest thermostat was updated to the new software last week and since then I have had issues with both shorter cycles and the thermostat running for an extended time (far beyond target temperature). I'm curious if anyone else is having issues.
I've contacted Google / Nest support and not one person has any details on the 6.2-22 version and this software version isn't listed on the software version page.
Seems Google doesn’t even acknowledge this firmware update exists.
As of this writing, 6.2-22 is still not listed on their list of firmware updates: https://support.google.com/googlenest/answer/9263516?hl=en#zippy=%2Cnest-thermostat%2Cnest-thermosta...
I just had a repair man out. The Thermostat shows that it's calling for heat but it doesn't actually send the signal to the furnace. This must be due to the software update. It causes the house to take forever to come up to temperature because it only intermittently sends the correct signal to the furnance
This is exactly the issue that I had. I spent hours on the phone with Google and the support people weren't aware of the issue and also really didn't care. They only cared that my thermostat was out of warranty. I couldn't wait for a fix as it's winter where I live and I had to have the thermostat replaced.
It's so annoying. I just restarted the thermostat. So the temperature was set to 23 degrees. After restarting, nest is sensing the room temperature is 22 and running again. I'm 100% sure that since updating to this 6.2-22 I'm seeing that my furnace is running longer and cycles are really short. Why there's no information about this software version on the Google nest version history! That's also another concern
Just spent a long chat session with Google tech support. The conclusion from their end is that there is a failure in the display causing the networking issue.
My display looks and behaves flawlessly, so I remain skeptical.
As soon as the unit received the 6.2-22 update, it no longer could connect to Wi-Fi.
My thermostat stopped responding commands from my phone, so I restarted it -- no change. Eventually I reset to factory. Once it booted up, I could no longer add to nest app (error M15), and skipping this part in the setup shows "no networks found" in the display. I think they bricked network on the device.
Anyone on the same situation, do not despair! I completed the setup in my Nest without connecting to the network (since it didn't find any), and after about 2 hours I was able to go to Settings > Network and add it again! It's working with my phone as well, so all good. Good luck!
I'm having the same internet connectity issue with the newest firmware update. The nest says its connected on the device, but the app says it is disconnected. I just had it reboot and it seems to have come back for now.
Yep my Nest Thermostat was unable to turn on my heat, fan, or AC after the 6.2-22 update on 10/26/21. I called customer service and they had me to a complete factory reset… It did fix the problem, but pretty annoying. There should just be a way to roll back to the previous firmware until the latest firmware is fixed.
My Nest also stopped working yesterday not too long after updating. I didn’t fully realize the connection to the update because my wife did it. Cause we’re already into cold nights and we have a toddler, I immediately called for furnace service, which localized the problem to the Nest. Wish I came in here first …..factory reset seemed to fix the issue and it’s running fine now. It says it’s still using 6.2-22
I did the same thing. We just had a new furnace installed in the summer months and of course this hits the same day we get our first freezing temperature night. My assumption was an issue with the furnace unit or the connection to it.
I just factory reset my Nest AND the HVAC tech gave me an old dumb thermostat to put next to it to test if the room reads the same temperature.
I had the exact same problem. Thermostat doesn’t call for heat. Thought furnace was bad. had a technician confirm that it is a problem with the thermostat. After removing nest from nest app, did the factory reset. It solved the problem I was having. Didn’t realize the issue was related to the firmware until I saw the update date coincided with when the thermostat stopped working. Of course it was also a cold day here in Colorado...
I have 3 Nest E’s. And they are now on 6.2-22. I am having issues control the thermostats with the iOS app and eco mode does not seem to work. Ended up having to drive up to the house (cabin) and verify everything. Seems to be working now but will do a factory reset tomorrow to hedge my bets. Weird there are no release notes or anything about this software version. Very frustrating!
Indeed. Google has screwed customers by pushing 6.2.22 to their working Nest Gen 3 Thermostats. My Nest Gen 3 was fine until one day automatically downloading 6.2.22 version and then I lost WiFi hence connectivity to Nest App. All efforts failed in working with Google after all day of calls and chats. It boiled down to “your thermostat is out of warranty”. I got no clarification on why I have this mysterious version firmware and not the one Google claims is the latest one on their website. Clearly they rolled out something to pilot or a rogue employee tinkered with technology and we are out of expensive thermostat. It’s a shame on Google. No wonder lawmakers are after these guys with too much air in their heads.
Yes, completely agree. I have chatted and talked to several members of the senior support team for Google / Nest and none of them even had any notes on the 6.2-22 Software Version. That does make it seem like this software version was mistakenly deployed, yet Google/Nest refuses to acknowledge this software version could be causing these issues and doesn't even offer the option to rollback to a previous version.
Incredibly frustrating, especially since the thermostat controls what is the most expensive piece of equipment in many people's homes (HVAC). I'm concerned these issues are causing unnecessary wear and tear on my system.
Thanks for the update.
Some updates from my observations after factory reset a day:
Seems like my furnace is running more than usual, cycles are longer and nest temperature keeps going low and takes longer to get into my desired temperature.
I'm keeping an eye on my furnace for sure. It's frustrating but nothing I can do. Last night it was so hot I woke up and turned down the temperature later.
Purchased Nest Learning to control both Heat (boiler) and AC (older system) in New England. Installed 1 Apr 21. Used heat and AC through mid June before transitioning to summer AC. While getting ready for winter on 6 Oct 21, turned on heat and controller in TACO box (interface between thermostats and boiler) just kept clicking. Called HVAC Co for PM and troubleshooting. No issue with boiler. Nest giving N72 error - no power to heat Rh wire (not true). Tech bypassed thermostat and started boiler. Contacted Nest - given unbelievable run around, including sending part that they knew wouldn't fix it. Contacted again today (10-29) and given same run around. Won't acknowledge problem or propose solution. Blames me. This is a common problem and not unique. Save the hassle and buy another brand. You can thank me later.
I tried the factory reset but still no luck. My furnace will turn on, get to the temp it is set to then shuts off but the nest is still orange like its calling for heat. The only way I can get it working again is turn off the heat then turn it back on. This started the other day when it did the upgrade. The furnace is 3 years old and it was just serviced at the beginning of the season and has been running great till the other day, glade Google is playing dumb haha looks like we might have to switch.