Net-metering on 3 phase (fix Sig sensor issue)

[saturnv5]

Sigenergy announced that the 1st-gen Sig energy sensor fails to report grid consumption with net-metering in mind. So if I'm exporting 2kW on phase A and importing 1kW each on phases B and C, the sensor aggregates that to 2kW of import and 2kW of export, instead of net-zero consumption.

I was hoping this HA solution would fix the issue, but sadly not.

Does anyone know if this is possible to fix in HA or will we need to wait for Sigenergy to fix it on their side?

[TypQxQ]

[saturnv5]

Gotcha, I'll check if I have a P1 port on my meter. I guess the alternative is to write a new sensor that tracks the change over a short period of time and nets the differences. My meter has a 5-minute settlement, so it nets the consumption every 5 minutes.

[Roving-Ronin]

This issue has been confirmed as being only for 3ph users and those users who DO NOT have a Sigenergy Gateway installed and whom instead are reliant upon a SigenSensor (v1), which is actually an Eastron SDM630 type meter. Sigenergy have advised that there's a new SigenSensor v2, called the 'TPH-CH' model (or actually an Eastron SDM630MCT V2), that is not affected by the limitations causing this issue that are in the v1.

Lastly Sigenergy have advised that they will be releasing an update to the mySigen App that will allow for choosing to either display GROSS import and export energy data (as it is now) or NET data (as probably all Australia and other users who are billed on Net Exports want). This will allow TP Gateway and Sigensor v2 users to have this choice.

Now we just need to wait and see how long it takes to appear in the mySigen App updates.