From 8151efd0bc76a0fe53281a48d0e89f5a367030e6 Mon Sep 17 00:00:00 2001
From: Stefan <37924749+stefanroelofs@users.noreply.github.com>
Date: Tue, 11 Aug 2020 13:05:41 +0200
Subject: [PATCH] Zone Trigger: changed entity_id from device_tracker to person
 (#14228)

Entity_id of a zone trigger can be both a person, or a device_tracker. I'd say that a person entity is the newer, recomended type.
---
 source/_docs/automation/trigger.markdown | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown
index c690ca7a1fb..f8c5bbf1cd9 100644
--- a/source/_docs/automation/trigger.markdown
+++ b/source/_docs/automation/trigger.markdown
@@ -367,13 +367,13 @@ Note that a given webhook can only be used in one automation at a time. That is,
 
 ### Zone trigger
 
-Zone trigger fires when an entity is entering or leaving the zone. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. This includes [GPS Logger](/integrations/gpslogger/), the [OwnTracks platform](/integrations/owntracks/) and the [iCloud platform](/integrations/icloud/).
+Zone trigger fires when an entity is entering or leaving the zone. The entity can be either a person, or a device_tracker. For zone automation to work, you need to have setup a device tracker platform that supports reporting GPS coordinates. This includes [GPS Logger](/integrations/gpslogger/), the [OwnTracks platform](/integrations/owntracks/) and the [iCloud platform](/integrations/icloud/).
 
 ```yaml
 automation:
   trigger:
     platform: zone
-    entity_id: device_tracker.paulus
+    entity_id: person.paulus
     zone: zone.home
     # Event is either enter or leave
     event: enter # or "leave"