I’d like to report a VRM aggregation bug where an energy counter reset is being interpreted as actual consumption, resulting in a completely unrealistic value.
System:
Cerbo GX (latest firmware)
Three-phase grid meter
Battery storage system with solar
The issue:
On 2026-01-15 between 10:00–10:59, VRM recorded a consumption of 27,432.96 kWh in a single one-hour bucket. This is obviously not real consumption – it appears to be the result of an energy counter reset that VRM interpreted as actual energy usage.
This single erroneous value inflates the entire day’s totals to meaningless numbers in the monthly and yearly overview.
What the other data shows for the same day:
The hourly Energy flow chart shows realistic values (under 5 kWh per hour) for all other hours
The Grid power graph (W) looks completely normal throughout the day
Battery SOC was stable at 55–56% during that hour – consistent with normal operation, not a 27 MWh event
Solar energy for the hour: 0.80 kWh – perfectly normal
Screenshots attached showing:
Monthly overview with the January spike
Hourly grid power (W) for 2026-01-15 – looks normal
Dashboard summary cards
Hourly Energy flow chart – looks normal
Tooltip showing the 27,432.96 kWh value in the 10:00–10:59 bucket ← key screenshot
Is there any way to correct or invalidate this specific data point on the VRM side? And is this a known issue with counter resets?
Energy Meter VM-3P75CT, standard installation, no modification, official Venus OS for that date (don’t remember the version). Problem is on that day only
This was a problem indeed addressed to us by @Hhalewijn , since then it has been fixed in the firmware, so it should not happen anymore on the latest GX firmware!
The fix was implemented retroactively in the latest stable release of Venus, so it should not happen anymore. Given your message, you had it last January, and that was when this bug was happening in the firmware.
Don’t know if you are using NodeRed for the Shelly, but if this is the case, please check in the virtual device, that “Initialize with defaults” is deactivated.
I had such a problem that sometimes, if the network or something else caused an restart of the shelly virtual device, there was such an fake consumption as well.