First spotted on the main VRM dashboard’s Energy widget: the AC Load / Base Load split looked off. Tracing it back, /stats?type=consumption is collapsing multi-instance daE uploads to a single series. With two com.victronenergy.acload services
on a site, only one channel’s deltas appear in daE.
Site 945553. Shelly Pro 2PM, both channels metered:
acload _0 (instance 53): /Ac/Energy/Forward = 3.011 kWh
acload _1 (instance 54): /Ac/Energy/Forward = 0.700 kWh
7-day API totals.daE = 0.629 kWh — matches instance 54 alone. Instance 53’s deltas are dropped.
The per-instance data IS in the cloud — VRM Advanced tiles show both correctly:
Pi-side /Ac/Energy/Forward VRM Advanced "Total energy forward"
acload _0 (instance 53): 3.011 → 3.08 kWh ✓
acload _1 (instance 54): 0.700 → 0.71 kWh ✓
So storage and ingestion are fine. The bug is specifically in the /stats?type=consumption aggregator that powers the Energy-widget split.
vrmlogger uploads per-instance keys. From kwhdeltas.py final loop in get_deltas():
result[code + "[" + str(tuple[0]) + "]"] = tuple[1]
so the payload carries both daE[53] and daE[54]. Both services are found at every boot in vrmlogger’s log. The cloud-side stats aggregator is flattening them.
Pc + Bc is correct; only daE is short.