A “choose” block with each of those triggers, and the set of actions to do.
This works fine but is kind of tedious, both to create and to maintain. Is there a way to consolidate this so I’m just giving a list of trigger conditions and their actions?
I know I could get the same kind of simplicity by simply making a bunch of different automations rather than trying to group the triggers and actions like this, but they’re related in some way (either something like “all actions that are triggered by this five-button remote” or the opposite, “the different ways to control this window blind”).
I’m probably missing something obvious… so I thought I should ask!
The specific thing you’re asking about doesn’t exist.
If what you care about is grouping together related trigger/action pairs, make individual automations as you consider above and use labels to group them.
Would it be possible to create a blueprint that could implement this pattern? After all these years I’m still a little hazy on blueprints as a concept.
Integrations will be able to create custom triggers. E.g. event entities with triggers based off the event type and time/date
Should drastically reduce the need for conditions and should also simplify automations. It’ll be a game changer and we will rely on state trigger less.
