True, but if you have several different blueprints and 30+ devices using these blueprints via 30+ automations, it will take time to go through all of them and update the mqtt topic for the correct device that triggers them, then locate the devices and actually test if they still work and you did it all correctly.
Had the Same issue…for me worked to activate “Homeassistent legacy Sensors”. After activating it in z2m it appears as action entity…maybe this helps someone nowadays🥳
6 Likes
Worked for me, thanks a lot!
thanks for sharing the gist! copied in HAOS and using successfully.
Using event entities on Z2M 2.0.0
1 Like
This is a good short term workaround, but I think isn’t the long term solution.
1 Like
Thank you. This worked for me too. Life saver as my wife kept asking “when are you going to fix the lights?” As this is a temporary fix, will the original blueprint have to be updated or will we have to migrate to a new one (if/when available)?
I’m using your Blueprint, just copied and pasted it into a new YAML file and everything is working perfectly with the legacy option disabled. Thank you! It goes way over my head and I’m not sure what the best practice is, but all I know is it’s working.
Is this something you can just takeover (the Blueprint)? So I don’t have to have this Blueprint too and the one I copied from your post earlier in the thread. If you fork it to a new GitHub we could all use that and get updates directly from you? You seem to be really responsive and definitely know your stuff. Just a suggestion.
Still though, massive thank you.
Edit: Just want to add a quick question. I’ve noticed the holding of the up/down buttons sometimes incurs a delay. It can be quite random, but I’ve noticed it usually happening on the 3 or 4 command. Is that an implementation thing, or just how it is? Can get pretty annoying when it stops and you’re not 100% sure it’s at full brightness.
Using the event version, all works fine except repeat on hold. When I hold, it triggers the action only once - despite the remote’s LED blinking repeatedly:
action: light.turn_on
metadata: {}
data:
brightness_step_pct: 5
target:
device_id:
- 34257c9a9f25fdb34bd95a5bea22a2f7
- 0ddc3eab40c1a256c97016db20a59234
Am I missing something or is there still a bug in the event version? Should I use the mqtt topic instead (not really wanting to go down the legacy route)?
I have the same problem, but I’m pretty sure the original version from @JetSerge didn’t work correctly on Hold, either. I haven’t played with it enough to try and fix it.
Best is to directly listen on a MQTT message used by the dimmer via Z2M and extract data from payload_json.action variable. It works correctly on my side.
Want to thank you for the updated BP, it’s working with my older model dimmer Philips 324131092621 just fine.
1 Like
Worked for me as well, thanks! 
Will await the update from JetSerge on the blueprint meanwhile.
how do you solve the double and tripple press with z2m v2.0 because the counter is not available anymore?
i’m user now 14 functions and with v2.0 i can only ise the press and hold so 8 functions.
i see there is a release function how does this work? the first press is always triggerd or not?
Hi, I added your blueprint, but I have no Zigbee2mqtt Hue Dimmer event entities available, am I missing something?
