Great news hope that progress …
Thanks
Transitions aren’t the same as central scene command class.
Transitions already work with several light platforms - basically, you can say “transition from off to 60% and take 2 minutes to do it” to get a nice slow fade (helpful for alarms clocks with a non-jarring wakeup).
I’m experiencing a similar issue. New installation of hass using latest raspbian + all-in-one. New HS-WD100+ dimmer out of the box came with an out-of-date firmware. Firmware updates on these switches requires a $50 piece of software (but which can be had for free if you buy $250 worth of the switches). My switch came with FW v5.17, so I flashed it to v5.19 whose changelog includes the following two items:
- Improved dimming performance for LED bulbs.
- Instant status updates via Z-Wave associations. This should allow for greater compatibility when using non-HomeSeer control systems.
I was hoping that the update would resolve this issue but no dice.
In my case, when I open the dimmer in the web UI and click a value (say, 25%), the dimmer will be set to 25% but the slider will snap back to the original value on screen which I opened the dimmer panel. If I click on a new value (say, 50%), it will again set the dimmer to 50%, then snap the slider back to 25%. If I then click on 75%, dimmer sets to 75% and UI snaps back to 50%.
It’s as if the slider is always set to the previous value.
edit: Looks like I misinterpreted the issue slightly. This appears to be the core problem here, it’s updating while still in the transition: https://github.com/home-assistant/home-assistant/pull/3893
Any updates? Having the exact same issue described by luma. I think I may need to return these and go with a supported dimmer, or are all dimmers having issues?
I have these working pretty well through Smartthings Hub. Only drawback is that they need to go through ST cloud for every adjustment which creates a little lag. I’m OK with it because I figure eventually someone will manage to get them working directly through Open-Z-Wave/Home Assistant.
What would truly be amazing was if a really skilled person were somehow able to crack the firmware and edit it.
My switches are now working reliably by making some configuration changes in the configuration.yaml like so:
zwave:
usb_path: /dev/ttyUSB0
device_config:
light.kitchen_ceiling_lights_level:
polling_intensity: 1
refresh_value: true
delay: 3
I’m using a slightly-modified version of the scripts posted by @mfdutra to monitor for double/triple clicks and to trigger events in response. The result is very fast (sub-second response time) and has been reliable thus far.
1 Like
@luma Even with that modification It doesn’t work correctly through the frontend for me. If I used the emulated hue component and Alexa it works just fine.
Not entirely sure at this point where the UI is going wrong.
For those watching this thread, we have been able to get a PR made and merged into the dev branch. I dont know when dev turns into master, but you can use dev if you want the feature sooner!
1 Like
Omg you are a hero. Can’t wait to try this out
How to implement this with the 0.53 ?
Yes! I’d love to see a noob oriented tutorial for setting this up, both the HASS and OZW parts.
I tried setting up the central scene but i don’t see scene data. I purchased ZWP dimmers which should be the same as the homeseer. Has anyone else gotten this to work?
2017-10-16 17:31:01.865 Detail, Node019, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x13, 0x05, 0x5b, 0x03, 0x16, 0x03, 0x01, 0xaa
2017-10-16 17:31:01.866 Detail,
2017-10-16 17:31:01.866 Info, Node019, Received Central Scene set from node 19: scene id=1 in 3 seconds. Sending event notification.
2017-10-16 17:31:01.866 Detail, Node019, Refreshed Value: old value=3, new value=3, type=int
2017-10-16 17:31:01.866 Detail, Node019, Changes to this value are not verified
2017-10-16 17:31:01.866 Detail, Node019, Notification: ValueChangedWhat’s the current status on the HS-WD100+ working with Home Assistant? I’m about to buy a bunch of these switches, but I don’t know if I also need to buy the HomeSeer software to take advantage of the Central Scene and Multitap capabilities.
Work fine; I have dozens of them up and going. Don’t use polling as not required for these switches.
I still have a hack to make the “instant update” work but they work fine otherwise. Multi tap works
- alias: 'HomeSeer Switch Fix On'
trigger:
platform: event
event_type: zwave.scene_activated
event_data:
scene_id: 1
scene_data: 0
action:
- service: switch.turn_on
data_template:
entity_id: '{{"switch." + trigger.event.data.entity_id.split(".")[1] + "_switch" }}'
- alias: 'HomeSeer Switch Fix Off'
trigger:
platform: event
event_type: zwave.scene_activated
event_data:
scene_id: 2
scene_data: 0
action:
- service: switch.turn_off
data_template:
entity_id: '{{"switch." + trigger.event.data.entity_id.split(".")[1] + "_switch" }}'
Basically, when you manually use the switch it sends a scene activated command so I have to manually update the switch status otherwise it appears to be off still.
1 Like
Anyone notice an issue with the WD100+ where it won’t fully turn off in home assistant via automation? I have an automation that sends a light.turn_off command, the light load and all the indicator LEDs turn off, but the state remains ‘on’ with a brightness of 10. I assume it has something to do with the way this dimmer fades out slowly and something in HA doesn’t follow the entire sequence to the end. Any tips on how to defeat this bug?
I recently learned a workaround to fix the ui lag for the WD100+ dimmers. You just need to set ‘refresh_value’ to true under the zwave component for that switch like this:
zwave: usb_path: /dev/ttyACM0 device_config: light.bedroom_level: refresh_value: true
1 Like
Thanks- does this do all the magic on it’s own? No need to set polling or anything? How often does it refresh itself?
On its own, it will send a refresh to update the state of the light with a default 2 second delay after its state changes (to change to a 1 second delay you would just add ‘delay: 1’). This doesn’t poll the switch in intervals, it just sends out a final delayed refresh after a state change. In practice, this totally fixes the UI brightness slider, which used to stutter badly, and it ensures that the light will accurately update to its final state after a couple seconds.
There are pull requests in HA and OZW to natively fix this issue (the HA one is waiting on the OZW one to get merged first).