-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Failing to Authenticate on 2024.3 #212
Comments
Please enable the debug log, run the process again and share the log |
same for me: the error is: |
Fixed: |
Do you still have the logs? This is a standard HA key and this one is used everywhere... What is youre HA version? |
I've deleted and reinstalled now and it is fine. |
Seems to be occurring here too since the last update (2024.3.3?) |
Thanks, This is not related to 2024.3.3.
Workaround currently: Delete integration in HA (not in HACS) and re-add integration after a restart. |
This is the error I got now This error originated from a custom integration. Logger: custom_components.mbapi2020.oauth Error requesting: https://id.mercedes-benz.com/as/token.oauth2 - 0 - {"error_description":"unknown, invalid, or expired refresh token","error":"invalid_grant"} |
In what context did you got this error? HA-Upgrade / Restore? |
I ran into the same problem after upgrading to 24.3.3. EDIT: retried few hours later and now works fine |
Hmm, I understand why the auth tokens expire and may need to be refreshed after an update, but why does authentication still not work after the reconfigure task completes successfully? |
Still unable to re-authenticate in v0.13. |
I have made one change in v0.14-beta1 and try to read from the HA config store first instead of using the file cache... But still testing it on my instances. |
I noticed this in the beta release notes. Not sure whether it is relevant but it sounds superficially related: https://developers.home-assistant.io/blog/2024/04/25/always-reload-after-successful-reauth-flow/ |
Sounds related but we want the reload after the auth issue. I changed the flow a little bit in the latest beta of the component. Now I try to load the tokens from the cache instead of the file system. |
Problem to create new hub. German Customer with *.com Email-Adress. Only can create a Hub for North America. But there it can´t find my car via VIN. The log file throw this error: Error requesting: https://bff.emea-prod.mobilesdk.mercedes-benz.com/v1/login - 0 Regards, Dirk |
I have a german *.de E-Mail-Adress and exactly the same problem. Maybe the authentication-server of Mercedes is temporarily down? Regards, Michael |
Yes, thats a option. I downgrade the integration to Version 0.12 and the problem was still there. I will try it tomorow again... |
Hi Dirk some issue here started today in the morning. Seems to be a general issue. |
see here #231 |
Will close this one. The first issue was a HA-core bug. |
The problem
My HA installation was failing to update to 2024.3 so I've redeployed from scratch and then restored from backup and then waas able to upgrade to 2024.3.
I get a message that I need to reauthenticate MercedesMe 2020, I get the email with the code and enter it but it fails to authenticate with the following error in the HA logs.
This error originated from a custom integration.
Logger: custom_components.mbapi2020
Source: custom_components/mbapi2020/init.py:63
integration: MercedesME 2020 (documentation, issues)
First occurred: 22:36:27 (2 occurrences)
Last logged: 22:37:21
Authentication failed. Please reauthenticate.
What version of MBAPI2020 do use?
v0.12.0
What was the last working version of MBAPI2020?
v0.11.1
What type of installation are you running?
Home Assistant OS
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: