Skip to main content
Selora Homes Selora Homes

Tesla Fleet Integration

Homeowners link a Tesla to their Home Assistant by signing in at tesla.com. Selora sets up the developer application, OAuth callback, public key hosting and command-signing keys.

Roadmap Selora Connect Tesla Fleet Homeowners Remote-Access Integrations

Summary

Homeowners connect their Tesla vehicles and energy products to Home Assistant by signing in at tesla.com. Selora sets up and maintains everything the Tesla Fleet integration needs: the developer application, the OAuth callback, public key hosting and the command-signing keys.

Problem

Setting up the Tesla Fleet integration by hand requires:

  1. A Tesla developer application at developer.tesla.com, with the right OAuth grant types, API scopes, an allowed origin and a redirect URI.
  2. A Home Assistant reachable at a stable public URL, for the OAuth callback.
  3. A public key file hosted on that domain so Tesla can verify signed vehicle commands, usually through the NGINX app or an external host.
  4. A client ID and secret pasted into the Home Assistant config flow.

A homeowner cannot check any of these steps, and a mistake in one breaks the whole setup.

Proposal

Selora already provides the two hard prerequisites:

  • A public URL per home, through Secure Remote Access. It gives the allowed origin and redirect URI Tesla requires, with no domain, port forwarding or NGINX app.
  • Per-home endpoints for third-party services, as built for Alexa Voice Control.

On top of these, Selora handles:

  • Developer application: registered with the grant types and scopes, bound to the home’s public URL.
  • Public key hosting: served from the home’s Selora public URL.
  • Private key: generated and stored like any other credential Selora manages.
  • Config flow: credentials injected and the flow completed for the homeowner.
  • Lifecycle: re-authentication, key rotation, and clean removal.

The homeowner flow becomes: Link your Tesla, sign in at tesla.com, done. The vehicle and energy entities then appear in Home Assistant as they would after a manual setup.

Scope

In scope

  • Provision the developer application, OAuth callback, public key and signing key.
  • Complete the Home Assistant config flow without the homeowner entering credentials.
  • Manage re-authentication, key rotation and removal per home.

Out of scope

  • Tesla controls in the Companion App (lock, climate, charging), which can build on this once linked.
  • Fleet API use outside the Home Assistant integration.
  • China-region accounts, which the integration does not support. The link flow says so instead of failing.

Decisions to make

  • Developer application: one per home, or one shared Selora application with per-home origins.
  • Public key location: the Selora public endpoint, or each Hub.
  • OAuth callback: whether to skip the My Home Assistant redirect, since Selora already holds the public URL.
  • Default scopes: vehicles only, or vehicles plus energy products (Powerwall, solar, Wall Connector).
  • Companion App flow: how the link step and the resulting entities are presented.

Success criteria

  • A homeowner links a Tesla without visiting developer.tesla.com or handling a key file.
  • The integration is working in Home Assistant within minutes of linking.
  • Re-authentication and key rotation need no action from the homeowner, and unlinking removes the integration, application binding and keys.

Type to search across

↑↓ navigate ↵ open
⌘K search