Modbus problem with Sungrow SH8.0RT-V112 and AC011E-01

Third party integrations
1

Hello Community,

I am using the Sungrow inverter SH8.0RT for more then 1 year and I am using the “integration” Sungrow-SHx-Inverter-Modbus-Home-Assistant by mkaiser. For this setup, I am using the rear LAN Port of the inverter to get it working - no problems!

Now I got a Sungrow Wallbox AC011E-01 and tried to integrate this wallbox into HA in the same way, I did it with the inverter. BUT - the problem is, that HA doesn’t accept to modbus connections to the same IP (of the inverter) and same port with different SlaveIDs.

I read about the Modbus Proxy, but before I’ll try it, I want to ask you, if anybody has experience with such a setup and knows how to configure?

2

While I dont have the proxy set up, I use the WiNet Modbus IP to get to the Wallbox.
But now that I think of it, was it really so, that you cant just make a new sensor under the normal hub just with a different slave id?

3

I tried it once again with your recommended configuration:

Inverter via LAN Port IP and SlaveID1
Wallbox via WiNet-S Port IP and SlaveID2

Now it’s working but I found 2 missing entities in the dashboard:

This dashboard refers to the following entities that are unknown to Home Assistant:

automation.wallbox_charger_remote_control_cmd
input_select.set_wb_remote_control

I checked the modbus_wallbox.yaml and I didn’t find these 2 entities. Did you extend the modbus_wallbox.yaml to get them? What am I making wrong?

Any help is welcome!

4

I think I got the same issue, but as I didn’t know what these do, they have been deleted.
But now as I searched what this is I found this sungrow/AC011E01_Holding-Register.tsv at 7fd90824c0ddabfe570f38588b9a5ca9fad3f775 · Eisbaeeer/sungrow · GitHub where you can control the actual charging. I can’t test this myself bc my grandparents don’t have an EV yet, but let me know, if you need help with setting this up.

5

Ok - thanks for the hint - I deleted them also and now it looks very well. Thanks a lot!