I received a response from SolarEdge this afternoon. They’ve downgraded my CPU firmware from version 4.23.36 to version 4.19.39.
I have just re-enabled the Modbus, so I’ll see if it works in the coming days.
The Modbus TCP connection between the Solaredge and the Victron has been running smoothly for two days now. The amount of generated energy in the Solaredge app matches what’s displayed in the VRM. It appears that a bug related to Modbus communication crept into one of Solaredge’s latest firmware updates. I don’t yet know if or when they will fix it, but I have asked them.
So, if you’re having problems with the Modbus TCP connection between Solaredge and Victron, ask Solaredge to install an older firmware version for your CPU. They can do this remotely.
3 Likes
And to think, it took a victron forum/staff to find the issue with another vendor’s gear.
Who else would have done that 
5 Likes
I also made a se ticket in the Netherlands and guess what, the solved it without further intervention. See there answer below..
Thank you for your patience.
The inverter firmware has now been successfully downgraded to version 4.22.44, as requested. This should help mitigate the Modbus communication issues and restore a stable connection to your Victron system.
Please monitor the system deployment for the recommended days and let us know if the issue persists or if further improvements are needed. We are here to support you every step of the way.
Happy days;)
1 Like
I’ve received a message from Solaredge.
They will fix this bug in a new firmware update, so they acknowledge there’s a bug in the latest firmware. However, they are unable/unwilling to provide a date for when the fix for this bug will be incorporated into the new firmware.
1 Like
Hello,
SolarEdge tech here - it’s not that we don’t want to provide a specific date or anything - it’s just that one hasn’t been released yet. Regarding feedback, it was provided. I have read the thread as it was mentioned in a case I worked on. As of now, I am downgrading the firmware of systems, but we are aware of the issue and are working on resolving it.
4 Likes
Thanks for the info. Raised a ticket with SolarEdge asking for a downgrade.
I contacted SolarEdge support to ask for a downgrade but they offered the new version 4.24.9 (not officially released yet).
Unfortunately the connection is still unstable, it still disconnects.
It does seem a little more stable though.
if I remember correctly it was not allowing to reconnect before while now after about a minute it reconnects again, even after an hour of running.
I now asked to downgrade to 4.22.44
@Dimitar.S fyi
Hi all
@Dimitar.S , thanks for your response. Appreciated!
@ all, today we released Venus OS version v3.66, which includes a fix related to the communication between the Solar Edge and the Victron GX.
In more detail:
One step in the initialization (retrieving a certain Modbus register from the Solar Edge) was repeated multiple times, increasing by one on each connection loss. After many connection losses, this would take progressively longer and longer to complete reconnection to the Solar Edge inverter.
Until a reboot of the Victron GX device.
That issue was introduced per v3.60.
—-
Note that that doesn’t fix everything yet. As discussed above, the latest Solar Edge firmware typically happens at a connection is lost a few times a day or more for approximately a minute at a time.also now and then wrong data is returned when requesting on register.
As written above, Solar Edge is working hard on fixing that. And meanwhile, if you have a system affected by this, you can request a firmware rollback at Solar Edge Support.
3 Likes
I updated but now it doesn’t connect at all… still on SolarEdge version 4.24.9
I can’t rule out if SolarEdge support did something wrong though.
Correction, after a few minutes (pretty long no?) it connected… for about 30 seconds.
Hopefully SolarEdge comes through and downgrades my inverter.
Hi @WEHA , I already took a look, and it seems like the same issue we found last time, that at times the PV-inverter is just not responding on our modbus queries.
I would like to try something else, with your permission. I want to bypass the new initialisation code that was added in Venus 3.60, that checks for- and sets it up to support limiting. By doing this, limiting will no longer be supported, but it will then return to how it worked in Venus 3.55. Should we try that?
Hello @iburger , I’m afraid the limiting is the biggest reason I need the connection. If it helps you guys to debug something then feel free. But if not then I’ll just wait for a fix.
Thank you for suggesting a solution.
I’ve short-circuited the part of the code where it checks the proprietary limiter of the SolarEdge inverter, so now it treats it as a straight SunSpec inverter. It does however detect SunSpec information model 704, which can be used for limiting. So it is possible that limiting might still work. I don’t know, that is something to test.
The idea is to check if it is now more stable.
I re-enabled the PV-inverter so that it will show up on your system again. I’ll keep an eye on it.
I was suddenly missing a lot of information and saw this on my cerbo:
After reboot it communicated again but I’m still missing a lot of information in Home Assistant.
Also the solaredge is still disconnecting with your change.
Not sure if everything is related but could you revert the change please?
thanks for trying!
Hi,
I reverted the changes.
With the proprietary limiter removed, it does seem to recover a little faster, but you are quite right: It still loses the connection periodically.
Thanks for letting me try. I started wondering if perhaps our writing of registers in the proprietary limiter might have an effect, but that seems to not be the case.
I’m still missing a lot of sensors in home assistant since 17:02
EDIT: Nevermind, i was able to fix it
I’m fairly sure that wasn’t something I did. Glad you were able to fix it.
I received a firmware upgrade from SolarEdge for my SE3000H (with display) from 3.2537 to 3.2543.
However, I had requested a downgrade due to the Modbus TCP communication issue.
The Victron Cerbo GX received an update from 3.65 to 3.66 (with a fix for the communication issue).
So far, however, I haven’t seen any improvement in the communication.
Has anyone maybe had a (successful?) downgrade to version 3.25xx from Solaredge ?
I have to stress that the tiny change made in 3.66 to improve SolarEdge communication doesn’t solve the underlying problem. The lost connection issues brought to light a small problem, which affects the amount of modbus communication that happens upon reconnection (some setup is repeated), and this could potentially make the problem worse over a long period of time. So that was fixed. But it does not solve the whole problem, unfortunately not.
1 Like
Did I get it right, that Venus OS added support for limiting SE?
I’m using this add-on GitHub - h4ckst0ck/dbus-solaredge: Victron Venus integration for SolarEdge Inverters to be able to limit SE and to get the grid data from the SE Smartmeter into Venus OS. This connection works stable for me (SE25K 4.23.514).
Does the new Venus OS supports the grid data from SE Smartmeter as well?