question

Update: looks like SolarEdge's meter riding is not implemented in Victron's dbus-fronius. At the same time SolarEdge confirmed there is no possibility to have second client through same or different interface (LAN,WiFi).

What about installation of modbus-proxy on cerboGX?

I was able to install modbus-proxy on Ubuntu and proxy CerboGX modbus successfully.

I have installed modbus-proxy on my ubuntu node on proxmox and now Victron CerboGX and HomeAssistant are connected to SolarEdge's ModbusTCP through configured modpus-proxy. It works.. On CerboGX you cannot specify sunspec port. It has hardcode as 502. You can only "proxy" to one SolarEdge.

Hi, i am interested this modbus proxy setup as I have SolarEdge and also Home Assistant that reads SolarEdge over modbus. As for setup, do you have the SolarEdge on the Victron AC out? What does the SolarEdge energy meter measure in your case? Grid point export/import meter or consumption meter? As for the Victron side, do you use physical meters ET112 to measure the SolarEdge production? Or only Modbus? I wonder one can eliminate buying ET112 this case when using only Modbus. Can you please share info how to install and configure modbus proxy on Ubuntu?

Intresting discussion regarding SolarEdge and Modbus, i have also being working with this at home, not with Victron, i have manage ro read out from head unit lots of values, but noting related to SolarEdge Batteries, like charging/discharging, percentage (%) etc...

anyone can shed some light on that?

I had some problems too but were able to solve this by using Home Assistant with a running Modbus Proxy on it. I cleared all the modbus connections in VenusOS and pointed them to the new Modbus proxy. The proxy is then communicating with 2 SolarEdge inverters, one is connected to the SolarEdge Smart Meter. I can now read all registers and also write to registers. I have connected the beta DynamicESS through Nodered to the SolarEdge inverters to control export limits. I made a Youtube video about itand you can find the nodered flows on my website: www.haroldhalewijn.nl. Unfortunately it is done and written in Dutch but perhaps it can help you.

Hi,

I can share a code that I developped to overcome this issue.

My config is Multiplus II GX with 3 x Pylontec US2000C and 3KW Solaredge PV on the AC input of the Multiplus. I had the Solaredge PV installed with a Solaredge grid meter before. When installing the Victron+BESS, I did not want to duplicate the grid meter and I have done some adjustment to the python code that Victron provides to establish Modbus TCP communication to the Carlo Gavazzi meters and other meters. Now the Multiplus reads permanently both the solaredge inverter and grid meter data and write them into the dbus so the values are available on the VRM and via modbus tcp on the Multiplus. The meter value provided by the solaredge meter is used directly by the ESS loop. I still need to do some fine tuning because the cumulated grid import and export energies on the VRM are wrong but this is due to the setup of the paths where I store values in dbus. However the power values are correct and ESS works fine. Sometimes, roughly once a day, the Solaredge reset the modbus TCP but I managed to have the Multiplus reestablishing the communication automatically so it does not go to passthru mode. This has been working for 4 months without any issue. If anyone is interested, I am happy to provide the code of the modules and some instructions how to use them. Just let me know.

Kind regards

JM

Hello everyone,

I wonder why power setpoint write variable is NOT implemented like it’s the case with Fronius. One ET340 and it works flawless with Fronius.

In Solaredge setup you will run into problems when:

- you want zero export limiting

- gpio can either have function of APS or external production limit - that being said you can not assign 2 functions to two different digital inputs of Solaredge - therefore when limiting export via gpio you have to turn on frequency shifting in normal grid tied mode and cross your fingers you have less then 50,2 Hz in your grid.

Lots of problem would be solved if Cerbo could natively throttle Solaredge over modbus - it can not at the moment. Someone managed to overcome this? Because if Cerbo uses the only one client slot for Modbus we cant even use BMS to solve this. Very troublesome.

Thank you.

@mvader (Victron Energy) @Guy Stewart (Victron Community Manager) Guys, sorry to drag you like this into this topic, but it seems, that Power Throttling is not working when in on-grid mode via Modbus. I reported this on Github:

https://github.com/victronenergy/dbus-fronius/issues/6

On github, there is a mention, that Solaredge does not publish datapoints for power throttling on Modbus, but Solaredge definitely has this option quite intelligently integrated since 2018- please see the file: ramp-up_down_and_active_power_control_02-01-19.pdf

It is causing lots of issues for us, because we either don't have function with which a distributor can cut production or we have to set frequency shifting in on-grid mode - because Solaredge GPIO can not handle two functions (even though it has 4 digital inputs), which I have described also here:

https://community.victronenergy.com/questions/181198/ac-and-dc-coupled-grid-tied-system-pv-inverter-thr.html?childToView=242343#comment-242343

Could someone explain, why Power Throttling over Modbus is not integrated yet (like it is for Fronius)? If it is - then it did not work for me. If not, please please please add it on feature list - might be a simple fix and for us it saves lots of pain. When we deploy Victron BESS and we have large scale installation, then we need to use Solaredge, because it simplifies everything and by far is the safest solution regarding DC handling.

Thank you.

Hi guys,

i got a Modbus proxy running for sharing the connection to SolarEdge modbusTCP. Home assistant is still reading my SolarEdge but as soon as i add the ip in the PV inverter menu all readings stop. Home Assistant cant read the data anymore and so cant CASmodbusScanner.

Any clues about this? Running 3.14 on my RPI with VenusOS