I just don't get it, WHY is this the behaviour?
And why is not_to not supported in the webui?
#Why does `trigger: state` with a `attribute: event_type` not trigger when triggered a second time?
lean perch
wet shore
Because it doesn't change
State triggers trigger when a state changes
The UI is a subset of what's available in YAML
lean perch
yeah but if i want to not use device IDs, this is the way, right? use events? but they are soo ... not convenient unlike device triggers?
wet shore
you're right, they're not very convenient
You have to use a trigger and a condition. Not hard, but not straightforward
lilac crane
It's possible that in a future home assistant release, the new work (currently in Labs) for adding entity-specific triggers will make this easier to handle.
For example, it might be possible for them to add separate triggers for "Single press", "Double press", "Long press", etc. to the event entities for matter buttons which all work as you expect.
lean perch
It's possible that in a future home assistant release, the new work (currently i...
that would be great
today, if I add say all buttons for a room into a state trigger, then filter on if state x for button y it works but if some other button event is triggered it also checks state x for button y and because it was the last thing that button did, then this check passes again
wet shore
Yes, these entities have issues
lean perch
i wonder if a triggered by could be extended to be for the inbound event, instead of the ids we manually assign, so i'd be able to triggered by button x because it got event single, right this moment
lilac crane
you can already do that, but you have to use templates to look at the trigger variable in your automation.
lean perch
i am aware of that, but that means i need to do that, instead of being able to use the user friendly frontend :/