Replies: 16 comments 14 replies
-
|
I can't find the commit right now, but they were intentionally removed some time last year. They have various issues ranging from weird artefacts that could theoretically be compensated for to straight up incorrect data. You're better off accumulating this history externally in Home Assistant from the total energy sensor. Of course the registers are still there on the inverter side, so you could look at the current code for simple input register sensors, and the old code, and add them back. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the fast reply. From my point of view i don't store my own statistics in Home Assistant, only the default 90 days without additional database. I found the statistics provided by default very useful. Is it possible for you to re-add those simple input registers for month, year and current, because if i do this manually i need to do this for every new version. I am not familiar with YAML can i do this as an include if i do it myself? |
Beta Was this translation helpful? Give feedback.
-
|
I also use this in part as home assistant sometimes implodes a bit and I use this as a backup - for me, these currently missing sensors, come in "correct enough" .. and is actually more consistent I find as home assistant loses track due to down time (restarts mainly, if for example home assistant restarted on the hour or month start..then my hourly/monthly data break as they are not reset as they should.. and both have happened too many times for me ) I use this data for statistics and trending primarily for comparing month on month, quarter to quarter. I also for more detailed statistics and year on year as well export from isolarcloud more or less quarterly on a monthly basis and import into long term data key values to get hourly data - there are probably better work-arounds but it is what I have found that provides the best data albeit it is a bit like holding your pants up with a belt and suspenders. So, I plan to include these and to do so I believe you just add the missing code (with some mod's necessary as one used variable has changed name ) and then it should work. While there are some functions using variables I believe they are all included but I may have overlooked something (?). Also, it does read from register values .. today out to 2028 but it looks like 2029+ will likely follow the pattern of taking the next odd value.. tbd. I include the code below of the sensors I found missing but I have NOT yet confirmed it as I realized in the rest of the code at least some of the script calls are different and I need to give it a think and to fix all of the various automations and scripts I have... but hopefully in the next week I will be able to give it a go (?) Code needs to be placed under the right section. I put it at the end of the sensors section which for me was around line 1350 and anyway after the block containing: ` ` |
Beta Was this translation helpful? Give feedback.
-
|
Looks about right. 👍 As to the quality of the yearly data: |
Beta Was this translation helpful? Give feedback.
-
|
Hi! A bit late to this discussion. I have also been wondering about the missing statistics. I am still using the 2025-version of the yaml-file. I think that my data looks reasonable, and without weird jumps (see below). Do You mean that none of the statistics from the inverter can be trusted (from Modbus input registers)? According to the comments when the registers were removed in the Yaml-file it was because only some inverters supported them. I have a SH8.0RT-v112 inverter. 
|
Beta Was this translation helpful? Give feedback.
-
|
Which firmware version is this? Maybe they have improved it. |
Beta Was this translation helpful? Give feedback.
-
|
And yes, only SHxRT support them, and only via the dedicated LAN port, not via WiNet-S, which some people use and SHxT users have to use (if they don't have a RS485 converter connected). |
Beta Was this translation helpful? Give feedback.
-
|
Sungrow Version 1: SAPPHIRE-H_01011.95.10 I started using HA in January 2025 so I have no relevant prior data. I updated the firmware at least twice last year. Maybe things would have looked different if I had the corresponding data for 2023 and 2024. I understand the dilemma with different inverter models and connections and what to include/exclude in/from the file. It's great that this initiative exists! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for giving the advice how to get back the longterm statistics. I would like to migrate to the actual version of the mkaiser integration, but I miss the cell specific data for my sbr128 battery, as given in the discussion #133. is it foreseen to implement it later on or can you give some advice how to transfer the yaml code into the new version?? in the old version it was ok to copy the content of the file into the sungrow_modbus.yaml and to adapt the secret.yaml. does it work now the same way?? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I don't think that I am the right one to answer your question, but I asked a related question recently: #659 P |
Beta Was this translation helpful? Give feedback.
-
|
If it's just simple sensors based on input registers, the procedure remains the same. Just append them to the section where all other sensors are defined. |
Beta Was this translation helpful? Give feedback.
-
|
thanks for you help |
Beta Was this translation helpful? Give feedback.
-
Code:
|
Beta Was this translation helpful? Give feedback.
-
|
Exactly the kind of reason these sensors were removed. 🤷🏻♂️ |
Beta Was this translation helpful? Give feedback.
-
|
I'm not arguing here, but I have perfect correspondence. It would be interesting to know what causes these discrepancies. Home Assistant registers: iSolarcloud Lifetime overview: 
|
Beta Was this translation helpful? Give feedback.
-
|
And monthly: |
Beta Was this translation helpful? Give feedback.
-
|
Excellent, I wonder if there's been any kind of hardware revision or if it was finally fixed in a recent firmware update. Ideally, someone who knows they had the issue and has since upgraded would confirm that the issue has disappeared for them. |
Beta Was this translation helpful? Give feedback.
-
|
It took a while, but I have now updated my system. I have included the software versions in the screenshot. I have also included the values again after the update and the code. The screenshot of "Jahresproduktion" is the export from iSolarCloud. 
` |
Beta Was this translation helpful? Give feedback.
-
|
So... apparently not. :D Still wondering what the difference is that makes it work for some but not for others. |
Beta Was this translation helpful? Give feedback.
-
|
It would be good to compare the software versions and also check whether the same hardware, i.e. the same device, is installed. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting. If the differences are due to different firmware/software versions I don't think you should expect the data in the yearly/monthly registers to be retrospectively "fixed" by updating to the hypothetical ideal version. It would be interesting to have other people's input on this. So far I have only seen my own perfect correspondence between HA and iSolarcloud. Are there others? |
Beta Was this translation helpful? Give feedback.
-
Do you have the same device and the same software? |
Beta Was this translation helpful? Give feedback.
-
|
What does your "Sungrow Protocol Version" sensor read? Mine reads 16781568. That should/could be V1.0.17 translated. I don't know if this register is used/updated. V1.0.17 seems wrong. |
Beta Was this translation helpful? Give feedback.
-
|
Your conversion is wrong: That should be version 1.0.11. However, there's no indication that this register actually refers to the version of the Modbus register documentation. It just says "Sungrow protocol version", with no further elaboration. The earliest Modbus register documentation has version 1.0.12, and a 1.0.17 isn't listed. Not sure what it is referring to. N.B.: My SH10RT is still on 95.0.1 and also reports 1.0.11. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, V1.0.11 was my original hypothesis. I took a look at how this is implemented in "ha-modbus-manager" (https://github.com/TCzerny/ha-modbus-manager). That code results in "V1.0.17" for the value 16781568. As far as i can see the comment for the register was added somewhere between V1.1.6 and V1.1.9 of the "Communication Protocol of Residential Hybrid Inverter". The example in the comment in V1.1.9 was for "V1.1.7". I concluded that this comment was likely added in V1.1.7 of the "Communication Protocol of Residential Hybrid Inverter", although there is no mention of this in the documentation. Hence, adding an example for "V1.1.7" for a register named "Protocol version" in "V1.1.7 of Communication Protocol of Residential Hybrid Inverter" seems like more than a coincidence. Furthermore, the earliest documentation "V1.0.12" is not far from V1.0.11 that is in the register. I was hoping that my reading was wrong so that 0x01001100 that is in the register should really be 0x01011100, i.e, V1.1.11, corresponding to the latest version of the "Communication Protocol of Residential Hybrid Inverter". Sadly it doesn't appear to be. My reasoning leads me to believe that the register was or is supposed refer to version info of the modbus documentation, but that it has not been implemented or updated. |
Beta Was this translation helpful? Give feedback.
-
|
you are right... I made a mistake in the calculation as it was not 100% clear from the sungrow docs... |
Beta Was this translation helpful? Give feedback.
-
|
My current setup: 
|
Beta Was this translation helpful? Give feedback.
-
|
As far as I can see I and Volker2828 have pretty much the same hardware, firmware and software currently. Just a thought: there shouldn't be differences in hardware and versions between countries, should there? I'm in Sweden. |
Beta Was this translation helpful? Give feedback.
-
|
Well, I already have other hardware: SH10RT-V112 my hardware and your Hardware: SH8.0RT-V112. Maybe they changed something in the registers. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, but these model names are a bit confusing to me. Shouldn't the only difference be in the rated power? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Developer Team, i want to thank you all for the great integration and the effort you invest to keep it alive.
I use it since about 2 years with a Sungrow SH6 Inverter and a Sungrow Battery Pack
A few days ago i have updated fro 2025-01-28 YAML zu the latest version but after following the migration guide all Monthly and Yearly Statistics are gone. They are not longer included in YAML, e.g. Yearly Export (2025)
Will they come back?
Beta Was this translation helpful? Give feedback.
All reactions