-
Notifications
You must be signed in to change notification settings - Fork 103
FAQ: Problems with the connection
No sensor values, HA log shows:
General exception: index out of range
Modbus IO exception Modbus Error: [Input/Output] Unable to decode request
Using the native LAN port of the inverter is required - the WiNet Ethernet port is not fully working! Recent Sungrow inverters come with WiNet-S, a Dongle for WLAN access / LAN interconnection. Although the dongle has an Ethernet port, modbus is not working properly with this port. Some users report, that they cannot establish a connection, some are able to, but several modbus registers are working, and some not. It seems like Sungrow is actively working on that, so maybe in the near future they will release firmware upgrades to improve the modbus via WiNet S support.
Some users reported, that the Inverter must be completely switched off and only is assigned an IP adress on cold-boot. So do the following:
- Turn off the AC to the inverter
- Wait 10 seconds
- Switch off battery (if available)
- Wait 10 seconds
- Switch off the DC power (the large switch at the side of the inverter)
- Attach the LAN cable to the internal port
- Wait 10 Minutes (so all capacitors inside completely discharge)
- Perform steps 5 to 1 to properly boot the inverter, again
- After bootup (give it 10 minutes), you should see the inverters IP adress in your LAN router.
If you are using Windows you can easily check, if the modbus connection generally works using QModMaster. I am pretty sure, that there are open source linux alternatives available :)
I tested it with the values shown in the screenshot. First set the TCP Settings (Options --> Modbus TCP) then adapt all highlighted parameters
The following values must match values from your secrets.yaml
Slave IP = sungrow_modbus_host_ip
TCP Port = sungrow_modbus_port
Unit ID = sungrow_modbus_slave
Users with single-phase inverters have reported multiple issues (sungrows nomenclature is SH3.RS - single phase, vs. SH10.RT - three phase). These inverters only support a subset of the modbus registers (although the users reported using the inverter's built-in LAN port.)
--> sorry, can't fix this. It is up to Sungrow to make a platform independent modbus implementation :/