Winet and LAN/Modbus?

[Caleb79]

Hi,
I've the Sungrow SH10RT and the SBR096 and this system is connectd via LAN from Winet to one port of my Switch/Router and the other LAN port is connected to the Switch as well to get the data via Modbus for Home Assistant.
Now, that the battery is running low, due to no sun ;) , I've every 4-6 days the problem that the system is not operating normally anymore, especially when the inverter wants to charge the battery because of the SoC percentage.
The issue is, that the inverter switches into a mode that I've to restart him.

I'm curios, if that is the case because of using both connections for different tasks.
I unplugged the modbus LAN for a couple of days and the system works properly.

Does any one of you have the same issue? Or should either use isolarcloud or modbus?

Thanks for helping.

[Gnarfoz]

I have exactly the same setup without such issues. I think that's a pretty common setup (WiNet-S for iSolarCloud, Ethernet for Modbus).
Can you elaborate more on this "mode" where the inverter needs to be restarted? Restarted how, exactly?

[Caleb79]

I thought so too but I need to investigate why these behavior happen to my environment.

If the battery is running low on capacity, let's say I've set the SoC to 20% and due to no sun, it's not charging for days, the capacity is running more low up to 16%. At that moment, normally the system decides to recharge the battery but not in my environment. At this moment, the inverter switches into "manually shut down". In that situation, no amperage is measured in iSolarcloud and the inverter led (the blue ring) pulsates.
The first time I had that issue, I restarted the inverter by cutting off the power (AC and DC).
The last time, I just unplugged the modbus and after a while the inverter started automatically.

But I cannot explain to my self, why this happens all the time.

[Gnarfoz]

Sounds like you have backup mode enabled (otherwise, setting the backup SoC does nothing). I don't have that enabled, so I'm not confident that I know the expected behavior. As far as I know, though, charging from the grid to maintain a certain SoC only happens when crossing the emergency charge threshold, which is far lower than 20%:

(Don't adjust that. Sungrow says to leave those at default unless directed otherwise by Sungrow.)

[Caleb79]

Yes, I've backup mode enabled and did set the battery soc to 20% (Sungrow says, that in Winter you should set this to 50%). The settings in your view I didn't changed although I've different ones:

[egaryw2011]

I have a question regarding the LAN and Winet, I have had the system running now for around a year, with no issues. I have the Modbus in the LAN and no dongle, the ISolarcloud must have been receiving the information from the LAN. Until they upgraded both the battery and the Inverter with new firmware vis the dongle which I had to install temporarily. Now IsolarCloud does not receive the information from the LAN. If I plug the dongle back in and provide wifi access IsolarClud recieves the information, however the system seems to be unstable and even shut down. When I reboot the system it starts up and shuts down again after a couple of miniuts, If I disconnect the LAN everything works as expected other than I do not have ModBus connection any longer? Any ideas anyone?

[Gnarfoz]

Since you mention you've had the system running for a year, I'll assume it's a SHxRT series device?
That one has a built-in Ethernet port just for Modbus - it does not communicate with iSolarCloud.
Additionally, the SHxRT series comes with a WiNet-S dongle that offers both Ethernet and WiFi connectivity. The dongle feeds iSolarCloud AND it offers Modbus access as well, although a small number of Modbus registers that are available on the Ethernet port of the inverter are not available here. WiNet-S WiFi and WiNet-S Ethernet are functionally equivalent and offer the same things. They can even be used at the same time, although I'm not sure why one would want to do that. ;-)
So... something does not entirely match up.

The shutdown thing sounds like what people are describing in #416 (particularly since you mention a recent firmware update). Spoiler: no solution yet, just a workaround.

[egaryw2011]

Yes your correct SH10RT 3 phase inverter.
"That one has a built-in ethernet port just for Modbus - it does not communicate with Isolarcloud" It did communicate to Isolarclud for over a year prior to the upgrade - The Sungrow technicians asked to install the WiNet-S dongle in order for them to upgrade the firmware to the battery, however they managed to upgrade the firmware of the inverter previously with no dongle. I suspect the Firmware stopped the Isolarcloud communication through the Modbus port.
I tried connecting to the RJ45 port on the back of the dongle however it didn't provide any Modbus connectivity. Question - what registers will not be available?
Additional info - The system was shutting down as already explained, so I disconnected the dongle and left the system connected to the Modbus port only and everything is working fine, however I have no connectivity to the Isolarcloud now. Today I will go ahead and prove everything again - when I am on the lower tariff
Step 1 - Dongle on wifi only should connect to Isolarcloud
Step 2 - Ethernet on the back of the dongle - see if it connects to IsolarCloud and provide limited Modbus access
Step 3 - Connect to the Modbus port and leave the dongle in - Hopefully works, however last time kept shutting down
Step 4 - depends on step 3, if step 3 starts shutting down remove dongle again.

[brendan-pike]

Not wanting to hijack your thread, but as a new SH10RS owner I'd like to know what I'll be limited by. This inverter does not have a LAN port and only a Winet one. It seems to be reading info okay, so what will be the issues I run into?

[Gnarfoz]

Not wanting to hijack your thread, but as a new SH10RS owner I'd like to know what I'll be limited by. This inverter does not have a LAN port and only a Winet one. It seems to be reading info okay, so what will be the issues I run into?

You'll have to live without the things Sungrow lists as "WiNet-S forwarding not supported" in the Modbus register documentation: https://github.com/Gnarfoz/Sungrow-Inverter/blob/main/Modbus%20Information/TI_20240924_Communication%20Protocol%20of%20Residential%20Hybrid%20Inverter-V1.1.5.pdf
That should be it. Recent WiNet-S firmware versions are pretty OK otherwise.

[egaryw2011]

Mmm when they say "added restriction on forwarding via ethernet", does that mean that the ethernet that we connect to the LAN for Modbus now will connect to the Isolarcloud?

[egaryw2011]

Sorry I meant "will not" connect to IsolarCloud

[Gnarfoz]

No. That's the changelog of the Modbus documentation and refers to the column I mentioned that lists which registers are not available via WiNet-S.

The dedicated Modbus port on the SHxRT series does not communicate with iSolarCloud, you need the WiNet-S dongle for that. Please refer to the user manual: https://info-support.sungrowpower.com/application/pdf/2024/12/02/SH5.0_6.0_8.0_10RT&SH5.0_6.0_8.0_10RT-20%20User%20Manual.pdf

[egaryw2011]

Thanks - I know thats what everyone says, including the manual :-) However, until the firmware upgrade I only had the dedicated LAN port in. The dongle was sitting on a shelf for around a year. Sungrow uploaded the firmware for the inverter through the LAN as well, it wasn't until they tried to upload the firmware for the battery that they asked me in install the dongle. Now when I take off the dongle there is no communication with the ISolarcloud :-(
Anyway I cant change it back now, moving forward if I want both, I tried to connect the dongle and the LAN however even though I was able to connect to ISolarCloud the inverter only took power from the grid for some reason, so I had to remove the dongle, today I will try and replicate the same to confirm.
I also tried to connect the Ethernet to the back of the dongle however there was no connection back to the router through that port?