#Event detected, but not firing
1 messages · Page 1 of 1 (latest)
trigger on entity state or any attribute change should work?
if you have multiple press types you can add that too with the event type
nice
I don't understand what I did wrong the first time. It was using the name with underscores instead of the friendly name. But it definitely autofilled.
It bothers me that I can't reproduce the break.
probably has some random thing set somewhere by accident. it happens and starting again fixes it
For posterity,
The Aqara Light Switch H2 US (4 button, 3 channel) using Thread/Matter only exposes the first three buttons as built in triggers. However, you can get the fourth button to work as a virtual button by creating an automation > new trigger > entity > "Aqara Smart Wall Switch Button (7)" as the entity (it should auto fill), and save the trigger with no further details.
It may be preferable to set up all 4 buttons this way. Otherwise you can't get the LEDs on the buttons to match the state of the lights you want to trigger.
There's no way I can tell to change the state of the bottom button. It's always off.
Otherwise it works quite well.
Confirmed, using the fourth button method (and not the built in triggers), I was able to get the button's LED state to match (inversely) the state of the light. I did have to add a 50 millisecond delay before the if/else statement.
Notably, the state only matches after pressing the button, regardless of previous state. If you use another method (such as HA on your phone) to turn on or off the light, the LED gets out of sync. I should be able to add another automation for that.