Tesla Fleet

If the above My button doesn’t work, you can also perform the following steps manually:

• Browse to your Home Assistant instance.

• Go to Settings > Devices & Services.

• In the bottom right corner, select the Add Integration button.

• From the list, select Tesla Fleet.

• Follow the instructions on screen to complete the setup.

While the Tesla Fleet API documentation Step 3 mentions this as a later step, it is recommended that you do this first to ensure key reachability before the rest of the integration. With this method, it is assumed that the NGINX Home Assistant SSL proxy Add-on is running as a reverse proxy for external access to your Home Assistant installation.

1. Open an SSH Terminal on your Home Assistant installation using the Terminal & SSH Add-on.
2. Run this command to create a private key: openssl ecparam -name prime256v1 -genkey -noout -out private-key.pem
3. Run this command to create and associate a public key with it: openssl ec -in private-key.pem -pubout -out public-key.pem
4. Backup both these files somewhere safe and private for access later.
5. Copy the public key file public-key.pem to /share/tesla/.well-known/appspecific/com.tesla.3p.public-key.pem. It needs to be exactly this location for Tesla’s API to partner with your account correctly.
6. Create a NGINX configuration file nginx_proxy_default_tesla.conf in /share with: echo 'location /.well-known/appspecific/com.tesla.3p.public-key.pem {\n root /share/tesla;\n}' > /share/nginx_proxy_default_tesla.conf
7. Close the Terminal and go to Settings->Add-Ons->NGINX Home Assistant SSL proxy->Configuration page. Change the customize.active option from the default false to true. Leave the config.default option at its default value: nginx_proxy_default*.conf.
8. Restart the NGINX Home Assistant SSL proxy Add-on on the Settings->Add-Ons->NGINX Home Assistant SSL proxy->Info page and test if the public key file is accessible at https://my.domain.com/.well-known/appspecific/com.tesla.3p.public-key.pem

While the Tesla Fleet API documentation Step 3 mentions this as a later step, it is recommended that you do this first to ensure key reachability before the rest of the integration.

1. Open a new terminal on your computer.
2. Run this command to create a private key: openssl ecparam -name prime256v1 -genkey -noout -out private-key.pem
3. Run this command to create and associate a public key with it: openssl ec -in private-key.pem -pubout -out public-key.pem
4. Rename the public key file to com.tesla.3p.public-key.pem. This needs to be exactly this for Tesla’s API to partner with your account correctly.
5. Backup both these files somewhere safe and private for access later.
6. Upload the public key file to your domain at the path /.well-known/appspecific/com.tesla.3p.public-key.pem. For example, if your domain is https://my.domain.com, the public key file must be accessible at https://my.domain.com/.well-known/appspecific/com.tesla.3p.public-key.pem. Do not use redirection logic to handle this, or the Tesla API will not recognize your app later in the process.

These steps are also summarized in the Tesla Fleet API documentation Step 2, but it is recommended to follow the steps below to cover specific details.

1. If you have not already set up your Tesla Developer account: Confirm that you have a verified email and multi-factor authentication set up.
2. Navigate to the Developer dashboard. Change your locale if needed to wherever your account is based, using the globe icon at the top-right corner.
3. Select Create New Application. This should launch a new page with the header Create Fleet API Application.
4. For simple integrations, under Registration Type, select Just for me. If you’re confident about your situation being a business setup instead, select For my business. Select Next.
5. At the Application Details step, use a name that is easy to refer to later, such as ha-integration. This will be needed later while configuring the integration. Select Next.
6. At the Client Details step, under Oauth Grant Type, select Authorization Code and Machine-to-Machine.
   • Under Allowed Origin URL(s), enter your domain where you hosted your public key earlier. Using the example above, this would be https://my.domain.com/.
   • Under Allowed Redirect URI(s), enter https://my.home-assistant.io/redirect/oauth.
   • Select Next.
7. At the API & Scopes step, select the configurations you’d like to access.
   • At least one of Vehicle Information or Energy Product Information must be selected for the integration to function. It is recommended you select all scopes for full functionality.
   • If you’re unsure, you can select only one of these two required scopes for now and update the scopes later from the Developer Dashboard. However, note that if the scopes are updated, you will need to reconfigure the integration fully (refer to the Integration is broken and needs to be reconfigured troubleshooting steps below).
   • Select Next.
