Releases: bluetti-community/pybluetti
Releases · bluetti-community/pybluetti
Release list
v0.2.1rc1
Pre-release - for testing
A real PEP 440 pre-release: pip install pybluetti will not pick this up. Test with:
pip install pybluetti==0.2.1rc1
Fixed
_run()was leaving the abandoned websocket connection open on every exit path except a token-expiry (msgCode 805) - anApplicationRuntimeException, a plain ERROR/CLOSE message, or an unexpected crash all skippedclose(). This let a concurrently-running heartbeat send slip past its own is-it-closed check and fail against the transport, reported asFailed to send heartbeat: Cannot write to closing transportrepeating on every ~30s reconnect cycle - confirmed in production on 0.2.0 itself, via bluetti-official/bluetti-home-assistant#145._run()now closes the connection itself as soon as it decides to abandon it.
See the CHANGELOG for the full technical writeup.
v0.2.0
StompClient reliability fixes
- Fixed an orphaned heartbeat task on every reconnect that follows a dropped or rejected connection - the previous connection's heartbeat task was never cancelled before starting a new one, only the token-expiry (msgCode 805) path did that.
- Fixed the same full traceback being re-logged on every retry of a persistently repeating STOMP ERROR frame, forever.
- Added
StompClient(on_error=...), invoked for any ERROR frame the cloud sends back other than a token-expiry, so a caller can react to a persistent error distinctly from an ordinary dropped connection.
Breaking: handler, on_auth_expired, and the new on_error are now keyword-only.
See the CHANGELOG for details. Root-caused from a real user report: bluetti-official/bluetti-home-assistant#145.
v0.1.2
v0.1.1
- Adopted
mypy --strictacross the whole package, fulfilling the "strict-typing" requirement of Home Assistant's Platinum integration quality scale. - Moved to the
bluetti-communityGitHub organization (waspybluetti); no change to the PyPI package name or install command.
See CHANGELOG.md for details.