Is it possible to have each automation in its own file? Even a relatively small number of automations (5-6) of reasonably complexity end up creating a massive file that is already unwieldy to edit and navigate. Greatly exacerbated by the fact YAML is super verbose to express even simple logic.
Any feature to split this up?
Oops, looks like there is a solution here.
1 Like
And then when you create a new automation, where does it go?
Is there a way to create a new file as you create a new automation?
If you are creating automations from the UI, they always go into automations.yaml.
Not from the UI.
Thanks, much appreciated.
Still new to HA and trying to make my way around it.
1 Like
No worries! Welcome to the gang! 
Oh wow – one negative to the split – you can no longer edit anything in the UI unless it’s in the automations.yaml file.
I usually like to use a combination of UI and yaml editing depending on what I’m changing. Certain things are easier from the UI certainly so this kind of sucks.
2 Likes
yep, yaml is not a first class citizen anymore. even when we get like tags or labels for automations, it will be just for GUI → while the simplest possible solution of files and folders is apparently nah
2 Likes