No more data after firmware update 4.24.9

[Mich-es]

Describe the bug

After running the FW updates from 4.23.36 to 4.24.9, no more data is being sent to HomeAssistant. Error message: An error occurred while attempting to open a Modbus/TCP connection.

Please confirm your configuration.

Expected behavior

Everything still works after the update

Screenshots

No response

Diagnostic File

Ich have no access, so i cant upload

Debug logs

Home Assistant Version

2025.10.1

solaredge-modbus-multi 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

[Mich-es]

Okay, it's working again. The fix was to go to the master's settings in SetApp. There, under Site Communications -> Modbus TCP -> Modbus TCP Disable, then Enable

I don't know why, but it worked for me.

[kino13]

I have this same issue, how did you access the SetApp?

[Mich-es]

You don't necessarily need SetApp, but you can download it from the PlayStore. Then take a photo of the QR code on your inverter. With any luck, you'll be able to access it. If not, you'll need to connect to your PC as described here: https://github.com/WillCodeForCats/solaredge-modbus-multi/wiki/Configuration

[kino13]

The SetApp didn't work for me, but I put the device into maintenance mode restarting and entering the local wlan.
What worries me is that the Modbus was ENABLED in the configuration, so I disabled it, enabled it again... and it started to work.

I am blocking the internet access of the inverter. No more unwanted firmware updates.

Incidentally, I have lost a lot of the sensors that I had, either they stopped responding or something has changed in the reporting, although the ones I was actively monitoring are still there.

Edit: The whole issue was unrelated to the Modbus-Multi integration.

[MattijsE]

Had the same issue (most likely after getting an update to 4.29.4). Disabling modbus and re-enabling it again solved it for me.

[kino13]

I am too scared that they will end up removing the functionality, is there any requirement or advantage in allowing internet access to the inverter?
Are the firmware updates fixing anything of importance? (I have not looked deep into this, no idea if they are publishing the changes).
Anyway, as I stated before, I am cutting the internet access to the device, no more surprises for me.

[widmermar]

Thank you, disabling and re-enabling modbus over TCP solved the issue. It's quite embarassing that this is necessary after a firmware update though.