ok, I’ve got all the lights bound using EP2, clusters 6 and 8, and they seem to work fine.
There are still some unexpected behaviors I observe, though.
The issue with dimming speed not being set when also changing the on/off state remains. I noticed that there’s a separate parameter called “on/off transition time” which I updated from the default (30) to 50, but the lights still fade on/off over about 1 second, not 3 or 5. There was no change when I updated “on/off transition time”
I noticed a new issue, which can be reproduced by
- Dim the switch and light to 40%. Wait for them to reach that level.
- Press down on the switch. Both the light and light bar fade to zero, although they use different speeds (this is the first bug). Wait for them to both finish.
- With the light and switch both off, hold the up paddle. The light bar on the switch starts fading up from zero, but the light bumps to 40% and then starts fading up at the same rate as the light bar on the switch, but a constant offset of 40% higher.
- Release the paddle when the light bar gets to around 50 or 60%. The light now quickly bumps back down from where it was (light bar + 40%) to the value of the light bar.
My guess as to what’s happening is that when the bulb gets the turn off command, it turns off, but its “current_level” is still set to whatever it was at when it was on. Then the switch sends a “move” command to increase the level at a certain rate, which it does, starting at its “current_level”.
I think the way to fix this would be to add logic to the switch firmware that, if the switch was off and you hold up on the paddle, before sending a move command, send a move_to_level (level = 0, transition_time = 0) command to bound devices.