v1.1.18

HACS release for FridgePower/app-side pack total unit correction. Scales non-HA1 app override pack total charge/discharge counters by /100 before exposing them as kWh. Keeps HA1 behavior from v1.1.17: one Battery Total Charge Energy entity, no mirrored discharge duplicate, and no meter total. Adds per-device app state override diagnostics to trace future FridgePower zero-value reports.

v1.1.17

HACS release for Hub A1/Apex telemetry improvements.

• Exposes one HA1 Battery Total Charge Energy sensor from packTotalChgEnergy, scaled as kWh.
• Ignores mirrored packTotalDsgEnergy so the total is not duplicated.
• Removes the non-working HA1 meter total energy sensor.
• Adds InverterTotalPower to HA1 field-source diagnostics from lastAlive.powerInvTotal for future sign/meaning checks.

Verified with unittest discovery, compileall, and git diff --check.

v1.1.16

Hub A1 zero-value follow-up:

• Map Hub A1 grid input from the lastAlive powerFeedBack alias when standard grid fields are zero or absent.
• Prefer non-zero lastAlive charge power and meter energy over realtime zero placeholders.
• Add Hub A1 pack total charge/discharge energy sensors using Wh units.
• Suppress label-only all-zero battery/PV/load/grid detail rows on fresh setup so they do not create misleading zero sensors.
• Add a serial-safe Hub A1 selected field-source summary log for future runtime checks.

Verified with 48 local tests, compileall, tracked-diff leak scan, and replay of the private HA1 capture through the mapper.

v1.1.15

Conservative Hub A1 telemetry cleanup. The latest runtime log confirms HA1 polling is active and SOC is coming from the real Hub A1 serial, but the field previously labeled HubA1BatterySoh reported an unlikely value. This release stops publishing that unverified HA1 SOH percentage while leaving SOC, voltage, switch state, detail rows, and the existing 60-second polling path in place.

v1.1.14

Fixes the Hub A1 serial-field parser/config path exposed by v1.1.13 diagnostics. The integration now rejects friendly-name/model fragments such as Hub/A1 as Hub A1 serials and removes cached synthetic HA1 products with invalid short sn values during setup. After installing, enter the actual Hub A1 serial in the Hub A1 serial field; friendly names are intentionally ignored.

v1.1.13

Diagnostics-first Hub A1 patch. Adds serial-safe target hash/length logging for app direct lookup, HA1 optional telemetry, and app home-device serial matching so the next Home Assistant log can prove whether runtime is querying the same Hub A1 serial that succeeded in capture. No raw serials or private payloads are logged.

v1.1.12 - Use direct HA1 values over zero telemetry

This patch fixes the zero-value path after v1.1.11. The verified direct HA1 deviceRemoteSearch response can contain non-zero batSOC and power fields, while optional realtime/lastAlive endpoints may return zero placeholders. HA1 state mapping now prefers the first non-zero trusted HA1 value, so non-zero direct HA1 fields are not masked by zero optional telemetry. The FridgePower copy prevention from v1.1.11 and stale homeDevices guard from v1.1.9 remain in place.

v1.1.11 - Stop copying FridgePower telemetry

This patch corrects the v1.1.10 model-gate mistake. In the live account, FP is FridgePower, not verified Hub A1/Apex system telemetry, so HA1 must not copy FP SOC or power readings. v1.1.11 removes FP from the Hub A1 related-source gate while keeping the v1.1.9 stale homeDevices.lastAlive guard in place.

v1.1.10 - Prefer fresh FP telemetry for Hub A1

This patch uses the new v1.1.9 runtime evidence: fresh app-side system telemetry is arriving from the FP row on each refresh, while EL100V2 is behaving like pack/detail telemetry and HA1-specific endpoints still return online-only data. Hub A1 related fallback now prefers fresh FP/Apex system telemetry and only allows battery SOC/SOH/voltage through that system-source path, keeping the stale EL100V2 guard intact.

v1.1.9 - Ignore stale Apex app fallback

This patch keeps the 60-second runtime refresh from v1.1.7/v1.1.8, but prevents stale Apex-family app home-device snapshots from overriding refreshed device state. Matching homeDevices.lastAlive rows now must pass the same freshness gate used by Hub A1 related fallback selection before they can win over the direct app/device payload. This should stop static SOC/power values such as stale EL100V2 snapshots from being surfaced as refreshed telemetry.