🐛 Fixed
- A cloud that cannot be reached no longer asks you to sign in again. When BLUETTI rejects the access token, the integration tries a refresh before sending you to the sign-in page - but any failure of that refresh counted as a refused one, so an account whose DNS was failing was asked to re-authenticate every few hours while its credentials were fine. A refresh now has to say something about the credentials before it is treated that way: a token the BLUETTI sign-in server refuses still sends you through re-authentication, while an unreachable cloud, a timeout or a server error just fails the poll, which Home Assistant retries on its own. The daily token check follows the same rule and no longer raises the "OAuth Expired" notice for a refresh it could not even attempt. Reported on an account in the UK, in #65.
Full Changelog: 1.5.1...1.5.2