mkaiser / Sungrow-SHx-Inverter-Modbus-Home-Assistant

Sungrow SH Integration for Home Assistant for SH3K6, SH4K6, SH5K-20, SH5K-V13, SH3K6-30, SH4K6-30, SH5K-30, SH3.RS, SH3.6RS, SH4.0RS, SH5.0RS, SH6.0RS, SH5.0RT, SH6.0RT, SH8.0RT, SH10RT, SH5.0RT-20, SH6.0RT-20, SH8.0RT-20, SH10RT-20, SH5.0RT-V112, SH6.0RT-V112, SH8.0RT-V112, SH10RT-V112, SH5.0RT-V122, SH6.0RT-V122, SH8.0RT-V122, SH10RT-V122, SH4.6R

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Yearly PV generations jumps around

majuss opened this issue · comments

Describe the bug
A clear and concise description of what the bug is.

Your Sungrow inverter:

  • Model: SH-10.RT v112

  • The inverter is connected via (mark one)

    • LAN (internal port)
  • Are you using a Modbus Proxy (mark one)

    • [] yes
    • no
    • [] I don't know what that is

Home Assistant :

  • Version: 2023.11.0]

modbus_sungrow.yaml:

  • Version/ time stamp :# last update: 2023-09-29

** Inverter Firmware Status:**

  • I made sure that the newest firmware is installed via the installers account

To Reproduce
Steps to reproduce the behavior:
Let the inverter run over several months I guess?

Expected behavior
Should report the real value iSolarcloud reports 10k, HA energy dashboard around 7k.

Screenshots
Screenshot 2023-11-08 at 12 14 27

Additional context
Add any other context about the problem here.

Same here.
SH10RT - every end of month, yearly stats go up. Exports and generation
image

I have the same problem. Got my PV System connected in March. Yearly PV Generation (Current and 2024) value was correct until 2024-03-31 23:59. The first value in April jumped to the 1,8x of the correct value. Same thing with Yearly Export, but this value jumped to the PV Generation value in April.

I am not sure if this is an error of the HA Integration or if the inverter transmits wrong values.

Same here. It seems to be a bug at Sungrow... also there are some reports (dated 24th December) in this thread in a German speaking forum: https://www.photovoltaikforum.com/thread/166134-daten-lesen-vom-sungrow-wechselrichtern-modbus/?postID=3528584&highlight=6265#post3528584

I would suggest not to rely on the yearly values. Instead generate you own with helpers in HA.

I now noticed that the values have jumped back down again and seem to be correct. Since the 16th of April "Yearly export (current)" e.g. shows the correct value.

The Yearly values of 2024 and current are now the same and also have a <1 kWh difference to the total values.

I guess, Sungrow probably fixed the values provided by the inverter.

I now noticed that the values have jumped back down again and seem to be correct. Since the 16th of April "Yearly export (current)" e.g. shows the correct value.

The Yearly values of 2024 and current are now the same and also have a <1 kWh difference to the total values.

I guess, Sungrow probably fixed the values provided by the inverter.

Did you do some update of the inverter firmware? Seems strange that Sungrow can fix this without update.

I now noticed that the values have jumped back down again and seem to be correct. Since the 16th of April "Yearly export (current)" e.g. shows the correct value.
The Yearly values of 2024 and current are now the same and also have a <1 kWh difference to the total values.
I guess, Sungrow probably fixed the values provided by the inverter.

Did you do some update of the inverter firmware? Seems strange that Sungrow can fix this without update.

Good point, no I did not.. I did however update to HA 2024.4 a day prior and revert back to 2024.3 (since I had missing values like in #274) the day after that. After reverting, I got the correct values again.

2024-04-19_15-04-43

can also confirm...
image

The "real" export is around 950kWh this year. I guess the spikes at the end of the month causes this. Roughly adding the "linear increases" would match the right values.

These are non-documented registers by sungrow. It is a firmware-thing, so there is no way to fix this within this integration.

I am thinking of completely removing them, as they don't bring any benefit, compared with the HA energy dashbord

On May, 1st, the values jumped up again for me.

I agree with you that the values don't bring any benefit, and I think I would also remove them.

What I find strange however is that the values got fixed for me in April after reverting an HA update.. If the values are simply read from the register, an HA update should not affect them in any way.

These are non-documented registers by sungrow. It is a firmware-thing, so there is no way to fix this within this integration.

The sensors aren‘t undocumented. They are in the normal register document.