Person Location for Home Assistant (Marketplace integration)

Installs: 222 sharing analytics
GitHub stars: 63
Connection: Works locally
Upkeep: Updated in the last 6 months
Version: v2026.09.26, October 10, 2026
Category: Presence and location, Trackers
Kind: Marketplace integration
Needs: Needs the Marketplace (HACS on 2026.10 and older)
Domain: person_location
Source: github.com/rodpayne/home-assistant_person_location
Issues: Report an issue

Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation.

Screenshots From the README of rodpayne/home-assistant_person_location.

About

Person Location combines the status of several device trackers into one location sensor for each person. It follows state changes of device tracker, sensor, binary sensor and person entities instead of polling, and it is set up in the UI. Moves between Home and Away pass through Just Arrived and Just Left states, so automations can react to them, and an option can report the zone name instead of Away. An action reverse geocodes a location through providers such as Open Street Map, MapQuest, Google Maps or Radar, and distance from home can be calculated in miles and minutes. Optional sensors expose attributes like latitude, longitude, direction and distance from home as states, and map cameras can be added from URL templates. Geocoding can be paused with an action, and diagnostics and repair notices are included.

Automatic summary of the README and code of rodpayne/home-assistant_person_location. Something wrong, or are you the maintainer and want your own text here? Get in touch

Supports

Works locally Talks to your devices on your own network. No vendor cloud in between.
From the Marketplace Installed through the Marketplace, formerly HACS.
Actively maintained Its author released or pushed a change in the last six months.

Provides

Cameras
Switches
Sensors

Setting it up

Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services.

Person Location Configuration Menu

Step through or choose a configuration section:

Person Location Geocode Configuration (1 of 2)

Google Language
Google Country Code
Google API Key
Mapbox Access Token
MapQuest API Key
OSM Nomination API Key (your eMail Address)
Radar API Key (publishable)

Person Location Geocode Configuration (2 of 2)

Source for driving distance and duration

Person Location Sensor Configuration

Sensors to create for person location
altitude
bread_crumbs
direction
driving_km
driving_miles
driving_minutes
geocoded
latitude
longitude
meters_from_home
miles_from_home
Platform for output sensor (experimental)

Person Location Trigger Configuration

Follow Person Integration?
Trigger Entity (device) to add
Person Name for the new trigger
Choose a trigger to edit, or return to menu:

Person Location Trigger Edit

Trigger Entity (device)
Person Name for the trigger

Person Location Map Camera Configuration

Choose the provider to edit, add a new one, or return to menu:

Person Location Map Camera Add

Map Camera Name
Map Camera State Template
Map Camera URL Template

After setup

Hours Extended Away
Minutes Just Arrived
Minutes Just Left
Show zone in state when away?
Friendly Name Template

Texts from the code of rodpayne/home-assistant_person_location.

Actions

Reverse GeocodeService to reverse geocode the location in a person status sensor.Fields: Entity ID, Force Update, Friendly Name Template
Geocode API OnResume using the Person Location services.
Geocode API OffPause using the Person Location services. This may be necessary if a malfunction causes an excessive number of calls or if the external site is unreachable. The Nominatim Usage Policy says, 'Apps must make sure that they can switch off the service at our request at any time (in particular, switching should be possible without requiring a software update).' This also pauses the WazeRouteCalculator calls.
Process TriggerService to process the changes of a device tracker or sensor.Fields: Entity ID, From State, To State