Totals and counters

Daily and lifetime energy

• Lifetime counters from different devices start at different times and do not add up across tiers. Use Energy (kWh) on the Flow page, which draws energy_d.
• For a node with an energy source, energy_d is the counter's rise since the boundary.
• For a node with power only, energy_d needs Derive kWh from power (Aggregation.Enabled).
• A counter that goes backwards is treated as a reset. Energy before it is kept.
• Set PeriodTimeZone or TZ. Diagnostics flags an unset or unknown zone.

Settings: Flow settings.

Where daily totals are stored

When totals do not carry over, the log says Daily energy totals did not carry over, and the Overview labels figures only since HH:MM.

Lifetime counters never go backwards

energy, energy_out and energy_in are published as state_class: total_increasing.

• For a node the bridge keeps a running total for (any node with an energy or power source), the value is that total. It keeps counting from power when the node's energy counter stops arriving.
• The first value continues from the last one published, and a drop in the total is absorbed, so the sensor never goes backwards.
• For a roll-up tier with no source of its own, a value lower than one already published is held back and logged:

Holding back main_panel|energy: 9800 is below the 14616.54 already published.

The offsets are stored with the high-water marks (<key>@offset). energy_d is not held back.

Repairing Home Assistant statistics

For sensor.energyflow_* statistics already corrupted by a counter drop:

pip install websockets
export HA_URL=http://homeassistant.local:8123
export HA_TOKEN=<long-lived access token>
python3 scripts/ha-clear-energyflow-statistics.py --dry-run
python3 scripts/ha-clear-energyflow-statistics.py --yes

Or Developer tools › Statistics in Home Assistant, one entity at a time.

Published fields

A tier with no value is absent from the scrape.