total_dc_power over a million watts
TomMarg opened this issue · comments
Using the latest version everything works perfect but every once in a while the total_dc_power is listed as over a million watts. Typically it happens on cloudy days when the sun comes out but I do not yet know how to ignore those values but they make the charts unreadable.
wanted to report this behavior.
Model: SH-10.RT v112]
-
The inverter is connected via (mark one)
- LAN (internal port)
- [] WiNet-S (LAN)
- [] WiNet-S (WLAN)
-
Are you using a Modbus Proxy (mark one)
- [] yes
- [] no
- I don't know what that is
Home Assistant version:
- Version: 2024.4.4
modbus_sungrow.yaml:
- Version/ time stamp : [e.g. 2023-09-08] (see header of the file)
- I ensured to use the most recent version
** Inverter Firmware Status:**
- [] I made sure that the newest firmware is installed via the installers account
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Some forums suggest it's just a communication issue, but I've also only started noticing this recently. I'm not on the most recent YAML file, so I'd say it is not directly related to this project itself. Possibly Home Assistant related. Or just bad luck and badly shielded network cables. 🫤
I've resorted to deleting such excessive values from the database, but it's pretty clear that it's not just bad cables. It's also quite unlikely to be this project, because it "just" uses the default Home Assistant Modbus integration to do the actual work.
Total DC power and load power are straight Modbus sensors with no helpers/templates in between. Meter active power uses a template sensor to filter out the edge case when the power grid is not available.
I wonder how it could be possible that this is related to the change to async library calls in the Modbus integration, but those changes fit the timeline.
Yeah, it could help avoid polluting the statistics with wrong data. Too bad max_value
replaces the excessive value with the max_value
instead of just omitting it, that'd be even cleaner...
If you have a battery and more DC power installed than your inverter's rated AC limit (e.g. SH10RT with 15 kWp), you should set such limits to the higher number. When there's free capacity in the battery, the inverter will send the DC directly to the battery, increasing "total DC power" above the AC limit.
I ran a query in the database to check which entities have shown the problem - I'm not sure there's any pattern:
sensor.total_active_power
sensor.reactive_power
sensor.load_power
sensor.meter_active_power_raw
sensor.total_direct_energy_consumption
sensor.total_dc_power
Limits on a "total energy" value are going to have to be preeetty high...