Generic Thermostat - graph not showing green fill after 0.96

[Taigar2015]

Home Assistant release with the issue:
0.96.5

Last working Home Assistant release (if known):
0.95

Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io

Component/platform:
Generic Thermostat

Description of problem:
Almost the same as #25578, I think the problem is related to the HA thermostat component. And not the custom component of the other issue.

After 0.96 the climate history graph is not showing the status shaded part (if it's cooling or not).

here is my entity status:

The history graph:

The history graph used to be something like this (the green part showing if it is actually cooling or not):

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

climate:
  - platform: generic_thermostat
    name: Ventilatie Receptie thermostaat
    heater: switch.ventilatie_receptie
    target_sensor: sensor.ventilatie_receptie_temperatuur_min
    ac_mode: true
    target_temp: 22
    initial_hvac_mode: "off"

Traceback (if applicable):

Additional information:
It also happens in the Honeywell Thermostat integration, according to this topic.

[Tediore]

Can confirm this issue also exists with Ecobee via HomeKit Controller even though it worked before.

[ltjessem]

Still not working in 0.97.0

[Hackashaq666]

This is definitely still an issue with Honeywell Climate. I wonder if any climate platform is recording state correctly?

[Tediore]

Also had an issue where the thermostat would respond to commands immediately, but the frontend would take a minute or more to update when before it was also immediate. Rolled back to 0.95 because of these issues, but I'll gladly flash the latest version of HASS on a spare SD card to test if needed.

[gb53smith]

I'm at HA 0.97.1
The green fill is not shown in the history for my climate - generic_thermostat platform and climate - mqtt platform. According to this fix if the hvac_action is either "heating" or "cooling" then the green fill should be shown but it is not.

[benquan]

Can someone determine if the problem is the climate component or the history graph itself?

[Tediore]

My guess is it's the history graph itself. The climate entity state pre-0.96 was what the HVAC equipment was currently doing (heating, cooling, idle, etc.), but starting in 0.96 it's a state attribute (hvac_action), and the entity state is what mode the thermostat is set to. The documentation for the history card is pretty sparse, so I can't confirm that this would be the reason for the problem.

Edit: corrected state attribute

[gb53smith]

I tested creating a History Graph using the UI. No Green Fill shown. Somewhere there is a mismatch/disconnect. This code shows History Graph is using hvac_action == heating or hvac_action == cooling. I can see the hvac_action attribute of my Climate component (MQTT HVAC) set to cooling but still no green fill.

[benquan]

why are they using hvac_action instead of the state == cool? What is the difference

[gb53smith]

hvac_action is status from the hvac device indicating that it has received the state value from HA.

[Tediore]

More specifically, climate state is now what mode the thermostat is set to (heat, cool, off, etc.) and hvac_action is what the HVAC system is currently doing (heating, cooling, idle).

[zxdavb]

@Hackashaq666

This is definitely still an issue with Honeywell Climate. I wonder if any climate platform is recording state correctly?

I deal with four distinct climate platforms, and none of them appears to be showing the green fill (although it is summer here), although my recall is that they did at some stage during the development of climate-1.0.

I think that the recording of the state is fine. Thus, I wonder if this issue is: home-assistant/frontend#3468 and this could be closed in favour of that issue.

[bryeartem]

Also not working with Nest component as well.

[benquan]

More specifically, climate state is now what mode the thermostat is set to (heat, cool, off, etc.) and hvac_action is what the HVAC system is currently doing (heating, cooling, idle).

OK got it.. One last doubt then. What is the difference between state and hvac_mode?

[Tediore]

No difference. The Climate state is always equal to hvac_mode.

[ltjessem]

Still not working in 0.98.0

[gb53smith]

Fixed in 0.99.2 for my Generic Thermostat and MQTT HVAC components.

[Hackashaq666]

Fixed here with US Honeywell Thermostat! 0.99.2

[stale]

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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[kristianwh]

I can confirm this works for me for Generic thermostat, on 0.102.

[nate922]

This is now broken in 0.103.5, was working on 0.100.x

Anyone else having this working on 0.103.5 ? I've got a generic and nest.

Thanks

[ltjessem]

It's working for me with generic on 0.103.5

[nate922]

Thanks ltjessem.

Strange how it's not working for me, it was prior to the upgrade.
Any tips on what I could look at? there's no errors in ha logs.

[stale]

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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[ciB89]

I have 3 identical (generic) thermostats, for 1 it's working and for the other two not... I'm baffled. But I also realized that there is no event log for the two that are not working correctly (the other one shows when the settings changed etc).