Display different PV inverters in details, just like MPPTs

Been thinking about this one for a while, actually.

On my narrowboat I'm running a couple of PV inverters alongside a Victron MPPT, and the difference in how they display on the GX is a bit frustrating. Hit Details on the MPPT side and you get lovely per-tracker breakdowns — handy when you're trying to work out if one panel string is underperforming. The PV inverters? Just a single combined lump. Not ideal when you're troubleshooting.

Would love to see something like:

• Inverter 1 — 320W
• Inverter 2 — 415W

...rather than just "735W from PV inverters." Even basic per-device figures would help massively with fault-finding.

I get that MPPTs talk directly to Cerbo/CCGX over VE.Direct so Victron have full visibility, whereas third-party PV inverters are coming in via AC coupling and the data path is different. But plenty of them do expose decent data over Modbus or their own protocols — so surely it's possible to pull it through?

Anyone else running multiple AC-coupled inverters and found a workaround? I've seen some folks doing custom Node-RED dashboards to pull it all together, but it'd be so much cleaner if VRM just handled it natively.

Feels like a reasonable feature request if enough of us are asking for it — worth logging on the Victron community portal?

@PanelBuff my tiny house has the same "one of these things is not like the others" situation on the GX dashboard — the MPPT gets its own glamour shot whilst the PV inverters lurk in the corner like uninvited relatives at Christmas. 🎄

Victron could pull proper per-string data through the AC-coupled power readings if they bothered, but right now it's just a sad single wattage figure with no voltage, current, or yield history — basically the energy monitoring equivalent of a Post-it note.

Worth raising on the Victron Community forum directly; they do occasionally promote feature requests when enough people pile on. The more narrowboaters and tiny housers who vote for it, the better the odds someone in Almere actually notices.

@PanelBuff yeah this bugs me too with my garden office setup. The MPPT tile gives you proper per-string granularity but the PV inverter just shows up as a lump sum on the AC input side. Makes fault-finding a pain when you can't tell which array is underperforming.

Victron's argument has always been that PV inverters report via AC metering rather than native DVCC so the data just isn't there at the same resolution — but that feels like a cop-out honestly. Some of the newer Fronius units feeding data over Modbus can get closer to it.

Worth raising on the Victron community forum directly if you haven't — they do actually implement popular feature requests eventually.

@PanelBuff the fundamental issue is that Victron's GX pulls rich data from MPPTs via VE.Direct or VE.Can — actual string voltage, current, daily yield, the lot. Third-party PV inverters typically only expose AC output via a meter reading, so the GX genuinely doesn't know what's happening on the DC side.

That said, some inverters with Modbus-TCP or SunSpec support (Fronius and SMA being the obvious ones) can feed considerably more telemetry through if you configure the integration properly. Worth digging into the Victron CCGX manual section on "AC-coupled PV" — there's more available than the default tile suggests.

For the rest, realistically you're looking at parallel monitoring via something like a Shelly EM or a dedicated Solis logger feeding into a separate dashboard. Not ideal, but until manufacturers expose proper SunSpec data, the GX is working with what it's given.

@DailySolar nails the protocol issue — and it's worth noting that some of the newer Fronius and SMA units do expose more granular data via Modbus TCP, which the GX can technically ingest if you're prepared to dig into the custom driver side. I've done something loosely similar on the shepherd's hut, pulling extra metrics through Node-RED and pushing them into the GX via MQTT. Not elegant, but it surfaces per-string figures alongside the MPPT tiles. The real ask here is Victron building proper normalised display templates for third-party inverters — similar to how they handle the Carlo Gavazzi meters. Whether that ends up in Venus OS is another matter entirely.