Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.96.x climate change broke heatit modes #25721

Closed
baronKanon opened this issue Aug 6, 2019 · 7 comments
Closed

0.96.x climate change broke heatit modes #25721

baronKanon opened this issue Aug 6, 2019 · 7 comments

Comments

@baronKanon
Copy link

@baronKanon baronKanon commented Aug 6, 2019

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:
The updated operating modes do not support the "Energy heat" or "Heat econ" hvac modes on the Heatit/Multireg zwave thermostats. These have the following settings in the openzwave config:

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

hvac_modes: eco,cool,heat,off

When I look at the entities, the entity for heat has the following properties:

hvac_modes: eco,cool,heat,off
current_temperature: 23 
min_temp: 7 
max_temp: 35 
temperature: 22.5 
node_id: 44 
value_index: 1 
value_instance: 1 
value_id: 72057594781417490 
friendly_name: Termostat Entré 
supported_features: 1

whereas the energy heat entity has the following properties:

hvac_modes: eco,cool,heat,off
current_temperature: 23 
min_temp: 7 
max_temp: 35 
temperature: 22.5 
node_id: 44 
value_index: 11 
value_instance: 1 
value_id: 72057594781417490 
friendly_name: Termostat Entré 
supported_features: 1

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

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

Traceback (if applicable):

2019-08-06 08:02:06 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.1874540656] value is not allowed for dictionary value @ data['hvac_mode']
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 121, in handle_call_service
    connection.context(msg))
  File "/usr/src/homeassistant/homeassistant/core.py", line 1130, in async_call
    processed_data = handler.schema(service_data)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 267, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 589, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 427, in validate_mapping
    raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: value is not allowed for dictionary value @ data['hvac_mode']

Additional information:
NA

@ghost

This comment has been minimized.

Copy link

@ghost ghost commented Aug 6, 2019

Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with a integration (zwave) you are listed as a codeowner for? Thanks!

This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people.

@Santobert

This comment has been minimized.

Copy link
Member

@Santobert Santobert commented Aug 7, 2019

This should be solved by PR #25694 and #25537. Please correct me, if I'm wrong.

@Santobert

This comment has been minimized.

Copy link
Member

@Santobert Santobert commented Aug 7, 2019

I should add that at least PR #25537 is part of the upcoming 0.97.0 release. Please update/close this issue after you have tested the new version.

@baronKanon

This comment has been minimized.

Copy link
Author

@baronKanon baronKanon commented Aug 8, 2019

It seems to work, but it is not referenced as a breaking change. It has broken all my automations, as they have used set_operation_mode (now set_hvac_mode) to toggle the modes, whereas now they need to change to set_preset_mode. Otherwise it shows the correct preset modes from openzwave

@Santobert

This comment has been minimized.

Copy link
Member

@Santobert Santobert commented Aug 8, 2019

It was a breaking change in Release 0.96.0.

https://www.home-assistant.io/blog/2019/07/17/release-96/

@baronKanon

This comment has been minimized.

Copy link
Author

@baronKanon baronKanon commented Aug 8, 2019

It was a breaking change in Release 0.96.0.

https://www.home-assistant.io/blog/2019/07/17/release-96/

I do not agree, as there was no mention of migrating operation modes to preset modes.

@stale

This comment has been minimized.

Copy link

@stale stale bot commented Nov 6, 2019

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.

@stale stale bot added the stale label Nov 6, 2019
@stale stale bot closed this Nov 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.