Delay and mismatch between Shelly measured PV power and Sungrow reported power

[skydado]

I'm using this add-on with my SH3.0RS and I'd like to measure actual PV power to manage possible household appliances for best energy use.

Sungrow inverter do have its meter and reports the PV power with this entity in my case:
sensor.gosungrow_virtual_5373483_14_1_1_pv_power
I've also added an external Shelly EM meter to have a double view on what is happening.

Unfortunatly, the GoSunGrow power has a delay of about 10 minutes compared to the actual power detected by the Shelly. This is not due to GoSunGrow because I see the same delay in the iSolarCloud app.
With this delay, it's hard to have a clear understanting of what is happening at instant consumption level to decide what to do with appliances.
Same delay applies to the binary_sensor.gosungrow_virtual_5373483_14_1_1_pv_power_active

On the other hand, the Shelly is also intercepting the power consumption of the inverter when the PV modules do not produce enough current to let the inverter start its job. To be more clear, the inverter's standard power is 10w (easily deductable), but when it's cloudy or at sunrise, instantaneous consumption grows inconsistently, based on irradiation, till it get over 80w, the minimum threshold for the inverter to activate.
So even the use of the Shelly power is not very reliable.

I tried with the SunGrow SHx Modbus integration because I guess that the modbus should be faster in sharing data with HA, but my SH3.0RS does not come with the internal LAN used by the modbus, and the Winet-S do show some registers, but not the few I need, like the instant power production.

I see an Alpha support for Modbus, (direct connect to your Sungrow inverter) in the code structure ... is there a chance to have it working with my Winet-S interface?

Any other suggestion?