Best Practice for Handmade and UI Automations

Configuration
1

I have a bunch of handmade automations that I’ve always kept in automations.yaml

I want to try UI automations and they want to take over automations.yaml. (Currently, if I try anything I get a 500 error.)

It seems like I have two choices for what to do with my handmade automations:

  1. Turn them into automation blocks (e.g. automation kitchen:). I’d rather not junk up my configuration.yaml file, so create a new file called auto.yaml and include that like this?
automation: !include automations.yaml
!include auto.yaml
  1. Give them each a unique ID and keep them in automations.yaml

Suggestions? Or am I missing something?

2

Rename your current automations.yaml file to something like my_manual_automations.yaml Then create a new blank automations.yaml file.

Then add this to your configuration.yaml file:

automation: !include automations.yaml
automation manual: !include my_manual_automations.yaml
2 Likes