core: Missing operating state for hvac via vera zwave
Home Assistant release with the issue:
0.96.5
Last working Home Assistant release (if known): NA
Operating environment (Hass.io/Docker/Windows/etc.): PyEnv on Linux VM
Description of problem: HVAC state isn’t getting pulled from Vera zwave climate device. It’s visible via the API but I’m not seeing it as an attribute of the climate entity
<state id="3425" service="urn:micasaverde-com:serviceId:HVAC_OperatingState1" variable="ModeState" value="PendingHeat"/>
<state id="3426" service="urn:micasaverde-com:serviceId:HVAC_OperatingState1" variable="ModeStateForEnergy" value="1"/>
Current attribute list for thermostat in question
fan_mode: auto
max_temp: 95
temperature: 68
fan_modes: on,auto
current_temperature: 69
supported_features: 9
friendly_name: Upstairs_Thermostat
min_temp: 45
hvac_modes: cool,heat,heat_cool,off
Vera Device Id: 18
battery_level: 93
Problem-relevant configuration.yaml
entries and (fill out even if it seems unimportant):
vera:
vera_controller_url: !secret vera_url
lights: [14, 15, 16, 17]
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 38 (8 by maintainers)
I personally do not see how an additional read-only property could break existing devices, but if you are unable to do it, then that’s fine.
I’ll maybe try my hand at raising a PR again…
@awooganl I would recommend that you open a PR for the changes you made.