Skip to content

v2.0.0

Choose a tag to compare

@chinezbrun chinezbrun released this 06 Sep 17:29
· 3 commits to main since this release
90338b7

Release note

Version 2.0.0 focuses on improving serial communication efficiency and robustness, particularly on systems with multiple batteries, while removing deprecated functionality and simplifying the codebase.

Improvements

  • Power/status data for all batteries is now retrieved using a single consolidated pwr command instead of one pwr N transaction per battery.
  • Reduced serial communication overhead and overall polling round-trip time.
  • On a 4-battery system, average polling round-trip time was reduced from approximately 1.2 s to 0.9 s (~25%). The benefit becomes increasingly significant on larger battery banks.
  • Improved retry handling for invalid or corrupted PWR and BAT data.
  • Improved MQTT handling when previous cell data is incomplete.
  • Removed obsolete code and diagnostics and cleaned up the internal code structure.

Compatibility

The following deprecated fields have been removed:

  • soh_st
  • coul_st
  • heater_st
  • bat_events
  • power_events
  • sys_events

The following obsolete counters have also been removed:

  • bat_events_no
  • pwr_events_no
  • sys_events_no

Integrations that directly use these fields or counters may require adjustment.

MariaDB

Existing v1.x databases remain compatible with v2.0.0. Deprecated columns may remain in the existing pwr_data table and will simply no longer be used.

No database migration or recreation is required when upgrading from v1.x. Removing the deprecated columns is optional.

New installations should use the updated v2.x MariaDB initialization SQL.

Upgrade

Upgrading from v1.1.1 to v2.0.0 is straightforward:

  • Replace the existing pytes_serial.py file with the v2.0.0 version.
  • Keep the existing pytes_serial.cfg configuration file; no configuration changes are required.
  • Existing MariaDB databases remain compatible and do not need to be recreated or migrated.
  • For new installations, use the updated v2.x MariaDB initialization SQL.
  • If you use custom integrations that rely on the removed fields or counters listed above, update them accordingly.