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.
Most of us in colder climates can't wait for Google to fix something that they won't even admit is a problem. I spoke with several tech support people who were only concerned about whether my thermostat was still in warranty. They wanted pictures and documents from the service technician with no intention of reimbursing for the costs. Time to dump the Nest and get a more reliable thermostat.
UPDATE: they downgraded one of my thermostats (without telling me they were doing so) and it fixed my problem. I installed the third thermostat and did a factory reset and it worked. So my system is now stable once again but I spent lots of money and time that I won’t ever get back.
I’ve had the same issue with both my Nest E. It would cycle on and off and stop working eventually after a few cycles. I replaced one nest E with the old dumb thermostat. That did not work. After replacing both thermostats, everything is back to normal. No more short cycling and we get heat when it’s called for.
Similar issues as others have mentioned. Gone through the usual troubleshooting steps including asking out an HVAC repairman to rule out the HVAC system. It's definitely the nest thermostat not triggering our heat pump. I've seen isolated success by cutting power to the whole system then everything works for a day or two.
Pretty sad as it's our first smart thermostat.
So my thermostats (3 Nest E) were rolled back to 6.1.1-21 a week or so ago and they seem to working fine for now. Not good that Google refuses to acknowledge the issue or a workaround, etc. Very poor experience … it doesn’t need to be this hard. I am in the software industry and I know how this all works. The left hand (dev) isn’t talking to the right hand (customer service). I would not expect that from Google - but whatever.
I am having the same issues with the Nest not sending heat signals properly to the furnace. A factory reset did not fix the problem. I have a display model 3.4 and software 6.2-22. Is there any hope of a fix? Will Google to roll back the firmware on the non-E models? I am getting frustrated waking up to a freezing house!
I think what is most infuriating is a) you have no way of rolling back your own firmware and b) you have no idea when they might do so for you. Mine got rolled back and they work just fine, but seems like so many still haven't been. What a fustercluck.
Our Nest thermostat worked fine until it burned out the gas valve this week. The HVAC tech said they have been finding that Nest thermostats and the simpler Lennox systems aren't perfectly compatible, except they are supposed to be. He said that the Nest is surging too much power to the furnace, thus burning out the gas valve, which then prevents the gas from firing up to the necessary level, thus reducing the amount of heat being sent to the house, thus meaning our house has been stuck at 68 for a couple of days, despite the fact that the furnace was running constantly. The Lennox Certified tech says their solution is installing a relay circuit between the Nest and the Lennox circuitry, rather than replacing all of the Nest thermostats they were enthusiastically installing these past few years. Don't know if this is related to the firmware upgrade, but I suspect that it is since the gas valve worked fine with the Nest through an initial partial heating season, one full winter and half of this one. I'm not a software or HVAC tech, so I can't be sure. Our Lennox is Model No. ML180UH.
I am having the same problem as others. My furnace would turn off but my fan didn't and then would blow cold air. I have the newest software update as well; how do I get google to take me back to the older version that had no issues? Also strange Nest sent an e-mail that my system had turned on and off 23 times in a 24- hour period? I thought maybe that was just how many times it stopped and started after getting to the correct temp as the fan issue didn't come up until a few weeks after getting that e-mail. You would think that information should tell Google something is amiss? I reset my Nest and I also moved my RC Red wire to my RH as I saw a guy demonstrate on Youtube. He has many videos so I figured why not? It seemed to work then I also read in this thread to turn off the Temp Max and Min so we shall see if that helped? I am in Utah so it is cold here as well, so fingers crossed. I think I have had my Nest for 3 or 4 years but for 300. you would expect it to last much longer.
So I just ran my furnace several times and it seems to be working! I had reset the Nest first. That did not solve the problem. Next I turned off power to the furnace (at breaker and on furnace) moved my red wire then is seemed like it was working but still slow to shut down fan, while doing all of this found this thread about the software so I turned the min/max temp off. It had gone off and on several times and appears to be working! I will see how it goes and contact Google to get the old version if necessary. So bottom line, not sure if it was changing my wires OR turning off the min/max temp so try one or do both?
All new comers welcome to the cheated club! Join the class action. Google has screwed thousands or hundreds of thousands of customers with this untested 6.2.22 firmware. I lost wifi connectivity but other things work. No help from customer service. Suggested me to get new Nest.
I have spoken with 3 different people in support and all they read off their little "what to say to customers who say it's the software" is - Our engineering dept has not told us there is an issue. I said well how about you GOGGLE 6.2-22 and see the thousands of ppl who can't all be wrong but of course they can't Google I guess? No help but if I get the claim # to Dsmit maybe I can get the new part they sent him?
Found a UTube video on how to turn your nest into a plain thermostat by turning off certain settings ! I just used it on mine and it started to heat right away! I’m going to look for a alternative thermostat to use or just use this one on the settings I have! The only thing I’m not sure about right now is the sensors I have around the house to set the temperature to that one. Will see about that after house gets warm!!! OH just look up that video as I stated it should come up.
I have this exact issue. I had an older model that had the same issue but with the AC a year ago. I replaced the backplate and it did not fix the issue. The Nest would call for AC but the AC wouldn't turn on. I ended up having the HVAC company put in a regular thermostat while I decided what to do with the old one. I ended up buying a new Nest learning one this past October. It worked fine until November. When I spoke to support they wanted to send me a new backplate. I waited a couple months almost before I got the backplate. When I had the HVAC install it the head would call from the Nest, but the furnace wouldn't turn on. I went back to Google support and they agreed to send me a new display. I got the display about a month ago and just last night it stopped working. The Nest calls for heat but the furnace doesn't turn on. The version on it is. 6.2-22. So I put the old one that had issues with the AC on to see if that one worked and sure enough the heat called and turned the furnace on. The old one is on version: 6.1.1-21. So I am using my old one that hasn't been updated yet and isn't connected to the internet so it won't update. Going to try support AGAIN since this is the second Nest display and third backplate.
Just an update on mine. I called support and explained my situation. the guy asked me to check a few things with the power settings and get some readings of the voltage. told me he didn't want to send me ANOTHER display which I agreed with. so he is escalating mine up to the dev teams. I did mention this thread and that many others are having the same exact issue I have. He added that to the ticket. so we will see what happens.... ¯\_(ツ)_/¯
If anyone is interested I got a response back and they want to replace this brand new one with ANOTHER brand new one. ¯\_(ツ)_/¯ they dont seem to think its a software issue. I find it hard to believe that it is a hardware issue. I have had a brand new display and back plate. Then another back plate. Then an entire new display and back plate and now they want to replace the whole set AGAIN.
At this point, what should we do? Start contacting our state's attorney generals and seeing if they can wake up Google and get some attention? Its absolutely disgusting how Google is ignoring this very obvious issue.
Ridiculous to all this has been going on since October and there have been no updates to fix the software and not one comment from Google text confirming or offering fixes on till they get it fixed..
My thermostat keeps saying no Wi-Fi signal and it switches on and off every 5 minutes until it reaches the heat. This is going to kill my brand new furnace.
I've also not once seen it turned to Eco Greenleaf mode when I've left the house I have it set to connect to my phone's Bluetooth and the sensors on the thermostat and it has yet to ever turn on that I'm home when I get home or show that I'm away when I leave after I manually set that I'm home.
I factory reset it disconnected reconnected and I still have all these problems and then it runs semi okay although it cycles frequently runs longer than usual and then after a couple weeks it says no Wi-Fi last time it said no power Wi-Fi turned off. There is no C Court connected to this but these are designed not to work with the c wire and I've never had a problem in the last year not having a C wire.
If I have to install one of the C wire editions then that's fine even though we specifically bought this more expensive one because it says right there that C wire is not needed and it will run just fine without it but we do have other options to add one if you have problems although all the problems I seem to be having have nothing to do with the C wire except for the last one where it said it turned off Wi-Fi for low power but that's the only time it's ever said that.
My parents I talked them into getting the new gen 3 learning because the previous one I had was so great at detecting when I was home and away and saved a lot of money but theirs is acting and behaving just as badly and they have a newer furnace and wiring that does have a C wire and still having the problems with the 6-22 firmware.
Be complaints and problems that you're going to ignore not even respond to before you give any sort of documentation or I don't know maybe revert back to the one that worked or maybe updated to fix the problem and if you don't know how to fix it revert it to the one that works before everybody started.
Ridiculous for how expensive these are and how it takes over 2 years to take the incredibly high price for these pay for the energy you save and that's if it's running correctly which is sure as heck isn't now.
I have a 2-stage heat pump system and after the Version 6.2-22 update, the AC stopped working. I called a technician who came out and said it was because of the Nest update. The HVAC system works fine, but after the October 6.2-22 update, Nest is no longer sending the command to turn on the AC.
The 6.2-22 software update was automatically applied on my thermostat on 10/27/21 -- exactly one month after my 2-year warranty ended. The AC hasn't worked since that update. I had my HVAC technician come out and he told me it was the Nest Thermostat and that the software updated caused it to no longer send the call for AC, only heat. I then called Google for support only for them to tell me that the warranty was expired and that I just needed to buy a new thermostat. Too bad they only make them to last for 2 years. Time to revert back to my Honeywell digital that was far cheaper and will last forever.
I'm curious if anyone has had the latest version (6.2-27) come through and if it fixed any of your issues? The last three versions from the support page are:
6.1.1-21 (September 2021) - everything seems to work under this version...my Nest E's were all rolled back to this unknowingly to me on December 28th and all have this version still as of today
6.2-22 (November 2021) - the "garbage" version that seems to be crapping out everyone's t-stats
6.2-27 (supposedly released February 2022) - ??????????
I haven't gotten it. My non-working on is still on the 6.2-22 version. I put it back on the last couple days because we had warm weather and I didn't need heat in hopes that the update would come down. It didn't.
Side note though, after putting it back on the wall the heat function started to work again sunday so I left it on the last two days. However this morning when I needed it the most because we got snow it stopping calling for heat. It showed the current house temp was 68 however when I put my older display unit with an older software version installed on it showed it was 63 in the house. ¯\_(ツ)_/¯
You know there has been no action by Google Nest to fix this crap so I’m thinking about a lawsuit against them! I had to replace my motherboard on my AC unit and it was only 3 years old or less! I’m pretty sure the best was the blame because it was always trying to fire up the heater!!! So I turned all the features of the nest off and for now just use it as a plain thermostat!
It’s now June ‘22 and Google still doesn’t admit that the firmware 6.2 update bricks the 3rd Gen thermostats. Spent 4 hours on customer service to be told I need to pay full price for replacem3nt displays. No way…changing out ALL Google products. I’m done
Since the June update the additional temperature pucks keep dropping off. I have to constantly reboot the thermostat (hold ring down until reboot) in order for them to come back. Unfortunately they don't stay around long. If it was only one it might be the battery, but its both of the two I have. I have not experienced the issues you describe however.