How can Victron VRM/DESS import to/access Enphase Solar production data?

[Frido]

Hi, since about a month I have my system up and running (MPII 48v/5kva/70a, Cerbo CX, Energymeter) with a 15kwh JK battery/BMS. On the AC Out1 I have the AC Coupled Solar (Enphase Gateway metered + 2 CT’s/ 11 IQM8s). Obviously the Victron’s (DESS) does not know about my solarproduction. How can I visualize/import/connect my solar production data into VRM so Victron DESS can use it? I was reading about Modbus but that does not look very easy to implement, is that the best option or are there easier alternatives?

This is what I found on modbus: Enphase Community & AC-coupling Enphase Modbus TCP

[Juanht]

Hi, Please note that in order to enable Modbus-TCP, it is necessary to request
this activation through support_emea@enphaseenergy.com. The following
document specifies the minimum firmware versions required as well as the compatible devices:

https://enphase.com/en-gb/download/ac-coupling-victron-battery-inverters-using-modbus-tcpip-tech-brief

Once Modbus-TCP has been enabled by Enphase, the Cerbo GX will be able to detect the
Enphase system and access only the photovoltaic production data. According to the document,
it is stated that only PV production data can be read; however, it is likely that additional
data may also be available through Modbus-TCP.
For further reference, you may review this discussion:

Help needed - SMA, Solar Edge, Kostal and others

Hey all, Per Venus OS, v3.60 now in beta, more PV Inverters (SMA, SolarEdge, Enphase, Kostal and others) can be controlled by a GX device. Rather than just monitored/read-out. Until v3.60 this feature was only available for Fronius and ABB/Fimer. There are two features related to this active control/limiting: The Zero-Feed in option (See Settings → ESS → Grid Feedin → AC Coupled PV - Feed in excess yes/no. When set to “no”, the GX will actively control the PV Inverters, and reduce their ou…

Additionally, I found a Python script that can be used for testing purposes:
GitHub - radioelf/test_ModbusTcp_Envoy: Codigo para leer los registros ModBus TCP del Envoy de enphase (in Spanish)

[A-P]

You can alternatively buy a VM3 meter or similar to measure the PV production from your Enphase system. That’s what I’ve done (the Enphase modbus function wasn’t available in my geo)

[Frido]

Thank you Juan for all the supporting info but the below option of just connecting an extra VM3 looks a bit easier, I will research further both options!

[Frido]

Thanks A-P, will look into it further.

[A-P]

Sure thing. The setup is pretty straightforward. You’ll just have to set the meter role in VictronConnect to “PV Inverter”.

[Frido]

Quick update: I was reading a lot of bad experiences on the modbus but did want to give it a try (I’m in the Netherlands). I set the IP of my Envoy & Cerbo to static, got on a chat w Enphase and requested the modbus enabling. 1 day later the modbus was enabled. in VRM, I scanned for PV inverters and the Envoy immediately showed up and I was able to see my solar production as part of the PV Inverter straight away. (I do have an Envoy metered and the firmware was up-to-date enough)

[Q.x (Quentin)]

If you didn’t already read it, may I suggest you to read my feedback.

Retour d'expérience sur intégration Enphase par Modbus TCP

J’ouvre ce sujet afin de partager et d’échanger autour de l’intégration de la passerelle Enphase au GX par communication Modbus TCP. Il y a quelques semaines Guilhem (@Guizmon) annonçait avoir rencontré quelques problèmes en réalisant cette intégration (voir Mulitplus Modbus + enphase = production solaire bloqué à 1kW). Finalement, ce n’était qu’une question de paramètres mal réglés suite à de multiples tests. Enphase a produit une note technique à ce sujet, datant de janvier 2025, dans laquel…

Generally speaking, it works, but the power limitation instructions are slow to be applied by the gateway (about 30 seconds). This makes power limitation less efficient.