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.
Ok folks...here something ppl are talking about:
The most frustrating part of this is an update which has hosed so many systems.
My heat pump cycles were extended and it was continuing to heat long after reaching the temperature I set on the thermostat.
I did the factory reset and now the easy setup I previously had for wiring doesn't seem to be the as easy and says it requires a 'pro setup'.
Still heating beyond the indicated temp as well.
Calls to support were of no help - they had 'no complaints' about this upgrade and wanted to walk me through a 'failure to heat' scenario.
Ecobee should be delivered today. This is inexcusable, Google, and ends a long 10 year relationship I've had with Nest products.
I was planning to get my next pixel but after hearing these stories!! forget it! I am not going to invest myslelf into their ecosystem.
Does it matter for others!!
Well you gotta start from somewhere. I want to have a peaceful life. Im investing onto their products and paying more than regular market price because its from Google and its "premium" and their services are crap! No sipmly not
Both my NEST E thermostats had issues with the software update which is now listed on the Google site.
My upstairs thermostat lost its schedule and my downstairs thermostat did that any would not stop heating the house. I woke up late last night with the heater running and the temperature at 80. It seems the software is treating AC as heat too, because when I tested just the AC, heat blew out and my outside unit was not running. Had to turn off the thermostat to stop the heat pouring into the house.
Google really needs to make a statement about this firmware version. Yesterday my Nest was calling for heat for hours but the furnace never turned on. House was freezing, almost 10 degrees from target temp. Initially I thought it might be a problem with the furnace but I had just gotten it serviced a few days ago. Then I thought maybe a software bug related to the time change which happened today.
Anyway, the furnace finally kicked on in the middle of the night. I am going to contact Google today and see what kind of response I get.
My Nest 3rd Gen Learning thermostat is also having issues since the update. Wont do anything unless i take it physically off the mount, wait a little bit and put it back on, then it works for a little while and happens again. I havent tried factory reset yet, but if i do, wont it eventually just update to 6.2.-22 again and break, or has Google atleast pulled the update?
A factory reset does not change the firmware version, so it would still be on 6.2-22. It will update only if they publish a newer version of the firmware.
Since my 3rd Gen Learning Thermostat can no longer find Wi-Fi networks (thanks to the 6.2-22 update), I did a factory reset and skipped the connectivity and app portions of setup. It seems to runs the HVAC just fine, but keeps telling me the time and date are not set. It says this even if I set them manually. Super frustrating, but at least we have heat, unlike some other folks are reporting.
Meanwhile, I’m still waiting for a response from my Google support case.
So i did the factory reset, still cant connect to wifi, but the thermostat has stayed up and working for more then 24 hours now. Before it would just do nothing like it was powered off, would have to disconnect and remount it to get it to kick into gear. So better but no wifi.
Will try support next, but thermostat is over 2 1/2 to 3 years old so probably not under warranty anymore
There appear to be numerous issues triggered with the 6.2-22 firmware update — some are having HVAC control irregularities (short cycling, temp not regulated, etc.), some are having connectivity issues, etc.
My issue (as stated above) appears to be isolated to Wi-Fi. Since the update, the unit cannot see any of several Wi-Fi networks available.
I thought I’d document other versions in my unit in case it’s helpful for comparing to your problem unit and seeing if there are patterns with which hardware versions exhibit which firmware issues.
The version numbers above are available in the Settings -> Technical Info menu.
Just came here before calling our heating company...
Going to hold off now. Our thermostat disconnected yesterday and we didn't notice all day due to warmer temps outside. 8 PM rolls around and we realize that it's offline. It powered itself down and refused to boot up. Eventually, thinking I had power problems and checking electrical panels, safety switches, everything on the furnace itself. Nothing wrong. I plugged the thermostat into USB to charge off base for an hour or so and it suddenly was fine. Been monitoring ever since and no power issues whatsoever.
My guess is it was related to this damned update. Our Nest updated about a week ago, but it hasn't been on much due to warmer temps. Gave me a heart attack thinking I had some massive electrical problem that would be impossible to sort out.
Thanks, Google. Thanks a bunch.
One thing I’ve done that may have fixed the connectivity issue: I connected it to an older repeater I had lying around. So far, it has not disconnected again for the last 18 hours or so. If it goes another day, that may have resolved the issue. I have no idea why connecting to a repeater would be more solid than a direct connection the the router, or why the firmware update of the Nest caused the instability to being with
For some of us, 6.2-22 means the unit cannot see any Wi-Fi signals. Between my own network and my neighbors’ there are at least 4 networks broadcasting at any given time.
My thermostat can’t see any of them. It also could not see the signal from a factory-reset Linksys router (2.4 MHz) I set up within a few feet of the thermostat. Nor could it find the network, even if I manually entered the SSID.
It could not see the Wi-Fi hotspot from my phone, inches away from the thermostat.
Interestingly, Bluetooth (used during setup by the Nest app) promptly and reliably found the thermostat. Then, when the setup flow gets to networking, it times out after a long search for Wi-Fi networks.
I don’t know if Nest uses an integrated wireless chip for both Wi-Fi and Bluetooth, though most products I’m familiar with do. With Bluetooth working fine, this further suggests that something in the 6.2-22 code can’t properly control the Wi-Fi system on some Gen 3 Learning Thermostats.
It was a couple years old, but it was also a warranty replacement directly from Nest.
All indications are that most of the problems since the 6.2-22 release are related to the firmware in some way. They don’t seem to kill all Gen 3 units, so there could have been component changes over the past few years where the bugs show up on older units but not new units. (My speculation, nothing definitive.)
If this is the case and if Nest no longer wants to support that older hardware, the burden is on them to not allow updates to the firmware that cause issues. Just stop updating older hardware and freeze it with firmware that works, just as the smartphone makers do.
In that case, it’s not a hardware warranty issue, it’s a matter of their implied obligation in software updates to do no harm. Intentionally or negligently doing harm to installed base could be interpreted as a tactic to drive replacement sales and would likely draw a lot of negative (and expensive) attention.
I’m skeptical that’s the case — I simply think 6.2-22 was released without full regression testing across all installed base combinations of chipsets and configurations and some of the bugs turned out to be device killers.