Sungrow SH10.RT Modbus integration

Third party integrations
174

Hallo Zusammen,
ich kämpfe gerade mit einer Sache.
Ich würde gerne über HA die Backup-Funktion aktivieren bzw. deaktivieren können.
Dazu gibt es aber keine entität bei M.Kaiser
Und welches Register das ist, finde ich auch nirgends.
Hat das jemand schon mal gebastelt?

Hello everyone,
I’m currently struggling with something.
I would like to be able to activate or deactivate the backup function via HA.
But there is no entity for this in M.Kaiser
And I can’t find anywhere which register this is.
Has anyone ever tinkered with this?

175

Has somebody two SH10RT-V112 running as master/slave?
I only seem to be able to read out the master.

176

Hi Mkai

I am totally fresh here and know near to nothing… trying to install the modbusTCP2MQTT to connect mysungrow inverter… but getting fail notification:

The command ‘/bin/ash -o pipefail -c pip install --upgrade pycryptodomex==3.11.0 --no-cache-dir -r requirements.txt’ returned a non-zero code: 1

what am I doing wrong?

177

Hi, I am wondering if you managed to get the SH10RS working.

I connected it to the single LAN port (WiNet-S2) port, as per the comments in this thread. I can access the WiNet-S2 portal page (shows live data for the device, via the same IP address in the below error - can add a screenshot of the page).

Note, I did try the two other COM ports, but they never produced a network connection of any sort - tried a few different ways to get a connection via them

I’ve followed the configuartion directions for this integration and am receiving an error:

Pymodbus: SungrowSHx: Error: device: 1 address: 4999 -> Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.86.140:502]

Did you have to make additional adjustments to get the Modbus to feed the data into Hass?

178

Hallo Achim,
bei mir hat der Installateur die Backup-Funktion aktiviert.
Allerdings meine ich, dass es über die icloudsolar-App auch gehen müsste, wenn du alle Berechtigungen erhalten hast.
Nach einmaliger Aktivierung habe ich die Funktion nicht wieder deaktiviert und passe nur die Backup-Reserve über HA der Wetterlage entsprechend an. Daher war die Aktivierung / Deaktivierung über HA bislang nicht notwendig.
VG Ralph

179

Hi,

I am working on a Sungrow Sh10RT inverter and I am finding that even when Self-consume mode is triggered the inverter is not supplying current to the house. I am not sure if it is a problem with the integration or the inverter? To keep things simple I have created a script that sends these modbus commands directly to the inverter, it matches this integration. Is there anything else I should be doing to trigger the inverter to go into Self-Consume mode?

alias: "SMART MOTION: Self-consumption mode battery"
sequence:
  - service: modbus.write_register
    data:
      hub: SungrowSHx
      slave: 1
      address: 13050
      value: 204
    alias: Set Stop (default)
  - service: modbus.write_register
    data:
      hub: SungrowSHx
      slave: 1
      address: 13049
      value: 0
    alias: Set EMS Mode Self-consumption mode (default)
180

Does anyone know how to get the scan_interval in practice down below 5 seconds?

181

Did you get readings to work with RS485?

182

I am doing the same thing, same inverter, seems to work fine for me:

    sequence:
      - service: modbus.write_register
        metadata: {}
        data:
          hub: SungrowSHx
          address: 13049
          slave: 1
          value: 0
      - service: modbus.write_register
        metadata: {}
        data:
          hub: SungrowSHx
          address: 13050
          slave: 1
          value: 204
184

Hallo,
kann es sein das der SH10RT nur von einem Gerät Modbus Abfragen annimmt?
Ich habe schon ein anderes Projekt laufen das den Sungrow abfragt über Modbus.
Jetzt wollte ich über Home Assistent zusätzlich die Werte abgreifen, da kommt aber
2024-06-21 08:55:11.582 ERROR (MainThread) [homeassistant.components.modbus.modbus] Pymodbus: SungrowSHx: Error: device: 1 address: 4999 → Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.2.211:502]

185

Hi, new to the forum, please go easy on me.

I am after the method to change parameters on the SH10RT to govern export management, via HA.

I have seen posts here from @mvandersteen, and from what I can read - it looks like you have cracked it, or have a line on it.

