I would like to have smarter conditions that are associated with the context and easily authored using the UI:
A) I could check whether the automation was triggered by Lovelace UI, hardwired device, or script/automation.
B) I could check if the automation was triggered by a particular user.
C) I could supply a different (or the same) automation entity and if the context.parent_id is associated with that other automation, you could ignore or accept the trigger. I don’t think this can be done in templates, but I assume that internally hass could look up the automation entity associated with a parent context ID.
Other Example Use Cases:
- This would allow you to create groups or lists of entities as triggers, then propagate some state change from one of those entities to the other entities in the list, but ignore state changes that were caused by this automation.
- You want to create an automation to respond to a state change or event, but only when it’s caused by a particular automation.