jeena/home-assistant.github.io
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Script - wait_template 'trigger.entity_id' support (#3593)

Browse source 
* * Updated wait_template to include 'trigger.entity_id' and 'variables' support

* * Deleted notes and whitespaces

* Small grammar correction
This commit is contained in:
cdce8p 2017-10-22 00:58:46 +02:00 • committed by Fabian Affolter
parent 8791e6e89a
commit e8733459d2
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

22
source/_docs/scripts.markdown
View file

@ -90,6 +90,28 @@ wait_template: {% raw %}"{{ states.climate.kitchen.attributes.valve < 10 }}"{% e
timeout: 00:01:00 timeout: 00:01:00
``` ```
When using `wait_template` within an automation `trigger.entity_id` is supported for `state`, `numeric_state` and `template` triggers, see also [Available-Trigger-Data](/docs/automation/templating/#available-trigger-data).
{% raw %}
```yaml
wait_template: "{{ is_state(trigger.entity_id, 'on') }}"
```
{% endraw %}
It is also possible to use dummy variables, e.g., in scripts, when using `wait_template`.
{% raw %}
```yaml
# Service call, e.g. from an automation.
service: script.do_something
data_template:
dummy: "{{ input_boolean.switch }}"
# Inside the script
wait_template: "{{ is_state(dummy, 'off') }}"
```
{% endraw %}
### {% linkable_title Fire an Event %} ### {% linkable_title 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 component that something is happening. For instance, in the below example it is used to create an entry in the logbook. This action allows you to fire an event. Events can be used for many things. It could trigger an automation or indicate to another component that something is happening. For instance, in the below example it is used to create an entry in the logbook.