The source compose is useful as a ZimaOS path example, but it was never confirmed by the original poster and should not be frozen as the current TeslaMate stack. TeslaMate's maintained Docker documentation still uses a multi-container Compose deployment and explicitly recommends running the service on an always-on machine with persistent database/Grafana state.
Current upstream guidance also emphasizes security because TeslaMate stores Tesla API tokens. Keep the service on a trusted home network or put remote access behind a VPN/Tailscale/Cloudflare Tunnel or a hardened reverse proxy rather than publishing the raw WebUI directly.
Check Current TeslaMate Requirements
Current TeslaMate documentation lists:
- Docker/Compose;
- an always-on host;
- at least 1 GB RAM for installation, with 2 GB recommended;
- Internet access to Tesla services;
- amd64 or arm64 hardware.
See the current TeslaMate Docker installation.
The Source Correctly Moved Persistent Data Under /DATA/AppData
The community compose stored Postgres data, Grafana data, and import data under dedicated ZimaOS AppData folders. That is a sound platform adaptation: container state should persist outside the disposable container filesystem.
Protect the PostgreSQL Database
TeslaMate's database contains historical vehicle data and application state. Back it up before image upgrades or major Compose changes.
Do not put the live Postgres data directory on an unreliable network share or remove it when cleaning containers.
Use a Strong ENCRYPTION_KEY
TeslaMate uses the encryption key to protect stored Tesla API tokens. The source placeholder says “some salt for encryption”; replace it with a strong random secret and keep it outside public screenshots or forum posts.
Use One Consistent Strong Database Password
The source correctly notes that the database password must match across Postgres, TeslaMate, and Grafana configuration. A mismatch can look like an application startup problem even though the containers themselves are running.
The Source Disabled MQTT; Current Upstream Includes It in the Standard Stack
The community compose set DISABLE_MQTT=true. Current TeslaMate Docker guidance includes Mosquitto in the standard example. MQTT remains optional depending on integrations, but current users should follow the upstream stack they actually need instead of inheriting a 2025 simplification automatically.
Secure Grafana Too
The source set anonymous Grafana access to true. That may be convenient on a private LAN but exposes vehicle dashboards to anyone who can reach the port. For remote access, use authentication and a protected network path.
Update the Whole Stack Deliberately
Before upgrading, back up the database, review TeslaMate release notes, pull the new images, recreate the stack, and verify Tesla data collection plus Grafana dashboards afterward.
TeslaMate on ZimaOS FAQ
Did the original poster confirm the community Compose worked?
No. They said they would try it, but the thread contains no result.
What data must persist?
At minimum the TeslaMate/Postgres database and Grafana state; protect any additional imported/configured data too.
Should TeslaMate be exposed directly to the public Internet?
Current TeslaMate guidance recommends a secure connection such as VPN, Cloudflare Tunnel, Tailscale, ZeroTier, or a hardened reverse proxy.
