From 2d9130fd0e9e7d69700f065e8839c5d83ae6a921 Mon Sep 17 00:00:00 2001 From: Gianni Fontanini Date: Fri, 6 Jan 2017 09:30:55 +0100 Subject: [PATCH] added example line of is_state_attr (#1720) --- source/getting-started/automation-trigger.markdown | 1 + 1 file changed, 1 insertion(+) diff --git a/source/getting-started/automation-trigger.markdown b/source/getting-started/automation-trigger.markdown index 79bbf3681fa..9a3e7d7dc35 100644 --- a/source/getting-started/automation-trigger.markdown +++ b/source/getting-started/automation-trigger.markdown @@ -95,6 +95,7 @@ automation: ### {% linkable_title Template trigger %} Template triggers work by evaluating a [template] on each state change. 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). +With template triggers you can also evaluate attribute changes by using is_state_attr (`{% raw %}{{ is_state_attr('climate.living_room', 'away_mode', 'off') }}{% endraw %}`) ```yaml automation: