From b4a694cb4d9b695d03112d29b19449e15a0d3068 Mon Sep 17 00:00:00 2001 From: David Date: Mon, 30 Jan 2017 15:01:01 +0100 Subject: [PATCH] Update automation-action.markdown (#1833) Added further explanation on how to use conditions in actions, and added to the example. --- source/getting-started/automation-action.markdown | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/source/getting-started/automation-action.markdown b/source/getting-started/automation-action.markdown index dda01b43073..cea9bc896c8 100644 --- a/source/getting-started/automation-action.markdown +++ b/source/getting-started/automation-action.markdown @@ -49,7 +49,7 @@ automation 2: ``` -Conditions can also be part of an action: +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 automation: @@ -59,6 +59,9 @@ automation: entity_id: sensor.mini_despacho to: 'ON' action: + - service: notify.notify + data: + message: Testing conditional actions - condition: or conditions: - condition: template