Failing to Authenticate on 2024.3 about mbapi2020

[ReneNulschDE]

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.

[tbkon3]

Fixed:
Deleted the old "Hub", reboot and reconfigured, all ok!!!

[74Rog]

I've deleted and reinstalled now and it is fine.
It did start to get a bit weird as I had multiple reconfigure buttons in Devices and Services but all good now.

[ReneNulschDE]

Please enable the debug log, run the process again and share the log

[tbkon3]

same for me: the error is:
[%key:common::config_flow::abort::reauth_successful%]

[ReneNulschDE]

same for me: the error is:
[%key:common::config_flow::abort::reauth_successful%]

Do you still have the logs? This is a standard HA key and this one is used everywhere... What is youre HA version?

[churchofnoise]

Seems to be occurring here too since the last update (2024.3.3?)

[ReneNulschDE]

Thanks, This is not related to 2024.3.3.

• The multiple button problem is on my list.
• Reauth-Problem: I assume that this happens after an upgrade of HA in an HAOS environment. Whenever the backup is not created near time (<10min) before the upgrade than there is a high risk that invalid keys are stored in the backup. (Reason: the auth and reauth keys are vaild for 120min only and are renewed every 110min)

Workaround currently: Delete integration in HA (not in HACS) and re-add integration after a restart.

[janwilms]

This is the error I got now

This error originated from a custom integration.

Logger: custom_components.mbapi2020.oauth
Source: custom_components/mbapi2020/oauth.py:312
integration: MercedesME 2020 (documentation, issues)
First occurred: 08:48:43 (3 occurrences)
Last logged: 08:52:47

Error requesting: https://id.mercedes-benz.com/as/token.oauth2 - 0 - {"error_description":"unknown, invalid, or expired refresh token","error":"invalid_grant"}

[ReneNulschDE]

In what context did you got this error? HA-Upgrade / Restore?

[Marijncouckuyt]

I ran into the same problem after upgrading to 24.3.3.
It fails to reauth after removing the integration and reinstalling it.
Gives 'unknown error'

EDIT: retried few hours later and now works fine

[j9brown]

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?

[j9brown]

Still unable to re-authenticate in v0.13.

[j9brown]

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/

[ReneNulschDE]

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.