Unable to set up Tesla Fleet integration

Configuration
1

Hi all,

I’ve spent a few hours today trying to get the Tesla Fleet integration installed and keep hitting a brick wall. I’m following the instructions on the integration’s page. After I authenticate with Tesla and then try to redirect to Home Assistant I just get an unhelpful ‘Error’ dialog box like so;

image
image1470×614 27.7 KB

I don’t know where to look for more details about what is going wrong here as log files no longer seem to be part of Home Assistant. I am behind CGNAT which may be an issue here? I don’t think it should be a problem until a few more steps down the instructions (I am planning on getting around it by using Tailscale Funnel).

Any clues?

2

Logs are still available but through the UI, go to settings>System>Logs

This integration still works for me: GitHub - alandtse/tesla: Tesla custom integration for Home Assistant. This requires a refresh token be generated by third-party apps to login.

3

I need the integration for my Powerwall 2, not a car so I don’t think that integration will work.
I had seen those logs in the UI but didn’t realise I had to click through to get details. Actually quite a nice setup. Anyway, I found the following in there which will point me in the right direction. Obviously I haven’t set up something quite right. I will hack away at this. Does anyone have any ideas?

ValueError: Partner login failed: {‘error’: ‘invalid_scope’, ‘error_description’: ‘The client is not allowed to access the requested resource.’, ‘referenceID’: ‘715b78fe-c74c-4c8c-a433-368bf842c7ce-1765628800358. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support’}

4

I have this same error. Did you get it resolved?

5

Nope. Still a mystery. The Home Assistant instance I’m trying it with is at a holiday house and I don’t have remote access to it so I haven’t been able to try anything further. I’ll be back there in a few days so will report back if I have any success.

6

Hi, I get the same error and the same message in the log files.
Using HA 2025.12.5, Tesla Fleet integration, Duckdns, Let’s Encrypt, and NGINX Home Assistant SSL proxy. Can publicly see the site with proper certificates. Gut feel if that the hand off from my.home-assistant.io to tesla api.

7

Has anyone made any progress on this?

8

Unable to set up Tesla Fleet integration - #2 by afsy_d this one is working for me.

9

hoping for some progress with this as well. got HA for Tesla solar integration specifically

10

Hopefully I can look at this again tomorrow, but I’m expecting the same result. There seem to be quite a few of us here with this issue. I will attempt to get the attention of the maintainer of the integration.

11

Having spent several hours on this, mine was as simple as adding my mailing address to the tesla portal. Although it never asked or seems to be a documented requirement it sprang to life as soon as I added my address and went through adding the Tesla Fleet integration again. GL.

12

Glad that worked for you. Added my address, but still experiencing the same error.

13

For those that have this working, can you confirm the scopes you’ve used in registering the application within the developer portal?

14

Good news. I got this working and it does what is promised.
Bad news. I’m not 100% sure what I did to get it working. My address was already added in the developer portal. What wasn’t added was my recovery email address. I did add that, but I didn’t do it in a nice clean way to see that it didn’t work before and it did work after. (Sorry).
So double check that everything is set up in your account settings and try again?
I used the fleetkey website to host my public key which worked fine. I haven’t got around to setting up my Tailscale self-hosting solution (and probably never will now).
I used all of the scopes to register the application in the developer portal as per attached screenshot. Sorry I can’t be more helpful.

image
image1248×1834 352 KB

15

I’ve just managed to surmount this issue myself.
What fixed it for me was adding billing information, even though I set the limit to zero.
I suspect this is what was meant above by “adding an address”, as this billing address is seperate from the account address which made no difference when added.

All a bit janky, as the documentation specifically says you can add this later, but hey, seems to be working now.

16

I’ve still been unsuccessful. It is some sort of OAuth error. Here is my log entry:

TypeError: TeslaFleetApi.init() missing 1 required positional argument: ‘access_token’

I have ChatGPT’s this to try to figure out what’s going on, but I don’t get any log entries that precedes this error to give me the clues I need. Any insights?

17

I ran into this as well and after some digging it seems the upstream library tesla_fleet_api introduced a breaking API change that broke HA integration

makes access_token a required argument

but the integration calcite

doesn’t send it.

18

Filed Tesla Fleet Integration broken by upstream library change · Issue #160582 · home-assistant/core · GitHub

19

Thanks for raising the issue on GitHub, I’ll take a look and try get this resolved ASAP.

20

Still experiencing this issue, same “access_token” issue in the log