Fixed:
- A token the cloud rejects is refreshed before you are asked to sign in again. The BLUETTI cloud has been seen rejecting an access token its own login server had issued for 31 days, less than 3 days later - with a refresh token at hand. The integration now uses that refresh token first (at most once an hour) and reloads itself with the new token; only if that fails does the "reconfigure" notice appear. An info line in the log records how far before its announced expiry the token was rejected. (#56)
- A lone gateway error no longer aborts the sign-in flow. Listing the account's devices during (re)authentication is retried once on HTTP 502/503/504 or a timeout, as the polling already is since 1.4.1. (#56)
Internal:
- The setup debug line includes the token's
expires_at(a timestamp, never a token value). (#56)