MaxGrmm/EF-PowerOcean-TcpModbus v2.9.1-beta.4 on GitHub

System Alerts sensor naming the active System State 2 bits as documented in EcoFlow's Open Modbus Protocol, or none.
Nothing is read from or written to the inverter, the heartbeat included, until it shows the entry's serial number. A different serial raises a repairs issue.
Diagnostic sensors with the device's own lifetime energy totals, such as Solar Yield Total (Device), next to the checked totals. They have no state class, so they never feed the Energy dashboard.
A repairs issue when an energy total has been held for more than 24 hours while the inverter reports another value, offering to take the inverter's value, or to report it with a filled-in bug report and the diagnostics.
The diagnostics download has an energy section: every counter as published and as the device reports it, when each total was last accepted, which totals are held, the daily snapshots and the maximum powers the totals are checked against.

Modbus requests time out after 3 s instead of 20 s, and a whole poll after 12 s.
Processing errors make the entities unavailable instead of publishing an empty update.
CI type-checks the integration with mypy in strict mode, lints with a wider set of ruff rules, and pins every GitHub Action to a commit.

A reconnect no longer holds the Modbus connection during its backoff, which stalled writes and unloading for up to two minutes.
Self-use Mode and Intelligent Mode no longer both turn on for an undocumented operating status.
Sensors shown without decimals round their value instead of cutting it off, so 1499.7 W shows as 1500 W.
A lifetime energy total whose first read is 0 no longer holds the real value back for days. The 0 is shown but not trusted, and the first real value is taken once the next read follows it as a counter would (#169).
An energy total held at 0 by an earlier version while the inverter reports its real total is corrected once the inverter's total rises in step with its daily counter (#169).
An energy total restored from a state file written by 2.4.0 is no longer frozen for good when its first poll after loading is held, for example because that poll came back without the energy registers (#169).

What's Changed

Improve code quality checks and CI by @windmark in #166
Bump pytest-homeassistant-custom-component from 0.13.368 to 0.13.371 by @dependabot[bot] in #167
Extend test coverage by @windmark in #168
Update pymodbus requirement from <4,>=3.15.0 to >=3.16.1,<4 by @dependabot[bot] in #170
Bump modbus-connection from 4.12.3 to 4.12.4 by @dependabot[bot] in #172
Bump pytest-homeassistant-custom-component from 0.13.371 to 0.13.372 by @dependabot[bot] in #171
Fix energy totals held after a bad first read or old state by @windmark in #173
Correct energy totals held at 0 and offer to take long-held totals by @windmark in #174

Full Changelog: v2.9.1-beta.1...v2.9.1-beta.4