Clarification on automations with the new editor feature vs. using older methods?

Just wanted to get a clarification from someone who knows for sure; assuming I want to upgrade to 0.45, but not use the new automation editor and currently have my automations in separate yaml files included using the following:

automation: !include_dir_merge_list automations

are there any changes I have to make before/after upgrading to continue to use my automations as in the previous versions?

I think it’s great that HA has an editor like this, especially for newer users, but I will never use it unless it supports separate yaml files; which I am guessing will be never due to the way it is constructed. That’s fine and I still applaud the core devs for reaching out to newer users but I just want to make sure I am set up correctly to proceed.

Thanks!

You can use old system, I’m using it right now with 0.45 version…
I think like you, I prefer to have separate yaml files. but is a great job

1 Like

Thanks!

So did you have to change anything at all in your includes or does it just remain the same? I’m just unclear if the

automation old:

is only required if you want to run the editor (for new, separate automations) AND use your old automations at the same time.

Don’t touch anything… it works for me…
automation old: if is you make any change to the new version

1 Like

Awesome - I just wanted to verify that before I updated; I really appreciate your quick reply!

1 Like

No problem… think about Telegram notifications, if you use them

Nah, I’m a Pushbullet guy - but thanks for the heads up.

1 Like