Pleos Vehicle Data for Home Assistant (Marketplace integration)

Installs: 63 sharing analytics
GitHub stars: 19
Connection: Uses the vendor's cloud
Upkeep: Updated in the last 6 months
Version: v0.11.0, October 25, 2026
Category: Vehicles and transport, Cars and EVs
Kind: Marketplace integration
Needs: Needs the Marketplace (HACS on 2026.10 and older)
Domain: pleos_vehicle_data
Source: github.com/jouwdan/ha-pleos
Issues: Report an issue

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

About

Pleos Vehicle Data is a read-only cloud integration for Hyundai, Kia and Genesis cars in Europe, using the Pleos personal Vehicle Data API. Each car becomes its own device, with sensors and binary sensors for battery and charging status, range, odometer, doors, ignition, climate and warnings, plus a location tracker and a trip event. It reads only what the car has already uploaded, so it cannot lock the car, start charging or climate control, or wake the vehicle. Status is polled every 15 minutes and trips every 60 minutes by default, and readings carry a reported time and a stale-data marker. Options cover location data, optional reverse geocoding through a chosen service, trip events, raw data archiving, and a correction for odometers reported in miles that are really kilometres. Setup happens in the UI with a personal API Client ID and Secret from the primary account, and several accounts can be added.

Automatic summary of the README and code of jouwdan/ha-pleos. 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

Sensors
Presence

Setting it up

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

Connect your vehicles

Manufacturer
Client IDCopy the Client ID from My Vehicle Data API in Pleos Playground.
Client SecretCopy the matching Client Secret. Home Assistant saves it in its private configuration.

Odometer

Correct odometer kilometres labelled as milesLeave empty for correctly reported km or miles. This corrects the API unit label before Home Assistant converts the distance; it does not choose your display unit.

Sign in again

Client IDCopy the Client ID from My Vehicle Data API in Pleos Playground.
Client SecretCopy the matching Client Secret. Home Assistant saves it in its private configuration.

Also asked when changing the connection.

After setup

Polling intervalHow often status data is requested from Pleos. Trip data has its own interval under Trips.
Stale-data thresholdOlder readings are marked with data_stale; they do not become unavailable.
Enable location data and GPS trackingQueries the location endpoint and exposes its data. A map tracker is created only for valid WGS84 coordinates.
Correct odometer kilometres labelled as milesSelect only cars whose API odometer value is in kilometres but labelled miles. Home Assistant will then convert it to your preferred display unit. Leave empty for correctly reported units. This affects new readings only; existing history and statistics are not repaired. Clear the selection if Pleos fixes the underlying data.
Reverse geocode vehicle locationSend valid GPS coordinates to your chosen service to resolve an address. Requires location data and a Nominatim-compatible service URL. Off by default.
Reverse geocoding service URLBase URL or /reverse endpoint. Use a URL without login details, query parameters or fragments; redirects are not followed. No service is configured by default.
Reverse geocoding API key / tokenOptional provider API key or access token. For compatible Nominatim-style services it is sent as the key parameter. The credential is sent only to the configured geocoding service and is redacted from diagnostics.
Trip data intervalHow often the four trip endpoints are queried. Pleos delivers trip data with a delay, so this can be longer than the polling interval. Trip readings are kept between queries.
Fire an event for each new tripOff by default. Fires pleos_vehicle_data_trip once per trip with every sample the API returned. Large trips can be excluded from the recorder. The Trip event entity records every trip regardless of this option.
Archive raw vehicle dataOff by default. Keeps raw snapshot payloads and trip objects in compressed files under pleos_vehicle_data/archive in your configuration folder. Unchanged responses are not written again, each trip is stored once, and nothing is deleted.

Texts from the code of jouwdan/ha-pleos.

Entities

Binary sensorsCharging, Plugged in, Accessory power, Ignition power, High-voltage system power, Ignition, Sleep mode, In park, Freezer, Climate control, Bonnet, Steering wheel heating, and 26 more
PresenceLocation
EventsTrip
SensorsArchive, Battery charging API, Battery capacity, Charge time remaining, Battery level, Charging status, DC charge limit, AC charge limit, Battery charging data age, Battery charging last reported, Connection, Driving status API, and 93 more

Actions

RefreshRequests the latest data already available in Pleos for this account. It cannot make the car upload new data.Fields: Account

Troubleshooting

DiagnosticsDownloads a diagnostics file to attach to a bug report.

From the README

Bring your Hyundai, Kia or Genesis vehicle into Home Assistant using the official Pleos personal Vehicle Data API. Each car gets its own device, with entities you can use in dashboards and automations. Multiple accounts are supported.
This is a read-only cloud integration for Europe. It reads the data your car has already uploaded; it cannot lock the car, start climate control or charging, or wake it for a fresh update.
Shows battery and charging status, fuel level, range and odometer readings.
Reports doors, ignition, climate settings, tyre pressures and warnings using native Home Assistant sensors and binary sensors.
Adds GPS tracking, trip summaries and driving statistics.
Estimates cumulative EV consumption since install in kWh/100 km or mi/kWh from valid battery and odometer reports.
Shows when data was reported, so you can tell how recent it is.

From the README of jouwdan/ha-pleos, MIT License. Shortened.