person integration allows connecting device tracker entities to one or more person entities. The state updates of a connected device tracker will set the state of the person. When multiple device trackers are used, the state of person will be determined in this order:
- If there are stationary trackers (non-GPS trackers, e.g., a router or Bluetooth device tracker) presenting the status
home, the tracker most recently updated will be used.
- If there are trackers of type
gps, then the most recently updated tracker will be used.
- Otherwise, the latest tracker with status
not_homewill be used.
Let’s say, for example, that you have three trackers:
- You’re at home, all three devices show status
home- status of your Person entity will be
tracker_ble, whichever was most recently updated.
- You just left home.
not_home, but the other two trackers show status
home(they may not have yet updated due to their
consider_homesetting see device_tracker). Since the stationary trackers have priority, you are considered
- After some time, both stationary trackers show status
not_home. Now your Person entity has status ‘not_home’ with source
- While you are away from home, your Home Assistant instance is restarted. Until the
tracker_gpsreceives an update, your status will be determined by the stationary trackers, since they will have the most recent update after a restart. Obviously, the status will be
- Then you’re going into a zone you have defined as
tracker_gpssends an update, and now your status is
- You’ve returned home and your mobile device has connected to the router, but
tracker_gpshasn’t updated yet. Your status will be
- After the
tracker_gpsupdate occurs, your status will still be
tracker_ble, whichever has the most recent update.
In short, when you’re at home, your position is determined first by stationary trackers (if any) and then by GPS. When you’re outside your home, your position is determined firstly by GPS and then by stationary trackers.
Hint: When you use multiple device trackers together, especially stationary and GPS trackers, it’s advisable to set
consider_home for stationary trackers as low as possible see device_tracker).
You can manage persons via the UI from the person page inside the configuration panel or via
YAML in your
This integration is by default enabled, unless you’ve disabled or removed the
default_config: line from your configuration. If that is the case, the following example shows you how to enable this integration manually:
If you prefer YAML, you can also configure your persons via the
# Example configuration.yaml entry person: - name: Ada id: ada6789 device_trackers: - device_tracker.ada
The user ID of the Home Assistant user account for the person.
ID) of users can be inspected in the “Users”/“Manage users” screen in the configuration panel.
An extended example would look like the following sample:
# Example configuration.yaml entry person: - name: Ada id: ada6789 device_trackers: - device_tracker.ada - name: Stacey id: stacey12345 user_id: 12345678912345678912345678912345 device_trackers: - device_tracker.stacey - device_tracker.beacon
If you change the YAML, you can reload it by calling the
You can easily upload a picture in the frontend. Simply click on a person, select or drop an image in the input field, and then crop it.
You can also do this using YAML. By following the instructions on the customizing entities page, you can customize the picture used for a person entity in the
customize: section of your configuration. For example:
customize: person.ada: entity_picture: "/local/ada.jpg"
See the documentation about hosting files for more information about the