From e777af9ea1d42f0f110f58feca0d0c7918469edc Mon Sep 17 00:00:00 2001
From: Jon Griffith <32052562+arretx@users.noreply.github.com>
Date: Tue, 26 Dec 2017 13:10:55 -0700
Subject: [PATCH] Clarification regarding the frequency... (#4280)

It's often been noted in the forums that Template Triggers are sometimes overload and that you want to use them sparingly.  I haven't stress tested my system with this idea, but if the template triggers are tested every time any state changes, then that is the clarification that I've proposed in the documentation.
---
 source/_docs/automation/trigger.markdown | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown
index a54145e0956..140fd421aed 100644
--- a/source/_docs/automation/trigger.markdown
+++ b/source/_docs/automation/trigger.markdown
@@ -138,7 +138,7 @@ The US Naval Observatory has a [tool](http://aa.usno.navy.mil/data/docs/AltAz.ph
 
 ### {% 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).
+Template triggers work by evaluating a [template] 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).
 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