⚠️ Breaking change
-
Local Modbus is removed from this integration. It was deprecated in 1.4.0; the BLUETTI Modbus integration reads the same devices on your network. If an entry still had a Modbus connection configured, the update does the following:
- removes its connection settings and its Modbus entities (sensors and battery SoC limit numbers);
- removes the firmware version and "Visit device" link that Modbus had added to the device;
- shows a Repairs notice that names the devices concerned.
Dashboards and automations that used those entities need to point at BLUETTI Modbus's entities instead. Nothing changes for entries without Modbus. The integration no longer installs
bluetti-modbus. Covered by tests; the migration has not yet been run on a real install. (#98)
✨ New
-
Download diagnostics shows how each cloud poll ended. For each device, it lists the recent polls with their outcome (answered, no readings, timeout, HTTP status, cloud error code, DNS or connection failure), duration and attempts, and merges failed polls in a row into failure windows (UTC). Failures ridden out on the last values are included, so a short cloud outage that never reached the entities shows up. The history is kept in memory only and covers at least 24 hours. No extra request is made to the cloud. Covered by tests. (#96, for bluetti-official/bluetti-home-assistant#183 and #81)
-
Four cloud health entities per device, diagnostic and disabled by default:
- Cloud API (connectivity);
- Cloud Response Time (ms);
- Cloud Last Result (how the latest poll ended);
- Websocket Last Message (when the websocket last brought readings).
They update after every poll, failed ones included, and stay available while the cloud fails. The README explains how to enable them and what each result means. Covered by tests. (#97)
Full Changelog: 1.5.12...2.0.0