v0.9.0b2 - VPP battery registers swapped on SPH
Pre-release
Pre-release
Release Notes
v0.9.0b2
- Fix: VPP battery charge/discharge today swapped on SPH V2.01 profiles (Issue #300):
battery_charge_todayandbattery_discharge_todayfrom VPP registers 31202 and 31206
were labelled the wrong way round onsph_3000_6000_v201andsph_7000_10000_v201.
VPP Protocol V2.01 specifies 31202 as daily charge and 31206 as daily discharge — the
integration had them reversed. The legacy storage-range registers (1052/1053 and 1056/1057)
were always correct; only the VPP-sourced entities were affected.
v0.9.0b1
- Fix: Universal Scanner DTC registers showing as zero on fresh TCP connection:
When using theexport_register_dumpscanner, the DTC identification registers (holding
30000 and holding 43) frequently returned 0 even though reading them individually via
read_registeralways worked. Root cause: the scanner opens a new raw TCP connection, which
displaces the coordinator's existing session. Until the inverter settles, the first reads
return 0 with no Modbus error. Fixed by adding a 500 ms warmup delay after connecting, plus
a single retry (with delay) for each DTC register if it reads back as zero.