same ) can u try pls
no luckā¦ still nothing working 
can you please share what have you done? please
can u provide z2m logs here when you press a key?
Iām using version: 1.18.1-1
Aqara WXKG12LM.
MQTT explorer shows the messages being sent.
I have uninstalled the bleuprintā¦ created a manual automation and it worksā¦ not sure why the blueprint does not workā¦
It didnt work. I found someone with a similar issue saying that there was no event trigger and got it resolved this wayā¦but its too advanced for me to understandā¦would really appreciate if you could guide me through the process.
Iām also not too sure what decouple does for a switchā¦
Hi there.
I have one QBKG22LM and one QBKG21LM. I also have one QBKG25LM (three-gang) but that one is known not to work with Z2M.
The issue manifests when I set homeassistant_legacy_triggers: false and try to use the action attribute like this:
- conditions:
- condition: state
entity_id: sensor.zigbee_button_smallroom_action
state: double
attribute: action
in Z2M config. The event generated then looks like this:
{
"event_type": "state_changed",
"data": {
"entity_id": "sensor.zigbee_switch_kitchen_action",
"old_state": {
"entity_id": "sensor.zigbee_switch_kitchen_action",
"state": "release_right",
"attributes": {
"action": "release_right",
"button_right": "release",
"linkquality": 99,
"operation_mode": "decoupled",
"operation_mode_left": "decoupled",
"operation_mode_right": "decoupled",
"state_left": "ON",
"state_right": "ON",
"friendly_name": "zigbee.switch.kitchen action",
"icon": "mdi:gesture-double-tap"
},
"last_changed": "2021-04-29T14:09:00.562730+00:00",
"last_updated": "2021-04-29T14:09:00.562730+00:00",
"context": {
"id": "cbec526666baa680ce0a95e81ed7b034",
"parent_id": null,
"user_id": null
}
},
"new_state": {
"entity_id": "sensor.zigbee_switch_kitchen_action",
"state": "release_right",
"attributes": {
"action": "",
"linkquality": 99,
"operation_mode": "decoupled",
"operation_mode_left": "decoupled",
"operation_mode_right": "decoupled",
"state_left": "ON",
"state_right": "ON",
"friendly_name": "zigbee.switch.kitchen action",
"icon": "mdi:gesture-double-tap"
},
"last_changed": "2021-04-29T14:09:00.562730+00:00",
"last_updated": "2021-04-29T14:09:00.572998+00:00",
"context": {
"id": "804978c97cc9e29542033e55b3d7da04",
"parent_id": null,
"user_id": null
}
}
},
"origin": "LOCAL",
"time_fired": "2021-04-29T14:09:00.572998+00:00",
"context": {
"id": "804978c97cc9e29542033e55b3d7da04",
"parent_id": null,
"user_id": null
}
}
Hello
when I try to import the schema to HA I get this message:
while scanning a simple key in āā, line 242, column 1: ^ could not find expected ā:ā in āā, line 243, column 1: < p> <img src = "https: // community-a ā¦ ^
can you help and tell what went wrong? 
mirek
Same here. Looks like it might be including the image HTML code after the code block, and deciding that this HTML code is not valid blueprint code.
The blueprint itself is fine. If I copy / paste the code block to a blueprint file myself, then I can use it.
thanks for the help
Blueprint updated!
Changelist:
- Now it works with any value of
homeassistant_legacy_entity_attributesof z2m. - Changed the mode to
parallelto get rid of ignoring some actions.
Iām having an issue where I single click the button and Home Assistant detects me pressing it 3 times.
What could be causing this?
1 Like
Hi, Iām having the same problem. Have you managed to fix it?
This is great! Thank you.
I am finding that my ātrippleā click isnāt working.
Tripple is spelled wrong (should be ātripleā with one p) on the blueprint front endā¦ could the typo be extending into the payload too?
Ah yep, it is. In the blueprint I was able to correct the typo of ātrippleā and the command works OK now.
Hello,
I find this confusing.
The first sentence indicates that legacy triggers are required, so to be left enabled.
The second sentence (set legacy to false), means according to the site this links to:
legacy: Set to false to disable the legacy integration (highly recommended), will change structure of the published payload (default true). The value must be true or false.
Nevertheless, independently of my confusion, the blueprint works with my mini switch on first try 
homeassistant_legacy_triggers is not the same legacy in device options. About triggers see Z2M Responding to button clicks. By default homeassistant_legacy_triggers: true and if you havenāt touched this - you donāt need to do anything.
legacy: false in device section removes the deprecated click sensor (we use action sensor instead) and itās not required, just a recommendation.