Checking on assumption of splitting up Automation.yaml

[Tyfoon]

The amount of automations is now growing fast. With everything in one Automation.yaml it’s getting a bit to large. I don’t prefer to split it up per automation (so a file for each automation) but in groups that belong together (for example all motion lights automations).

I personally find the documentation about this a bit tough to interpret. So double checking. Hoping someone can confirm below is correct in the context of above.

So my understanding is that I can just split up my Automation.yaml in multiple parts (for example one with all my 6 light/motion automations and one with my presence/away automations etc.) without changing any formatting. Put them in a directory (let’s call it /automations) and then use automation: !include include_dir_merge_list automations in my configuration.yaml

[sebk-666 (Sebastian)]

Yep, that should work.
I explained it with a bit more detail here:

YAML formatting explanation for newbie

To be a little more specific: include_dir_list will basically take every file in the specified directory, add a single “-” at the beginning and indent everything by 2 spaces. Every file’s contents become one entry in a list: - file 1 contents - file 2 contents - file 3 contents If you have a file with two “items”: item 1 item 2 You will get: - item 1 item 2 - file 2 contents - file 3 contents which is not a valid syntax - hence you can only have one item per file. include_dir_merge_lis…

Sebastian

[rpitera (Robert Pitera)]

And you did a great job of it as well. Just wanted to thank you.

[Tyfoon]

Thanks! All working fine!

Just for completeness it’s below (I made a typo in mine above):

automation: !include_dir_merge_list automation/