home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.59k stars 29.91k forks source link

Nest - Thermostat reporting “off” when actually heating #62845

Closed PeteRager closed 2 years ago

PeteRager commented 2 years ago

The problem

The climate entity in Home Assistant was reporting the hvac_action as off, when the thermostat was actually “heating”.

In HA I reloaded the UI and viewed the entity in developer tools and the all reported Off, as well as the history data. Interestingly, the heat setpoints were reflected correctly, whether set from HA or the NEST App. Also, it had been reporting fine yesterday, so this anomaly was just within the last 24 hours.

I then went to the integration panel and selected “reload” at which point the entity started reporting correctly,

Not much to go on, I will continue to monitor to see if it occurs again. Let me know if there is debug logging to enable to grab more info.

What version of Home Assistant Core has the issue?

2021.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Nest

Link to integration documentation on our website

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

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No

Additional information

No response

probot-home-assistant[bot] commented 2 years ago

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! (message by CodeOwnersMention)


nest documentation nest source (message by IssueLinks)

allenporter commented 2 years ago

Thanks for the bug report.

The nest integration queries the API on startup, then any future updates are delivered over a pub/sub feed. It makes sense if a message were dropped that reloading the integration would get everything into the correct state. Now the question is what happened to the message?

Can you enable debug logging to capture events delivered from google to home assistant? Add this to your configuration.yaml and it will show the contents of events being received, which should include updates to the hvac mode:

logger:
  default: info
  logs:
    homeassistant.components.nest: debug
    homeassistant.components.nest.climate_sdm: debug
    google_nest_sdm: debug
    google_nest_sdm.device: debug
    google_nest_sdm.event: debug

Generally https://www.home-assistant.io/integrations/nest/#troubleshooting discusses more details about diagnosing subscriber related issues.

PeteRager commented 2 years ago

Sounds good. I’ll turn the logging on. Btw - thanks for putting in that desktop authorization mode, it made the setup easy (and I had been putting it off since the web based oauth looked like a bunch of work)

It was at least two messages as the system cycled to Heating then Off and back to Heating.

PeteRager commented 2 years ago

This did reoccur, unfortunately due to my error no debug logs. Reset and this time a verified the logs are being generated.

PeteRager commented 2 years ago

Actually I’m mistaken, the issue did not reoccur. Reviewing logs on the original incident, I did notice that my router had rebooted several times (was editing firewall rules). Could be this loss of connection causes the breakdown. I’ll let it run for a few more day see if it recreates, if not Ill try some router reboots.

phildespres commented 2 years ago

Similar behavior described here: https://community.home-assistant.io/t/nest-integration-climate-set-hvac-mode-set-to-off-not-working/351878/2

allenporter commented 2 years ago

That sounds like the opposite, that you can't shut it off. On that issue I got a contact on the nest team to confirm they are aware of the issue and working on a resolution.

phildespres commented 2 years ago

Ok thanks! Glad to know they are aware, this was driving me crazy.

PeteRager commented 2 years ago

I also saw a case where the temperature was not reported. Unfortunately that happened right after an upgrade when I turned debug off to tail the log for errors. I also saw a failure to set a setpoint - returned a 500 - that I do have a log for - I’ll try to get that uploaded.

phildespres commented 2 years ago

Other piece of information: the thermostat will not obey a temperature_set command via API if it is in pre-heating mode (to reach a programmed temperature). I set the temperature to 9 C to shut down heating as a workaround for not being able to put it in "off" mode this morning, the Nest app correctly reported the correct 9 C set temperature but the heating did not stop (temp was at 19 C and wanted 20 C as program target). Hopefully, the off mode bug will be resolved soon...

allenporter commented 2 years ago

The off mode bug has been resolved by the nest API team and I have confirmed it works for me.

Anyway, back to the original issue discussed here @PeteRager are you seeing any issues left? Perhaps we can recap the current state of things for your issue since it seems like its the opposite of the issue we dug into here.

PeteRager commented 2 years ago

I have not seen this reoccur in a long time. I’d say let’s close it for now.

allenporter commented 2 years ago

Thanks 👍🏼