llamafilm
commented
7 months ago Thank you for the detailed report. Would you please raise this on the Tesla integration instead? https://github.com/alandtse/tesla
I’m pretty sure the problem is on that side with the reauth config flow holding on to the old token.
Describe the bug Tesla integration was configured via Proxy and was running fine for about the day, but after restart of the server can't get it running again. Error in the logs below
To Reproduce Steps to reproduce the behavior:
Expected behavior Tesla integration to connect via Proxy
Screenshots
Environment (please complete the following information):
Logs: 2024-03-19 18:47:43.738 DEBUG (MainThread) [custom_components.tesla_custom.config_flow] Credentials successfully connected to the Tesla API 2024-03-19 18:47:43.739 DEBUG (MainThread) [custom_components.tesla_custom] <ssl.SSLContext object at 0x7fb857b29fd0> 2024-03-19 18:47:43.753 DEBUG (MainThread) [teslajsonpy.controller] 552 endpoints loaded 2024-03-19 18:47:43.753 DEBUG (MainThread) [teslajsonpy.connection] Token expiration in -19802 days, 5:12:17 2024-03-19 18:47:43.753 DEBUG (MainThread) [teslajsonpy.connection] Oauth expiration detected 2024-03-19 18:47:43.753 DEBUG (MainThread) [teslajsonpy.connection] Refreshing access token with refresh_token 2024-03-19 18:47:44.780 DEBUG (MainThread) [teslajsonpy.connection] Unable to refresh sso oauth token 2024-03-19 18:47:44.780 DEBUG (MainThread) [teslajsonpy.connection] Auth returned {'error': 'login_required', 'error_description': 'Login required', 'referenceID': '7175ac84-6357-4b99-ad60-14c283d63ae6-1710845264535'} Additional context Add any other context about the problem here.