Integration gets stuck when token refresh fails

[msvisser]

Integration gets stuck when token refresh fails

[msvisser]

I've seen some weird behaviour from the OAuth2 endpoint, where it sometimes just returns a 400 Bad Request response on a token refresh causing the integration to get stuck. I have a workaround planned that will be in the next version, which allows you to manually re-authenticate, but I'm investigating the underlying problem.

Issue #20 is probably also related to this problem.

[msvisser]

In version v0.1.10 I have added in a workaround which allows you to re-authenticate from the Home Assistant user interface. The integration should now also log the error, which can be used for further debugging.

[HanSyt]

Solved it, noticed that there was version 1.9, installed that one - didn't help. Added a new instance of the integration,filled out user name and password and it was back online.

[dsgepers]

In version v0.1.10 I have added in a workaround which allows you to re-authenticate from the Home Assistant user interface. The integration should now also log the error, which can be used for further debugging.

Can you elaborate on this re-authenticate from the HA UI?

I cannot seem to find this feature in v0.1.12

[msvisser]

The re-authentication feature will only show up if the current token cannot be refreshed. In that case a message will show up on the Remeha Home integration and it will allow you to login again.

If you are running in to this issue, please post the error log from the Remeha Home integration.

[dsgepers]

I was, however, the issue was unrelated in the end. My instance has having issues with connecting over IPv6. Disabeling it resolved this (and other) issue(s).

Thanks for taking the time to reply though! :-)