Places for Home Assistant (Marketplace integration)

Installs: 1.7k sharing analytics
GitHub stars: 218
Connection: Uses the vendor's cloud
Upkeep: Updated in the last 6 months
Version: v3.0.2, October 24, 2026
Category: Presence and location, Trackers
Kind: Marketplace integration
Needs: Needs the Marketplace (HACS on 2026.10 and older)
Domain: places
Source: github.com/custom-components/places
Issues: Report an issue

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

About

Places is an integration that reverse geocodes a tracked entity's coordinates through OpenStreetMap. It takes a device tracker, person or sensor and creates a main sensor whose state follows chosen display options, with child sensors for place name, zone name, city, state, country, street, map link, direction of travel and distance from home. Some country and detailed address sensors are disabled by default. Further entities include a force update button, a map provider select, a switch for showing the last updated time, and a text entity for display options. An optional extended data diagnostic sensor holds the raw OpenStreetMap and Wikidata payloads, and an event is fired after each successful state update. It relies on an online lookup, is configured in the UI, and offers options such as map zoom, language, home zone and an email address for the OpenStreetMap API.

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

Supports

Uses the vendor's cloud Needs an internet connection and an account with the vendor.
From the Marketplace Installed through the Marketplace, formerly HACS.
Actively maintained Its author released or pushed a change in the last six months.

Provides

Switches
Sensors

Setting it up

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

Places: OpenStreetMap Sensor

Sensor Name
Tracked Entity ID
Home Zone
Display Options
Map Provider
Map Zoom
Email to use as OpenStreetMap API Key (optional)
Language (optional)
Use GPS AccuracySet this to False if your Device Tracker has a GPS Accuracy (gps_accuracy) attribute, but it always shows 0 even if the latitude and longitude are correct.
Enable Extended AttributesCreate an Extended data diagnostic sensor and fetch raw OSM details/Wikidata payloads. When disabled, the sensor is removed and the extra lookups are skipped.
Show last updated time at end of state '(since xx:yy)'
Date format to show at end of state when not changed >24h

After setup

Tracked Entity ID
Home Zone
Display Options
Map Provider
Map Zoom
Email to use as OpenStreetMap API Key (optional)
Language (optional)
Use GPS AccuracySet this to False if your Device Tracker has a GPS Accuracy (gps_accuracy) attribute, but it always shows 0 even if the latitude and longitude are correct.
Enable Extended AttributesCreate an Extended data diagnostic sensor and fetch raw OSM details/Wikidata payloads. When disabled, the sensor is removed and the extra lookups are skipped.
Show last updated time at end of state '(since xx:yy)'
Date format to show at end of state when not changed >24h

Texts from the code of custom-components/places.

Entities

ButtonsForce Update
SelectsMap Provider
SensorsPlace Name, Zone Name, City, State, Direction of Travel, Map Link, Distance From Home, Distance Traveled, Country, Country Code, Street Number, Street, and 17 more
SwitchesShow Last Updated
TextsDisplay Options

From the README

_Component to integrate with OpenStreetMap Reverse Geocode and create a sensor with numerous address and place attributes from a device_tracker, person, or sensor_

From the README of custom-components/places, GNU GPL v3.0. Shortened.