Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nest Integration Thermostat has spurious Heat value #131173

Closed
puterboy opened this issue Nov 21, 2024 · 11 comments
Closed

Nest Integration Thermostat has spurious Heat value #131173

puterboy opened this issue Nov 21, 2024 · 11 comments

Comments

@puterboy
Copy link

puterboy commented Nov 21, 2024

The problem

I have had one of my thermostats set to ECO with temperature = 50 degF (10 degC) for 2 days now without changes.
This morning, I noticed that HA shows the value at 32 degF (0 degC) even though nothing has changed and the thermostat itself as well as the Android App still show ECO mode with temperature = 50.

Querying the Google Nest API using CURL, shows that the heat setpoint is indeed 50 degF.

So somehow, the HA Nest Integration recorded a spurious change to 32 degF (0 deg C) -- given that the core units are Centigrade, it seems as if the HA Nest Integration somehow just set the value to zero

What version of Home Assistant Core has the issue?

core-2024.11.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Nest

Link to integration documentation on our website

https://www.home-assistant.io/integrations/nest/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

The sqlite database shows:

2024-11-20 17:26:31|heat|204015|{"current_temperature":64,"temperature":50,"hvac_action":"idle","preset_mode":"eco","friendly_name":"Kitchen"}
2024-11-20 21:25:53|heat|203938|{"current_temperature":65,"temperature":50,"hvac_action":"idle","preset_mode":"eco","friendly_name":"Kitchen"}
2024-11-20 21:35:53|heat|204015|{"current_temperature":64,"temperature":50,"hvac_action":"idle","preset_mode":"eco","friendly_name":"Kitchen"}
2024-11-20 22:50:52|heat|203938|{"current_temperature":65,"temperature":50,"hvac_action":"idle","preset_mode":"eco","friendly_name":"Kitchen"}
2024-11-21 01:25:52|heat|204015|{"current_temperature":64,"temperature":50,"hvac_action":"idle","preset_mode":"eco","friendly_name":"Kitchen"}
2024-11-21 03:00:52|heat|204116|{"current_temperature":63,"temperature":50,"hvac_action":"idle","preset_mode":"eco","friendly_name":"Kitchen"}
2024-11-21 05:29:26|heat|359280|{"current_temperature":62,"temperature":50,"hvac_action":"idle","preset_mode":"eco","friendly_name":"Kitchen"}
2024-11-21 08:00:05|heat|416614|{"current_temperature":62,"temperature":32,"hvac_action":"idle","preset_mode":"eco","friendly_name":"Kitchen"}
2024-11-21 08:55:52|heat|416749|{"current_temperature":61,"temperature":32,"hvac_action":"idle","preset_mode":"eco","friendly_name":"Kitchen"}
2024-11-21 09:10:33|heat|416614|{"current_temperature":62,"temperature":32,"hvac_action":"idle","preset_mode":"eco","friendly_name":"Kitchen"}
@home-assistant
Copy link

Hey there @allenporter, mind taking a look at this issue as it has been labeled with an integration (nest) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of nest can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign nest Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


nest documentation
nest source
(message by IssueLinks)

@todanator
Copy link

This may a slightly different issue but I've also noticed a delta between the temp reported in HA vs the temp on the nest app.
IMG_0072
IMG_0072

@robsug90
Copy link

Also having this issue with Nest Thermostat reporting incorrect temperatures in HA. In the Nest app it works.

@allenporter
Copy link
Contributor

Presumably the pubsub feed is publishing incorrect events. Can you enable debug logging for the integration? We need to capture logs when it transitions to this happening, e.g. when it sends an event message that is invalid

@robsug90
Copy link

Here's a few days of logs
error_log.zip

@allenporter
Copy link
Contributor

@robsug90 Thanks for collecting the detail. The other bit we need is if this happened again: around which time during this log did you see the problem? Nothing stands out during this time from a quick look.

@todanator
Copy link

Sorry I suspect my issue is an error from pubsub events from Google like this issue.
#110010

@IngmarVerheij
Copy link

(not sure if this the same issue, but its plausible)
When displaying the Nest in Celsius there's an offset as well. Nest is configured to heat to 20.5c, but home assistant reports as 20.3c

@iTrim
Copy link

iTrim commented Dec 18, 2024

I also have same issue - reloading Nest Integration entries temp fixes it but issue comes back

@iTrim
Copy link

iTrim commented Dec 18, 2024

Look for nest entry ID in /homeassistant/.storage/core.config_entries

Then create a new automation or paste into YAML

alias: Nest Script
description: Reload nest every 5mins
triggers:
  - trigger: time_pattern
    minutes: /5
conditions: []
actions:
  - data:
      entry_id: PASTE NEST entry ID HERE
    action: homeassistant.reload_config_entry
mode: single

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants