Skip to content

v1.13.4

Choose a tag to compare

@alexdelprete alexdelprete released this 21 May 23:33
v1.13.4
63c0932

Release v1.13.4

GitHub Downloads

Release Date: 2026-05-21

Type: Patch release - Extends cold-restart energy-doubling protection to all 17 energy sensors.

What's Changed

Fixed

  • Daily F1-F6 energy sensors could double-count after a Home Assistant restart -
    v1.13.3 protected only the 5 lifetime energy sensors from the cold-restart warm-up
    zero. The 12 daily time-band sensors (energia_{prelevata,immessa}_giornaliera_f1..f6)
    are also TOTAL_INCREASING and were left exposed — a warm-up 0 after a restart was
    read by HA's statistics as a meter reset and double-counted. All 17 energy sensors are
    now protected.

Changed

  • Reworked cold-restart protection into a metadata-driven two-guard model (ported
    from the sibling ha-abb-fimer-pvi-vsn-rest integration). Each energy sensor carries
    a sensor_scope tag (lifetime or periodic); protection is derived from
    state_class and sensor_scope instead of a hand-maintained list. Two independent
    guards now run in the sensor's native_value:
    • Guard 1 — lifetime sensors may never decrease while a live state exists; daily
      sensors are excluded so their legitimate midnight reset still works.
    • Guard 2 — after a cold restart, any accumulating sensor whose value falls below
      its RestoreSensor baseline is held back through the device warm-up window.
      The restored baseline is now kept on the entity instead of being written back into the
      coordinator's data, removing a fragile coupling.
  • RestoreSensor restore logic now applies only to the 17 accumulating energy sensors
    rather than every sensor.

Known limitation

  • If Home Assistant restarts within the device warm-up window immediately after
    midnight
    , a daily F1-F6 sensor's genuinely-low post-reset value can be held back by
    Guard 2 until it re-accumulates past the pre-restart value. This is a rare edge case
    and matches the reference implementation's accepted behaviour.

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