Setup connectivity issues

[och29]

Can anyone help me troubleshoot my setup - I can't connect HomeAssistant and my Sig setup. I note a previous Discussion where the installer hadn't setup the ModBus so I will query that with them (similarly they sent photo evidence) after the weekend but I want to exclude an issue with my setup locally. On the day the setup was commissioned I had network issues related to a router which I've now replaced. Initial setup was completed via WiFi bypassing a switch that was being affected by router issues. Connectivity was fine and I have always been able to access the app with full function.

Layout:

SigenStor with 10kW inverter with 4x 8kW batteries + solar PV
--> Ethernet connection from RJ45 1 to Unifi Mini Flex switch

• I have reterminated the cables to ensure that's not an issue

--> Unifi Mini Flex to UniFi switch

• Other devices on the mini flex are functioning well
• The light on the port used for the SigenStor shows an FE connection as expected based on the Sig documentation

--> Unifi Switch to UniFi Router (with PiHole for DNS)

• The SigenStor is given an IP for both the WiFi and ethernet connections

Status:

Unifi - Ethernet and WiFi IP address show as connected with no issues
SigEn app shows matching ethernet and wifi IP addresses
SigEn app is able to swap between by two wifi networks (I have a IoT network under a different VLAN and the IP address is correct based on that VLAN tag)
SigEn app shows the SigenStor Ethernet as 'currently used' (wifi and cellular also 'green')

Troubleshooting:

Ping wifi ip from HomeAssistant and laptop - no issues
Ping ethernet ip - no connection
HomeAssistant template sensors, modbus sensors etc all show up
HomeAssistant igen_modbus_host_ip

• WiFi IP does not work
• WiFI IP when on my other network doesn't work
• Ethernet IP doesn't work

I've tried some free ModBus TCP programs to see if I can connect - again, I'm not able.

Any suggestions for troubleshooting or fixes would be greatly appreciated

I suspect this is an issue relating the the modbus setup or the ethernet connection but am at a loss for what to do next.

[polakatl]

First, make sure your installer setup modbus correctly as in the screenshot below.
Next make sure your secrets.yaml has the correct IP address. Try the WiFi IP as HA is able to ping that.

[och29]

Hi, thanks for the quick response. I've already tried those steps. Do you have a suggestion for how to troubleshoot the connection? I've also tried with the ModBus Proxy Add On and setting the IP secret to 0 - that also didn't work. I think it must be a connection issue but I'm not sure how else I can troubleshoot.

secrets.yaml

UniFi console

MySigen App

Image from my installer

[polakatl]

You have a complex networking scheme using Unifi, VLANs and Pu Hole etc. You can try to simplify it for testing. I also have Unifi with a iot wifi Vlan that is wide open for now to my main LAN. HA connected straight away without any fuss. As soon as I rebooted HA with the correct Yaml files the sensors were live.

…

