Creating a new feature request will just get closed as duplicate (as it should).
Pretty sure it is on their radar. It has been mentioned in one of the release streams that they know, but have not found a good way to implement yet (or something along those lines). At least that is how I understood it.
So the way I’ve been getting around this is to have convoluted automations with multiple triggers.
Trigger when where’s motion in the kitchen, trigger when there’s no motion in the kitchen for a while.
Trigger when the garage door is open, trigger when the garage door has been closed for 30 minutes.
In all cases, I set a Trigger ID, then for the action, I choose to turn the lights on or off based on which Trigger ID set off the automation.
It’s effectively combining two or three automations into one when two or three automations would have been fine, but it permenently ties them together, and I can name them whatever I want without having to use Yoda Notation (Garage, the light turn on. Garage, the lights turn off. Kitchen, the lights turn on…) just to alphabetically keep what are effectively two sides to the same automation next to each other, instead of all the "Turn off the"s together followed by all the "Turn on the…"s
I am all in for this feature request. After some time, we can have dozens of automations and it is so difficult to remember which one is doing what. It would be great to have groups or categories created and add members (automation). Those groups would be “belong to” entities for the automations, knowing that one automation could be a member of several groups. Having the ability to also add tags to each automation would be useful for search or filter. Both features together would be great.
Wanted to request this feature also. But saw was already requested for long time ago.
We can select room to get the automations. But if that room has already 20automations, than it would be nice to group them more.
What I did is group them by name, so have the light automations for that room all starting whit a number 2 for example.
Than in the big list it is grouped together already.
But we should be able to group them visually
meaning that in the YAML file we put extra line, for grouping.
than when we have the big list we can select the room and than select also light entities to get only light entities for that room.
On the contrary. Despite what this topic brings us, a naming convention is something one should always use, not only in HA. Naming conventions aren’t a workaround, they are good practice!
+1 on on this important feature. @Grant10k got the description perfect in early 2020.
I love the power of automations. But I dislike that automations to turn something on, followed by another trigger to turn it off, have to be implemented as a pair of automations and these cannot be linked for simplifying the listing in the automation config UI. Also if you want to deactivate this automation pair, you have to search for and deactivate two automations.
Though now for any new automation, I create one automation with both on/off triggers, then a conditional based on which trigger fired. It’s a little convoluted, but less so than having the on/off automations totally separate. And when you disable it, both ‘automation paths’ of course turn off at the same time.
