automation
and automation old
in the same time
Additional comment and example to explain we can use the both sections in the same time.
This commit is contained in:
parent
4144fb0974
commit
f6b1e6aa8c
1 changed files with 8 additions and 0 deletions
|
@ -65,6 +65,14 @@ automation old:
|
||||||
platform: ...
|
platform: ...
|
||||||
```
|
```
|
||||||
|
|
||||||
|
You can use the `automation:` and `automation old:` sections in the same time to keep yout manual designed automations and use the editor for next ones:
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
automation: !include automations.yaml
|
||||||
|
automation old: !include_dir_merge_list automations
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
## {% linkable_title Migrating your automations to `automations.yaml` %}
|
## {% linkable_title Migrating your automations to `automations.yaml` %}
|
||||||
|
|
||||||
If you want to migrate your old automations to use the editor, you'll have to copy them to `automations.yaml`. Make sure that `automations.yaml` remains a list! For each automation that you copy over you'll have to add an `id`. This can be any string as long as it's unique.
|
If you want to migrate your old automations to use the editor, you'll have to copy them to `automations.yaml`. Make sure that `automations.yaml` remains a list! For each automation that you copy over you'll have to add an `id`. This can be any string as long as it's unique.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue