Since last upgrade of HA (2024.12.1) my thermostat card / integration doesn’t work right anymore. It shows it is warming (verwarmen) while the kettle is not running and i even switched warming off. The thermostat still shows it is warming.
I reinstalled the Plugwise integration but the problem is still the same.
I have a Plugwise Anna thermostat.
I hope someone knows what is going on and can help me?
Maybe @bouwew can shine a light on this?
@Gerard-mst the state Verwarmen that you are looking at is not a representation of the state of the heating-system. It is a so-called HVACMode specific for HA.
When you look at the options shown for this item you will probably see “auto” and “verwarmen”.
“Auto” in this context means that a schedule (made in the Plugwise App) is active, the heating of the house is done based on a programmed time-schedule.
“Verwarmen” in this context means that no schedule is active and the system will start the heating when the temperature goes below the setpoint, and stop heating when the temperature goes above the setpoint, within a certain margin.
Wen i switch back to auto again the Verwarmen text and the orange glow are still there. This wasn’t like this befor.
The schedule switches to night mode here at 21:45 everyday. It is now after midnight and it is still showing verwarmen (heating up).
The kettle isn’t actually heating since the schedule turned the temperature for the night at 12 degrees Celcius but the integration still shows Verwamen (heating up).
This wasn’t the case before and doesn’t makes sence since the kettle is not actually heating up but is off.
I upgraded to 2024.12.2 a minute ago. After that i rebooted the VM system HA is running on. Now the Thermostat integration looks normal again. But if i do a scheduled start or a manual start in both the orange text “verwamen” and the orange glow did not come back.
And yes, sorry, you were correct I realize, the text Verwarmen in the first picture, and Inactief in the 2nd picture are the HAVCAction state, indeed showing what the system is doing.
And the problem seems to be that the state is reversed for some reason. Can you please create an Issue for this problem in the Home Assistant github here: Sign in to GitHub · GitHub
Unless you don’t have a github login? Then we’ll discuss further here.
I’ve looked a bit at the Plugwise code, I’m wondering, is you Anna connected to an Adam? Only then the climate HAVCAction state can differ from the binary_sensor_xyz_verwarmen state.
If you don’t have an Adam, what is the firmware version of your Anna, and how does your heating system look like? Is it OpenTherm or OnOff controlled?
Having an issue in the HA github helps a lot with rolling out bugfixes to the HA (Plugwise) code.
Let’s continue this in the HA Issue you are creating.
Even een berichtje over de Plugwise updates in Home Assistant 2024.12.0:
De climate- en bijbehorende select-entities van (alleen) de Adam zijn veranderd, deze zijn verplaatst van devices (Lisa, Tom, Jip, enz.) naar (virtuele) devices met de modelnaam ThermoZone. Hierdoor zullen zeer waarschijnlijk de namen van alle climate-entities veranderen naar de naam van de Zones zoals die zijn gedefinieerd in de Plugwise App.
Door een bugrapport in de HA github realiseerde ik me kortgeleden dat ik/we al jaren een fout hebben gemaakt bij de implementeren van de climate-entities. Die fout is in HA 2024.12.0 gecorrigeerd. De Plugwise integratie toont nu de climate-entities als zone-thermostaten, net zoals in de Plugwise App.