-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication failed since v3.20.2 #898
Comments
Rolling back to 3.19.11 solve the issue. |
Same here, updated to 3.20.2 and it stopped working. (Model 3, 2019) Edit: I am on 2024.3.0 |
Same for me. Updated to 3.20.2 yesterday evening to find a notification this morning that I needed to re-authenticate. Authentication went ok (without using fleet api or a proxy), but then the integration failed to setup. Downgrading to 3.19.11 fixed it (2022 MY) |
FYI |
The stacktrace in the initial bug seems more related to a bug |
This comment was marked as duplicate.
This comment was marked as duplicate.
Same issue here, but I can't reauthenticate even on the old version anymore :( |
Generate a new Refresh token and it should work. |
@jmcollin78 please describe your environment. Are you running Home Assistant OS, supervisor, etc.? Are you running the Tesla HTTP Proxy addon? |
Interesting...I've tried that yesterday via phone and the token was accepted, but there was an issue with the reauthentication later. |
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Sonoff
|
Thanks. The exception shown in your log was a bug which is now fixed. But this is still going to fail because you have selected "Use API Proxy" in the Tesla component, and you do not have the Tesla HTTP Proxy addon installed. |
If I remember well there was one option "use Fleet API" or something like that. Should I check this checkbox ? If yes that is major compatibility break and should be reported ? Ok I will read the Readme and try to understand what should I do. EDIT: I'm not concerned by Fleet API (Model 3 03/2022). So I did not check the "Use fleet API" checkbox and I don't remember to have a "Use API Proxy" option. So I don't understand what I should do. |
I had the above but rollback to 3.19 rectified issue. Then, I upgrade to 3.20.3, failed again, rolled back to 3.19 and this time is deauthenticated permanently. 3.19 offers re-authentication but 3.20 does not. Disabled for now, may actually come back once i setup proxy but writing here to flag that maybe 3.20.3 isn't a fix. |
@jmcollin78 @alandtse this is not solved, please do not close this ticket. |
I didn't close the ticket. The issue is still there. |
I have the proxy all set up but i still get the the "unknown error" .. any help appreciated `Logger: aiohttp.server Error handling request |
Since the installation of release 3.20.2, the authentication failed. I try to renew the Refresh Token but I still have issue in the log:
and
Previous working release was 3.19.11. I will rollback.
The text was updated successfully, but these errors were encountered: