setting up Tesla Custom Integration #111
-
Hi Just a quick question. After I have setup the Tesla http proxy, and enroled the key in my vehicle, I need to setup the Tesla Custom Integration and configure it to use Fleet API. It then asks for email and refresh token. Either the one I use on my normal tesla user account, or the one I used when I created the third party application on developer.tesla.com? Same question for the refresh token. Should I use my normal account or the one connected to the tesla-http-proxy I have tried both, and my home assistant reports either authentication failed or configuration failed. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 11 replies
-
For the developer site, perhaps you should have login using your current Tesla account (email / password) instead of creating an account specific to the developer site. That would have made things easier…. Since you’ve created a different developer account, you could still login using your current Tesla “car” account and start over the configuration using the same email address all over the place. Otherwise, if you keep both logins; for both the Tesla http proxy and the integration - I believe you need to use your Tesla email address but to be honest, I’m not sure. I suggest you start over using the same account. Perhaps someone will reply with the right way to make this work. |
Beta Was this translation helpful? Give feedback.
-
This is exactly what I had when I tried. Got key in the car, proxy was sort of happy, then this expired token which is 20.000 days behind. Didn't figure out what's wrong, uninstalled instead and waiting till someone solves this. |
Beta Was this translation helpful? Give feedback.
-
I figured out what the problem is!!! It seems there is a new format of the tesla tokens that is much shorter. After using this token, I have full access to my Car. |
Beta Was this translation helpful? Give feedback.
-
I'm hitting this issue now. I don't know if it was today or yesterday, but the integration is reporting an issue with authentication. When I provide all of the required fleet info, I see |
Beta Was this translation helpful? Give feedback.
-
Hi
It is still working fine for me.
Best Jens
Hent BlueMail til Android
Den 19. okt. 2024 23.50, fra 23.50, JVoss-glitch ***@***.***> skrev:
…
@JensBiltoft Does the API still works for you? For me the Duck DNS,
NGINX and Tesla HTTP Proxy are running well. Though after filling in
the refresh token with the Tesla HTTP Proxy it will sign in succesfully
though the tesla custom integration will keep noticing "Failed setup,
will retry: all connection attempts failed" with no further logging.
--
Reply to this email directly or view it on GitHub:
#111 (comment)
You are receiving this because you were mentioned.
Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
I figured out what the problem is!!!
It turns out that you cant use the refresh token generated by any of the tools mentioned in the Tesla Custom Integration, or the Chrome extension that uses https://auth.tesla.com/
Instead you must use the Tesla HTTP proxy addon web-interface to generate a new refresh token same way as you did when enrolling your public key in the vehicle
It seems there is a new format of the tesla tokens that is much shorter.
After using this token, I have full access to my Car.