ℹ️ This version (1.0.3) has made significant changes to the OAuth access token. It is recommended to remove the BLUETTI integration and add it again. If you do not reconfigure the integration, you will not receive real-time device messages from the BLUETTI cloud.
ℹ️ It is recommended to connect a maximum of 3 Bluetooth devices at the same time.
✨What’s new
- Add French translation and README. Thanks @chpego.
- Implement BLE controller mode for most devices for #5, which supports three platforms: x86, ARM and Raspberry Pi.
- New models support for EB3A, AORA200V2, AP200, and AP300V2.
- Split "Grid Input Power" into "Grid Import Power" and "Grid Export Power".
🚀Improvements
- On OAuth login, return the optimal cloud endpoint for the account to reduce “OAuth expired” errors when accessing the cloud across regions. Endpoint selection depends on the account’s registration country—please ensure it is set correctly. Ideally, the registration country matches the country where the energy storage device is located.
- Negotiate the WebSocket heartbeat interval with the cloud. The default interval is changed from 10s to 60s. The heartbeat task now starts only after a
CONNECTEDresponse is received from the cloud. - Implemented stricter authorization checks for real-time device message subscriptions, ensuring each account can only access messages from devices it is authorized to manage. This hardening was identified and resolved proactively during our internal security review. No user data was affected, and no action is required from users.
🐞Bug fixes
- Fixed an issue where the integration did not attempt a token refresh when the cloud reported that the token had expired.
- Fixed an issue where the cloud did not return a new refresh token when a token refresh was attempted.
- Fixed an issue where the WebSocket real-time messages could be occasionally lost in cluster deployments.