🐛 Fixed
- The integration no longer gets stuck on "initialising" when the BLUETTI cloud goes quiet. Setting the entry up waits for the websocket connection, and a failed attempt used to retry inside that wait instead of behind it - so for as long as the cloud stayed unreachable, setup never finished. The entry sat on "initialising" with no Reload in its menu, because Home Assistant only offers reload once setup has finished, and nothing but restarting Home Assistant cleared it. One owner spent three hours there, and needed no sign-in afterwards: his session had been valid the whole time. Setup now makes a single attempt and leaves the retries running behind it, so your entities come back whatever the cloud is doing - the readings come from the 30-second poll, not from the websocket. (#68, #65)
- And every failed attempt used to leak a connection, until new ones had to queue for a free slot and timed out five minutes later - which is why those retries crawled instead of running on their thirty-second backoff. Each attempt now closes what the last one left open.
📦 Dependencies
pybluetti0.2.5 → 0.2.6, which carries both fixes above, plus two smaller ones on the same path: the reconnect backoff is reset once a connection succeeds, so it is per outage rather than cumulative, and disconnecting also cancels a pending reconnect.
Full Changelog: 1.5.3...1.5.4