Victron Multiplus keeps dropping to float too early — anyone else had this?

Had exactly this with our shepherd's hut setup last winter. The Multiplus was calling float after maybe 45 minutes of absorption, nowhere near the 2 hours I'd programmed in VE.Configure.

Turned out the culprit was the repeated absorption setting interacting oddly with my Fogstar 200Ah lithium cells. The BMS was occasionally sending a brief "battery full" signal during absorption, and the Multiplus was interpreting that as permission to drop to float early. Took me an embarrassing amount of time to spot it.

A few things worth checking:

• Tail current threshold — if it's set too high relative to your battery capacity, it'll trigger float prematurely. I dropped mine from 4% to 1% and the behaviour completely changed.
• VE.Bus BMS integration — are you running any BMS comms into the Multiplus? That can override your timed settings entirely.
• Battery temperature — colder cells accept charge more slowly, so the tail current drops off sooner than expected.

I'd also strongly recommend grabbing the VRM portal logs if you haven't already. Being able to see exactly where the voltage and current were at the point of transition was what finally let me diagnose mine properly rather than just guessing.

Worth mentioning — Victron's own forum has a couple of threads on this specific behaviour going back to certain firmware versions on the Multiplus-II. Might be worth cross-referencing your firmware against those reports.

What battery chemistry are you running, and are you on a fixed time absorption or adaptive? That'd help narrow it down considerably.

Had this exact issue on the boat last season. Worth checking your repeated absorption setting — if the battery voltage had barely dipped since the last charge cycle, Victron's algorithm decides it doesn't need the full absorption time and cuts it short. Annoying when you know the bank isn't actually full.

Also double-check your absorption voltage is set correctly for your chemistry. I dropped mine 0.1V by accident after a firmware update and it threw everything off.

@PartnerBuild curious what batteries you're running? With my Fogstar lithium I ended up using a fixed absorption time rather than the adaptive setting — much more predictable behaviour once I stopped letting it "think" for itself. 😄

Ah, the classic "I set it to 2 hours but Victron had other plans" situation. 😄

Worth double-checking your tail current setting in VE.Configure — if it's set too high, the Multiplus thinks the battery is full when it absolutely isn't and legs it to float early. Caught me out with my Fog

Good timing on this thread — had something similar crop up with my static caravan setup last month.

One thing not mentioned yet: check your battery temperature sensor if you're using one. A faulty or poorly positioned BTS can cause the Multiplus to think the battery is warmer than it is, which triggers early float as a protection measure.

Also worth looking at in VE.Configure:

• Absorption time: is it set to adaptive or fixed? Adaptive will shorten absorption based on bulk duration, which catches people out
• BatterySafe mode — can interfere with expected charge curves

What battery chemistry are you running @PartnerBuild? With LiFePO4 the tail current threshold matters enormously, as @CotswoldNomad seems to be hinting at. If it's AGM, the voltage thresholds in VE.Configure may just need tightening up.

Great thread — had this bite me on my garden office setup last year.

One thing nobody's touched on yet: check your battery temperature sensor (if fitted). A faulty or poorly-positioned BMS temp reading can convince the Multiplus that the battery is warmer than it is, causing it to aggressively curtail absorption to protect the cells. My Fogstar Drift 200Ah was reading 4–5°C above ambient due to the sensor being too close to a BMS MOSFET — Victron dutifully bailed out of absorption early every time.

Also worth connecting to VRM or VictronConnect during a charge cycle and watching the actual tail current live. If it's genuinely hitting your configured tail current threshold (default is often 4% of bank capacity), the Multiplus is behaving correctly — the programmed time is a maximum, not a target.

@PartnerBuild what's your configured tail current set to in VE.Configure?

Had this exact thing with my garden office setup. Worth checking your absorption voltage threshold in VE.Configure — if it's set too low, the Multiplus thinks the battery is "full" earlier than it actually is.

Also, are you on lithium or lead-acid? With lithium (I run Fogstar Drift cells) the tail current setting matters massively. If your BMS is already nudging the charge current down before true absorption ends, the Multiplus can interpret that as the battery being done and bail out early.

Try logging a proper charge cycle via VRM — even just on the free tier — and look at the current curve during absorption. Usually tells you immediately whether it's a settings issue or the BMS interfering.