PV power reports MW values with three-phase-hv since version 1.1.0

[dobrovodskyroman-source]

Hello,

I would like to report a possible regression affecting the combined
PV power sensor with SENSOR_DEFINITIONS: three-phase-hv.

My inverter is detected as:

• Device type: High-voltage three-phase hybrid
• Rated power: 30,000 W
• Protocol: 1.4
• Connection: Solarman TCP logger on port 8899
• Sensor definitions: three-phase-hv

The PV power sensor worked correctly with add-on version 0.10.1.

After updating to newer releases, including 1.1.0 and 1.2.0, PV power
reports an unrealistically large value displayed in MW. I also tested
some intermediate releases and the problem persisted.

The individual sensors PV1 power, PV2 power and PV3 power continue to
show correct values.

I noticed that version 0.10.1 used:

MathSensor(
(672, 673, 674, 675),
"PV power",
WATT,
factors=(10, 10, 10, 10),
)

From version 1.1.0, this was replaced by:

PVDynamicTotalSensor(0, "PV power", WATT)

The problem therefore appears to be related to the dynamic PV total
calculation for the three-phase-hv profile.

Other Deye inverters that I manage use SENSOR_DEFINITIONS: three-phase
and their PV power values work correctly.

Expected result:

PV power = PV1 power + PV2 power + PV3 power + PV4 power

Actual result:

PV1, PV2 and PV3 power are correct, but the combined PV power is an
extremely large value displayed in MW.

The three-phase-hv profile is required because the normal three-phase
profile does not report the high-voltage battery correctly.

I can provide startup and daytime logs with the exact values.

Thank you.

[kellerza]

Hi, the new dynamic power measurement should use the individual pvN_power sensors

So it is strange when you say they are correct, but the sum not

Can you check if you have other sensors configured, like pv5/6/7/8?

[dobrovodskyroman-source]

Hello, Thank you for your quick response, and please accept my apologies. You were correct—the problem was in my configuration. I had the following entry enabled: SENSORS: - all This also enabled the unused PV5–PV8 sensors, which were then included in the new dynamic PV power calculation. After removing all and explicitly configuring only the PV inputs used by my inverter, the combined PV power value is now correct. My corrected configuration is: SENSORS: - energy_management - power_flow_card - pv1 - pv2 - pv3 The add-on is now working correctly. This was therefore a configuration issue on my side, not a bug in PVDynamicTotalSensor. Thank you again for pointing me in the right direction, and I apologize for the incorrect bug report. Best regards, Roman Dobrovodský št 27. 8. 2026 o 9:12 Johann Kellerman ***@***.***> napísal(a):

…

Hi, the new dynamic power measurement should use the individual pvN_power sensors So it is strange when you say they are correct, but the sum not Can you check if you have other sensors configured, like pv5/6/7/8? — Reply to this email directly, view it on GitHub <#684?email_source=notifications&email_token=CHEVTDLXZU3A4P6RFHTMJZD5L7NN3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRG4ZDCNJWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-18172156>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CHEVTDLR4TYT2JCBEG3H3QL5L7NN3AVCNFSNUABIKJSXA33TNF2G64TZHM2DAMZWGU3DAOJRHNCGS43DOVZXG2LPNY5TCMBWHE2DAMJVUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CHEVTDLTBC7YA2Z7NKACZZL5L7NN3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRG4ZDCNJWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM> and Android <https://github.com/notifications/mobile/android/CHEVTDK66APBLXB64APNVYL5L7NN3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRG4ZDCNJWUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[kellerza]

Glad you got it working!

all stores everything in home assistant stats,- which could burn through an SD card fairly quickly. So in the long run better not to use it. The docs also has a nice table of available sensors if you want to add something specific