setting up Tesla Custom Integration #111

JensBiltoft · 2024-06-07T12:59:56Z

JensBiltoft
Jun 7, 2024

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.
Which email should I use

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.

Answered by JensBiltoft

Jun 11, 2024

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.

View full answer

baylanger · 2024-06-07T18:50:16Z

baylanger
Jun 7, 2024

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.

5 replies

JensBiltoft Jun 7, 2024
Author

Ok, so I did a restart... again... and got my tesla http proxy configured with a new domain and got the domain setup in develop.tesla.com using my normal tesla account. That went super smooth.
I still get error when I try to setup the custom integration, so it did not really solve my problem.
I activated the debugging in HA and got this

2024-06-07 22:57:19.598 DEBUG (MainThread) [teslajsonpy.controller] 552 endpoints loaded
2024-06-07 22:57:19.599 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19882 days, 1:02:41
2024-06-07 22:57:19.599 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected
2024-06-07 22:57:19.599 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token
2024-06-07 22:57:19.905 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token
2024-06-07 22:57:19.905 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'server_error', 'error_description': 'Internal server error', 'error_uri': '880fc4e2-5196-4385-ae35-7516e2837f2d-1717793839781. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support'}
2024-06-07 22:57:21.704 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19882 days, 1:02:39
2024-06-07 22:57:21.704 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected
2024-06-07 22:57:21.704 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token
2024-06-07 22:57:21.977 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token
2024-06-07 22:57:21.978 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'server_error', 'error_description': 'Internal server error', 'error_uri': '109e10ad-b3cf-4504-a640-b92da303dc38-1717793841866. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support'}
2024-06-07 22:57:24.805 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19882 days, 1:02:36
2024-06-07 22:57:24.805 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected
2024-06-07 22:57:24.806 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token
2024-06-07 22:57:25.141 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token
2024-06-07 22:57:25.141 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'server_error', 'error_description': 'Internal server error', 'error_uri': 'defb13ac-6408-4801-b709-70f247396dfc-1717793845012. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support'}
2024-06-07 22:57:30.060 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19882 days, 1:02:30
2024-06-07 22:57:30.060 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected
2024-06-07 22:57:30.060 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token
2024-06-07 22:57:30.374 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token
2024-06-07 22:57:30.374 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'server_error', 'error_description': 'Internal server error', 'error_uri': 'f92142b7-9280-4e85-b754-6d2008be3acd-1717793850258. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support'}
2024-06-07 22:57:34.601 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19882 days, 1:02:26
2024-06-07 22:57:34.602 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected
2024-06-07 22:57:34.602 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token
2024-06-07 22:57:34.964 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token
2024-06-07 22:57:34.965 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'server_error', 'error_description': 'Internal server error', 'error_uri': '8d3b93a3-755b-4496-8e18-3d5d1953ec03-1717793854841. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support'}
2024-06-07 22:57:34.966 WARNING (MainThread) [homeassistant.config_entries] Config entry '[email protected]' for tesla_custom integration could not authenticate

Not sure what to make of this.

llamafilm Jun 8, 2024
Maintainer

Do you see anything in the proxy addon logs at this time?

JensBiltoft Jun 8, 2024
Author

No, there is nothing in the proxy addon log😕

llamafilm Jun 10, 2024
Maintainer

Make sure you’ve enable debug logging in the add on config. I’d be really surprised if it doesn’t log anything for a 500 error.

I believe you should be using the email for your Tesla vehicle account, not your developer account. Although I never tested that, I used the same for both.

JensBiltoft Jun 10, 2024
Author

I have restarted the http addon, with debug enabled and I reinstalled the Tesla Custom Integration.
Select fleet API.
entered e-mail and refresh token generated by chrome extension.
Got message that configuration was done. But when I look at the integration, it says configuration failed.

This is all that is in the http addon log after the restart, and it all came before the integration was added.

 * Running on all addresses (0.0.0.0)
 * Running on http://127.0.0.1:8099
 * Running on http://172.30.33.5:8099
[21:58:13] werkzeug:INFO: Press CTRL+C to quit
[21:58:14] INFO: Found existing keypair
[21:58:14] INFO: Testing public key...
curl: (28) Resolving timed out after 2000 milliseconds
Warning: Problem : timeout. Will retry in 1 seconds. 14 retries left.
curl: (28) Resolving timed out after 2000 milliseconds
Warning: Problem : timeout. Will retry in 2 seconds. 13 retries left.
curl: (28) Resolving timed out after 2000 milliseconds
Warning: Problem : timeout. Will retry in 4 seconds. 12 retries left.
HTTP/2 200 
server: nginx
date: Mon, 10 Jun 2024 19:58:27 GMT
content-type: text/plain
content-length: 178
last-modified: Fri, 07 Jun 2024 20:19:58 GMT
etag: "66636b6e-b2"
strict-transport-security: max-age=31536000; includeSubDomains
accept-ranges: bytes

-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEN7weagQ4eb0JTbyDsRllJ8i2mRf8
ySt06pdEMhFnOxoTPfNsFJrONNnIvRVQewIhxQZzAvkqNo2HcCP0zqeIaw==
-----END PUBLIC KEY-----
[21:58:28] INFO: Starting Tesla HTTP Proxy

Do not listen on a network interface without adding client authentication. Unauthorized clients may
be used to create excessive traffic from your IP address to Tesla's servers, which Tesla may respond
to by rate limiting or blocking your connections.
2024-06-10T21:58:28+02:00 [debug] Creating proxy
2024-06-10T21:58:28+02:00 [info ] Listening on 0.0.0.0:443

"Refresh of authentication succeded"

The debugging log in HA when refreshing the Tesla Custom Integration:

2024-06-10 22:53:02.160 DEBUG (MainThread) [custom_components.tesla_custom.config_flow] Running in supervised environment
2024-06-10 22:53:02.267 DEBUG (MainThread) [custom_components.tesla_custom.config_flow] Found addon: c03d64a7_tesla_http_proxy
2024-06-10 22:53:24.072 DEBUG (MainThread) [custom_components.tesla_custom.config_flow] Credentials successfully connected to the Tesla API
2024-06-10 22:53:24.079 DEBUG (MainThread) [custom_components.tesla_custom] Trusting CA: {'subject': ((('countryName', 'TR'),), (('localityName', 'Gebze - Kocaeli'),), (('organizationName', 'Turkiye Bilimsel ve Teknolojik Arastirma Kurumu - TUBITAK'),), (('organizationalUnitName', 'Kamu Sertifikasyon Merkezi - Kamu SM'),), (('commonName', 'TUBITAK Kamu SM SSL Kok Sertifikasi - Surum 1'),)), 'issuer': ((('countryName', 'TR'),), (('localityName', 'Gebze - Kocaeli'),), (('organizationName', 'Turkiye Bilimsel ve Teknolojik Arastirma Kurumu - TUBITAK'),), (('organizationalUnitName', 'Kamu Sertifikasyon Merkezi - Kamu SM'),), (('commonName', 'TUBITAK Kamu SM SSL Kok Sertifikasi - Surum 1'),)), 'version': 3, 'serialNumber': '01', 'notBefore': 'Nov 25 08:25:55 2013 GMT', 'notAfter': 'Oct 25 08:25:55 2043 GMT'}
2024-06-10 22:53:24.127 DEBUG (MainThread) [teslajsonpy.controller] 552 endpoints loaded
2024-06-10 22:53:24.127 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19885 days, 1:06:36
2024-06-10 22:53:24.127 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected
2024-06-10 22:53:24.127 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token
2024-06-10 22:53:24.848 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token
2024-06-10 22:53:24.848 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'server_error', 'error_description': 'Internal server error', 'error_uri': '72bddf3c-ef09-4e7c-86a0-ad961a302bf2-1718052804737. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support'}
2024-06-10 22:53:26.306 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19885 days, 1:06:34
2024-06-10 22:53:26.307 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected
2024-06-10 22:53:26.307 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token
2024-06-10 22:53:26.632 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token
2024-06-10 22:53:26.632 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'server_error', 'error_description': 'Internal server error', 'error_uri': 'a8c96715-6a5d-4bd3-b13f-8d9c96db2c5a-1718052806500. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support'}
2024-06-10 22:53:29.339 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19885 days, 1:06:31
2024-06-10 22:53:29.340 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected
2024-06-10 22:53:29.340 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token
2024-06-10 22:53:29.624 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token
2024-06-10 22:53:29.625 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'server_error', 'error_description': 'Internal server error', 'error_uri': '96a7775e-4a81-48f3-a25d-9727ec8f9263-1718052809518. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support'}
2024-06-10 22:53:33.668 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19885 days, 1:06:27
2024-06-10 22:53:33.669 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected
2024-06-10 22:53:33.669 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token
2024-06-10 22:53:33.960 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token
2024-06-10 22:53:33.961 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'server_error', 'error_description': 'Internal server error', 'error_uri': '26ebe9e1-e23c-4932-9641-57e5d8f49102-1718052813844. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support'}
2024-06-10 22:53:39.130 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19885 days, 1:06:21
2024-06-10 22:53:39.130 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected
2024-06-10 22:53:39.130 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token
2024-06-10 22:53:39.430 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token
2024-06-10 22:53:39.430 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'server_error', 'error_description': 'Internal server error', 'error_uri': '50dec1c6-23a8-4a2a-b797-975644225f0f-1718052819316. For more information, visit: https://developer.tesla.com/docs/fleet-api#help-and-support'}
2024-06-10 22:53:39.432 WARNING (MainThread) [homeassistant.config_entries] Config entry '[email protected]' for tesla_custom integration could not authenticate
2024-06-10 22:53:51.554 DEBUG (MainThread) [homeassistant.components.sun.entity] sun position_update@2024-06-10T20:53:51.554156+00:00: elevation=-4.87 azimuth=326.61

An interesting observation. the token expired on 01-01-1970 00:00:00 that may give some indication on where to look for the problem?

darek-margas · 2024-06-08T03:36:54Z

darek-margas
Jun 8, 2024

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.

0 replies

JensBiltoft · 2024-06-11T11:55:10Z

JensBiltoft
Jun 11, 2024
Author

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.

5 replies

efficiencynerd Jun 12, 2024

I just spent so much time trying to figure this out, this solution worked immediately. The docs really need to be updated. Thanks!

llamafilm Jun 12, 2024
Maintainer

This is explained in the docs. If you have an idea to improve it, PRs are welcome.

efficiencynerd Jun 12, 2024

This is explained in the docs. If you have an idea to improve it, PRs are welcome.

My apologies, the docs for this addon do explain this; however, my issue was with the Tesla Custom Integration, which states

To use the component, you will need an application to generate a Tesla refresh token:

Android: Tesla Tokens

iOS: Auth App for Tesla

TeslaFi: Tesla v3 API Tokens

Chromium/Edge: Chromium Tesla Token Generator

which is no longer true, we must create a refresh token using this Tesla http proxy addon.

llamafilm Jun 12, 2024
Maintainer

Agreed, that part needs some work. alandtse/tesla#879

baylanger Jun 12, 2024

I wasn't too sure what was the consensus, I never did the PR but with the info in here - I'll give a bite this week.

rubin110 · 2024-07-05T06:12:26Z

rubin110
Jul 5, 2024

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 Token expiration in -19910 days, 22:49:49 errors. I am using the refresh token provided by the http proxy.

1 reply

rubin110 Jul 10, 2024

I'm embarrassed to say my issue was rooted in not properly copying my refresh token. I'm back up an running now.

JensBiltoft · 2024-10-21T05:46:05Z

JensBiltoft
Oct 21, 2024
Author

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: ***@***.***>

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

setting up Tesla Custom Integration #111

{{title}}

Replies: 5 comments 11 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

setting up Tesla Custom Integration #111

Replies: 5 comments · 11 replies

JensBiltoft Jun 7, 2024 Author

llamafilm Jun 8, 2024 Maintainer

JensBiltoft Jun 8, 2024 Author

llamafilm Jun 10, 2024 Maintainer

JensBiltoft Jun 10, 2024 Author

JensBiltoft Jun 11, 2024 Author

llamafilm Jun 12, 2024 Maintainer

llamafilm Jun 12, 2024 Maintainer

JensBiltoft Oct 21, 2024 Author

Replies: 5 comments 11 replies

JensBiltoft Jun 7, 2024
Author

llamafilm Jun 8, 2024
Maintainer

JensBiltoft Jun 8, 2024
Author

llamafilm Jun 10, 2024
Maintainer

JensBiltoft Jun 10, 2024
Author

JensBiltoft
Jun 11, 2024
Author

llamafilm Jun 12, 2024
Maintainer

llamafilm Jun 12, 2024
Maintainer

JensBiltoft
Oct 21, 2024
Author