Victron Multiplus keeps throwing a low battery warning but voltages look fine?

Had almost exactly this a few months back with my Multiplus II. Voltages looked perfectly healthy on the display but the warnings kept firing — turned out the issue was with the battery temperature sensor giving false readings, which was causing the BMS to report a lower state of charge than reality.

Few things worth checking:

• VE.Bus Smart Dongle — are you monitoring via that or just the front panel? The dongle gives you a much fuller picture of what's actually happening
• Check your absorption/float settings in VEConfigure — if they're set too conservatively the Multiplus can get confused about where the battery actually is in its charge cycle
• What batteries are you running? If it's lithium (Fogstar Drift or similar), make sure the DVCC settings are enabled and the BMS is actually talking to the Multiplus properly

The voltage reading alone can be misleading — a LiFePO4 cell sits at a fairly flat voltage curve for most of its capacity, so the Multiplus might be seeing a brief sag under load and interpreting that as a critical low even if resting voltage looks fine.

Worth pulling the VRM logs if you've got that set up — the granular data usually shows exactly when the warnings trigger and whether there's a load spike causing momentary sag.

What's your battery bank capacity and what loads are you running when it kicks off?

@MoorLee that's a really useful find — temperature compensation is massively underappreciated.

Worth adding: if you're running Victron Smart Lithium or even Fogstar Drift cells, check whether your BMS is actually communicating battery temperature back to the Multiplus via VE.Bus or the temp sensor cable. If it's not, the Multiplus falls back to assuming ambient — which in a motorhome over winter can be wildly off from actual cell temp.

In my setup I had the temp sensor dangling loose behind a panel rather than actually clamped to the battery. Looked connected, wasn't doing anything useful. Five-minute fix that stopped months of phantom warnings.

Also double-check your low battery voltage and dynamic cutoff settings in VEConfigure — the defaults aren't always appropriate for LiFePO4 chemistry and can trigger well before the cells are genuinely stressed.

@MoorLee interesting — I've had similar head-scratching moments with my shepherd's hut setup. One thing worth checking that hasn't been mentioned: are your battery cables adequately sized? I had what looked like healthy resting voltages on my Victron BMV-712 but under any real load the voltage was dropping enough to trip the warning. Turned out my cable run was slightly undersized for the distance. Upgraded to proper 70mm² and the phantom warnings stopped.

Also worth double-checking your battery peukert exponent settings in VictronConnect — if it's misconfigured for your specific cells (especially if you're running Fogstar Drift LiFePO4 like me) it can make the BMV report pessimistically and confuse things further.

@MoorLee this rang a bell immediately — went through almost identical confusion on my boat last winter.

What nobody mentioned yet: check your cable run lengths and termination quality before chasing software settings. I had perfectly healthy resting voltages but the Multiplus was seeing a different voltage under load because of resistance built up in a dodgy crimp. Essentially the inverter was reacting to a real problem, just not the one I expected.

Grabbed a clamp meter, ran a load test, and watched the voltage at the battery terminals versus what VRM was reporting — the discrepancy told the whole story.

On a boat especially, salt air does horrible things to terminals over time. Annual inspection and retorquing has saved me more grief than any firmware update ever has.

Seen this exact gremlin in my motorhome — Victron's low battery threshold is calculated against a loaded voltage, so if your BMS is reporting resting voltage but the Multiplus is measuring under load, you'll get phantom warnings all day long.

Check your VEConfigure settings for the DC input low shut-down and restart thresholds — mine were set absurdly high from factory for AGM and I'm running Fogstar lithium, so it was basically panicking at perfectly healthy voltages.

Also worth running VictronConnect and pulling the actual event log rather than just glancing at the live display — the timestamps often reveal it's only triggering under heavy load spikes, which points squarely at voltage sag rather than genuine low state of charge.

@MoorLee temperature compensation angle is solid but rule out the threshold misconfiguration first, it's a five-minute fix.