From 8dac0b232c1b3992e5d7dbbecaad845390c3ac4b Mon Sep 17 00:00:00 2001 From: akasma74 Date: Mon, 13 Jan 2020 10:13:22 +0000 Subject: [PATCH] continue_on_timeout clarification (#11723) It was a bit unclear what happens if one omits continue_on_timeout (i.e what's its default value) so I decided to test it and fill the gap so others shouldn't do it again --- source/_docs/scripts.markdown | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/source/_docs/scripts.markdown b/source/_docs/scripts.markdown index c871b6303da..ee17347b3da 100644 --- a/source/_docs/scripts.markdown +++ b/source/_docs/scripts.markdown @@ -107,7 +107,6 @@ Wait until some things are complete. We support at the moment `wait_template` fo # Wait for sensor to trigger or 1 minute before continuing to execute. - wait_template: "{{ is_state('binary_sensor.entrance', 'on') }}" timeout: '00:01:00' - continue_on_timeout: 'true' ``` {% endraw %} @@ -133,7 +132,7 @@ It is also possible to use dummy variables, e.g., in scripts, when using `wait_t ``` {% endraw %} -You can also get the script to abort after the timeout by using `continue_on_timeout` +You can also get the script to abort after the timeout by using optional `continue_on_timeout` {% raw %} ```yaml @@ -144,6 +143,8 @@ You can also get the script to abort after the timeout by using `continue_on_tim ``` {% endraw %} +Without `continue_on_timeout` the script will always continue. + ### Fire an Event This action allows you to fire an event. Events can be used for many things. It could trigger an automation or indicate to another integration that something is happening. For instance, in the below example it is used to create an entry in the logbook.