Skip to content

v1.13.5

Choose a tag to compare

@alexdelprete alexdelprete released this 22 May 10:15
v1.13.5
f43b5a3

Release v1.13.5

GitHub Downloads

Release Date: 2026-05-22

Type: Patch release - Adds a device warm-up gate that handles an edge-case energy doubling after an HA restart.

What's Changed

Fixed

  • Energy doubling when the device returns zeroed meter data - In some setups —
    reported by one user — the Alfa can return 0 on every register for a few minutes
    instead of its real values (observed after an HA restart). The exact cause is not
    confirmed — it may be a slow or unreliable Chain2 link between the Alfa and the
    energy meter, or the device still initialising. This is an edge case: most
    installations never hit it. But when it happens, HA's TOTAL_INCREASING statistics
    read the 0 as a meter
    reset and double-count the cumulative total. The v1.13.3/v1.13.4 RestoreSensor
    guards could not cover the first restart after upgrading from a version that never
    persisted restore data — there was no baseline to compare against. A new warm-up
    gate
    detects this state with no dependence on prior data and rejects the affected
    poll.
    (Reported in #207)

Added

  • Device warm-up detection - When the device exhibits the warm-up state described
    above, the API identifies it from two physically-impossible readings on independent
    registers — energia_prelevata == 0 (a lifetime grid-import meter is never 0 on a
    real install) and fascia_oraria_attuale == "F0" (there is no tariff band 0). The
    poll is then rejected so no sensor publishes zeroed data; if it coincides with an HA
    restart, the integration simply reports not ready and retries until the device is
    up.
  • Warm-up repair notification - A dedicated repair notification is shown while the
    device is warming up (distinct from the connection-failure notification), and a
    recovery notification confirms when the device finishes warming up and data resumes.
    Translated into all 10 supported languages.

How to recover existing bad data

If a previous restart already produced a spurious spike on the Energy Dashboard, correct
it via Developer Tools -> Statistics, which lets you fix or remove the bad data point.

Full Changelog:
compare/v1.13.4...v1.13.5