← Directory

TeslaMate-ABRP

TeslaMate ABRP is a bridge that syncs vehicle data from TeslaMate to A Better Route Planner (ABRP) so charging plans stay current and your Tesla doesn't sleep…

  • Automation
  • Tools & Utilities
TeslaMate ABRP is a bridge that syncs vehicle data from TeslaMate to A Better Route Planner (ABRP) so charging plans stay current and your Tesla doesn't sleep on long trips.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

63/100 Good

Maintained
93last commit 24 days ago
Popular
3878 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 9 days ago

GitHub stars
78
Open issues
0
Last commit
2026-09-21
Latest release
v4.0.1
License
MIT
Activity
declining

Checked 7 days ago - source: GitHub (fetzu/teslamate-abrp)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set container connection settings first Run the app in a Docker container and set ENCRYPTION_KEY, DATABASE_HOST, and MQTT_HOST, then map port 8080 so other apps can reach the API. If the database or MQTT address is wrong, the API cannot reach your TeslaMate data or message broker. source
  • Keep the encryption key the same Use the same ENCRYPTION_KEY that was used to encrypt the Tesla access token stored in TeslaMate's database. If it is missing or different, the API cannot decrypt the token, so car data or commands will fail. source
  • Protect API calls with a token Set the API_TOKEN setting (a secret key for API calls) for any dashboards, scripts, or apps that will use the API. If you leave it empty, keep the API reachable only by trusted devices, because there is no shared token value to identify callers. source

Fetched 16 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How does TeslaMate-ABRP deliver TeslaMate data to A Better Route Planner?

It is described as an MQTT-to-ABRP path. It gets vehicle data from TeslaMate and sends it to A Better Route Planner.

What containers are typically present in the TeslaMate Docker compose stack?

Using compose on Ubuntu includes TeslaMate, Postgres, Mosquitto, and Grafana. They run in the same stack, which is different from how Unraid handles them.

What should be checked if the integration cannot reach TeslaMate data?

Check DATABASE_HOST and MQTT_HOST. If the database or MQTT address is wrong, the API cannot reach TeslaMate data or the message broker.

Should API_TOKEN be left empty if the API is only used locally?

Set API_TOKEN for any dashboards, scripts, or apps that use the API. If it is left empty, keep the API reachable only by trusted devices because there is no shared token value to identify callers.

Answers sourced from fetzu.github.io, github.com, github.com, www.reddit.com

Community

Collected 11 days ago - public community threads