jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-28 03:37:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

continue_on_timeout clarification (#11723)

Browse Source 
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
This commit is contained in:
akasma74 2020-01-13 10:13:22 +00:00 committed by Franck Nijhof
parent ae2509e233
commit 8dac0b232c
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
source/_docs/scripts.markdown
View File

@ -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.