diff --git a/docs/automation/trigger/index.html b/docs/automation/trigger/index.html
index 7b4d39085b..b13eca3682 100644
--- a/docs/automation/trigger/index.html
+++ b/docs/automation/trigger/index.html
@@ -181,11 +181,15 @@ In the example above, a numeric_state that is 17.1-24.9 would fire this trigger.
The US Naval Observatory has a tool that will help you estimate what the solar angle will be at any specific time.
Template trigger
+
+ If your template trigger has no entity_id listed, then it is evaluted on every state change for every entity. Instead you should create a template sensor or template binary sensor and use that in your automation.
+
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 ({{ is_state('device_tracker.paulus', 'home') }}) or by having the template render ‘true’ (example below).
With template triggers you can also evaluate attribute changes by using is_state_attr ({{ is_state_attr('climate.living_room', 'away_mode', 'off') }})
automation:
trigger:
platform: template
+ entity_id: device_tracker.paulus
value_template: "{% if is_state('device_tracker.paulus', 'home') %}true{% endif %}"