After commnication loss (April 24, see above) and manual Cerbo reset, my communication is up and running again (4.24.22 with Cerbo 3,72). On April 29, SE downgraded my inverter to 4.22.44 (although I requested to downgrade to 4.21.23 as this was working fine for me last year for months / until HW Failure in March 26) .
Surprisingly this is now running with no communication losses already 25 days
@GadingeL the v3.80 is the beta version, correct?
On regular released versions i see the v3.73 as latest for the large version.
Still running my SE on 4.22.24 after having them down graded.
Your 3.80 still running stable with the latest SE firmware?
A question that is not answered yet (or asked I think) is if Solaredge 4.24.25 runs stable with Venus 3.73
So that we don’t have to run beta software to make it work 
Thanks!
V3.80~27 is a beta version
Since 8. May I use FW 4.24.25 on my SE9K and several V3.80 beta’s wihout any communication drop.
just installed V3.73 in my SolarEdge - Victron Setup , after a first test (disconnect SE-LAN for 5 min) comunication recovers without falling in a 5 minute comunication drop loop ( as observed with SE 4.24.22 )
Will test this setup in the next weeks and give feedback here in about 2 weeks
I asked SolarEdge to upgrade my SE5K to firmware version 4.24.25 and upgraded my Cerbo GX to Victron 3.80~32. It’s been over 24 hours and the inverter has not dropped yet.
I asked SolarEdge for the release notes for this firmware version but they are yet to reply,
hi, this might be a really silly question, but could you explain to me how this works?
greetings, Bas
Hi GadingeL, not sure about your 3.73 and the 4.24.25 … yesterday the solaredge support has upgraded my firmware to 4.24.25 from 4.22.44 and untill now i have not seen any glitches (and very few sun today). I am running 3.75 as latest version on my Cerbo GX.
Thanks for all the experimenting …
Hi, can confirm that since SE FW 4.24.25 I had no “communication lost-loop”, SE still is performing a hard reboot every evening, but Venus OS can deal with this.
Meanwhile I use V3.80~39 (=beta) with out any SE communiation problems.
I’ve also had no problems with the same SE firmware for 1.5 years. The units are an SE7K and an SE3860H.
The firmware on my Cerbo is V3.72.
Hi all,
Any news on this issue? All problem’s solved? Can everyone update the SolarEdge firmware to the latest version without risk? Close the topic?
I have been running on 3.67 for a long time because of this issue. I have tried 3.72 and the earlier 3.80 betas but the problem was still there, it failed after a week on average. Now I have installed 3.79 (stable) and still no issue after 2 weeks. Will now try the 3.80 (stable).
I still have a problem with my SE2200H (LCD) running firmware version 3.2527. I have a Victron Multi RS Solar inverter with a Cerbo GX (firmware 3.79). The Modbus communication keeps dropping out. The production graph for the SolarEdge AC PV inverter has gaps every day. As a result, DESS doesn’t work properly. I’m not a programmer.
I found a solution by using a home assistant computer. I installed the app GitHub - Akulatraxas/ha-modbusproxy: Hassio Addon packaging modus-proxy · GitHub
Now the home assistant is a passthrough for the modbus tcp signal. In the victron ‘remote console’ I added manually the IP adres of the home assistant computer. (settings > integrations > PV inverters > manually add IP adress)
This was highlighted in this topic more than a year ago already
Alternative: a Python proxy that multiplexes the requests also works on any other host or Docker container. It doesn’t always have to be Home Assistant.
just ask copilot/claude/you_favorite for a python proxy (and a container config) 
BTW:
…if you have two batteries/storage systems (connected to Victron and an SE10K-RWS) like I do,
you should seriously consider actively controlling the SolarEdge system to prevent cross-charging
(especially at night) from SolarEdge → Victron.
That costs quite a bit of efficiency, after all.
I handle this outside of Home Assistant in dedicated containers:
SolarEdge (at acout-1) is (almost) fully controlled externally in a 1-second control loop to minimize losses.
Victron handles sudden load changes and power peaks until the SolarEdge control loop has settled.
It also takes care of maintaining sufficient battery reserve when PV production exceeds 10 kW
(the highest peak at se10krws so far was 13 kW due to overprovisioning → max 5kw to battery 8kw to grid/victron ),
so the system is prepared for a sudden transition to island operation and SE dimming via control loop resp. SE-APS.