Modbus connection not stable

[joelegg]

Describe the bug

not sure if this is something that can be fixed on this side, but solaedges latest firmware has had issues with modbus connection staying stable. firmware 4.24.14

The conneciton connects (reload) then fails/drops after 5 seconds or so after that.

Failed setup, will retry: Setup failed: Modbus Error: [Input/Output] No response received after 3 retries, continue with next request

It seems to connect sometimes not others.

Expected behavior

stable connection

Screenshots

No response

Diagnostic File

config_entry-solaredge_modbus_multi-01JYR0FMQPPWCAVG782ANQWBFJ (2).json

Debug logs

Home Assistant Version

2025.10.1

solaredge-modbus-multi Version

Version 3.1.7

Installation Type

HAOS

Read the Instructions

• [x] My configuration follows https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Configuration
• [x] I have read the Known Issues https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Known-Issues
• [x] This issue is not about a template error (do not report template errors, read https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Template-Design-Notes)

Additional Context

No response

[haferm]

maybe this is because you have another solaredge plugin installed? "https://github.com/binsentsu/home-assistant-solaredge-modbus" just an idea...

[joelegg]

could be! its instaled but not setup. i have just deleted it.

[kino13]

I have the same issue, and I have verified that no other solaredge integration is installed.

I am also scanning the ports of the inverter... and I can't find or detect anything. The modbus should be in the tcp 1502, is it possible that SolarEdge has disabled the function?

[joelegg]

Yes. You need to connect to your inverter and enable it.

On Fri, Oct 10, 2025, 9:24 PM kino13 @.***> wrote:

kino13 left a comment (WillCodeForCats/solaredge-modbus-multi#913) https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/913#issuecomment-3389247125

I have the same issue, and I have verified that no other solaredge integration is installed.

I am also scanning the ports of the inverter... and I can't find or detect anything. The modbus should be in the tcp 1502, is it possible that SolarEdge has disabled the function?

— Reply to this email directly, view it on GitHub https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/913#issuecomment-3389247125, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7LMITOHJ253ZA67OUVRPT3W6COZAVCNFSM6AAAAACIV2V2PGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBZGI2DOMJSGU . You are receiving this because you authored the thread.Message ID: @.***>

[RaAdNe]

I have the same ModBus-TCP issue on my SolarEdge inverter, plus an open service case with SolarEdge via my PV Installer. HA with access to the SolarEdge Modbus-Multi integration only.

At least since August twice a day short inverter comm interruptions, sometimes wrong smartmeter SunSpec DID in the data after ModBus-TCP were available again by the inverter. At the end the ModbusTCP stopped working completely until my installer disabled and enabled the interface in the inverter setting, which finally he gave up to perform every day.

Since then SW CPU SW versions up-&downgraded by SolarEdge: start point V 4.23.36, DSP1 1.20.23108, DSP2 2.20.23030 1st update V 4.29.9, DSP1 1.20.24102, DSP2 2.20.23030 2nd downgrade/update V 4.24.16, DSP1 1.20.24102, DSP2 2.20.23034 3nd downgrade V 4.22.44 DSP1 1.20.24102, DSP2 2.20.23034

With the partial SW downgrade ModBus-TCP communication got more stable, i.e. not total freeze since then, but new issues with power and battery management poped up. There is no proper working solution yet, but it's not a solaredge-modbus-multi bug, it's clearly the Solar Edge inverter SW issue.

[m4rc77]

See: https://github.com/WillCodeForCats/solaredge-modbus-multi/issues/914#issuecomment-3617538990 ... an update to CPU firmware 4.24.20 might solve the issues.