08-19-2023
08:27 PM
- last edited on
09-17-2023
09:24 AM
by
Jenelyn_O
This problem started on August 14, 2023
After doing some investigation I found the following on the thread:
08-14-2022 10:17 AM
I am surprised this is happening to a newer Nest thermostat. I have one that is now 7 years old and just this summer it started randomly turning cooling down to 19 C (66.2F). The AC could run for hours before anyone notices if we are even home. It is not scheduled to do this nor has anyone touched the manual or app controls. It just wastes energy and causes my Hydro bill to increase needlessly.
Nothing has been changed since it was physically set up 7 years ago.
The only thing that has changed are periodic software updates directly from Google to the thermostat.
I would certainly like to see any logs detailing what action was taken when the thermostat was turned down.
This just happened a few minutes ago that I noticed the AC running, checking it to find cooling set at 19c and put it on eco for now. Normally we have it set around 23 C (73.4 F) during the summer.
Nowhere in the schedule does it have 19 C set, but I have just turned the learning option off now so we’ll see if this helps at all.
I would say this just started happening for me within the last month.
It appears to me that some type of Software or Firmware update has been applied to Nest Thermostats that is causing this bug.
Model | Display-3.4 |
Backplate model | Backplate-5.3 |
Serial no. | ################ |
Software | 6.2-27 |
Updated | May 3, 2022 11:13 PM |
Anyone else have this problem?
Answered! Go to the Recommended Answer.
08-23-2023 08:44 PM
On August 21, 2023 I removed all connections to Google Home that were in "Works with Nest" in the Nest settings and set the Nest thermostat to 24° C.
08-20-2023 08:46 AM
This is the log entry that gets made in the Energy History log when the set temperature inexplicably gets changed due to what appears to be a Nest thermostat (software) fault.
This fault appears to affect both Heating and Cooling Cycles, and this has been identified by myself and other Nest Thermostat users.
If this fault were to cause overheating of the HVAC system which in turn caused a fire and a house burned down, then I expect the legal liability for this would fall upon Google Nest and Alphabet. If the insurance company were to look for someone to sue for the damages I expect that it would be Alphabet and I am quite sure that a competent Software Engineer could determine the cause from the underlying software logs from the Nest thermostat.
This is more than an inconvenience, it is an identified safety hazard that would appear to be the responsibility of Alphabet, Google Nest.
08-23-2023 08:44 PM
On August 21, 2023 I removed all connections to Google Home that were in "Works with Nest" in the Nest settings and set the Nest thermostat to 24° C.
09-17-2023 09:29 AM
Hi JBurr,
Thanks for posting in the Google Nest Community forum. I'm sorry for the delay. For the safety of our Community members, your first comment on this post was edited to remove personally identifiable information.
We appreciate you being a step ahead of us, and we are glad that the issue seems now resolved. Please feel free to let us know if you still have questions or concerns, as we'll be willing to help.
Cheers,
Jenelyn
09-22-2023 10:43 AM
Can you share how to remove those other connections?
09-25-2023 09:31 AM
Hi Bedryden,
Could you please tell us more about your request? Also, what do you mean about other connections? I'd like to help.
Kind regards,
Jenelyn