formal elm
I'm in the process of setting up a new HA instance and wanting to use the Tesla Fleet integration.
I've followed the bouncing ball, have my Fleet API setup done, and attempt to link the account:
Then I get a very quick "Loading next step" and then an error.
Thoughts on how to diagnose?
(on my previous/current HA instance, I've only used the Tesla PW integration but the new one needs to use Fleet for control)
formal elm
@timid jetty any thought on debugging this ? Sorry to ping
timid jetty
Hrm, thats not a useful error
I don't mind the ping, I never would have seen this otherwise. Can you check your logs and see if you have anything tesla_fleet related?
formal elm
something that makes me go hmmm
File "/usr/src/homeassistant/homeassistant/components/tesla_fleet/config_flow.py", line 91, in async_oauth_create_entry
await self.api.partner_login(
implementation.client_id, implementation.client_secret
)
File "/usr/local/lib/python3.13/site-packages/tesla_fleet_api/tesla/fleet.py", line 194, in partner_login
raise ValueError(f"Partner login failed: {error_data}")
ValueError: Partner login failed: {'error': 'invalid_scope', 'error_description': 'The client is not allowed to access the requested resource.', 'referenceID': '680fed4f-5878-4eae-afbb-25b445f7e311-1759120145746. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support'}[0m
I'll go back thru the developer API setup and wipe and start again
formal elm
I found the fault. I don't have a Tesla vehicle, so I never bothered ticking the 4 vehicle rights as per image. I went back and granted that, and it worked.
formal elm
so @timid jetty it looks like the initial setup either makes an API call that needs vehicle API as well as the "profile" data, and the return code where that's not granted doesn't seem being handled.