Still cant get my sigenenergy ess to work with integration

[Michaelhasweden]

Hi,

I’m trying to integrate my Sigenergy ESS with the Sigenergy ESS Home Assistant HACS integration but I cannot get the integration to connect even though Modbus TCP itself appears functional.

My setup:

• Home Assistant latest version
• HACS installed correctly
• Integration: Sigenergy ESS
• Sigenergy firmware: V100R001C21
• Modbus TCP enabled in installer mode
• Installer confirmed SAVE was pressed after enabling
• Modbus Native (Slave) Address set to 1
• Device connected via Ethernet
• Static DHCP reservation configured
• Mesh disabled for device in TP-Link Deco
• Device locked to single node
• WiFi disabled during testing
• Ethernet IP currently: 192.168.68.90

What I verified:

• Ping to ESS works reliably
• Port 502 is OPEN
• nc -zv 192.168.68.90 502 succeeds
• tnc 192.168.68.90 -port 502 succeeds
• Home Assistant and ESS are on same subnet
• No firewall isolation active
• Tried both WiFi and Ethernet
• Rebooted ESS multiple times
• Re-enabled Modbus TCP multiple times
• Restarted Home Assistant multiple times

What I tested in the integration:

• inverter_slave_ids 1–9
• Port 502
• Correct IP confirmed
• Read-only mode enabled

Behavior:

• Integration always returns “Couldn’t connect”
• No meaningful HA log entries appear
• No TCP timeout anymore after fixing networking
• Modbus port clearly responds but integration still cannot initialize

Any advise?

Thanks!

[Rayeliint]

I am in the same boat as well, pretty much done everything that Michaelhasweden has done.
Also I noticed on the installer side when setting up the Modbus, you can sellect Modbus RTU Host or Modbus RTU Slave. Can someone confirm what this should be?
Additionally, in the latest app when logged in as a user, under Settings- System Settings- scroll down to Modbus TCP Server Settings, there is a switch to turn this on there now.

[Michaelhasweden]

Thank you for the information, missed that setting in the app. After turning the setting on the integration found my system and is now running.

the instruction for installing should update.

thank you again

[Rayeliint]

Wish it would work for me!!
Can you confirm if the Modbus RTU Host or Modbus RTU Slave is set by the tech?
This may help me.

[TypQxQ]

Yes. I am rolling out the update myself and will update it later.

[Rayeliint]

An update to the instructions or an update to the integration or both?

[Michaelhasweden]

set to slave
Integration wont start tho i see it…

[Rayeliint]

Bit frustrating for me as I had it working perfectly for months, then had a recall on the inverter and swapped over. Had to remove the system and set up again, but not able to.

[Michaelhasweden]

This solved it for me
Integration wont start on ethernet
Rolled back wifi locked ip, no mesh
Integration found all batteries and inverer so maybe try wifi and or ethernet.

[MarkeeMark]

Looking for help here too. I have tried all that Michael did and still having no luck.
I have installer access on my app and have updated to the latest version.
Sigenergy support have suggested it is settings in home assistant after raising a ticket.
I am on a wireless only connection, cannot currently get an Ethernet cable to my Gateway.

Should I delete the SigESS from HACS and if I did do I have to clear anything from any memory or cache as such?

Here’s hoping an update helps.

[MarkeeMark]

Have now requested an update from my ISP.

[EnterTheMaelstrom]

Did you find a solution yet?

I had an internet connection loss for a few days, then installed current firmware and app updates and now I cannot connect to my system anymore (per Modbus). It had been running perfect for like a year, but now it tells me (via tnc); port 502 is closed. Installer modbus settings were not touched and I activated the new switch in my app...

Sigen support told me everything is fine from their side and requested communication protocol logs of my 3rd party app (whatever exactly they mean by that).

[MarkeeMark]

Yes my problem was my router, TPLink Deco x50 not allowing access on port 502 while having the Sigenstor on the guest network.
So a hardware issue fixed by upgrading to a Ubiquity Unifi Express 7. Setup up a VLAN for the Sigenstor and it works beautifully.
Now adding a Flex Mini switch to have my HA (and all devices) on its own IoT VLAN which can see the Sigenstor on the other VLAN, which again is limited by the Express 7 only having one LAN ethernet port. If this makes sense. A lot of help was had from an IT friend and Claude though.

[EnterTheMaelstrom]

I also use Unifi Equipment, although my SigenStor is currently in the same network as my Home Assistant. All connected via FE through two switches. And it did work already before my internet outage/updates, so I assume the network is okay.

Guess I have to get me an IT friend too :D
Thanks

[EnterTheMaelstrom]

For reference or other users who stumble upon this thread: If you have similar problems, a part of it might be, that you need to do a physical restart of the sigenstor. It is not enough to switch it off and on in the app.

When changing networks, there seems to be a bug (found a hint on reddit) that the modbus service can crash and is out of sync with the information shown in the app(s). Even Sigenergy support could not see that the service was actually not running and as a result, port 502 was unreachable.

So, "did you turn it off and on again?" is actually a valid strategy to restart the linux service, but you have to follow the manual on how to do so with your setup (extra step if you have a gateway).

Maybe, if Sigenergy reads the posts here, they could add a service restart when you toggle the button on/off or even show the service status somewhere.