First, GE dimmers (at least the 12718 that I’m using), by default, take time (about 3 sec) to turn on and off (if you don’t specify a brightness level.) So, you should make sure you have refresh_value: true
and delay: 3
set in your configuration. This is what I have in my configuration.yaml:
zwave:
usb_path: /dev/zwave
network_key: !secret zwave_network_key
polling_interval: 10000
device_config:
light.family_room_lamp:
refresh_value: true
delay: 3
With this configuration, after HA tells the dimmer to change, it will check the dimmer’s status after 3 sec to make sure it shows the correct level.
Now, having said that, if you use HA to change the dimmer to a specific level, the dimmer will (more than likely) do that instantly. This is just the way I’ve found the dimmer works. (I would assume all their dimmers behave the same way.)
Next, when you change the level via a service call (i.e., light.turn_on
), you can specify the brightness one of two ways: brightness
or brightness_pct
. The first has a range of 0 - 255, whereas the second has a range of 0 - 100. (brightness_pct
will actually be converted by HA to brightness
, so when you look at the dimmer in HA, the brightness will be reported as a value in the range of 0 - 255.)
Lastly, if you just turn the dimmer on from HA (e.g., you use the light.turn_on
service call, but you don’t specify a brightness), this is a special case. Basically HA tells the dimmer to turn on to the same brightness level it was at the last time it was on. (This is a function of the dimmer, and it remembers the level, not HA.)
So, this might be more than you were asking for, but I figured it doesn’t hurt to share what I discovered about how these dimmers work. Hopefully this helps. If not, feel free to ask more questions.