No. There already is a sorting method similar to tags, you can add them in the title and filter.
This is not about sorting them once in a while when needed, we’re talking about organizing automations in a tree structure for immediate sorting and visualization of the whole thing.
Tags could be a lovely added feature but it’s not relevant to this FR.
So, just so people know, I’ve consolidated many many many grouping UI automation feature requests into 1 FR. This thread happened to be the 1st thread, so everything got pushed into this. You’ll notice that the votes jumped to a staggering 344 at the time of this post.
12 Likes
I think that a folder structure would be a good idea, but tags as an addition would be excellent. There are some things that merit being considered in multiple different ways, like all of the automations to do with lights, and all of the automations to do with the kitchen, etc.
This feature will come in one of the next releases. It was announced at the last release party on Youtube.
2 Likes
Awesome! Looking forward to it…
I think you are incorrect there… Just saying…
I think you are confused by the possible addition of light groups and such to the UI (which is unrelated to this feature request).
2 Likes
That’s so sad… 
Seems I have interpreted the buzzword “groups in UI” differently. Since you were referring not to have this show up at month of what the heck I assumed that the (besides Matter) most requested feature was meant…
The references in the Live stream were about adding features that allow configuring the groups integration in the UI. Currently it can only be configured via yaml. These new tools will pave the way towards adding light groups, cover groups, media_player groups, etc into the UI.
This doesn’t mean this feature request is being ignored. It is not. It’s just not coming next month. Currently, there is no timeframe for this FR, however it has been talked about. As always, be patient.
3 Likes
Is there a specific reason why this hasn’t been implemented? Or are we just waiting on someone to actually make it and pr?
We are just waiting for someone to add it. Keep in mind, it needs to conform with the current standards in the UI and the backend. So if you want to do the work, you’d just need to start a discussion with in the discussion area on the frontend.
Please include grouping for automations, scenes, scripts, and helpers.
Since it seems most entities can be added to an area, perhaps adding automations, and scripts to areas (like scenes and helpers) is intuitive, and shouldn’t be difficult to implement.
We could create areas that only contain / group automations and scripts as needed.
+1 on this! I’m migrating my automations from node red to the UI editor for the ease of use on mobile and this came as a problem. This would be great to better organize my automations!
1 Like
Adding automations to areas is already helpful, in order to do this it would be nice if I can filter the automations for area = empty, by that I could ensure that all automations have been mapped
Yeah, agree kinda. As a workaround: Go to Devices & Services → Entities, search for automation. (yes, with the . dot) and sort the table by area, now you’ll see all automations without an area neatly grouped together.
2 Likes
Would be nice to expose that when creating/editing an automation. Right now you need to get to the pop-up to set the Area.
1 Like
I’d like to be able to hide disabled automations. Often I disable an automation because I have moved the automation to Nodered, so I don’t need to see it listed under settings > automations
How about using tags, but giving the automation list a “Group by X” option so it behaves like folders?
You get the flexibility of tags but with quick finding of automations without the extra step people don’t like (if the preference was remembered).
You could set your view to “Group by area” if that’s the way you work, and home assistant would remember this. Maybe even if you wanted nesting you could set multiple tags to group on?
1 Like