Strange PV production and consumption in VRM early in the morning

DIY
, , , , ,
1

Hello Community,

I am seeking some insight into a strange data behavior I’m seeing on my VRM dashboard every morning.

System Setup:

  • GX Device: Ekrano GX (Firmware: v3.80~7 - Release Candidate)

  • Inverter/Charger: 3x MultiPlus-II 48/5000 (Three-phase system)

  • PV Inverter: GoodWe SDT20 (connected as Sunspec PV Inverter via Modbus TCP)

  • Solar Chargers: SmartSolar MPPT RS 450/100 & 450/200 (Firmware v1.27)

  • Grid Meter: VM-3P75CT (Firmware v1.11)

  • Batteries: JK-BMS (via Pylontech driver) and SmartShunt 500A

  • Additional Loads: EM24 Ethernet (Heat pump) & MQTT EV Charger

The Issue:

Every morning, exactly when the first PV production begins and the GoodWe inverter wakes up from its “Deep Sleep” mode, I see a massive, instantaneous peak in both PV Production and Consumption on the VRM Overview.

image
image2521×906 97.4 KB

image
image2395×819 28.4 KB

Observations:

  1. Symmetry: The consumption peak perfectly mirrors the PV peak. This leads me to believe it is a calculation artifact, as the GX device likely assumes the “extra” reported power is being consumed to balance the system logic.

Clean “Advanced” Data: When I look at the individual widgets for the MPPT or the Inverter under the Advanced tab, these peaks are not present. The logged data there looks perfectly normal.

  1. Timing: The issue only occurs when communication resumes after the GoodWe inverter’s nightly shutdown.

image
image959×778 54.9 KB

image
image953×777 49.3 KB

My Theory:

It seems that when the Modbus TCP connection re-establishes, there might be a “stale” or cumulative value sent in the first data packet that the GX device interprets as a massive instantaneous power spike. However, because this happens so quickly, it doesn’t seem to make it into the long-term logged data (Advanced tab), yet it remains visible on the Overview dashboard.

Has anyone encountered similar behavior with GoodWe inverters or other Modbus-connected PV inverters? Is there a known way to “debounce” this initial data or a setting in the GX/Ekrano to ignore these startup spikes?

Any help or suggestions would be greatly appreciated!

2

exactly. If your inverter reports 7.5 kWh “out of a sudden” that is not recorded to go anywhere (grid, battery) - then it’s mathematically considered consumption.

Can you see if the EnergyForward Counter of your Goodwee does reflect that spike as well? (The bar graph is calculated out of the counters, not out of the momentary values)

3

Same behaviour here, and I think I can answer the open question about the counter.

My setup is close to yours: Cerbo GX v3.75, 3x MultiPlus-II 48/5000 three-phase, ESS, and an AC-coupled PV inverter on AC input 1 read as a SunSpec PV inverter over Modbus TCP. Mine is badged AEG (AS-IC02-4000-2), but AEG solar inverters are white-label GoodWe. The inverter menu even offers SunSpec or GoodWe as the Modbus protocol. So this is probably the same hardware twice, not two brands with the same symptom.

On the energy counter: yes, it reflects the spike. I log the GX total yield into Home Assistant. At night the value is unavailable; at sunrise it first returns as 0.0 and jumps to its real value minutes later. The GX books that difference as production in one minute, and since nothing accounts for where the energy went, the same amount lands in calculated consumption. So it is the counter, not the momentary power. It also explains why the peak is the same size every morning: it equals the counter value, not the day’s yield.

Related, on my unit the scale factor of that same register looks wrong by a factor of 1000: AC-coupled PV inverter total yield reported 1000x too low via SunSpec (AEG AS-IC02-4000-2)

Either way, if the GX could ignore a lifetime counter that drops to zero and comes back, the morning peak would disappear. Any progress on your side since March?