It appears those variabkles are not populated, meaning there was no trigger, further meaning you probably clicked the run instead of actually triggering this with the button to get a real trigger.
It looks that i have a similar problem with 86sw2 and sw1
Looking at the blueprint, and previous version, this is the “pressed” part that is not working anymore. If i used the old blueprint without pressed detection, it works but triggers the event two times (pressed and release).
pressed: “{{ trigger.event.data.args.value }}”
Update : I fallback to 2024.7.4 and it works again. Initially, i was still in May release as i didn t do any upgrade during summer.
blueprint:
name: ZHA - Aqara Wireless Remote Switch (Double Rocker 86sw2)
description: Automate your Xiaomi Aqara Wireless Remote Switch (Double Rocker) (lumi.sensor_86sw2 Version) using ZHA events.
domain: automation
input:
aqara_mini_switch:
name: Select the Aqara Wireless Remote Switch (Double Rocker)
description: Aqara Wireless Remote Switch (Double Rocker)
selector:
device:
integration: zha
manufacturer: LUMI
entity:
domain: sensor
device_class: battery
button_press_left:
name: Single Press Left
description: Action to run on single press
default: []
selector:
action:
button_press_right:
name: Single Press Right
description: Action to run on single press
default: []
selector:
action:
button_press_both:
name: Single Press Both Buttons
description: Action to run on single presses
default: []
selector:
action:
mode: restart
max_exceeded: silent
trigger:
- platform: event
event_type: zha_event
event_data:
device_id: !input aqara_mini_switch
action:
- variables:
command: "{{ trigger.event.data.endpoint_id }}"
pressed: "{{ trigger.event.data.args.value }}"
- choose:
- conditions:
- "{{ command == 1 }}"
- "{{ pressed == 'Bool.true' }}"
sequence: !input button_press_left
- conditions:
- "{{ command == 2 }}"
- "{{ pressed == 'Bool.true' }}"
sequence: !input button_press_right
- conditions:
- "{{ command == 3 }}"
- "{{ pressed == 'Bool.true' }}"
sequence: !input button_press_both
OK, so I think I finally found the blueprint we are discussing here It was written 4 years ago so it probably has problems. I would look thru the thread and see if someone has updated it and bring your concerns there. I don’t know if the author is still supporting it or if someone else is, but that is your best bet a this time. I don’t have any desire to work on is because I don’t have the hardware to test anything, sadly.
Yes this the one for me. What do not work is the pressed part and specifically this variable trigger.event.data.args.value.
There is one version which do not use the variable however for this switch, it can t work as it trigger the action two times (press and release). Then it is far above my skills in HA. I just tried to determine the problem.