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

• My configuration follows https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Configuration
• I have read the Known Issues https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Known-Issues
• 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) <#913 (comment)> 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 <#913 (comment)>, 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: #914 (comment) ... an update to CPU firmware 4.24.20 might solve the issues.

[Zandor300]

Also note that only a single connection may be opened to the inverter’s Modbus TCP server at a time. So if you have multiple integrations that connect to the same inverter, only a single integration will be able to connect at a time.

[RaAdNe]

See: #914 (comment) ... an update to CPU firmware 4.24.20 might solve the issues.

Unfortunately CPU Firmware update together with battery SW update 3.5.10 does not solve the ModBus-TCP issue on my system. Both were installesd about 10 days ago by Solaregde via Remote support, no information, no comunication just silent update.

And of course there is only one active connection to the inverter Modbus-TCP Server. Currently its set to close after every pull-request, an d request are send efery 5 seconds. Keeping the connection open and variing the pull request timing between 1 second and 30 seconds doesn't change the result.

However I received an E-Mail from a SolarEdge Sales employee confirming that they have some inverters with ModBus-TCP com issues as described here. So at least they acknoledged there is an issue and no solution yet.

[tijmenvanstraten]

I repeatedly get this error message. Is this similar or the same?

Currently have the 3.2.1 version of the integration installed, but I've been getting this for months. It doesn't seem to affect data or control of the inverter though. Sometimes I receive an error message and I have to click resolve to fix it.

Logger: pymodbus.logging
Bron: custom_components/solaredge_modbus_multi/hub.py:500
integratie: SolarEdge Modbus Multi (documentatie, problemen)
Eerst voorgekomen: 23 januari 2026 om 12:54:32 (430 gebeurtenissen)
Laatst gelogd: 13:24:08

Failed to connect
Repeating....
Failed to connect [Errno 111] Connect call failed ('XXX.XXX.X.XXX', XXX)

[KriVaTri]

I’m having the same issue for many months now and it seems to be getting worse.
Luckily it always recovers.

[RaAdNe]

Months (>1/2 year), various e-mails and phone calls with my PV seller/installer and one of the SolarEdge sales staff for CH later, the problem remains unsolved. It appears SolarEdge has no clue how to solve the issue in their SW.

SE remotely installed different CPU SW versions (upgrades & downgrades) which made the situation even worse, e.g. with uncontrolled 30sec 1kW cycles charging the battery from mains at night (even charging from main is disabled in the settings), loss of SoC info for back-up reserve etc.

My solution is a firewall rule to block the inverter comm with internet to prevent SolarEdge from uncontrolled trial and error remote installations. Before I installed a SW combination that "only" has the ModBus-TCP com issue. For this I used the SE installer app and registered myself as self-installer. Important: Handle with care and don not change settings you do not fully understand.

The next step is installation of 2 Shelly power meters (Pro3 EM) to properly measure import and export from mains and inverter.

For my HA set-up and load balancing automation this means the use of reliable Shelly smart meters (Pro 3EM) while the SE integration will be used for DC load and battery load & SoC data only.

[wendels]

Logger: pymodbus.logging
Source: custom_components/solaredge_modbus_multi/hub.py:538
integration: SolarEdge Modbus Multi (documentation, issues)
First occurred: 5:47:37 AM (2 occurrences)
Last logged: 6:56:16 AM

No response received after 3 retries, continue with next request >>>>>

I've been getting the same pretty consistently over the past 4-8 weeks.

Version 3.2.2
with
SE15K-RW000BNN4 // Firmware: 0004.0024.0016
SE-MTR-3Y-400V-A // Firmware: 79

update/edit:

Logger: pymodbus.logging
Source: runner.py:289
First occurred: 2:32:54 PM (120 occurrences)
Last logged: 8:15:56 PM

ERROR: request ask for transaction_id=534 but got id=533,
...
ERROR: request ask for transaction_id=1470 but got id=1469
ERROR: request ask for transaction_id=1470 but got id=1469
ERROR: request ask for transaction_id=1470 but got id=1469
...

[Menz01]

it happens to me alot as well. then it will go a long time with it working too. right now its flapping again

This error originated from a custom integration.

Logger: pymodbus.logging
Source: custom_components/solaredge_modbus_multi/hub.py:521
Integration: SolarEdge Modbus Multi (documentation, issues)
First occurred: 11:50:45 AM (5 occurrences)
Last logged: 11:54:18 AM

Failed to connect
Repeating....