From 77bdc16fb8b8425540303ca6040172b9561e3f2b Mon Sep 17 00:00:00 2001 From: Dubh Ad Date: Sun, 24 Jan 2021 00:05:29 +0000 Subject: [PATCH] Update trigger.markdown (#16271) Geolocation vs zone causes regular confusion. --- source/_docs/automation/trigger.markdown | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index c6ace8ed612..a1b137fd4fb 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -569,6 +569,13 @@ automation: Geolocation trigger fires when an entity is appearing in or disappearing from a zone. Entities that are created by a [Geolocation](/integrations/geo_location/) platform support reporting GPS coordinates. Because entities are generated and removed by these platforms automatically, the entity id normally cannot be predicted. Instead, this trigger requires the definition of a `source`, which is directly linked to one of the Geolocation platforms. +
+ +This isn't for use with `device_tracker` entities. For those look above at the `zone` trigger. + +
+ + ```yaml automation: trigger: