Ve smart networking with cerbo

Running a Cerbo GX in my tiny house setup and this exact question's been rattling round my head like a loose panel screw.

My kit talks to the Cerbo via VE.Direct cables — Victron MPPT, BMV-712, the works — so the Cerbo's already bossing all the data around. But I've still got VE.Smart Networking switched on between the MPPT and the BMV because... honestly, I'm not entirely sure why anymore. Habit? Fear of turning things off? Classic British indecision?

The way I understand it, without DVCC enabled, the Cerbo's basically just watching — it's not actually controlling anything, just aggregating data for the dashboard. VE.Smart Networking, meanwhile, lets the MPPT pull temperature and voltage data directly from the BMV for more accurate charging. So theoretically they're doing different jobs and can happily coexist?

But here's where I'm genuinely unsure — if the VE.Direct connection already feeds accurate battery voltage to the Cerbo, and the MPPT can see that data too somehow, is VE.Smart Networking actually adding anything meaningful? Or am I just creating a slightly confused system where two things are whispering the same numbers at the MPPT simultaneously?

Has anyone actually tested charge behaviour with and without VE.Smart on a Cerbo setup? Fogstar drift cells if it matters — running 48V, so accuracy genuinely counts.

Suspect the answer is "it doesn't hurt but doesn't help much either" but I'd rather hear it from someone who's actually dug into the Victron firmware rather than just vibing at it like I am. 🔌

@PhilJackson the BMV-712 and MPPT will gossip about SOC all day long over VE.Bus like old women at a bingo hall, but the Cerbo's the one actually making decisions — your MPPT will throttle based on BMV data once you've got DVCC switched on, which is where the magic (and occasional chaos) happens.

@OffGridGeek worth clarifying — BMV-712 and MPPT communicate over VE.Direct, not VE.Bus. Common mix-up but important distinction, especially for @PhilJackson's setup.

The Cerbo acts as the hub here rather than VE.Smart network doing the heavy lifting. Once everything's wired VE.Direct into the Cerbo, the battery sense and temperature data gets shared internally — you don't necessarily need VE.Smart networking on top of that.

Where VE.Smart still earns its keep is if you've got multiple MPPTs doing synchronised charging, or units physically too far from the Cerbo for another cable run. In my shepherd's hut setup I run both — VE.Direct into Cerbo and VE.Smart between the two Renogy-replaced Victron controllers — but honestly if you're single MPPT, single BMV, the Cerbo handles coordination adequately without it.

Check your MPPT firmware is current though. Older versions had quirks with SOC sync over VE.Direct that caused head-

Good catch @LesWood78 — that distinction matters when you're planning cable runs and port counts on the Cerbo.

Worth adding: once both the BMV-712 and MPPT are connected to the Cerbo via VE.Direct, the Cerbo essentially orchestrates the data sharing between them — you don't need VE.Smart networking (Bluetooth mesh) as well unless you have devices that aren't Cerbo-connected.

For my static caravan setup I initially had VE.Smart running and VE.Direct to the Cerbo, which is redundant. Stripped out the Bluetooth networking and let the Cerbo handle synchronisation — cleaner and one less thing to troubleshoot.

Practical question for @PhilJackson — how many VE.Direct ports does your Cerbo have available? If you're running out, a VE.Direct to USB adapter is an option, though some features become read-only depending on the device.

@LesWood78 saving souls one corrected protocol at a time — and yes, the Cerbo's got 3 VE.Direct ports so count them before you start zip-tying cables like it's Christmas.

Good point from @BrookLover on the port count — caught me out on my boat build. I had the BMV-712, two MPPTs, and a SmartShunt all queuing up for VE.Direct ports and suddenly three felt very finite.

Worth knowing: a VE.Direct to USB cable into one of the Cerbo's USB ports is a legitimate workaround if you're running short. Works a treat, been running mine that way for eight months without a hiccup.

Also — if your MPPT is a SmartSolar, it'll be chatting over VE.Smart Bluetooth in parallel to share data with the BMV for voltage compensation. The Cerbo doesn't join that wireless network directly, but it still sees everything through VE.Direct. Two separate conversations happening simultaneously, which trips people up.