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.

[jamesrossell]

I am having the same issue, but it is going off repeatedly. I either have to toggle modbus using setapp or power cycle the inverter.

It then comes back in home assistant for a while but then stops responding again.

I've validated no network issues. Inverter is solid on ethernet.

Has anyone spoken to solaredge about this?

[m4rc77]

@jamesrossell also having the issue that the modbus-tcp-server on the inverter (firmware version 4.24.9) stops working repeatedly. In my case interestingly its always around 21:00 CET sometimes daily sometimes it works for a few days.

If you have a linux or mac system you can check the connection to the modbus-tcp-server with nc -vz inverter-ip-here 1502 command e.g. nc -vz 192.168.10.20 1502

If the modus-tcp-server of the inverter is still working. you get
Connection to <inverter-ip-here>port 1502 [tcp/shivadiscovery] succeeded!

if the modbus-tcp-server of the inverter is no longer working you get
nc: connectx to <inverter-ip-here> port 1502 (tcp) failed: Connection refused

I am pretty sure it's a firmware issue. Hope it gets fixed with a firmware >4.24.9. I read about people that requested downgrades from SE to solve it. I contacted my installer and asked if there is any update / fix available but I think it is not (yet) the case if I look at https://www.solaredge.com/en/support/residential-inverters-firmware

[r-stoeger]

Have the same issue.
Firmware Update to 4.24.16 did not solve the problem.
Actually I have an open case with Solaredge, hopening they can solve it.

[jamesrossell]

Thanks @m4rc77 for that validation and context.

I reached out to Solaredge support and they did a remote downgrade on my firmware and it seems to be stable again now, which is both good and frustrating. Why can't companies do updates without breaking suff and some kind of regression testing.

This is the reply I had from their support

"You've had an update to your case Modbus on SE8K-RWB48BFN4 losing connection with new FW (# 6255654) on 2025-11-20 10:09:28:
Naga Shreyas N said:
Hello!

I hope all is well.
I am following up on the ongoing issue.

Our senior team has reviewed the situation and downgraded the inverter firmware.
Please monitor the system and notify us if you notice any discrepancies.

Have a nice day!!

Thanks and kind regards,

Naga Shreyas N

Technical Support Engineer - Tier 1"

[kino13]

That is disappointing. In any case as I have commented I blocked the internet access of the inverter after the last update, I don't need any new functionality and it works for me. No more surprises

…

On November 24, 2025 4:29:50 PM GMT+07:00, James Rossell ***@***.***> wrote: jamesrossell left a comment (WillCodeForCats/solaredge-modbus-multi#914) Thanks @m4rc77 for that validation and context. I reached out to Solaredge support and they did a remote downgrade on my firmware and it seems to be stable again now, which is both good and frustrating. Why can't companies do updates without breaking suff and some kind of regression testing. This is the reply I had from their support "You've had an update to your case Modbus on SE8K-RWB48BFN4 losing connection with new FW (# 6255654) on 2025-11-20 10:09:28: Naga Shreyas N said: Hello! I hope all is well. I am following up on the ongoing issue. Our senior team has reviewed the situation and downgraded the inverter firmware. Please monitor the system and notify us if you notice any discrepancies. Have a nice day!! Thanks and kind regards, Naga Shreyas N Technical Support Engineer - Tier 1" -- Reply to this email directly or view it on GitHub: #914 (comment) You are receiving this because you commented. Message ID: ***@***.***>

[r-stoeger]

SolarEdge's solution for me: downgrade to 4.22.44 until a newer working firmware exists.
It would be nice, if I can block firmware updates without loosing cloud-based monitoring/statistics, but I think there is no chance to configure that.

[RaAdNe]

There are two threads on basically the same issue, see also #913 .

In my case downgrade CPU SW to 4.22.44 solved the complete ModBus-TCP freeze issue, but not wrong smartmeter Sunspec DID and added new issues with battery and power management. Probably caused by CPU , DSP1 and DSP2 SW incompatibilities.

[m4rc77]

FYI: Via my open case with SE I got a firmware update to CPU SW 4.24.20 that solved the modbus-tcp freezes.
I am just wondering why this version it is not listed under https://www.solaredge.com/en/support/residential-inverters-firmware ... maybe it is still BETA ... who knows. In any cases the modbus works stable but i have in my opinion a little too many errors in the error protocol of my inverter ... but this is another story.

[RaAdNe]

@m4rc77, thx for this info, in my open SE case there is no real progress, SE wrote about some remote management on my system and advised to restart. All failures remained. SW Verion still 4.22.44 (after SE Downgrade). As usual they did not specify what they remotely "managed" on my system. I do cross fingers to soon be in the position to report a stable and proper working SW configuration here (CPU, DSP1, DSP2 and Battery).