Part of the symptom, aiui, is once the SE stops responding, eventually after retries, the GX gives up, so rebooting would give it a chance to restart again.
One of the recent discoveries was that the inverter also responds with data for a different request, which is a pretty poor bug.
Oke, thx Nick,
If i dont want to wait for a proper solution i best use a VM-3P75CT to measure the pv energie or is there a better solution?
In my case I noticed that the communication between Cerbo GX and SolarEdge (SE16K) drop out after SE goes into sleep/standby mode at night. The Cerbo/dbus-fronius keep retrying indefinitely, but when SE comes back from sleep at the morning connection is still spotty until I restart Cerbo (I havenāt tried restarting dbus-fronius only), after reboot it works perfectly whole day without issues until night falls and the issues start all over.
I have TCPdump available if needed, captured during issues.
Are you using DHCP or fixed IP addresses?
Static on both. Itās not a networking issue, since you can see SE acknowledging requests from Cerbo on the TCPdump.
While not privy to the details, I can assure you Victron are doing their bit. There is dialogue going on between engineers, so hopefully something comes from it.
Just received response from solar edge that the information is finally sent to 2nd line support 
Youāve gotten further with Solaredge than I have here. They keep giving me standard answers, and I havenāt been transferred to second-line support yet. Iāll keep asking Solaredge questions.
I got response from solaredge 2 days ago that their senior team did a rollback of the firmware. Donāt know the exact date they did the rollback but I see a stable connection now already for 4 days. So, looks like they indeed create a bug in the latest firmware.
Iāll keep you guys posted when I get more information
Hello
I have an Ekrano GX, 3x Multiplus 2 5000, ESS, and a SolarEdge SE17K Inverter on AcOut1 in my configuration. With OS 3.62, everything works good.
If I try to use OS 3.64, then it looses connection to SE17K after a few seconds, and reconnects again and looses again and so onā¦.
SE17K runs on latest firmware.
Is there a bug fix available? Or other ideas?
I was also able to get SolarEdge to respond and like @blieve they reverted the firmware update and thereās no more connection issues. Definitely a bug in their latest firmware.
So which firmware version do you use now? Mine is 0004.0023.0036
And is dynamic power limiting working with the older SolarEdge firmware?
I was on 4.23.36 like you and they reverted back to 4.22.44. Dynamic power limiting works.
Thanks for all the effort, so the solution is to wait until SE releases a fw update that fixes the bug?
To what firmware version did they do the rollback, so i can also give Solaredge that information
literally posted above..
I have exactly the same problem with the communication between Cerbo GX and SolarEdge inverters.
Since last june I have next system :
The communication is very unstable with sometimes both inverters giving the message āNOT CONNECTEDā (in VRM Remote Console ā Devices), sometimes one of 2 working, sometimes both, but never both working for long timeā¦
I was wondering if it is possible to create a separate direct communication line with the Victron USB-RS485 cable between Cerbo GX and the SolarEdge inverter and extract the SE energy data ??
If the problem canāt be resolved I will install a Victron ET340 meter to measure the power of the 2 SolarEdge inverters.
So I got now the old firmware back on my SE17K, you can not do it by yourself, even if you have an installer account :-(. I opened a ticket on their website and requested a downgrade. I had to explain them why i wanted it, but now its running whithout connection issues.
Firmware is now 4.22.44, same as @nani
RESOLVED - DUE TO UNRELATED ISSUE.
4 days ago was the last time the Cerbo saw the SE inverter, SE inverter is the only device and its not on the IP shown, instead last number is 81. I have checked its set correctly many times today.
SE inverter software is 4.23.27. It has not been updated in months by a person, unless live updates come down over the internet. I can amend this to provide any other useful information. I have spent half the day trying to restore this. Its a nice to have, not currently critical.
The SE inverter is not being detected at all. Any thoughts on this?
UPDATE - RESOLVED
Its always the last thing you check. Long story short, networking issue, jumped to another network that should not be active.
I can confirm it works on SE inverter software 4.23.27
They wanted to just close my ticket now that it is resolvedā¦ I kindly requested to give the feedback to their development team so that they can fix it in a new firmware. No response on this yet, if they will ever fix it or not
