I saw this image. However, the SH10RS, though it technically has 3 RJ45 ports, only the one the WiNet attaches to seems LAN capable. Unless your saying don’t use the module, and plug directly into that port?
you are right. I thought the SH10RS was more like the SH10RT, but it isn’t 
Apparently, you have no other choice than using the WinetS LAN port
I could not to find the datasheet on the sungrow page. Do you have a link to the official datasheet? (just took a peek look into a datasheet from a internet shop…, but it may be outdated)
just found out, that the SH** RS are not sold in germany. So the german sungrowpower website did not show them
Do you have a modbus register file for the SH10RS? in my modbus register description, only 2 MPPT registers are listed.
I wouldn’t know where to look for the register file - sorry.
@basti242 - can you elaborate on how this is done for a person who has enough tech knowledge to break something but not enough to fix it without guidance… 
Thanks
Carry out the installation in the same way as the initial installation. Should be simple.
Hi mkai,
My friend has a SH10.RT, I just installed the home assistant at his house and it all comes through to the dashboards following your documentation.
Thank you so much!
1 Like
Hi all,
I have a Sungrow SH5K30 and have been using the Modbus integration for a while. After the recent issues, I stayed on HA 2023.08 until I had a bit more confidence the Modbus issues were resolved. ( OK, I actually upgraded, but then rolled back )
Ive now updated all Core and HA to current versions, and updated the modbus_sungrow.yaml to the latest as above.
All the data seems to be coming through OK, however - there is always a delay from anywhere from 10 minutes up to over an hour. On a few occasions, the delayed data is over 15 hours old.
Battery % is one I watch a little closer - and this can be up to 2 hours old…
Some entities update fairly routinely, every 5 minutes. Some ‘seem’ random ( Im sure they aren’t.)
scan_interval in the modbus_sungrow.yaml is 10.
If I log directly into the inverters webserver - the parameters all update about every second:
Any suggestions?
Thanks,
Jarrod.
please make sure you have the current firmware installed
next step would be to use a modbus proxy: FAQ: My Modbus connection always cuts out · mkaiser/Sungrow-SHx-Inverter-Modbus-Home-Assistant Wiki · GitHub
Hi mkai,
Thanks heaps. I understood latest firmware to mean HA core and supervisor, which it is. ( or could you have meant the Inverter F/W? - cant seem to see that anywhere in the web gui )
The modbus proxy is up and running, but there seems to be a lot of timeout errors / read write issues?
> 2023-11-10 15:55:47,797 INFO modbus-proxy.ModBus(10.1.1.209:502): connecting to modbus...
> 2023-11-10 15:55:47,801 INFO modbus-proxy.ModBus(10.1.1.209:502): connected!
> 2023-11-10 15:55:47,801 INFO modbus-proxy.ModBus(10.1.1.209:502): delay after connect: 0.1
> 2023-11-10 15:55:57,907 ERROR modbus-proxy.ModBus(10.1.1.209:502): write_read error [1/2]: TimeoutError()
> 2023-11-10 15:55:57,908 INFO modbus-proxy.ModBus(10.1.1.209:502): closing connection...
> 2023-11-10 15:55:57,908 INFO modbus-proxy.ModBus(10.1.1.209:502): connection closed
> 2023-11-10 15:55:57,908 INFO modbus-proxy.ModBus(10.1.1.209:502): connecting to modbus...
> 2023-11-10 15:55:57,912 INFO modbus-proxy.ModBus(10.1.1.209:502): connected!
> 2023-11-10 15:55:57,912 INFO modbus-proxy.ModBus(10.1.1.209:502): delay after connect: 0.1
> 2023-11-10 15:56:08,014 ERROR modbus-proxy.ModBus(10.1.1.209:502): write_read error [2/2]: TimeoutError()
> 2023-11-10 15:56:08,014 INFO modbus-proxy.ModBus(10.1.1.209:502): closing connection...
> 2023-11-10 15:56:08,014 INFO modbus-proxy.ModBus(10.1.1.209:502): connection closed
> 2023-11-10 15:56:08,015 INFO modbus-proxy.Client(172.30.32.1:40668): closing connection...
> 2023-11-10 15:56:08,015 INFO modbus-proxy.Client(172.30.32.1:40668): connection closed
> 2023-11-10 15:56:08,018 INFO modbus-proxy.Client(172.30.32.1:56420): new client connection
> 2023-11-10 15:56:08,018 INFO modbus-proxy.ModBus(10.1.1.209:502): connecting to modbus...
> 2023-11-10 15:56:08,021 INFO modbus-proxy.ModBus(10.1.1.209:502): connected!
> 2023-11-10 15:56:08,021 INFO modbus-proxy.ModBus(10.1.1.209:502): delay after connect: 0.1
> 2023-11-10 15:56:18,126 ERROR modbus-proxy.ModBus(10.1.1.209:502): write_read error [1/2]: TimeoutError()
> 2023-11-10 15:56:18,126 INFO modbus-proxy.ModBus(10.1.1.209:502): closing connection...
> 2023-11-10 15:56:18,126 INFO modbus-proxy.ModBus(10.1.1.209:502): connection closed
> 2023-11-10 15:56:18,127 INFO modbus-proxy.ModBus(10.1.1.209:502): connecting to modbus...
> 2023-11-10 15:56:18,133 INFO modbus-proxy.ModBus(10.1.1.209:502): connected!
> 2023-11-10 15:56:18,133 INFO modbus-proxy.ModBus(10.1.1.209:502): delay after connect: 0.1
> 2023-11-10 15:56:28,235 ERROR modbus-proxy.ModBus(10.1.1.209:502): write_read error [2/2]: TimeoutError()
> 2023-11-10 15:56:28,235 INFO modbus-proxy.ModBus(10.1.1.209:502): closing connection...
> 2023-11-10 15:56:28,235 INFO modbus-proxy.ModBus(10.1.1.209:502): connection closed
> 2023-11-10 15:56:28,236 INFO modbus-proxy.Client(172.30.32.1:56420): closing connection...
> 2023-11-10 15:56:28,236 INFO modbus-proxy.Client(172.30.32.1:56420): connection closed
> 2023-11-10 15:56:28,238 INFO modbus-proxy.Client(172.30.32.1:42146): new client connection
> 2023-11-10 15:56:28,239 INFO modbus-proxy.ModBus(10.1.1.209:502): connecting to modbus...
> 2023-11-10 15:56:28,241 INFO modbus-proxy.ModBus(10.1.1.209:502): connected!
> 2023-11-10 15:56:28,241 INFO modbus-proxy.ModBus(10.1.1.209:502): delay after connect: 0.1
> 2023-11-10 15:56:31,349 INFO modbus-proxy.Client(172.30.32.1:42146): client closed connection
> 2023-11-10 15:56:31,349 INFO modbus-proxy.Client(172.30.32.1:42146): closing connection...
> 2023-11-10 15:56:31,350 INFO modbus-proxy.Client(172.30.32.1:42146): connection closed
The inverter IP is 10.1.1.209, but no idea what the 172.30.32.1 with multiple different ports are?
Gut feel is some sort of conflict?
If I look at all entities and sort by intergration - the only Modbus intergations all tie back to the sungrow inverter.
I also disabled all sungrow automations ( right or wrong) but to remove any other suspects. Nil change.
any advice welcome.
Cheers,
Jarrod.
With “firmware” I meant the inverters firmware by sungrow.
You can flash a current firmware using the webgui with an installers account (not the normal user) or with the sungrow App using local access.
The log looks like there are some acesses to registers with are not present in the modbus implementation of the inverter (I assume it is because of an outdated inverter firmware).
Please let me know, if an update helps 
Cheers.
isolarcloud offline, and I cant get it to connect ( havent actually used it for 12+ months, possibly why the F/W is an old version.
Interestingly, my install was completed using a LAN ethernet connection, not the WiFi dongle, so sungrow local access isnt an option. 
Ive sent a ticket to sungrow support. Plenty of screen shots and narrative, underlining the fact its an Ethernet connection, I can log in to the local webgui etc. I have a bad feeling i’ll get told to ‘follow this guide’ on how to set up wifi…
Once I get isolrcloud and sungrow app connectivity sorted, I’ll go from there.
Appreciate your help to date.
Jarrod.
Hi Folks,
I tried to integrate my SG8.0RT Inverter to my HA using the code from @basti242
Everything looks fine, so far but I miss some values
How kann I read the data of my energymeter?
Especially the power values of the different phases.
How can I find out the right registers?
Thanks and regards
BJ70
There is an open issue in the git here:
I wrote some code for the energy meter (but could not test it). It would be great, if you could do some test and give us some feedback
I can try, but remind that I have an SG Inverter…
sorry, I misread your post.
The SG series has a very different register mapping than the SG series.
So you don’t need to try, it will most probably not work 
Who can name the differences of the register mapping betwen SH anSG inverters?
@mkai I have a copy of V1.1.2 from sungrow (unclassified). Same doc as per the SH10RT. with a bit of info about a few addresses which are not supported for the 10RS.
I’m still having a number of issues getting ALL of the same information I can get from the SH10RT (I have one SH10RT and one SH10RS installed - so easy to test side by side).
Using the modbus addresses in the doc and the Generic Modbus/Jbus Tester, I am getting a number of ffff HEX returns of ffff ffff over 32 bits where the data is U32.
p.s. I have also tried both of the RJ45 ports beside the BMS port, and neither work for ethernet. So I am plugged into the end of my wifi dongle.
Using one of your dashboards … you can see that my Battery Discharging Start Power Shed is bollux. I’m going to spend some time in the next couple of weeks with the Modbus tester working out what I can get and what I can’t.
Generally, though, I have enough info and enough setters to be able to control the SH10RS …
Notice also that the Daily Imported and Daily Exported for the shed (SH10RS) are 0 (I have definitely exported today).
Sorry if this has been addressed somewhere else already, but I am still looking for explanations for the differences of the following value pairs:
“Total PV generation” (currently 11.833 kWh) vs “Total PV generation & battery discharge” (currently 11.479 kWh) - what does “battery discharge” mean in this context?
“Total battery charge” (currently 2.415 kWh) vs “Total battery charge from PV” (currently 2408 kWh) - I only have one power generating system that can charge the battery
“Total exported energy” (currently 6.797 kWh) vs “Total exported energy from PV” (currently 6.936 kWh) - here the “from PV” number is actually higher
Any help would be highly appreciated!!!