Connecting LifePo4 to Cerbo GX via Bluetooth

Been down this exact rabbit hole recently with my cabin setup, so thought it worth sharing what I've found.

The short answer is: it depends entirely on which LiFePO4 batteries you have.

The Cerbo GX has native Bluetooth support, but it's not a free-for-all — Victron maintains a compatibility list, and only batteries running supported BMS firmware will actually appear in the device list. If you're running Victron Smart Lithium batteries, you're golden. Third-party packs (Fogstar Drift, SOK, Enjoybot, etc.) are a different story.

For most non-Victron LiFePO4 packs, the recommended path is a VE.Bus BMS or a compatible third-party BMS with a CANbus or RS485 interface rather than Bluetooth. Bluetooth comms between the Cerbo and battery BMS is genuinely limited outside the Victron ecosystem.

What does work brilliantly is using a BMV-712 (which you already have) as your primary battery monitor feeding into the Cerbo via VE.Direct. You'll get SoC, voltage, current, and historical data all in VRM — which honestly covers 90% of what most people need day-to-day.

If you want proper per-cell monitoring from a third-party pack, I'd look at whether your BMS supports UART to USB and whether you can pull that into a Raspberry Pi running something like dbus-serialbattery alongside Venus OS. More faff, but it works.

What make/model are the batteries? That's really the crux of it — the answer shifts quite a bit depending on whether you've got a proprietary BMS or something more open.

Worth cross-referencing the

Good summary @VitoCamper.

Worth adding — if you're running Fogstar Drift cells, they communicate via their own BMS app but won't talk directly to the Cerbo. You'll need either:

• A Victron SmartShunt inline to give the Cerbo something useful to work with
• Or a supported battery with native DVCC integration (Pylontech being the obvious one)

I went the SmartShunt route on my static caravan setup. Not perfect — the Cerbo doesn't see cell-level data — but state of charge, voltage and current all feed through cleanly into VRM, which is what matters day-to-day.

The VE.Can route is cleaner if your BMS supports it, but that's usually proprietary to more expensive battery brands.

Bottom line: budget an extra £60-80 for the SmartShunt if you're not on a natively supported battery. Saves a lot of head-scratching later.

@RetiredPlumber makes a good point about the Fogstar Drift — learned that the hard way myself when I swapped out my old AGMs.

What caught me off guard was that even when the BMS does talk to the Cerbo GX natively, you're still not guaranteed accurate SOC readings without proper configuration. My Victron setup was showing wildly optimistic percentages for weeks until I sat down with VE.Configure and sorted the battery parameters properly.

If your BMS is Bluetooth-only with no Victron integration, the Victron SmartShunt is genuinely the cleanest workaround — it sits between the battery and the Cerbo and gives you proper SOC data regardless of what BMS you're running.

Not a perfect solution, adds cost, but it's solid and reliable which matters when you're depending on the system for actual off-grid living rather than just weekend trips.

Really useful thread, this. Been wrestling with exactly this for my cabin setup and EV charging monitoring integration.

@SprinterLife curious what you ended up swapping to? I'm currently looking at whether a Victron Smart Lithium bank would just make life easier given native GX Device communication over VE.Direct — seems like the path of least resistance if you want everything talking properly in VRM.

The thing that keeps tripping me up is whether third-party BMS units (I've been looking at some Renogy options) can realistically pass proper SOC data through to the Cerbo, or whether you end up with estimated/guessed values that aren't trustworthy for load management decisions.

Anyone actually running non-Victron cells with solid, reliable SOC reporting on their Cerbo rather than just approximate values?

Great thread @VitoCamper. One thing worth flagging that hasn't been mentioned yet — even when you do get proper comms established between your LiFePO4 and the Cerbo GX, it's worth double-checking that the DVCC settings are configured correctly afterwards. I've seen setups where the battery data was coming through fine on the dashboard but the charge current limits from the BMS weren't actually being respected by the inverter/charger because DVCC was either disabled or misconfigured. Spent a frustrating afternoon troubleshooting that on my own system before I spotted it. @OffGridFreak might want to bear that in mind especially if you're pulling EV charging into the mix — the current demands can be significant and you really want the BMS talking properly to everything upstream.

Really timely thread for me — I've got a couple of Fogstar Drift 100Ah batteries in my shepherd's hut build and was planning to rely on Bluetooth monitoring. Sounds like I need to rethink that?

Is anyone running a JK BMS or similar as a workaround on batteries that lack native Victron comms? I've seen mention of using a RS485 to VE.Can adaptor but I'm genuinely not sure if that's overkill for a smallish 200Ah system.

Also wondering whether the VRM portal gives you anything useful even without direct battery comms — like can you at least infer SOC from the MPPT and inverter data, even if it's not perfect? That's how I've been managing on my boat and it's... fine-ish, but I'd love proper BMS data feeding through to the Cerbo.