TeslaSync documentation
Get started
Self-hosted Tesla intelligence. Install it, connect a vehicle, then use the catalogue to find every screen.
1. InstallDocker Compose on a trusted host. No Go or Node required for a trial.2. Connect TeslaFleet API application, scopes, redirect URI, and owner consent.3. Enable streamingFleet Telemetry receiver, TLS, virtual key, and signed config.4. Find a screenEvery route grouped like the app sidebar, with empty-state notes.
Common paths
Deploy with DockerCompose, ports, secrets, and a local trial vs a public host.Deploy with KubernetesHelm chart, values, and homelab-sized recovery.ConfigurationEnvironment variables that must stay in sync across Compose and Helm.TroubleshootingNo data, MQTT, auth, and telemetry gaps.Charging in the appSessions, Tesla billing history, Wait Oracle, curves.Driving in the appDrives, FSD, trips, Ghost Racing, drive detail.
Operate and contribute
Release verificationWhat to check before you roll a build.SecretsTokens, encryption, and rotation.ContributeCode structure, adding features, API notes.FAQRequirements, Tesla constraints, what we do not promise.
Before you expose anything
A local trial is not a public deployment. Add TLS, an authenticating proxy, strong secrets, and backups before you expose the API.