From 660d2c297dae10624834e25e82e65a495cd341c3 Mon Sep 17 00:00:00 2001 From: Igor Shults Date: Mon, 13 Feb 2017 05:23:29 -0600 Subject: [PATCH] Remove blurb about being able to use conditions (#1664) It doesn't seem like you can use conditions in actions (anymore?), so remove the snippet to avoid confusion. --- source/getting-started/automation-action.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/getting-started/automation-action.markdown b/source/getting-started/automation-action.markdown index cea9bc896c8..485e3514f42 100644 --- a/source/getting-started/automation-action.markdown +++ b/source/getting-started/automation-action.markdown @@ -48,7 +48,6 @@ automation 2: message: Oh wow you really missed something great. ``` - Conditions can also be part of an action. You can combine multiple service calls and conditions in a single action, and they will be processed in the order you put them in. If the result of a condition is false, the action will stop there so any service calls after that condition will not be executed. ```yaml @@ -70,4 +69,4 @@ automation: value_template: '{% raw %}{{ states.sensor.sensorluz_7_0.state < 10 }}{% endraw %}' - service: scene.turn_on entity_id: scene.DespiertaDespacho -``` +``` \ No newline at end of file