From dc147644223a4a5cfcfafc0c921c866149e1fbcb Mon Sep 17 00:00:00 2001 From: Tobias Haase Date: Mon, 4 Nov 2019 17:47:57 +0100 Subject: [PATCH 1/2] Improve scene.create service --- source/_integrations/scene.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/source/_integrations/scene.markdown b/source/_integrations/scene.markdown index 0e52c743523c..0487451dff69 100644 --- a/source/_integrations/scene.markdown +++ b/source/_integrations/scene.markdown @@ -95,6 +95,8 @@ Create a new scene without having to configure it by calling the `scene.create` You need to pass a `scene_id` in lowercase and with underscores instead of spaces. You also need to specify the entities in the same format as when configuring the scene. +If the scene was previously created by `scene.create`, it will be overwritten. If the scene was created by YAML, an error will occur. + ```yaml # Example automation automation: From 0c49edab8d0fa9b897024ebbd9f69de9fcf6ddb8 Mon Sep 17 00:00:00 2001 From: Santobert Date: Mon, 4 Nov 2019 18:55:14 +0100 Subject: [PATCH 2/2] Update scene.markdown --- source/_integrations/scene.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/scene.markdown b/source/_integrations/scene.markdown index 0487451dff69..feeb97158ae2 100644 --- a/source/_integrations/scene.markdown +++ b/source/_integrations/scene.markdown @@ -95,7 +95,7 @@ Create a new scene without having to configure it by calling the `scene.create` You need to pass a `scene_id` in lowercase and with underscores instead of spaces. You also need to specify the entities in the same format as when configuring the scene. -If the scene was previously created by `scene.create`, it will be overwritten. If the scene was created by YAML, an error will occur. +If the scene was previously created by `scene.create`, it will be overwritten. If the scene was created by YAML, nothing happens but a warning in your log files. ```yaml # Example automation