Access via Modbus broken after inverter firmware update

[mtbsteve]

Describe the bug

Since yesterday, I cannot access my Solaredge Environment via ModbusMulti anymore.
SE Inverter Firmware version: 4.25.11
ModbusMulti Version 3.3.0-evse.6
HA Core 2026.6.4
The Inverter is properly connected to the internet, reporting via the official SE app works, Access via the SE API works,
I can connect directly with the SE App to the inverter, no issues in the error logs.-
restart of HA or reload of the ModbusMulti adapter did not solve it.
The Modbus Interface was working fine over the past 2,5 years w/o any issues.
Any ideas?

Expected behavior

Access via Modbus interface

Screenshots

No response

Diagnostic File

This error originated from a custom integration.

Logger: pymodbus.logging
Source: custom_components/solaredge_modbus_multi/hub.py:544
Integration: SolarEdge Modbus Multi (documentation, issues)
First occurred: 5:51:18 PM (28 occurrences)
Last logged: 8:01:37 PM

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

Debug logs

Home Assistant Version

2026.6.4

solaredge-modbus-multi Version

3.3.0-evse.6

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

[WillCodeForCats]

Follow the instructions in known issues and cycle the modbus setting Disabled, save, then Enabled again.

[xperseguers]

Confirming that it fixed the problem. Funny I got the same problem since yesterday as well and tried to reboot multiple times but forgot about the toggling of the Modbus setting. Thanks @WillCodeForCats for the reminder :)

After having a look at the history of the SolarEdge version, it jumped from 4.23.27 to 4.25.11 before breaking the link, so this auto-update from SolarEdge must somehow take over the Modbus link somehow I guess...

[Free-LM]

Alternative solution that worked for me (for people without setapp or the right accessprofile):

1. disabled the hub in HA
2. put the invertor P-I-O switch to the Off state
3. disconnected power by switching the circuit breaker off
4. wait 20 sec
5. Put circuit breaker back on
6. put the invertor P-I-O switch back to on
7. activated the hub in HA again

Before swithing off the invertor I saw that the modbusconnection was still claimed according to the invertor.
Cleared this appearantly by taking the power off instead of the other solution of toggling the Modbus setting.

[mig235]

I can agree, and I can confirm that changing the Modbus Settings from "Enabled" to "disabled" and than "enable" it again solved the issue.
I can only access http://172.16.0.1 via IOS Devices but have issues with Android devices. The connection with my Inverter SE10K-RWB48BFN4 works way better, faster and is more stable with IOS than Android.

[WillCodeForCats]

I've seen reports that the inverter doesn't always use 172.16.0.1, sometimes it uses a .1 address in a different range. You can always look at network status/details and whatever the "router" address is that will be the inverter.

[WillCodeForCats]

Alternative solution that worked for me (for people without setapp or the right accessprofile):

I've added this to the wiki entry.

[mtbsteve]

Works again! Thanks to all of you for your help.