Multiplus losing settings

Bit of an odd one I've been meaning to post about for a while now.

Running a Multiplus-II 48/5000 in my garden office setup, paired with a Victron SmartSolar MPPT 150/35 and a Fogstar 48V LiFePO4 pack. Everything talks through a Cerbo GX.

A few weeks back I noticed the unit had apparently reset several custom settings — specifically my grid input current limit and some of the ESS charge voltage thresholds. No obvious trigger I could identify. No power cuts, no firmware updates I'd initiated. Just... gone, replaced with defaults.

Logged into VRM and dug through the historical data. Found a brief comms dropout between the Cerbo and the Multiplus around the time I suspect it happened, but I couldn't definitively link the two.

A few things I'm wondering:

• Has anyone seen this behaviour after a Cerbo GX firmware auto-update? I have auto-updates enabled (yes, I know...)
• Is there a known bug where a comms interruption causes the Multiplus to revert ESS parameters?
• Worth raising with Victron's support directly, or is this something the community has already documented?

I've since exported a full settings backup via VictronConnect and will be more disciplined about doing that after any change. Should have been doing it from day one, frankly.

Not a disaster in my case — garden office load is modest — but if this happened in a remote installation running critical kit, you'd not necessarily notice until something went wrong.

Anyone else seen similar? Curious whether this is isolated or a pattern others have hit.

@LochSpirit mine did this on the houseboat until I realised the MK3-USB interface was having a loose connection moment every time someone walked past and vibrated the hull — settings were reverting because VE.Configure thought it was a fresh connection each time. Worth wiggling yours suspiciously.

Had this exact issue in my shepherd's hut build. Turned out to be the VE.Config version not matching the firmware on the unit — settings would appear to save then silently revert after a restart.

Worth checking:

• Firmware fully up to date via VictronConnect
• VE.Config version matches
• Are you saving the .rvsc file locally before sending to device?

Also — if you're on a shared neutral setup make sure your grid code is set correctly, that caused weird behaviour for me before I spotted it.

@BorderWanderer raises a fair point on the MK3 connection too, those connectors are surprisingly fussy for something that costs what they do.

@Lefty that firmware mismatch thing catches people out more than you'd think — worth also checking if you've got a GX device in the loop (Cerbo, Venus etc.) because if VE.Configure and the GX are both set to push config it can create a weird conflict where they're basically fighting each other and the Multiplus ends up reverting.

Had something similar-ish on my shepherd's hut setup, different inverter but same principle. Once I let the Cerbo GX be the single source of truth and stopped pushing settings via VE.Configure separately it sorted itself out.

Also — is your ESS assistant installed? Some settings behave oddly if the assistant config gets corrupted after a firmware update.

Hey @LochSpirit, one thing nobody's mentioned yet — have you checked your grid code settings specifically? On the Multiplus-II these can reset independently of other settings after a firmware update, which can cause some confusing behaviour. Also worth looking at whether you've got Virtual Switch or Assistants configured, as these occasionally need rewriting to non-volatile memory separately from the main config.

If you're using VEConfigure, make sure you're hitting Send Settings and waiting for the full confirmation rather than just closing the window — sounds obvious but it's caught me out before! What firmware version are you currently on? That might help narrow things down.