I have 3 solaredge inverters (Se2200H, SE5K and SE5K) I had to do (Very annoying, no more SE for me..) firmware updates on 2 of them. Now 2 of them stopped communicating with Victron properly. Keeps loosing connection, as mentioned a lot above. Requested SE to rollback firmware.
If i can help in any way, just let me know.
EDIT: Added a snip. PV readings through Victron (In Homeassistant)
Thanks for all this information shared - like @WEHA I got updated to SolarEdge SW build 4.24.9 and I was asked to give it a try: Cerbo is on latest V3.66 - there is no difference compared to previous 4.23.36 build. I couldnāt find a release note of this build 4.24.9 to check if there is a change in the communication area at all.
My home automation relies on the central data collection of VICTRON Cerbo for all my 5 different PV-inverter. This worked perfectly for a long time - this SolarEdge bug introduced is a mess for my system thus. Next SolarEdge Service Level was informed.
I want to share an interresting observation with you guys.
SE5K South orientation, 16 panels. Yellow line, CPU FW4.23.36
SE5K West orientation, 16 panels, Red line, CPU FW 4.24.9
SE2200H East (7 panels) /West (6 panels) ,Blue line, CPU FW 4.24.9
Last Thursday all of a sudden the connection with Victron returned to normal for extender period.
Snip from HomeAssistant:
But then on Friday everything was back to ācrapā 
Literally nothing changed in SolarEdge or Victron settings over these 2 days,so what could have caused the connection to become normal temporary?
Just luck, Iām afraid. Itās typical for this bug. Sometimes the stars align and it just works for 2 days and then breaks again.
Hallo allemaal. Ook ik heb een soortgelijk probleem. De communicatie tussen mijn SolarEdge omvormer en de Victron hapert en is meest van de tijd onderbroken.
Ik lees dus graag mee.
Ik las op dit forum dat dagelijks herstarten van de Cerbo een tijdelijke oplossing gaf.
Ik herstart nu de Cerbo sinds een aantal dagen vlak nadat de SolarEdge vermogen gaat afgeven. ( rond 9 uur) De communicatie herstelt zich en nlijft dan gedurende de dag goed. Nadat de zonproductie aan het einde van de dag beeindigd is, komt de storing weer na een uurtje terug.
Ik heb een HD wave SE5000h met Firmware 4.23.36
Ik zag dat er een firmware update 4.24.9 was. Deze heb ik zojuist geinstalleerd. Ik wacht afā¦
Aanvulling 26-10-2025. De firmware 4.24.9 geeft geen verbetering en het probleem van onderbrekingen in de communicatie tussen mijn SE5000h en de Cerbo blijven bestaan.
Dit is duidelijk waarneembaar in de VRM grafiek Omvormer SE-PV (L1 Voltage, L1 Current).
Voor mij werkt de eerder genoemde tijdelijke oplossing. Dagelijks, als de PV productie op gang is gekomen, de Cerbo even herstarten. Dan zijn na c.a. 2 minuten de PV gegevens weer aanwezig en deze blijven aanwezig, totdat de zon ondergaat en er geen PV productie meer is. De communicatie is elke dag gedurende de donkere avond en nacht verstoord, tot de volgende morgen na herstarten van de Cerbo.
Pas NA het tijdstip van herstarten, is er een goede communicatie. Dus herstarten later in de ochtend, zorgt voor onjuiste (te lage) PV waarden.
Just installed the new solaredge firmware 4.24.9 to my SE10K and SE10K Hybrid (Storedge). The communication with the SE10K looks to be working just fine now. As for the Hybridā¦ it falls in and out of communication every few seconds. It starts then to reconnect afterwards it happens again, and again.
Have restarted the Cerbo what didnāt work. Did the same with the SEās. Just to be certain. That didnāt work either.
Question: The last working firmware is 4.23.27?
Can anyone pls tell us the latest stable working Solaredge version ?
I noticed the problem in my 4.23.36, the upgrade to 4.24.9 was not helping me (and others)
I got downgraded to 4.23.15 but up to now I cannot see any improvement (Not sure when the SW was changed - SolarEdge is changing the SW without any customer informationā¦.? I can still see regular communication losses )
Above I see SW 4.22.44 is a stable one - can someone pls. confirm this ?
This information may help Solaredge as well to identify the bug introduction
Now Iāve got another upgrade (i.s.o. the requested downgrade) from SolarEdge from 3.2543 to 3.2807.
But also this upgrade did not improve anything.
On the SE website I see only the firmware 3.2537 for my SE3000H/SE2200H inverters with LCD and no StorEdge, the versions 3.2543 and 3.2807 are not mentioned there.
In this topic(message 60) I see that user wgrant had a firmware version 3.1818 that was running a stable modbus TCP communication (but not with Victron).
I have asked now for a downgrade to version 3.1818
It seems that Iām the only one in this topic that is using an SE inverter with LCD (and no StorEdge) ?
@Honza I have a SE17K with cpu-version 3.2537 and it has been working perfectly up to now. Venu OS 3.66 works, but the total production is way too low in latest beta versions ( 3.70~71)
Just my 5 cents:
I have a SE10k-RWS on FW 4.22.44 and this has been stable for a long time. SE is coupled to Victron via Modbus TCP by means of Home Assistant Proxy addon.
Keeping my fingers crossed that it stays this way 
I have a SE6K updated to version 4.24.9. Sadly the modbus communication remains unstable. I have to reboot my Cerbo on a daily basis to get the connection back.
Open a ticket, request to revert back to 4.22.44.
I can confirm that worked for a SE5K and SE2200H.
Doneā¦ thanx! Hope this helps
The downgrade to 4.23.15 had some improvements - but only in the Victron grafical representation of the SE values (the charts were mostly complete), but the logged values in my influxDB (generated by Cerbo NodeRed export via MQTT) still showed interruptions (every 4 minutes) and I could see the SE entity come-and-go.
After this report to solarEdge Support I got further downgraded to 4.21.23 - this now looks stable to me after some days ;>)
I asked SE to downgrade the firmware to 4.22.44ā¦ they replied they did.. but it is showing as version 4.24.15 nowā¦
Sadly, no improvements in MODbus connection sability. Will place a second request for downgrade..
Same here, logged a ticket for a customer and again got replies next to the question. Instead of downgrading, upgrading. Very frustrating
@Dimitar.S can you shed a light on how the fix is progressing? or if no fix soon, at least inform your firstline support about it. Now tickets get blocked or back and forth 3-4-5 times before we finally receive the downgrade.
Thanx!
I integrated my solaredge SE4000 today and noticed the communication was extremely unstable. It would work for a few seconds, then drop out for 10 minutes and then come back for a few seconds. Victron is at version 3.66 and I also upgraded the solaredge inverter to the latest firmware using setapp.
Interestingly enough after doing a reboot of the victron the communication now seems to be stable. But according to comments here, this situation will come back? So why does a reboot of the victron fix the communication?
Worked for a few days, then communication dropped again. This is for sure an issue with victron because a victron reboot fixes it.
I had the same issue with my SolarEdge system. I contacted SolarEdge support to request a downgrade from version 4.23.36 to 4.22.44. They asked whether I was an installer or the owner (I said installer ā otherwise they donāt provide much assistance). They opened a ticket, and after about a week I received instructions for the downgrade, but it didnāt work. I reached out to them again, and this time they completed the downgrade on their end. Iām now running version 4.22.44, and everything works perfectly on the dashboard.
I still have an issue with the VRM portal ā it reads my grid values incorrectly, but that might be a Victron problem. The same configuration appears differently on the dashboard and in the VRM portal, so maybe Iāll find the answer in another topic. This topic was very helpful for me, thank you all.
I explain my problem in this topic : VRM portal show different grid data from Dashboard
