Yes you are right, the single and double work. What doesn’t work is the rotate_right and rotate_left, which are used to increase and decrease brightness respectively.
hello
i created a new issue because one device: xiaomi button WXKG01LM
not include all the actions available
1 Like
Next week I will check and fix that!
There is for a lot of people also a problem with the Tuya TS0041, TS0042, TS0043 and TS0044.
I found a solution made by someone, which I adopted a bit.
Is is an idea to add these devices to your blueprint?
I can send you my adapted blueprint ( originally made by someone else!)
Just let me know
KR
Sjors
Great idea, great blueprint. I have currently replaced all my old automations with this blueprint and there is just one problem:
With my Aqara Opple Buttons (WXCJKG13LM) the “hold” function does not seem to work. The same actions with “tripple” are working fine, only “hold” does nothing. Is there something I am missing?
Hi Davizinho,
I think thats not a problem in the Blueprint but a problem with home assistant.
I have the same problem some switches are worrking other switches not.
i have more type’s of WXKG12LM
When i look in Developer Current entity states i see al the actions.
I cant find whats the problem.
1 Like
but i dont think the problem is not the bluepint.
I have WXKG01LM thant supports more clicks. in zigbee2mqtt support triple click and cuadruple click.
but in the blueprint I cant setup this events for the WXKG01LM
if @Remco_van_Geel can add, i will test and confirm
1 Like
Ill do It hopefully end of the week. This week i was to busy…
2 Likes
yes offcource. maybe you can edit my file and add it?
you can test! sorry for the delay!
don;t understand. Hold is in the events for single switches that have to work.
can you test again?
THANKS! i will test!
Great idea! My Hue switches do not work (model 9290023986 en 324131137411) I see it working in Z2M, but the automation is not triggered. Any idea why? I tried both press and press_release
Z2M : 2.1.3-1
Great work Remco, Thanks!
Would it be possible to add the Aqara WXKG15LM switch as a compatible device? It does not appear as a compatible device when setting up an automation with your blueprint. Thank you in advance!!
1 Like
Hi Remco,
I just saw that people had added data to make your work easier. I would really appreciate your help in including these two switches (the Aqara I had mentioned on Saturday).
Paulmann 501.34
on_1 , off_1 , on_2 , off_2 , brightness_move_up_1 , brightness_move_down_1 , brightness_stop_1 , brightness_move_up_2 , brightness_move_down_2 , brightness_stop_2
Aqara WXKG15LM
single_left , single_right , single_both , double_left , double_right , double_both , triple_left , triple_right , triple_both , hold_left , hold_right , hold_both
I really appreciate your assistance with this!!
Cheers, Christoph
1 Like
I added both 
can you confirm and test?
Hi Remco, thank you for this! 
I’m in the process of configuring this blueprint.
What’s the status with the center (on/off) button from the IKEA E1524/E1810 ?
I’m using Version 0.91 Beta from your BP but eventhough the events are changing, the automation doesn’t do anything.
Thanks for this blueprint too!
One question about button hold: I want to configure continuous brighter/darker for the corresponding buttons (IKEA button and light). What is the most efficient way to do this and what action is required?
DId not dig a lot but looks like this blueprint is not very future friendly, it uses legacy action, instead of how Zigbee2Mqtt v2 suggests.
Also i dont think you should make this per device. Just make universal based on action. so people could choose, ANY device and blueprint just act on actions, “left_single”, “left_double” and so on…no matter which device created that action. People of course have to knwo what actions is supported by their device, some supports release, hold and so on, some don’t. SO this would make this even more universal IMO.
1 Like