8. At the Billing Details (Optional) step, enter your billing details if needed, then select Submit. Tesla does not support billing in all countries yet. Developers in countries that do not yet support payments will not see this step.
   • Tesla provides a $10 monthly credit for personal API usage, so your level of usage may be covered for free. Detailed pricing info for commands, data polling, and wake signals can be found at developer.tesla.com. Use these details to calculate your usage estimate if you rely heavily on this integration.
   • If unsure, you can select Skip & Submit for now and add the billing details later when your usage is close to the free threshold.
9. Your developer application is ready for use!

These steps are also summarized in the Tesla Fleet API documentation Step 4, but the steps below provide easier copy-pasteable code and additional checks.

1. Get your OAuth details by going to your Developer dashboard. Under the app you set up for Home Assistant integration select View Details. Then, select the Credentials & APIs tab. Note the Client ID and Client Secret strings.

2. Run this CURL request, replacing the variable values as specified in the notes below:

   CLIENT_ID=REPLACE_THIS_WITH_YOUR_CLIENT_ID
   CLIENT_SECRET=REPLACE_THIS_WITH_YOUR_CLIENT_SECRET
   AUDIENCE="https://fleet-api.prd.na.vn.cloud.tesla.com"
   curl --request POST \
     --header 'Content-Type: application/x-www-form-urlencoded' \
     --data-urlencode 'grant_type=client_credentials' \
     --data-urlencode "client_id=$CLIENT_ID" \
     --data-urlencode "client_secret=$CLIENT_SECRET" \
     --data-urlencode 'scope=openid vehicle_device_data vehicle_cmds vehicle_charging_cmds' \
     --data-urlencode "audience=$AUDIENCE" \
     'https://fleet-auth.prd.vn.cloud.tesla.com/oauth2/v3/token'
   

   Notes about the variable values:

   • For the CLIENT_SECRET value, depending on your terminal environment, you may need to escape any ! and $ characters in the string, or the curl request will fail.
   • Replace the AUDIENCE value with your region-specific URL. The URL in the example is for users in North America and Asia-Pacific (excluding China). Refer to the Base URLs documentation for the URLs for other regions.
   • For the scope=... line, replace the values with a space-delimited list of the official scope keywords, as you defined them earlier in your app.

3. The CURL request should return a response that looks something like:

   {"access_token":"ACCESS_TOKEN","expires_in":28800,"token_type":"Bearer"}
   

   This is your access token. Copy everything between the double-quotes to be used next.

4. Run this CURL request, replacing the variable values as specified in the notes below:

   curl --location 'https://fleet-api.prd.na.vn.cloud.tesla.com/api/1/partner_accounts' \
   --header 'Content-Type: application/json' \
   --header 'Authorization: Bearer ACCESS_TOKEN' \
   --data '{
       "domain": "my.domain.com"
   }'
   

   • If you had to change the AUDIENCE URL for your region in step 2, update the main domain of the --location arg.
   • Replace ACCESS_TOKEN with the access token that you copied in the previous step.
   • In the domain: line, enter your domain without the leading https:// and the trailing /.

5. You should see a response that contains information about your Tesla Fleet developer app, pricing info, and such. This confirms that the Tesla Fleet API has successfully registered your developer application as a partner. The hard part is over.

1. Get your OAuth details by going to your Developer dashboard. Select View Details under the app you set up for Home Assistant integration. Then, select the Credentials & APIs tab. Note the Client ID and Client Secret strings, these will be needed later.
2. In Home Assistant, the integration wizard should walk you through the default steps. If not already started, scroll above and select the ADD INTEGRATION TO MY button to start the integration wizard. The integration will ask you for all of the necessary integration configurations.
3. In the Add credentials step in the wizard, enter your Tesla Fleet developer application name (from step 5 in the Setting up the Developer Application section above), and the Oauth Client ID and Client Secret (from step 1 above). Select Submit.
4. At this step, you should be taken to the Tesla authentication page. You will need to re-enter your Tesla account login credentials.
5. At the confirmation page with the header Allow ha-integration access to your Tesla Account (the specific application name will be whatever you set earlier), select the Select All button. This list of scopes is already limited to the specific scopes you chose for the application information earlier, so it is not necessary to review them again. Select Allow.
6. You should now see a Home Assistant page asking if you would like to Link account to Home Assistant?. Select Link account.
7. You’re all set! The integration should fetch your device details into Home Assistant.