I’ve been playing with the listen_state with the duration option today. I was using my office lights as a test case. About two or three minutes ago, I realized my problem. I was using a “light” not a switch. As soon as I switched to using the switch.front_door_light as my test case everything started working as it should.
The way lights dim their way off and then sometimes don’t report that they are indeed off for a minute or two after the light stops shining is frustrating. It’s the only device I know of where we can’t trust that the light is turned_off when we send it a turn_off command.
How is everyone else programming around the “light” issue?
Yeah, if you’ve got the same stupid GE dimmers that I do then getting accurate reporting back from them after switching them on or off can be annoying. It’s a problem with the firmware on the switches; fortunately Home Assistant has a workaround. If you don’t already have a zwave_device_config.yaml file in your configuration directory, create one. Then for each of your Z-Wave entity IDs, put something like this into zwave_device_config.yaml:
light.bedroom_light_level_27_0:
refresh_value: True
delay: 3
This will tell HA to wait 3 seconds after toggling the light, and then explicitly go and ask it what iits level is. As far as I’ve been able to figure out, you have to do this for every single device you have that has the problem.
You can play with the delay and see if you can get it lower; if you poke at the device with OZWCP you can make dim faster or slower, see https://community.openhab.org/t/change-brightness-level-smoothly-on-ge-jasco-dimmers-12724-45715/11868 for more details on that. I have Parameters 7 and 8 both set to 1 (fastest possible dimming) and I run with delay: 1. It seemed to work well all the way down to delay: 0.8. With delay: 0.6, HA was checking back in with the light too quickly to see its final state.
1 Like
Oh and you need something like this in your configuration.yaml after you create the zwave_device_config.yaml:
zwave:
... other stuff ...
device_config: !include zwave_device_config.yaml
Which hardware?
The GE lights that Jordemort is talking about.
Does this only work on lights controlled through a Zwave stick, or will it work with ones found from another hub like wink?
I’ve only ever used a stick. I’m not sure if there’s a way to make Wink poll the lights for their status in the same way; if there is the configuration would be different, I figured out the above by reading through the source of the zwave component
seems like a zwave thing if i search on google.
but you could try it because i remember that i have seen refreshrate on other places too.
you could also try if a template switch based on those lights, but with a time entity attached to it makes any difference.