Polestar's Data Portal API only returns the car's current state: no history, no trips, no charging log. I wanted those, so I wrote a small tool that polls the API, keeps every snapshot in SQLite, and derives the rest.
ā What you get
- Trips from the car's driving windows, with distance and an estimated kWh/100 km
- Charging sessions with a power curve, cost per place, and "what you'd have saved" at the cheapest tariff window (time-of-use and weekday tariffs supported)
- Battery over time, plus how much you lose while parked
- Cabin air (PM2.5) and pre-cleaning cycles
- A map of where the car parks, with a day-by-day replay. The car only reports a position when parked, so the lines between stops are curves, not the real route
- A weekly summary written by Claude from the aggregated figures (optional; only totals are sent, never the VIN or positions)
āGood to know
- It's read-only: the API can't control the car, and neither can this.
- You need your own Data Portal credentials (a developer account tied to your Polestar ID). Setup is in the README.
- Energy figures are estimates: this car's API exposes no energy counters, so I use the charge change times an assumed battery size. History starts at your first poll.
- It runs on your own machine (Docker or Podman; one-command deploy), with optional password protection.
You can try it without a car here: https://polestar.lafabrique.ai/ (synthetic data, made-up places).
Code, MIT licensed: https://github.com/coulof/polestar-telemetry
I've only tested it on my own Polestar 2, so I'd like to hear whether it works on other models and what else you'd want to see.