Person
The Person integrationIntegrations connect and integrate Home Assistant with your devices, services, and more. [Learn more] allows connecting device tracker entities to one or more person entities. The state updates of a connected device tracker set the state of the person. When you use multiple device trackers, the state of the person is determined in this order:
- If there are stationary trackers (non-GPS trackers, such as a router or Bluetooth device tracker) presenting the state
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 state
not_homewill be used.
Let’s say, for example, that you have three trackers: tracker_gps, tracker_router, and tracker_ble.
- You’re at home, and all three devices show state
home. The state of your Person entity will behomewith sourcetracker_routerortracker_ble, whichever was most recently updated. - You just left home.
tracker_gpsshows statenot_home, but the other two trackers show statehome(they may not have yet updated due to theirconsider_homesetting, see device_tracker). Since the stationary trackers have priority, you are consideredhome. - After some time, both stationary trackers show state
not_home. Now your Person entity has statenot_homewith sourcetracker_gps. - 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. The state will benot_home. - Then you’re going into a zone you have defined as
zone1,tracker_gpssends an update, and now your state iszone1with sourcetracker_gps. - You’ve returned home and your mobile device has connected to the router, but
tracker_gpshasn’t updated yet. Your state will behomewith sourcetracker_router. - After the
tracker_gpsupdate occurs, your state will still behomewith sourcetracker_routerortracker_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 first by GPS and then by stationary trackers.
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 configuration.yamlThe configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file.
Adding a person to Home Assistant
If you have administrator rights, you can add other persons to Home Assistant and create user accounts for them. Depending on the rights you give them, they can then use Home Assistant on their own devices, have their own dashboards, and be included in automations.
- Go to Settings > People and select Add person.
- Enter their Name.
- Add an image if you like.
- Under Allow login, select whether they should be able to sign in.
- If they cannot sign in, they do not get a user account and cannot do much with Home Assistant.
- They cannot have their own dashboard, for example.
- But they can still be used for device tracking, show up on a map, and be included in automations.
- If they are able to sign in, fill in the user information.
- Check if the username is correct. Home Assistant suggests one based on the person name, but the two do not have to be identical.
- The username must be lowercase and contain no spaces.
- The username is required to sign in.
- The person name is the name displayed in the UI.
- Enter a password and store it in a safe location.
- Define if they should have Local access only.
- If this is enabled, they won’t have access to Home Assistant when they are outside your network, for example, from their phone.
- Define if they should have Administrator rights.
- Select Create.
- Check if the username is correct. Home Assistant suggests one based on the person name, but the two do not have to be identical.
- If you have already set up devices for presence detection, select the devices that belong to this person.
Customizing the picture for a person
To upload a picture in the frontend, open a person’s page, select an image file or drag and drop one into the input field, and then crop it.
See the documentation about hosting files for more information about the www folder.
Configuring the person integration via the Home Assistant configuration panel
This integration is enabled by default, unless you’ve disabled or removed the default_config: line from your configuration. If that is the case, enable it manually by adding the following to your configuration:
person:
Configuring the person integration via YAML
If you prefer YAML, you can also configure your persons via the configuration.yamlThe configuration.yaml file is the main configuration file for Home Assistant. It lists the integrations to be loaded and their specific configurations. In some cases, the configuration needs to be edited manually directly in the configuration.yaml file. Most integrations can be configured in the UI. [Learn more] file:
# Example configuration.yaml entry
person:
- name: Ada
id: ada6789
device_trackers:
- device_tracker.ada
Configuration Variables
The user ID of the Home Assistant user account for the person. You can find the user_id (also shown as ID) under Settings > People, on the Users tab.
Here’s an extended example:
# 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 person.reload action.