From b06feb63e4e5946b3ad3dd1ca767925137ac394d Mon Sep 17 00:00:00 2001 From: jonwaland <33437424+jonwaland@users.noreply.github.com> Date: Mon, 8 Mar 2021 11:54:26 +1100 Subject: [PATCH 1/6] Update using_blueprints.markdown as per https://github.com/home-assistant/home-assistant.io/issues/16623 --- source/_docs/automation/using_blueprints.markdown | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/source/_docs/automation/using_blueprints.markdown b/source/_docs/automation/using_blueprints.markdown index a17617bacd12..8db062be2106 100644 --- a/source/_docs/automation/using_blueprints.markdown +++ b/source/_docs/automation/using_blueprints.markdown @@ -44,3 +44,7 @@ The Home Assistant Community forums have a specific tag for blueprints. This tag [Visit the Home Assistant forums][blueprint-forums] [blueprint-forums]: /get-blueprints + +## 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 ed64c82b8fa7c42ca74cb8961e4977d8da4c4b25 Mon Sep 17 00:00:00 2001 From: jonwaland <33437424+jonwaland@users.noreply.github.com> Date: Tue, 9 Mar 2021 11:14:15 +1100 Subject: [PATCH 2/6] Update using_blueprints.markdown --- source/_docs/automation/using_blueprints.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/_docs/automation/using_blueprints.markdown b/source/_docs/automation/using_blueprints.markdown index 8db062be2106..48de45e959c1 100644 --- a/source/_docs/automation/using_blueprints.markdown +++ b/source/_docs/automation/using_blueprints.markdown @@ -45,6 +45,6 @@ The Home Assistant Community forums have a specific tag for blueprints. This tag [blueprint-forums]: /get-blueprints -## 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 blueprints, 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 a289b5552461af5449f662c17215a18725f5c35e Mon Sep 17 00:00:00 2001 From: jonwaland <33437424+jonwaland@users.noreply.github.com> Date: Tue, 16 Mar 2021 12:13:06 +1100 Subject: [PATCH 3/6] Update using_blueprints.markdown --- source/_docs/automation/using_blueprints.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/automation/using_blueprints.markdown b/source/_docs/automation/using_blueprints.markdown index 48de45e959c1..7058f193eaec 100644 --- a/source/_docs/automation/using_blueprints.markdown +++ b/source/_docs/automation/using_blueprints.markdown @@ -47,4 +47,4 @@ The Home Assistant Community forums have a specific tag for blueprints. This tag ## Troubleshooting missing automations -Some users may find that when creating automations using the blueprints, 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 blueprints, 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 606fa4c558332e1684da7a0aa42e74fbc28f6863 Mon Sep 17 00:00:00 2001 From: jonwaland <33437424+jonwaland@users.noreply.github.com> Date: Fri, 19 Mar 2021 12:10:19 +1100 Subject: [PATCH 4/6] Update using_blueprints.markdown --- source/_docs/automation/using_blueprints.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/automation/using_blueprints.markdown b/source/_docs/automation/using_blueprints.markdown index 7058f193eaec..80a5b7a5dd8d 100644 --- a/source/_docs/automation/using_blueprints.markdown +++ b/source/_docs/automation/using_blueprints.markdown @@ -47,4 +47,4 @@ The Home Assistant Community forums have a specific tag for blueprints. This tag ## Troubleshooting missing automations -When creating automations using blueprints, 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 creating automations using blueprints, 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` make sure you have `automation: !include automations.yaml` in `configuration.yaml`. From 483f205b851974ec0288fc8b5f28b1f7867507d0 Mon Sep 17 00:00:00 2001 From: jonwaland <33437424+jonwaland@users.noreply.github.com> Date: Fri, 19 Mar 2021 12:12:22 +1100 Subject: [PATCH 5/6] Update using_blueprints.markdown --- source/_docs/automation/using_blueprints.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/automation/using_blueprints.markdown b/source/_docs/automation/using_blueprints.markdown index 80a5b7a5dd8d..5b5b0fd9510c 100644 --- a/source/_docs/automation/using_blueprints.markdown +++ b/source/_docs/automation/using_blueprints.markdown @@ -47,4 +47,4 @@ The Home Assistant Community forums have a specific tag for blueprints. This tag ## Troubleshooting missing automations -When creating automations using blueprints, 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` make sure you have `automation: !include automations.yaml` in `configuration.yaml`. +When creating automations using blueprints, 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`; make sure you have `automation: !include automations.yaml` in `configuration.yaml`. From b8d2ada421721f61cd23295d8f7558f7740ab505 Mon Sep 17 00:00:00 2001 From: Paulus Schoutsen Date: Thu, 18 Mar 2021 20:31:03 -0700 Subject: [PATCH 6/6] Apply suggestions from code review --- source/_docs/automation/using_blueprints.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/automation/using_blueprints.markdown b/source/_docs/automation/using_blueprints.markdown index 5b5b0fd9510c..61db6a92a1b3 100644 --- a/source/_docs/automation/using_blueprints.markdown +++ b/source/_docs/automation/using_blueprints.markdown @@ -47,4 +47,4 @@ The Home Assistant Community forums have a specific tag for blueprints. This tag ## Troubleshooting missing automations -When creating automations using blueprints, 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`; make sure you have `automation: !include automations.yaml` in `configuration.yaml`. +When you're creating automations using blueprints 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`.