nest thermostat fan status is not reporting properly

[mgeorgia]

The problem

I believe this is different than the open issue listed here.

In my issue, the thermostat commands work perfectly fine with my thermostat. And the button to turn the fan on works as well. However, because the fan status is not reporting properly, the fan continues to show as off in HA (even though the fan is on). Since the fan shows as off, there's no easy way for me to turn the fan off using HA. If I go to the "actions" area and turn the fan off that will actually turn the fan off.

I will also note that I have a starling hub set up and everything for the thermostat works great on the hub, including fan control. Unfortunately, due to reasons that I don't understand, integrating the Starling directly into HA isn't a solution that will wok for me because the nest camera that I have does not stream properly if I do that.

Unfortunately I'm not getting any error messages at all when I do this. All that happens is that the fan state doesn't change in HA (even though the fan state is changing IRL). Please let me know what other sort of information I can provide that can help to debug this.

What version of Home Assistant Core has the issue?

core-2024.10.4

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/#climate

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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)}}

[allenporter]

The symptoms sound like the fan command is sent, but the event updating the home assistant state is never published.

I suspect that reloading the integration would re-pull the information from the server and get it back into the correct state? Just asking since that would help explain the issue (and could be a temporary workaround if in a pinch).

[mgeorgia]

Thanks for the quick reply. Could you help me understand what you mean by “reloading the integration”? Happy to test this out tomorrow but just need to know what you mean by that. What I can say is that if I go to the thermostat in the states page, I can confirm the state for the fan is incorrect and if I click the refresh button on that page, it doesn’t change but it also doesn’t seem to be doing a fresh pull from nest either. Apologies - bit of a noob still with home assistant. On Oct 27, 2024, at 9:59 PM, Allen Porter @.***> wrote: The symptoms sound like the fan command is sent, but the event updating the home assistant state is never published. I suspect that reloading the integration would re-pull the information from the server and get it back into the correct state? Just asking since that would help explain the issue (and could be a temporary workaround if in a pinch).

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[allenporter]

Go into settings then integrations then find nest and look around in the "..." menus for a reload.

[gary-sargent]

I've also had a few issues over the last few weeks where the state of the Nest Thermostat in HA doesn't match the actual state, and reloading the integration fixes this. It's only recently that this has started being an issue.

[mgeorgia]

Ok so I did the following:

The starting state was that my thermostat was in heat_cool mode but was not running (no heat, no cool, no fan). Then, using the card in my dashboard, I turned the fan on. In real life the fan turned on. Before reloading the integration, I went to Developer Tools -> States and copied the state of my thermostat climate.hallway_thermostat. Then I waited a few minutes, went and reloaded the integration, then went back to Developer Tools -> States, clicked the refresh button there, and then again copied the state of my thermostat. Both states are pasted below. The fan_mode state did not change after refreshing the integration.

Before reloading integration:

hvac_modes:
  - heat
  - cool
  - heat_cool
  - "off"
min_temp: 50
max_temp: 90
fan_modes:
  - "on"
  - "off"
preset_modes:
  - none
  - eco
current_temperature: 68
temperature: null
target_temp_high: 77
target_temp_low: 64
fan_mode: "off"
hvac_action: idle
preset_mode: none
icon: mdi:thermostat
friendly_name: Hallway Thermostat
supported_features: 411

After reloading integration:

hvac_modes:
  - heat
  - cool
  - heat_cool
  - "off"
min_temp: 50
max_temp: 90
fan_modes:
  - "on"
  - "off"
preset_modes:
  - none
  - eco
icon: mdi:thermostat
supported_features: 411
current_temperature: 68
temperature: null
target_temp_high: 77
target_temp_low: 64
fan_mode: "off"
hvac_action: idle
preset_mode: none
friendly_name: Hallway Thermostat

[allenporter]

OK, thanks. That implies it is a bug where the API is not returning the right fan state. One other thing you could do is save the diagnostics and that would give us the raw data returned from the API to rule out a home assistant bug.

[allenporter]

(Likely, this will need to file a google ticket similar to the ticket referenced in the other bug)

[mgeorgia]

config_entry-nest-01JARZJAZHTWMM2AGWM5TY4R3D.json

[mgeorgia]

I added the exported diagnostics logs above ^

So I too would think it would be a nest API bug, but then the controls via the starling hub are working just fine.

Maybe I should just create a simple integration with the local API exposed by Starling so Home Assistant can piggy back off that rather than use a separate integration.