TeslaMate

[MickLesk]

Name of the Script

TeslaMate

Script Type

CT (LXC Container)

Does this script support arm64?

arm64 supported

📋 Script Details

TeslaMate logs Tesla vehicle data — drives, charges, battery health, efficiency, updates — into PostgreSQL and visualises it through prebuilt Grafana dashboards, with optional MQTT publishing.

• Follows upstream website/docs/installation/unsupported/debian.md. Debian trixie ships everything needed in-repo: elixir 1.18.3 (upstream needs >= 1.17), erlang, postgresql-17, mosquitto, nodejs.
• Build: mix local.hex/local.rebar --force, mix deps.get --only prod, npm install/run deploy --prefix ./assets, MIX_ENV=prod mix do phx.digest, release --overwrite → _build/prod/rel/teslamate/bin/teslamate. Several minutes, hence (Patience).
• ExecStartPre runs TeslaMate.Release.migrate, as in the upstream unit.
• Locale: en_US.UTF-8 is generated during install — TeslaMate refuses to start without a UTF-8 capable locale.
• Grafana from apt.grafana.com (not in Debian), provisioned with the TeslaMate datasource and all three dashboard providers (TeslaMate, Internal, Reports) pointed at /opt/teslamate/grafana/dashboards, folder UIDs kept identical to upstream so dashboard cross-links keep working. Default home dashboard set to internal/home.json.
• Note: TeslaMate has no auth of its own and stores Tesla API tokens — never expose :4000 directly. ENCRYPTION_KEY is generated at install; losing it means re-authenticating every vehicle. Both flagged as warnings.
• Grafana on :3000 with admin/admin, must be changed on first login.

Source: https://github.com/teslamate-org/teslamate

[github-actions]

The TeslaMate script is ready for testing:

bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/teslamate.sh)"

Default credentials:
Username: admin
Password: admin

Two web interfaces: TeslaMate on port 4000 (sign in with your Tesla account there) and Grafana on port 3000 with the TeslaMate dashboards. The Grafana credentials admin/admin must be changed on first login.
TeslaMate has no authentication of its own. Your Tesla API tokens are stored in it, so never expose port 4000 to the internet without putting an authenticating reverse proxy in front of it.
A local Mosquitto broker is installed and TeslaMate publishes to it on 127.0.0.1. Point your home automation at port 1883, or set DISABLE_MQTT=true in /opt/teslamate.env if you do not need it.
ENCRYPTION_KEY in /opt/teslamate.env encrypts the stored Tesla tokens - losing it means re-authenticating every vehicle. Set TZ to your local timezone for correct drive and charge timestamps. Vehicle data lives in the PostgreSQL database 'teslamate'.
Built from source with Elixir/Phoenix - the initial build takes several minutes.

Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.

Discord testing thread: https://discord.com/channels/1302816934508630047/1533816370918330409

[bjk201]

Its working! Thanks

[github-actions]

A PR has been created for teslamate: community-scripts/ProxmoxVE#16385

[michelroegl-brunner]

Merged with #16385 in ProxmoxVE