Unable to authentificate after configuring Fleet API - Fleet API needs the token from the HTTP Proxy

[madsdyd]

Is there an existing issue for this?

• I have searched both the existing open issues & recently closed issues and did not find a duplicate of this issue.

I have read about the Fleet API and understand I may need to use it

• I understand issues relating to read only commands will be auto closed if not using the Fleet API.

Version of the Tesla component

v3.24.0

Version of the Tesla car software

2024.20.9 and 2024.20.1

Model

Model 3 and Model 3

Current Behavior

After installing the Tesla HTTP Proxy and trying to configure the Tesla Integration to use the Fleet API, I can not authentificate in the Tesla Integration. It completes the setup/configuration process with "Created the configuration for [email protected])" (in danish) but the cars are not shown in the list, instead an error is shown: "No devices or entities" "Configuration failed: Could not authenticate" (Again, in Danish).

Disabling the Fleet API allows authentification to complete.

Turns out, per this message: #1020 (comment) that when enabling the Fleet API, the refresh token is now the one, one can get from the Tesla HTTP Proxy, not the one you should get from any of the APPS or similar. I think this could be made clearer in the config flow, and help save a lot of us a lot of time :-)

Expected Behavior

A hint in the GUI about what token to use, when enabling the Fleet API.

Debug logs

I do not think logs are relevant in this case.

Config entry '[email protected]' for tesla_custom integration could not authenticate

There are no "new"

Anything else?

Thank you for a great integration.