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-08 09:56:52 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add missing tag trigger documentation (#15608)

Browse Source
This commit is contained in:
Franck Nijhof 2020-11-11 10:31:55 +01:00 committed by GitHub
parent 430514b892
commit e48fed44e2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
source/_docs/automation/trigger.markdown
View File

@ -314,6 +314,37 @@ Although the actual amount of light depends on weather, topography and land cove
A very thorough explanation of this is available in the Wikipedia article about the [Twilight](https://en.wikipedia.org/wiki/Twilight).
### Tag trigger
Fires when a [tag](/integrations/tag) is scanned. For example, a NFC tag is
scanned using the Home Assistant Companion mobile application.
{% raw %}
```yaml
automation:
trigger:
platform: tag
tag_id: A7-6B-90-5F
```
{% endraw %}
Additionally, you can also only trigger if a card is scanned by a specific
device/scanner by setting the `device_id`:
{% raw %}
```yaml
automation:
trigger:
platform: tag
tag_id: A7-6B-90-5F
device_id: 0e19cd3cf2b311ea88f469a7512c307d
```
{% endraw %}
### Template trigger
Template triggers work by evaluating a [template](/docs/configuration/templating/) on every state change for all of the recognized entities. The trigger will fire if the state change caused the template to render 'true'. This is achieved by having the template result in a true boolean expression (`{% raw %}{{ is_state('device_tracker.paulus', 'home') }}{% endraw %}`) or by having the template render 'true' (example below). Being a boolean expression the template must evaluate to false (or anything other than true) before the trigger will fire again.