Status Quo
- Users that learn about trigger IDs seem to be happy to find out about them and like to use them
- Use of trigger IDs greatly de-clutters the list of automations and allows to keep semantically connected trigger/action combinations clustered in one automation instead of creating many individual but related automations that clutter the list.
- Triggers currently have an autogenerated description that makes it easy to identify them in automations with several triggers.
- The list of triggers is very easily legible, but the actions in a
choose between X actionsare much less legible.
Suggestion: Make Trigger IDs default behaviour in Automations
- use the autogenerated descriptions as default trigger ids
- in the actions section of the automation UI config, default to actions by trigger ID. so there is a separate actions section for each defined trigger, listed by their description/ID
- allow service calls to switch on/off individual triggers as well as whole automations.
This would facilitate intuitive use of structured, clustered automations and potentially reduce the number of individual automations, reducing interface clutter in the automations interface.
