My SE3000 was downgraded last year October on my request to 4.21.23 (see above) and was working fine since then with Victron Modbus TCP integration. In March 26 the SE3000 HW failed and I got recently a new SE3000 with updated 4.24.22 FW. Suprisingly this works now stable with my GX 3.72 already for 3 days…
I will follow-up this and will inform you on any news
I use Modbus ID 126 instead of 1, does this makes the difference?
Hello,
how is the connection stability? I’m still having trouble with it.
Hello
i have the same problem with the SolarEdge after upgrade to the new firmware. The only way to restart communication is to reboot the cerbo. i requested to put the older version firmware back in the SolarEdge invert. Maybe an automatisch reconnect is possible in the cerbo. It drop Every 2-3 days.
For whatever reason my system is stable now for a week after SE HW exchange with the SW loads written above and no Cerbo resets from my side:
In the SE inverter in can find error logs from 2022, so this seems to be no new HW revision.
Here the current extended VRM Portal presentation of my SE system (which was faulty / interrupted back in 2025 with recent SW loads at that time)
Hello, I have the same problem with a 5k homewave solaredge. The invertor goes into standby overnite. Sometimes it reports correctly in the morning and sometimes it requires a reset. Currently on 4.24.22.
Any pointers would be great. Many thanks.
Hello
I need some help or advise. I have read the complete thread and could not find a solution yet other than going back to the previous CerboGX firmware.
My setup is like this:
Two SE inverters running fine for more that 2 years
Currently running CerboGX firmware version 3.40. No issues with modbus communications.
No homeassistant. Only CerboGX
I have updated the CerboGX firmware to latest stable version 3.72 (because of the new GUI) and immediately problems started with communications with the SE2200 The communication with the SE4k seems to be fine.
I could see that Dynamic Power limit was jumping in and out in the SE2200 configuration screen, like mentioned by others in this thread. This option in the SE4K configuration screen stayed constantly there. To to me SE4K seems to be fine.
Also I noticed some red error lights on the SE2200 when communication was lost. Could not see it myself but someone on site mentioned it.
I went back to CerboGX version 3.40 and all seems to be stable and working again.
I have red that a firmware downgrade of the SE inverters could “solve” the issue. Could someone suggest to what version I should downgrade the SE2200?
Thanks for your help
It is a SE firmware issue with sunspec. The solution is to downgrade the inverters to a specific version mentioned numerous times in this topic.
Thanks Nick Yes I have red the whole thread.
I know the real issue is a bug in SE firmware. But I don’t know what version works for the SE2200
The official release is 3.2537 (on the SE website). In this thread people are talking about versions 3.2543 and even 3.2807
As far as I can see no 3.2XXX version is solving the issue. @Honza even @KajC has a working system with version 3.2537 with Venus OS 3.66
My system is working good with Venus OS version 3.40.
So to me it’s seems a combination of VenusOS version and SE firmware version.
It would be nice if victron could create a configuration option to disable the Dynamic Power limit feature until SE has fixed there firmware so we can upgrade to the latest CerboGX firmware
Fair enough. Most of the complaints are on devices using the 4.x code stream.
Is there any possibility to help us here, users with SE hardware with firmware 3.2XXX?
It seems that VenusOS > 3.40 doesn’t work with SE inverters with firmware 3.2XXX
It would be nice if we could use the latest VenusOS versions with our SE hardware until SE fixes there firmware.
Thanks in advance
FYI, I have an SE1000M with firmware version 4.15.012 which is interfacing well with all latest Venus OS releases. My SE5K and SE9K needed down grades. All is running fine now.
Realise that you are asking Victron to make changes to cope with SolarEdge bugs!! Bugs SolarEdge does not want to fix, apparently. The first topic here is from 18 July last year and back then the issue was already well known for them. Several firmware releases have been issued since then, and the issue has not been addressed. The fact that you can easily communicate with Victron staff and SolarEdge support is behind a firewall, does not imply that bugs of others are compensated for (automatically).
Companies like for example SolarEdge and Sigenergy are intentionally closed systems and these companies like you to stay within their ecosystem. The SolarEdge sunspec implementation is not as open as may be expected. There is a limit on the number of requests you can issue in a time slot, after which there is no response any more. After the timeout it works again.
Although my personal SolarEdge systems are now working well, for a future system or replacement, I will consider other options. To be future-proof, you need open systems, like Victron.
Thanks @Bertus
I understand your point completely.
But from my point of view “the issue” is a combination of VenusOS version and SE firmware version.
VenusOS 3.40 is working fine with my setup of two SE inverters (SE 2200 fwv 3.2537 and SE4k fwv 4.22.39)
VenusOS 3.72 isn’t.
Somewhere between version VenusOS version 3.40 and 3.72 Victron introduced a new sunspec feature “Dynamic Power limit”
It seems that several SE devices (at least one of mine = SE2200 ) cannot cope with this new feature (due to a bug in SE’s firmware).
I want to ask SE to upgrade or downgrade my firmware but I have no clue to what version. I don’t know if my SE2200 support the 4.XX.XXX firmware.
I have red the complete forum/thread and I could not find a working SE firmware/VenusOS version combination for my SE2200.
So desperate I am asking Victron if there is a possibility to disable this “Dynamic Power limit” feature/code in VenusOS so I can safely upgrade to the latest VenusOS version until SE fixed there firmware.
i have downgrade my solar edge firmware to 4.21.23 and al is working at the moment. No communication failure any more.
Hi there,
my new SE3000 HW with 4.24.22 Firmware and Cerbo GC 3.72 was surprisingly working stable for 18 days - but failed this morning (see screenshot of my VRM Portal with no data of today):
So I will request for SE SW downgrade as this worked fine for several months with my previous inverter before HW failure.
Yes Martijn, I understand that you focus on the differences. Thing is, this one is obvious, the “Dynamic Power limit”. But there will be many differences to look at, for example:
- I understood that other updates have been made to the Sunspec implementation by Victron. This was also related to the Solaredge issues.
- New general features have been implemented in the OS. This will take somehow performance of the system. If your issues are is timing related, the not functioning today can be related to this.
- I assume that over time changes have been made to internal data structures and module interactions. This can also create a delta affecting the performance of your system.
- And there will be more.
So, disabling the “Dynamic Power limit” feature in SW can be the solution but is questionable after so many updates to the OS.
Some suggestions:
1 Submit a support request in the SolarEdge portal and describe your problem and ask them to advise of which firmware version to use. You will need probably to wait a couple of weeks for an answer.
2 Select the old user interface on the Cerbo. The old user interface uses less performance. If it is timing related, this can maybe help. A longshot, but you never know.
3 Disable the “Dynamic Power limit” yourself. Reboot your SE2200 and wait till it is fully stable, initializing and converting again. Then reboot the Cerbo and give it some time to stabilize and communicate. This is the moment that all interactions between your SolarEdge and Cerbo are optimal. Venus OS adapts to the devices it has found and what featured are offered. If Venus OS sees that the “Dynamic Power limit” is supported, if will show in the menu: Setting/Integrations/PV Inverters/Inverters/[the name of your inverter]/Dynamic Power Limiting/ => selected now enabled or disabled.
Not entirely accurate.
If the cerbo is overloaded, the advanced widget - dbus round trip time - will show high latency. If it does not, then cerbo resources are not an issue.
On the new UI you can also disable animations which will reduce cpu load.
Thanks Bertus for your help.
I maintain two Victron installations and have multiple CerboGX devices.
1 test Raspberry-Pi (beta firmware) and Two official CerboGX devices.
Two systems (CerboGX and RP) are up-to-date to the latest VenusOS firmware and one CerboGX (with SE Inverters) is “stuck” to 3.40
I checked several things and I don’t believe it’s a performance/timing issue.
Thanks for you suggestion to disable the “Dynamic Power limit” for the SE2200. But that was the first thing I did. But still SE2200 disappears and comes back in the GUI. Communication errors on the SE2200 side.
It would be nice if someone has a working/stable 3.XXX (not 4.XXX) firmware version so I can ask to SE to downgrade my SE2200 to this version.
Or maybe Victron has a suggestion or workaround?
(I have some skills to modify python code)
It seems that other inverter brands are having similar issues…
I use VenusOS v3.72 with an SE3000 from 2014 which is running firmware version 3.2537 and have no issues with the communication other than that the SolarEdge disconnects once per day in the evening and the Cerbo then reconnects after 5 seconds. But the Cerbo connects to the SolarEdge via a multithreaded modbus proxy, running on the Cerbo. That could make a difference. I use the proxy to be able to control the power limit of the SolarEdge from a node-red flow. I have the “Dynamic power limiting” feature of VenusOS disabled.
Do you have some link or info how to set-up/configure such modbus proxy?
