MPPT Charge Controllers Appear in Devices but don’t appear on VRM Display

Had something similar driving me mad on my cabin setup last winter — three MPPTs showing in the device list on VRM and visible in the app widget, but completely absent from the overview graphic and the GX Touch display. Felt like they existed in some kind of limbo.

Mine turned out to be a combination of issues:

• The two VE.Can units needed their VRM instance numbers set correctly — they were conflicting with each other, which I think confused the display logic
• The VE.Direct one had somehow lost its "show on overview" toggle in the GX device settings (easy to miss that)

Worth checking a few things if you're in the same boat:

1. Go into Device List → [each MPPT] → Device and check the VRM instance isn't duplicated across your CAN devices
2. On the GX Touch, check Settings → Display & Language → Show overview type settings — there are visibility toggles that don't always default to on
3. Firmware — I was running slightly mismatched versions across my Victron kit and that caused some genuinely weird display behaviour until I updated everything through VictronConnect

The fact that disconnecting the VE.Direct unit changes the behaviour of the other two is interesting — suggests there might be an instance conflict or a comms priority issue rather than a simple config problem.

Anyone else had CAN and VE.Direct MPPTs coexist without issues? Curious whether mixing the two connection types is just inherently flakey or whether there's a clean way to get it all playing nicely on the one display.

@Davo24 had exactly this with my narrowboat setup last year! Drove me absolutely mental 🙄

The trick that sorted mine was checking the VE.Bus system role settings — if your Cerbo (or whatever GX device you're using) hasn't got the MPPTs properly assigned as "system devices" they'll ghost like that on the overview.

Also worth checking:

• Firmware on the Cerbo is fully up to date
• Each MPPT has a unique VE.Direct port assignment
• No duplicate device IDs (happened to me with two identical Victron 100/30s)

Mine reappeared properly after a full Cerbo reboot after the firmware update — not during, which caught me out the first time!

Check the Victron community forum too, there's a specific thread about multi-MPPT visibility bugs on VRM that was super helpful.

Worth checking whether your MPPTs are connected via a VE.Can network rather than VE.Direct — VRM occasionally gets confused about which device "owns" the data and just quietly hides them from the overview like an embarrassed relative at Christmas. 🎄

On my garden office setup I had three Victron MPPTs pulling this exact stunt until I dug into Settings > VRM > Overview and manually added them to the display tiles — turns out VRM doesn't always auto-populate the overview even when it can clearly see the devices. Absolutely maddening logic from an otherwise brilliant platform.

Also worth a firmware check on your Cerbo GX (or whatever your portal device is) — there were a couple of releases around v2.9x that had known quirks with multi-MPPT display rendering that got quietly patched.

@Davo24 nothing quite like paying Victron prices only to have your kit play hide and seek on the dashboard — VRM's overview graphic has the energy of a bouncer selectively letting devices into the club depending on which "data source" role they've been assigned in the installation settings. Worth digging into Settings → System Setup on VRM and checking whether each

@Davo24 funny you should mention this — had the exact same pantomime on my boat last spring. Three MPPTs dutifully showing up in the device list like they'd turned up to the party, but absolutely nowhere to be seen on the overview graphic.

Turned out my GX device firmware was slightly behind, and the overview topology essentially didn't know how to "place" multiple controllers in the display hierarchy. One firmware update via the Cerbo GX remote console and they all popped into the diagram like they'd never been hiding.

Worth checking Settings > Firmware > Check for updates before diving too deep into VE.Can vs VE.Direct rabbit holes — sometimes the boring answer is the right one.

Also double-check your installation type setting on the GX; if it's set to something generic, VRM can get rather confused about what goes where on that overview.