hvac_action not updating
strelniece opened this issue · 4 comments
To start with, thanks a lot for fixing this component, right now I'm only mad ad myself for not noticing untill now ;)
Just one thing, don't know if it's a bug or a feature. the hva_action doesn't seem to update it's state exept for when you turn it off.
Yes, of course it could be something weird with my thermostat, but I don't think so, set the setpoint to very low, ant the temperature is falling and no update from the energy.
I guess it could be a thing with the API, since the state doesn't show in either app or web.
If that is the reason, if anyone has an idea how to figure out how often it turns on/off, I would be even more happy :)
Hi @strelniece, are you still getting this issue? There have been a few changes in HA and the way this component fits into it, and I'm wondering if that might have improved things for you?
Hi, and sorry for completely missing this.
Afraid the answer is no, still no change in the sta :(
In a nutshell, right now there isn't a way in Home Assistant to know whether the Warmup system is actually heating or not without looking at temperature changes.
Based on my experience with other climate entities, I believe the hvac_action attribute should reflect whether the system is heating or not. With the current code if the system isn't turned off, hvac action is always set to heating, so Home Assistant always believes the system is running.
To see why this matters, here's an Ecobee thermostat via the Ecobee integration. You can see when the heat is actually running and how the current temperature changes.
Honeywell Lyric T6 thermostat that is integrated into Home Assistant through Apple HomeKit. The lovelace card is a history graph. (There is a lot of the graph filled in because the heat was running a lot on the 15th. (Unlike the Ecobee, the Honeywell doesn't give good data about what the current temperature is.)
Here's a Warmup climate entity. Most of the time the Warmpup target termpature was set to 60 F, so the floor heat wasn't running. However all of area under current temperature is filled in because Home Assistant thinks the Warmup system is running continuously. (There were some short intervals when the system was set to boost/override around 7pm and 8am)
The warmup integration is getting the current temperature and target temperature correctly. It is also picking up the attributes related to boost.
This is an old but still present issue - Has anyone ever figured out whether it is possible to tell from the warmup "API" whether the thermostat is currently "calling for heat" - i.e. turning the system on?
I do see any indication in the iOS app or web portal. However the thermostat must be sending that data to warmup's service so that it can compute energy.