Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
0.96.x climate change broke heatit modes #25721
Home Assistant release with the issue: 0.96.5
Last working Home Assistant release: 0.95.4
Operating environment: hass.io on RPi 3B+ running docker in Raspbian
Component/platform: zwave climate
Description of problem:
<Value genre="user" index="0" instance="1" label="Mode" max="0" min="0" read_only="false" size="1" type="list" units="" value="0" write_only="false"> <Item label="Off" value="0"/> <Item label="Heat (Default)" value="1"/> <Item label="Cool" value="2"/> <Item label="Energy Heat" value="11"/> </Value> <SupportedModes> <Mode index="0" label="Off"/> <Mode index="1" label="Heat"/> <Mode index="2" label="Cool"/> <Mode index="11" label="Energy Heat"/>
Where mode 11 is not available in GUI (blank entry). See traceback below for error when trying to issue command.
I tried manually editing the zwcfg to replace "Energy Heat" or "Heat Econ" modes with the string "eco". The empty selection in the faceplate for the climate entity got a description (eco was added in my language), but the command issued got the same error message. I also tried running the set_hvac_mode manually with the same result.
In the status page, the following hvac_modes list is present (after altering the zwcfgXXX.xml):
When I look at the entities, the entity for heat has the following properties:
whereas the energy heat entity has the following properties:
Due to this issue, I either need to rewrite all my automations to low level parameter setting on the zwave devices or I will have to restore my snapshot for 0.95.4 (once again).
Traceback (if applicable):
It seems to work, but it is not referenced as a breaking change. It has broken all my automations, as they have used
It was a breaking change in Release 0.96.0.
I do not agree, as there was no mention of migrating operation modes to preset modes.
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.