done, hope this will work! 
ready to be tested!
1 Like
I really commend the idea but I do wonder if the Philips group is really appropriate. I have a bunch of Hue Dimmer V2 and to me, right and left does not make sense for them…
Possibly more intuitive to have various incarnations and name them after the Product name or at least add that to the model number? I know Z2M also uses the number and I keep wondering there, too…
You might want to add the below as a separate condition to ensure that unintentional triggers don’t cause the automation to run:
{{ trigger.from_state.state not in ['unknown', 'unavailable'] }}
Obviously, feel free to change state.state to state.attributes if it’s more suitable for this blueprint
1 Like
thanks ! will try that!
Implemented and tested! thank you very much!!
1 Like
Hey Remco, this is exactly the blueprint I’m looking for to automate lights with my Opple and Aqara WXKG07LM switches, moving away from the legacy action triggers. Thank you for creating this.
I’m on version HA 2025.1.2 and Zigbee2MQTT 2.0.0. ‘Home Assistant legacy action sensors’ is disabled. If I look at MQTT info for this switch the button presses are auto discovered.
automation_type: trigger
device:
hw_version: 20
identifiers:
- zigbee2mqtt_0x00158d000593dc28
manufacturer: Aqara
model: Wireless remote switch D1 (double rocker)
model_id: WXKG07LM
sw_version: 3000-0001
via_device: zigbee2mqtt_bridge_0x00124b00258cc1e4
name: Switch double livingroom
origin:
support_url: https://www.zigbee2mqtt.io
sw_version: 2.0.0
name: Zigbee2MQTT
payload: single_left
subtype: single_left
topic: zigbee2mqtt/Switch double livingroom/action
type: action
I must be overlooking something very obvious, since everybody is able to use this blueprint in their automations. When I create a new automation using this blueprint, I cannot select anything in the drop down box ‘Switch to use’ (No matching entities found).
Does this not yet work through the GUI? Should I setup this up in YAML? If so, can someone provide an example.
What am I missing here? Thanks in advance!
I think I am also missing something - Z2M been working for ages. Entered the required Legacy actions sensors - But get “No matching entities found” when looking for switch’s. Its going to be obvious I know but I can’t see it at the moment.
He Remco! Lekker aan de home assistant? 
Gr Sicco
1 Like
Not finding any entities, am I doing something wrong or is there a bug?
HA updated, z2m 2.0 in use and three compatible ikea switches exist in my network and they report button presses when looking at z2m control interface.
for the ones who don’t see switches. i have done the following:
- update zigbee2mqtt to the latest version
- reimport latest version of the blueprint
- enable Home Assistant experimental event entities in zigbee2mqtt
- disable the legacy support in zigbee2mqtt
- restart home assistant and zigbee2mqtt
please report if this is the solution or not.
Yes, this did the trick. It now sees the event-based entities. Thanks for the support. Keep up the great work!
Hi,
It looks like condition for “toggle” event is missing. I have Ikea E1524 and got other buttons to work, but the middle toggle button does not. It reports events “toggle” and “toggle_hold”.
The blueprint has building blocks for “toggle” and “toggle_hold” but after taking over the automation and looked at the yaml code, “toggle” had to be manually inserted and action for “toggle_hold” was also missing.
Good job working on the blueprint, I really appreciate. I’m just happy to report a bug if it helps.
Edit: Also “toggle_hold” seems to activate option for “hold”. But this works after moving my actions under “hold” option.
ikea and the single buttons uses hold.
therefore i have to delete on (choosed to delete it under ikea)
so open the single and choose the hold from that to test. will you do that?