connection question

[phatlewt]

Hello,

I've been using this integration for a while now, with my sigenstor connected through wifi. I plugged in a lan cable to sigenstor recently and from the sigen app it shows it's using the lan connection now. I tried setting up a new plant in HA, entering the sigenstor's lan ip but it doesn't seem to be able to communicate with the battery. I've also tried removing the existing integration containing the connection using the wireless ip and going through the setup process for the new lan ip but it still wasn't able to communicate. I can ping both the lan and wireless ip, both ips are statically assigned by router, and modbus is enabled (connection through wireless ip works fine).

Does anyone know if:

• modbus comms is only enabled for the wifi interface?
• do i actually need to disconnect sigenstor from the wifi network? (not sure how to do this from the app)
• any suggestions on how to go about troubleshooting this?

[phatlewt]

Update: I've managed to add the lan ip as a new plant after turning off the router's wifi.. not sure if it only allows modbus on 1 interface but if someone could confirm this it'd be great, thank you very much!

[StroppyOz]

I can't confirm for the Sigen stack but it's not uncommon for modbus to only allow one connection. To get around this, you can use a modus proxy such as https://github.com/Akulatraxas/ha-modbusproxy. From: phatlewt ***@***.***> Sent: Monday, 10 November 2025 11:09 AM To: TypQxQ/Sigenergy-Local-Modbus ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [TypQxQ/Sigenergy-Local-Modbus] connection question (Discussion #254) Update: I've managed to add the lan ip as a new plant after turning off the router's wifi.. not sure if it only allows modbus on 1 interface but if someone could confirm this it'd be great, thank you very much! - Reply to this email directly, view it on GitHub<#254 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPOKID4NTNRQ3VZI7BEJL63337JR3AVCNFSM6AAAAACLTLDM4GVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOJRHA3DONA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>

[StroppyOz]

* modbus comms is only enabled for the wifi interface? No. A network connection is a network connection. The medium in which it is delivered makes no difference. * do i actually need to disconnect sigenstor from the wifi network? (not sure how to do this from the app) If you're connecting to both wifi and LAN then I would disconnect wifi (the LAN connection is far quicker and more stable). Technically a double connection like this can work provided the Sigen stack knows how to handle it. However, as I mentioned in my other reply to you, the modbus connection may not be shareable, which might be causing your problem. * any suggestions on how to go about troubleshooting this? From: phatlewt ***@***.***> Sent: Monday, 10 November 2025 11:03 AM To: TypQxQ/Sigenergy-Local-Modbus ***@***.***> Cc: Subscribed ***@***.***> Subject: [TypQxQ/Sigenergy-Local-Modbus] connection question (Discussion #254) Hello, I've been using this integration for a while now, with my sigenstor connected through wifi. I plugged in a lan cable to sigenstor recently and from the sigen app it shows it's using the lan connection now. I tried setting up a new plant in HA, entering the sigenstor's lan ip but it doesn't seem to be able to communicate with the battery. I've also tried removing the existing integration containing the connection using the wireless ip and going through the setup process for the new lan ip but it still wasn't able to communicate. I can ping both the lan and wireless ip, both ips are statically assigned by router, and modbus is enabled (connection through wireless ip works fine). Does anyone know if: * modbus comms is only enabled for the wifi interface? * do i actually need to disconnect sigenstor from the wifi network? (not sure how to do this from the app) * any suggestions on how to go about troubleshooting this? - Reply to this email directly, view it on GitHub<#254>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BPOKID23JIR66I3KHEORML3337I3NAVCNFSM6AAAAACLTLDM4GVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZZGEZDEOJUGQ>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>