From 157117b2236dd1eff2bb552030d75d195378e2a5 Mon Sep 17 00:00:00 2001 From: jonwaland <33437424+jonwaland@users.noreply.github.com> Date: Mon, 8 Mar 2021 11:55:03 +1100 Subject: [PATCH 1/4] Update editor.markdown as per https://github.com/home-assistant/home-assistant.io/issues/16624 --- source/_docs/automation/editor.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_docs/automation/editor.markdown b/source/_docs/automation/editor.markdown index a4f8cab57a04..19d39206f3c1 100644 --- a/source/_docs/automation/editor.markdown +++ b/source/_docs/automation/editor.markdown @@ -31,3 +31,7 @@ message: Sensor value greater than 10 Automation created or edited via the user interface, are activated immediately after save the automation. + +## Split Config + +When creating automations using the GUI, they are written to `automations.yaml` even if you have a [split config](/docs/configuration/splitting_configuration/#example-combine-include_dir_merge_list-with-automationsyaml). Make sure you are correctly including the base `automations.yaml` file. From f603194788e42e6a749b8d3126773e6f2f04babf Mon Sep 17 00:00:00 2001 From: jonwaland <33437424+jonwaland@users.noreply.github.com> Date: Tue, 9 Mar 2021 11:22:41 +1100 Subject: [PATCH 2/4] Update editor.markdown --- source/_docs/automation/editor.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/automation/editor.markdown b/source/_docs/automation/editor.markdown index 19d39206f3c1..366be61649e1 100644 --- a/source/_docs/automation/editor.markdown +++ b/source/_docs/automation/editor.markdown @@ -32,6 +32,6 @@ message: Sensor value greater than 10 Automation created or edited via the user interface, are activated immediately after save the automation. -## Split Config +## Troubleshooting missing automations -When creating automations using the GUI, they are written to `automations.yaml` even if you have a [split config](/docs/configuration/splitting_configuration/#example-combine-include_dir_merge_list-with-automationsyaml). Make sure you are correctly including the base `automations.yaml` file. +Some users may find that when creating automations using the GUI, they appear to be created but never show in the automations page. When creating automations using the GUI, they are written to `automations.yaml` even if you have a [split configuration](/docs/configuration/splitting_configuration/#example-combine-include_dir_merge_list-with-automationsyaml). Make sure you are correctly including the base `automations.yaml` file to ensure they are loaded. From 085ab1222b5e80aabbf31fb845467b1a50b44b91 Mon Sep 17 00:00:00 2001 From: jonwaland <33437424+jonwaland@users.noreply.github.com> Date: Tue, 16 Mar 2021 12:10:53 +1100 Subject: [PATCH 3/4] Update editor.markdown --- source/_docs/automation/editor.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/automation/editor.markdown b/source/_docs/automation/editor.markdown index 366be61649e1..69c5786eac13 100644 --- a/source/_docs/automation/editor.markdown +++ b/source/_docs/automation/editor.markdown @@ -34,4 +34,4 @@ after save the automation. ## Troubleshooting missing automations -Some users may find that when creating automations using the GUI, they appear to be created but never show in the automations page. When creating automations using the GUI, they are written to `automations.yaml` even if you have a [split configuration](/docs/configuration/splitting_configuration/#example-combine-include_dir_merge_list-with-automationsyaml). Make sure you are correctly including the base `automations.yaml` file to ensure they are loaded. +When creating automations using the GUI, you may find they appear to be created but never show in the automations page. When creating automations using the GUI, they are written to `automations.yaml` even if you have a [split configuration](/docs/configuration/splitting_configuration/#example-combine-include_dir_merge_list-with-automationsyaml). Make sure you are correctly including the base `automations.yaml` file to ensure they are loaded. From 0ec60a8239d0e846588dad2cb04fcd272877a5d7 Mon Sep 17 00:00:00 2001 From: jonwaland <33437424+jonwaland@users.noreply.github.com> Date: Fri, 19 Mar 2021 16:48:43 +1100 Subject: [PATCH 4/4] Update editor.markdown --- source/_docs/automation/editor.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/automation/editor.markdown b/source/_docs/automation/editor.markdown index 69c5786eac13..e19c4423f092 100644 --- a/source/_docs/automation/editor.markdown +++ b/source/_docs/automation/editor.markdown @@ -34,4 +34,4 @@ after save the automation. ## Troubleshooting missing automations -When creating automations using the GUI, you may find they appear to be created but never show in the automations page. When creating automations using the GUI, they are written to `automations.yaml` even if you have a [split configuration](/docs/configuration/splitting_configuration/#example-combine-include_dir_merge_list-with-automationsyaml). Make sure you are correctly including the base `automations.yaml` file to ensure they are loaded. +When you're creating automations using the GUI and they don't appear in the UI, make sure that you add back `automation: !include automations.yaml` from the default configuration to your `configuration.yaml`.