Tesla Fleet Setup
Instructions for setting up the Tesla Fleet integration in Home Assistant. This is an advanced setup process (for now).
- Sign in with your Tesla Account credentials and create a new app. Give it a unique name to ensure no one else has used the same name:
- In the Tesla app setting, set the Redirect URL to:
https://my.home-assistant.io/redirect/oauth - For the Allowed Origin(s)
setting,settingenteryouhttps://freakycowbot.com
need You can enter youra public domainifwhere youhavecanonehostandawantfile.toHopefullyusesoonyourweowncanpubsimplifykey.this step.
openssl ecparam -name prime256v1 -genkey -noout -out private-key.pemopenssl ec -in private-key.pem -pubout -out public-key.pem
- https://your-domain.com/.well-known/appspecific/com.tesla.3p.public-key.pem
- Here is a Postman collection you can import: Tesla Fleet.postman_collection.json
- This assumes Tesla North America or Asia-Pacific. If you're in a different region like Europe, find your URL here and update the audience field: https://developer.tesla.com/docs/fleet-api/getting-started/base-urls
freakycowbot.comhttps:// portion).- Remember,
unless you're using the domain listed here,you must place the public key you created on the Allowed Origins domain you specified at the following location:- https://your-domain.com/.well-known/appspecific/com.tesla.3p.public-key.pem
- Select Tesla Fleet as the Integration and Enter your app name, client_id, client_secret, then click Add
Notes:
-
- Questions/Comments? Reach out on Mastodon: @JaggedJax@hostux.social
- This guide does not yet cover Command Signing which may be required by newer vehicles to perform actions. It is not required just to read stats: https://www.home-assistant.io/integrations/tesla_fleet#command-signing
- It doesn't appear that the public key or Allowed Origin URL is actually validated, beyond one just existing.