core: ozw: Homeseer HS-WD200+ dimmer status is not updating when toggling the dimmer
The problem
Testing out new ozw integration with my HS-WD200+ switches the state of the switch doesn’t initially match (I had the same issue with zwave integration as well)
The on/off switch (HS-WS200+) work fantastic. The result is near instantaneous and works great.
However on the HS-WD200+ if i turn on or off the switch (or change the dimmer) the status toggles and then toggles back before the dimming is complete leaving the switch in the wrong state. Toggling it again fixes the problem
For example if my lights are on toggling the dimmer to off will toggle the HA state to off and the immediately back to on. Mean time the switch/lights will remain off. Switching back to off seems ot fix this.
Looking at MQTT explorer i see there is a Target Value but it doesn’t seem to be updated at all (perhaps a problem with ozw?)
Environment
- Home Assistant Core release with the issue: 0.11.0.7
- Last working Home Assistant Core release (if known): N/A
- Operating environment (Home Assistant/Supervised/Docker/venv): These get renamed so often i am not sure. I am running the image on a RPi
- Integration causing this issue: ozw
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/ozw/
Problem-relevant configuration.yaml
None.
Traceback/Error logs
None.
Additional information
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 1
- Comments: 33 (10 by maintainers)
This seems better on HA 0.114.0. The devices will toggle, go back during dimming then update to the final state at the end. However there are still instances where the HA state and the actual state of the dimmer are different (HA says on, light is off or visa versa).
This one issue is really holding me back from HA and I would love to help out on providing a fix, but its’ not clear to me where to go next or where to start.
I would recommend you attach two MQTT dumps to this issue. Replace
24with your node ID.The first dump would be the entire node, so
topic: OpenZWave/1/node/24/#.The second dump would capture the activity while you toggle the switch, This would show whether the Target Value is being published by OZW or not. For that, you could dump
topic: OpenZWave/1/node/24/instance/1/commandclass/38/value/#. Make sure thedurationvalue of the dump is set long enough for you to toggle the switch.You could also turn on MQTT debug logs but it gets busy quickly.
Question for the developers, the light component is checking for a target value, but the discovery schema does configure it, is it necessary to add it to pickup the Target value?
That has never worked for me. Even assigning the ramp config values to be as quickly as possible, the GET after the SET always reports the wrong value.
0-99 are the valid brightness values. 255 means toggle the last value.
You should be able to follow the logs and see the interaction between the OZW library and the switch. You’ll see logs that say
[ozw.library]. Are you using the addon or using docker on your own? If using the addon, also make sure you’re up to date there. The logs should be in the supervisor somewhere. If standalone docker, the logs are output to the docker logs. If using the allinone image, there is an ozwdaemon.log file.Yes, I think we need to add it to the discovery schema. If I get a dump from the device I can try to fix it.