Victron Energy (pv)
The Victron Energy (pv) template reads system-level PV production data from a Victron GX device over Modbus TCP. It targets the com.victronenergy.system service at Unit ID 100, covering AC-coupled PV power on the AC output across phases L1, L2, and L3 (registers 808 to 810), AC-coupled PV power on the AC input across L1, L2, and L3 (registers 811 to 813), and total DC-coupled PV power from all connected MPPT solar chargers (register 850). Use this template to consolidate all Victron PV generation sources into a single portal view without polling individual device unit IDs.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 7, read only
- Brand
- Victron
- Last updated
Registers (7)
7 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power_a | W | Read | |||
| power_b | W | Read | |||
| power_c | W | Read | |||
| power_d | W | Read | |||
| power_e | W | Read | |||
| power_f | W | Read | |||
| power_g | W | Read |
Loading registers…
Send your device list
If a device is not in the library yet, we build the template for free as soon as we have the register data.
Use cases
- Monitor total DC-coupled MPPT solar output to verify generation against expected panel capacity.
- Compare AC-coupled PV power on AC output versus AC input to detect inverter coupling misconfigurations.
- Track per-phase AC-coupled PV production to spot imbalanced three-phase solar installations.
- Alert on a drop in DC-coupled PV power during daylight hours to catch MPPT faults early.
- Report combined AC and DC PV generation totals across multiple sites from the ModbusCloud portal.
Installation
Enable Modbus TCP on the Victron GX device by navigating to Settings, then Services, and switching the Modbus-TCP service on.
Connect the ModbusCloud Gateway to the same LAN as the GX device, ensuring the GX device has a static or reserved IP address.
In the ModbusCloud portal, add the GX device as a new Modbus TCP target, import the Victron Energy (pv) template, and set the Unit ID to 100.
Spot-check register 850 in the live data view during daylight to confirm DC-coupled PV power reads a non-zero value matching the VRM dashboard.
Things to watch for
All PV registers return zero even during daylight. Why?
Registers 808 to 813 only populate when AC-coupled PV inverters are present and active in the system. Register 850 only populates when MPPT solar chargers are connected and producing. If neither device type is installed, these fields will read zero. Confirm the connected device types in the GX remote console under Device List.
The GX device is reachable but the gateway returns no response.
Modbus TCP is disabled by default on Victron GX devices. Verify it is enabled under Settings, Services, Modbus-TCP. Also confirm the gateway is polling port 502 and that no firewall rule on the local network is blocking that port between the gateway and the GX device.
I see data on some phases but not others. What is wrong?
AC-coupled PV registers are per connection point and per phase. If the PV inverter is single-phase on L1, registers for L2 and L3 (power_b, power_c, power_e, power_f) will return zero. This is normal behaviour. Only phases with active AC-coupled inverters will show non-zero values.
Function code 4 is used here but the Victron manual says FC3. Is that correct?
Yes. Victron GX devices accept both function code 3 and function code 4 for reading registers. There is no functional difference between them in the GX Modbus TCP implementation. Either code returns identical results for these system registers.
Want to see how it works?
