Victron PV-Inverter
The Victron PV-Inverter template reads live and cumulative data from any grid-tie PV inverter registered under the com.victronenergy.pvinverter service on a Victron GX device. Using Modbus TCP, the ModbusCloud Gateway polls per-phase voltage, current, and active power across all three phases, along with cumulative energy production per phase and the inverter connection position. This gives installers and asset managers a complete picture of solar generation in one-phase and three-phase systems without additional hardware.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 14, read only
- Brand
- Victron
- Last updated
Registers (14)
14 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| position | Read | ||||
| voltage_l1 | V | Read | |||
| current_l1 | A | Read | |||
| active_power_l1 | W | Read | |||
| voltage_l2 | V | Read | |||
| current_l2 | A | Read | |||
| active_power_l2 | W | Read | |||
| voltage_l3 | V | Read | |||
| current_l3 | A | Read | |||
| active_power_l3 | W | Read | |||
| serial_number | Read | ||||
| active_production_energy_l1 | kWh | Read | |||
| active_production_energy_l2 | kWh | Read | |||
| active_production_energy_l3 | kWh | 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 per-phase active power on L1, L2, and L3 to detect asymmetric generation across phases.
- Track cumulative energy production per phase over time to verify yield against design estimates.
- Alert on unexpected drops in voltage or current on any phase to catch grid or inverter faults early.
- Verify the position register value to confirm the PV inverter is connected to the correct AC bus point.
- Compare daily energy totals across phases to identify shading or stringing issues on specific strings.
Installation
Enable Modbus TCP on the Victron GX device by navigating to Settings, then Services, and switching on the Modbus-TCP service.
Connect the ModbusCloud Gateway to the same LAN as the GX device, ensuring TCP port 502 is reachable between them.
In the ModbusCloud portal, add the Gateway, import the Victron PV-Inverter template, and set the Unit ID to match the PV inverter instance shown under Settings, Services, Modbus/TCP, Available services on the GX device.
Spot-check the active_power_l1 register in the portal live view while the PV system is producing to confirm values are updating correctly.
Things to watch for
Voltage and current values look ten times too high. Why?
The raw Modbus register values for voltage and current on all three phases use a scale factor of 10, meaning the raw integer must be divided by 10 to obtain the actual value in volts or amps. Confirm your portal or integration is applying this scaling correctly before displaying or alerting on these registers.
The gateway connects but all registers return zero or no data.
The most common cause is an incorrect Unit ID. Each PV inverter instance on the GX device is assigned a unique Unit ID. Navigate to Settings, Services, Modbus/TCP, Available services on the GX device to find the correct Unit ID for your PV inverter, then update the portal accordingly.
Energy counters on registers 1046, 1048, and 1050 show unexpected large values.
These uint32 cumulative energy registers use a scale factor of 100, so the raw value must be divided by 100 to get kWh. A raw value of 100000 equals 1000.00 kWh. Ensure your dashboard formula applies this divisor before comparing against billing or yield data.
Modbus TCP was working, then suddenly stopped returning data after a firmware update.
Victron GX firmware updates can reset the Modbus TCP service to disabled. After any firmware update, re-verify that Modbus TCP is still enabled under Settings, Services, and confirm the Unit ID assignments have not changed, as device instance numbers can shift if devices are reconnected.
Want to see how it works?
