Replies: 7 comments 8 replies
-
|
I have the same issue. I've removed the integration due to the (re-)authentication problem and added it again. After the adding process (using proxy, adding refresh token) the integration says "success". But no car is added and the integration remains in "could not authenticate" error. |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue since today. I have the last version of the integration |
Beta Was this translation helpful? Give feedback.
-
|
I thought I have found the problem. You must use the second token of tesla tokens. The first one is not suitable for the integration |
Beta Was this translation helpful? Give feedback.
-
|
I reinstalled everything and I'm up and running again. Hopefully this isn't a pattern. |
Beta Was this translation helpful? Give feedback.
-
|
The reauth flow is currently broken. Instead you need to delete the integration and add it back again. |
Beta Was this translation helpful? Give feedback.
-
|
I tried deleting (rebooting), re-adding (rebooting) and it still won't authenticate using the new method. Mine's a mid-2020 Model 3 - could this be the issue? I'm keen to get it back up and running in the next 30 days before I lose all my entity history. |
Beta Was this translation helpful? Give feedback.
-
|
So, today I tried to switch over to proxy.
-----BEGIN PUBLIC KEY----- Do not listen on a network interface without adding client authentication. Unauthorized clients may Then, deleted token from core.config_entries, this caused re-authentication. ` 2024-04-01 16:00:25.363 DEBUG (MainThread) [custom_components.tesla_custom] <ssl.SSLContext object at 0x7f2669c82050> 2024-04-01 16:00:25.380 DEBUG (MainThread) [teslajsonpy.controller] 552 endpoints loaded 2024-04-01 16:00:25.380 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19815 days, 7:59:35 2024-04-01 16:00:25.380 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected 2024-04-01 16:00:25.380 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token 2024-04-01 16:00:29.365 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token 2024-04-01 16:00:29.365 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'login_required', 'error_description': 'Login 2024-04-01 16:00:30.459 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19815 days, 7:59:30 2024-04-01 16:00:30.459 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected 2024-04-01 16:00:30.459 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token 2024-04-01 16:00:31.144 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token 2024-04-01 16:00:31.144 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'login_required', 'error_description': 'Login 2024-04-01 16:00:33.353 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19815 days, 7:59:27 2024-04-01 16:00:33.354 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected 2024-04-01 16:00:33.354 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token 2024-04-01 16:00:35.325 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token 2024-04-01 16:00:35.325 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'login_required', 'error_description': 'Login 2024-04-01 16:00:39.714 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19815 days, 7:59:21 2024-04-01 16:00:39.714 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected 2024-04-01 16:00:39.714 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token 2024-04-01 16:00:40.417 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token 2024-04-01 16:00:40.417 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'login_required', 'error_description': 'Login 2024-04-01 16:00:40.417 WARNING (MainThread) [homeassistant.config_entries] Config entry '[email protected]' for tesla_custom integration could not authenticate I deleted integration, re-downloaded from hacs, re-added integration, went over the same config flow and always the same. Without ticking proxy, I was able to re-authenticate with old token. What do I miss? |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried this? You must use the second token of tesla tokens. The first one is not suitable for the integration I posted it days ago. If you use the first token of tesla token app the integration connects to tesla account but you can't see anything. You have to logoff and login with the second token of the app. |
Beta Was this translation helpful? Give feedback.
-
When I set up proxy (using container, not addon), I used previous version which went over onboarding and also provided token, just one token. Does it mean I can re-use token which works without proxy? |
Beta Was this translation helpful? Give feedback.
-
|
Just tested - no joy, refresh-token working directly does not help via proxy. |
Beta Was this translation helpful? Give feedback.
-
|
Also fresh token from tesla-auth, for fleet api does not work. |
Beta Was this translation helpful? Give feedback.
-
|
I am having the same issue here. I have also noted that the Tesla Tokens app won't let me login with what I know are the correct details now. Additionally the Tesla Tokens app doesn't show up in the Android app store anymore so I have no idea what's going on there. Either way, I can't get the integration to authenticate using the refresh token I have so I think the app isn't refreshing those tokens when requested and hence I am trying to use the same refresh token again. |
Beta Was this translation helpful? Give feedback.
-
|
I think it is a bug, why does it refresh token with negative time to lapse? |
Beta Was this translation helpful? Give feedback.
-
|
I see that number a lot, it shouldn't be a problem. I think this is the default value from the API because teslajsonpy omits the expiration date. @IanK6449 the new style tokens should be fairly short and begins with NA_ or EU_. I don't think Tesla Tokens has been updated in a long time, so it probably doesn't support Fleet API. I suggest using the proxy addon to create the token. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I realised afterwards that it was the refresh token generated by the Proxy that I should be using. All seems to be working perfectlty now so thank you for building all this stuff :-) |
Beta Was this translation helpful? Give feedback.
-
I got the integration working with the add-on proxy server when it came out. Last night I installed a Tesla software update to my car and it seems around the same time my ha integration stopped working. Now it seems there is an authentication issue with my integration.
HA keeps saying the integration fails to start, sends me to the re-Auth flow, which says it successfully authenticates, but the integration still fails to start.
Anyone else seeing this? All of my entities show "unknown" status.
Beta Was this translation helpful? Give feedback.
All reactions