FYI - I have the SH10RT, with 38kw of storage, have just gone wholesale on the grid provider, so having tight, automated control on when we should and should not export is now a big deal. The modbus/TCP integration is on sing, I can see all of the data from the inverter, but I have not sussed out how to change it. Specifically the parameters that govern the export management.

Appreciate people’s patience with this specific query, and will be grateful for any assistance.

Cheers !

186

Still struggling to find out the IP address of my inverter. Tried different IP scanners but don’t seem to find the correct one.
I have found the IP address of the WiFi dongle but not the LAN.
Both are connected.

Any tips on how to get a hold of it?

I have a SH10RT-v112.

BR,
Håkan

187

Log into your router! Then plug and unplug until you know!

188

There is no difference in the connected clients in the router when I unplug the cable.
Does anyone now if I somehow can login to the inverter to see the IP-address?

I asked the company that installed the inverter and the battery if they could provide me with the admin login credentials.
I said I needed them for an integration.

They told me I had to sign a non-disclosure agreement with Sungrow to get an access key. But is that correct? Isn’t that for developers using the API, as for the creator of this integration, not me as end user of the integration right?

189

I mean, when you get the password you can change all the important settings, so it is reasonable, that they want to be safe.
I’m not sure if you can see the ip by connecting to the inverter hotspot, but you can try.
But if you unplug the inverter, be sure to wait some time, before looking for changed devices. The name could be Espressif. Also if you want to go really far the MAC address issuer (the first 6 letters) is either Espressif or Sungrow Power Supply (for modbus).

Another thing to look for is if they are using a router of their own to be able to remote login. That way you would never be able to see the IP in your router.

190

and specific error noted in this post:
Pymodbus: SungrowSHx: Error: device: 1 address: 4999 → Modbus Error: [Connection] Not connected[AsyncModbusTcpClient 192.168.86.140:502]

I’m getting the same error as this. My installation was running fine for months maybe over a year without issue and then suddenly on 28th August 4:05pm it stops working. As far as I am aware no updates were undertaken at that time or even in the couple of months before that.
I’ve updated supervisor and core and this has not helped. I’ve relooked at the Github code and made a few changes to bring what I have inline with that, but short of re-copying the whole lot into my installation I’m not sure what has gone wrong.

I don’t see any record on my inverter of an update, but I guess it is possible.

did anyone happen to see similar and find a route to a fix?

191

I’ve had no luck unfortunately- hoping your update sparks some new ideas

1 Like
192

OK I got it going.
I worked my way though the FAQ for the integration one by one.
I don’t know what has changed, but I now have to use a modbus proxy.
After a full reboot it was working again. Yay!

FAQ: My Modbus connection always cuts out · mkaiser/Sungrow-SHx-Inverter-Modbus-Home-Assistant Wiki (github.com)

193

This weekend I finally got time to examine my battery installation checking where all the network cables were going and why my inverter does not show up in my router.

I opened up the box where the CM10 (Checkwatt gateway) was installed and I now think I know why I can’t see the inverter on my network.

Conclusion:
The battery has a network cable that is connected directly to my network (through a switch).
The CM10 (a gateway that is controlled by Checkwatt) is also connected to my network.
Checkwatt is a company that offers a service where you lend out your battery for adjustments in the electric network (charge/dischange to balance the network) and you get paid for it.

I can see both the battery and the CM10 in my router.
But the inverter is not directly connected to my switch. It is connected via the LAN output directly into the CM10, that is why I don’t see it in my router!?

The first couple of weeks after I got everything installed, it was running on Self Consumption, not using the CM10. That is when I tried to connect to the inverter.
Now it has been taken over by Checkwatt and they control everything.

My plan is to use Self Consumption during the summer when my solar panels can charge the battery and use Checkwatt in the winters.

But I guess I need to unplug the LAN cable from the CM10 and plug it into my switch to be able to see it in my router?

Anyone understand what I’m talking about and have some input?

BR,
Håkan

194

Maybe this is a silly question, but… I can’t find proper documentation.

What exactly is ‘External EMS Mode’ used for? How does it differ from the ‘Forced charge/discharge’ mode?