Fix InvalidSessionException treated as permanent auth failure

[arpena]

Summary

InvalidSessionException inherits from UnauthorizedException, so it was being caught by the (AuthenticationException, UnauthorizedException) handler which raises ConfigEntryAuthFailed. This permanently disables the integration and marks all entities as unavailable, requiring user re-authentication.

Problem

When the router invalidates a session (e.g., due to a concurren login to the web interface using the same client IP as the Home Assistant server), the integration receives XMO_INVALID_SESSION_ERR. This is a transient condition, not a credentials problem. However, due to the exception hierarchy (InvalidSessionException → UnauthorizedException), it was treated as a permanent auth failure.

Fix

Catch InvalidSessionException explicitly before the UnauthorizedException handler and raise UpdateFailed instead of ConfigEntryAuthFailed. This allows the coordinator to retry on the next polling cycle and recover automatically.

Testing

Reproduced the issue by logging into the router web interface during a poll cycle. Before the fix, the integration died permanently. After the fix, it logs a warning and recovers on the next poll.

[iMicknl]

Thanks @arpena! We might want to fix this in the underlying library, what do you think? It seems that this is a transient error indeed, not an authentication error.

[arpena]

Hi @iMicknl ! You are saying that we should change InvalidSessionException to inherit from BaseSagemcomException in exceptions.py?

[iMicknl]

Yes!

[arpena]

Closing in favor of fixing this at the library level: iMicknl/python-sagemcom-api#520

The root cause is that InvalidSessionException inherits from UnauthorizedException, so the fix belongs in python-sagemcom-api by changing the exception hierarchy. Once that's merged, this integration-side workaround is no longer needed.