________________________________ From: och29 ***@***.***> Sent: Saturday, March 8, 2025 1:27:55 PM To: TypQxQ/Sigenergy-Home-Assistant-Integration ***@***.***> Cc: polakatl ***@***.***>; Comment ***@***.***> Subject: Re: [TypQxQ/Sigenergy-Home-Assistant-Integration] Setup connectivity issues (Discussion #74) Hi, thanks for the quick response. I've already tried those steps. Do you have a suggestion for how to troubleshoot the connection? I've also tried with the ModBus Proxy Add On and setting the IP secret to 0 - that also didn't work. I think it must be a connection issue but I'm not sure how else I can troubleshoot. secrets.yaml image.png (view on web)<https://github.com/user-attachments/assets/7d31668f-b48b-4306-aa01-df262a17aecc> UniFi console image.png (view on web)<https://github.com/user-attachments/assets/fabf6aab-4ed8-4ded-b4f1-f9558aad1849> MySigen App image.png (view on web)<https://github.com/user-attachments/assets/4c5c7238-5190-406c-8036-4192a5942402> Image from my installer image.png (view on web)<https://github.com/user-attachments/assets/5c240860-34db-444c-99fb-8e17dd556387> — Reply to this email directly, view it on GitHub<#74 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BM2IVT4LVXMTMSL4GVB447L2TLO4XAVCNFSM6AAAAABYSF4WN6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBTGQ2TKMY>. You are receiving this because you commented.Message ID: ***@***.***>

[och29]

Thanks for the response. I agree it could be thought of as complex but it didn't work with a simple setup. PiHole is for DNS so I don't think that's an issue and I've confirmed this by turning it off. I've also tried without a VLAN, connecting it to my 'default' network - again, this didn't work.

I've now tried unplugging the ethernet cable and reverting to WiFi. I can ping the SigenStor from my PC and from HomeAssistant (on both by IoT VLAN and the default network) but the ModBus sensors still don't work.

While it could be that the installer didn't enable the ModBus correctly, the fact I can't ping the ethernet IP is strange.

[polakatl]

I can ping my Sigenstor with both modbus enabled and disabled. It's possible that your installer doesn't know what to do or is ignoring you. They need to click on the Sigenstor image in the home graphic and scroll down to the modbus section. The TCP server needs to be enabled like in the screenshot I shared. Ask that they send a screenshot of this before tearing your network apart.

…

On Sat, Mar 8, 2025 at 9:24 PM och29 ***@***.***> wrote: Thanks for the response. I agree it could be thought of as complex but it didn't work with a simple setup. PiHole is for DNS so I don't think that's an issue and I've confirmed this by turning it off. I've also tried without a VLAN, connecting it to my 'default' network - again, this didn't work. I've now tried unplugging the ethernet cable and reverting to WiFi. I can ping the SigenStor from my PC and from HomeAssistant (on both by IoT VLAN and the default network) but the ModBus sensors still don't work. While it could be that the installer didn't enable the ModBus correctly, the fact I can't ping the ethernet IP is strange. — Reply to this email directly, view it on GitHub <#74 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BM2IVT4FJTAUCBL34WP6PXD2TNGZHAVCNFSM6AAAAABYSF4WN6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBTGY3DQOI> . You are receiving this because you commented.Message ID: <TypQxQ/Sigenergy-Home-Assistant-Integration/repo-discussions/74/comments/12436689 @github.com>

[och29]

Interesting. I did share the screenshot from my installer already... maybe they didn't click save? The only thing that makes me question this is that the ethernet connection doesn't seem to work as expected.

[maxw3l]

This looks exactly like the issue I reported here: #67

Is there a difference in app versions that installers have?

Edit: I can ping the IP address, and PowerHud Modbus Tester refuses to connect via TCP but connects via UDP but then gives "Error: Timeout".

[och29]

Yes, it does seem the same.
My image from the installers app is the same. I checked with them and they say the Modbus setting was activated. From what I understand, the new version of the app just needs 'Modbus TCP Server Enable' set to on and saved. There isn't an option for port and the other settings are for RS485 connections rather than over ethernet.

My installers have contact Sig to find out what might be causing the issue and I'll update the thread when I hear back.

[och29]

Disappointingly, this was an issue with my installer. I suspect they hadn't tapped save after turning on 'Modbus TCP Server Enable'. However, it maybe an issue in the installer app as I've had a similar issue in Connectivity which didn't save the first time I tried it.

I would encourage anyone having issues to ask your installer to re-open the setting once they enable the modbus and double check it is enabled (perhaps telling them there have been issues previously).

I did get the following response that Sig sent to my installer. I'm not sure it's helpful for users but I'll leave it here and suggest it as an addition to the documentation.

When the device is connected to a third-party EMS that needs to use ModBus-TCP communication, click "Settings" on the "Device" page through the mySigen app, and set the following parameters on the "All-in-One Settings" screen.
1.ModBus Server Address: Specifies the IP address of a third-party EMS server when the device functions as the Modbus TCP client.
2.ModBus Server Port: Specifies the port for the device to communicate with a third-party EMS when the device functions as the Modbus TCP client.
3.ModBus Local (Slave) Address: Specifies the Modbus address of the device when the Modbus protocol is used. You must set different Modbus addresses for devices in parallel mode.
4.ModBus TCP Server Enable: When this parameter is set to , the device functions as the Modbus TCP server and enables connection with a third-party EMS.

[polakatl]

Installers should not have a problem. Like anything done remotely it's best practice to refresh or reload the page after saving to make sure the settings took. If the installer doesn't do this they risk customer service issues. The installer has the same app, it's just different user permissions that enable the additional functionality. I think Sigen should have an option for the installer to enable these settings to the end user. After all, the user is purchasing the equipment and not leasing it as a managed service from the installer.

…

On Tue, Mar 11, 2025 at 11:29 AM Maxwell Shifman ***@***.***> wrote: This looks exactly like the issue I reported here: #67 <#67> Is there a difference in app versions that installers have? — Reply to this email directly, view it on GitHub <#74 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BM2IVT4FMILNDJS3QUTPDSL2T23IBAVCNFSM6AAAAABYSF4WN6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBWGAYTKNY> . You are receiving this because you commented.Message ID: <TypQxQ/Sigenergy-Home-Assistant-Integration/repo-discussions/74/comments/12460157 @github.com>

[och29]

I agree, this should be an option for end users to enable 'advanced' settings - perhaps we could suggest this to Sig so there's a chance something will actually change?

In terms of installers, this is clearly not an isolated issue so perhaps there is an issue with the app function or the training Sig provide to installers to make them aware of best practice.

To help future users here, I think it would be worth updating the docs since and the FAQs - I'll add it to my to do list.

[maxw3l]

I've had my installer check and recheck, pushing the Save button, and I'm still not receiving any data.

…

________________________________ From: och29 ***@***.***> Sent: Wednesday, March 12, 2025 8:41:10 AM To: TypQxQ/Sigenergy-Home-Assistant-Integration ***@***.***> Cc: Maxwell Shifman ***@***.***>; Comment ***@***.***> Subject: Re: [TypQxQ/Sigenergy-Home-Assistant-Integration] Setup connectivity issues (Discussion #74) I agree, this should be an option for end users to enable 'advanced' settings - perhaps we could suggest this to Sig so there's a chance something will actually change? In terms of installers, this is clearly not an isolated issue so perhaps there is an issue with the app function or the training Sig provide to installers to make them aware of best practice. — Reply to this email directly, view it on GitHub<#74 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAPJPV26QTIFKRBFSWDCW2L2T5J7NAVCNFSM6AAAAABYSF4WN6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBWG4ZDIMI>. You are receiving this because you commented.Message ID: ***@***.***>

[polakatl]

Verify you have the correct IP address for the Sigenstor - check your router or other networking tools. Verify you can ping the Sigenstor from the network that Home Assistant is on. Verify that you have the correct IP address in Home Assistant secrets yaml. The Defaults for port should work.

…

On Wed, Mar 12, 2025 at 12:10 AM Maxwell Shifman ***@***.***> wrote: I've had my installer check and recheck, pushing the Save button, and I'm still not receiving any data. ________________________________ From: och29 ***@***.***> Sent: Wednesday, March 12, 2025 8:41:10 AM To: TypQxQ/Sigenergy-Home-Assistant-Integration ***@***.***> Cc: Maxwell Shifman ***@***.***>; Comment ***@***.***> Subject: Re: [TypQxQ/Sigenergy-Home-Assistant-Integration] Setup connectivity issues (Discussion #74) I agree, this should be an option for end users to enable 'advanced' settings - perhaps we could suggest this to Sig so there's a chance something will actually change? In terms of installers, this is clearly not an isolated issue so perhaps there is an issue with the app function or the training Sig provide to installers to make them aware of best practice. — Reply to this email directly, view it on GitHub< #74 (reply in thread)>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AAPJPV26QTIFKRBFSWDCW2L2T5J7NAVCNFSM6AAAAABYSF4WN6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBWG4ZDIMI>. You are receiving this because you commented.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#74 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BM2IVT37UYNGPD7MIBLVSNT2T5UPHAVCNFSM6AAAAABYSF4WN6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBWG43TSOI> . You are receiving this because you commented.Message ID: <TypQxQ/Sigenergy-Home-Assistant-Integration/repo-discussions/74/comments/12467799 @github.com>

[maxw3l]

I've 100% confirmed the IP address is correct. It's in the app, and the same IP is showing up on my UniFi gateway.  Secrets.yaml shows the correct IP:  I can ping the device fine from the network (and it's obviously connected as the Sigen app works:  Any other thoughts?

[dHamburgler]

I am in the same boat as @och29 after having a Sigenstor installed and the Modbus TCP was deactivated. I clicked around the site and discovered that you can now set "Remote EMS Mode" in the Operation Mode setup. After this mode is set, the internal IP over port 502 was open.
$ nc -zv 192.168.178.X 502
Connection to 192.168.178.X 502 port [tcp/*] succeeded!

Once finished, I changed the Operation Mode to what I had before. Hopefully the setting sticks and is not reset at a later date.