I too ran into an issue with my ZEN72 700 series dimmer on the hold actions. Listening to the event in developer tools I noticed that the raw value (value_raw ) did not match the blueprint on KeyReleased and KeyHeldDown . I corrected the values in the blueprint (KeyReleased from 2 to 1 ; KeyHeldDown from 1 to 2 ), but that broke everything. Instead I removed the or value_raw == <NUMBER> from all the conditions and now everything is working.
Thank you, I had to reverse these as well for it to start working with the dimming on hold
Thank you. I did make the changes you suggested. Now the hold action only “kind of” works. There is a huge lag. When I keep the button pressed, I see one step increase, but the second step takes forever. And what’s more is that even when I let the button go, it keeps going in the increase/decrease direction. I am setting the delay for the loop to 10 millisecond. So, I would have expected a much faster response.
Set the Automation mode to “Restart” and try it. This made it much better. It still kind of changes in steps which frankly is a bit annoying and slow for me. Not sure I’m going to keep the Zen 72 for a smart light config.
So, this blueprint is great. I had written a much crappier version of it to get done what I wanted and have since moved all my stuff over to this one.
Now, I don’t have just Zen72’s, I also have 71’s, 73’s and 76’s, in smart light mode (no relay control, no local programming, scene control on) with Hue lights on the circuit. This integration works with all of them as far as I have tested, as long as this modification is made:
Thanks for the shout-out! I had a unifying BP in the works that would cover all ZEN switches/remotes, but between work, life, and the ability to more easily edit BPs released in 2024.7, that project was relegated to the back burner.
For anyone else wondering, the following switches should follow the same schema: