Probleme nach Firmware Update v3.79 - No BMS oder Alarm Low Battery

So this has sent me down a rabbit hole this evening — been reading about the v3.79 firmware issues on the Multiplus II GX and honestly it's giving me cold sweats thinking about our setup on the motorhome.

We're running a Victron Multiplus-II 12/3000 paired with a Fogstar Drift 200Ah lithium battery, and the BMS communication side of things is something I'm genuinely precious about. The thought of a firmware update silently breaking that handshake — and then getting a phantom "Low Battery" alarm or a BMS disconnect — is the kind of thing that'd ruin a wild camp weekend pretty spectacularly.

From what I've been piecing together, the issue seems to be around how the GX device negotiates with the BMS post-update. Some folks are finding:

• The inverter drops into a protection state it won't come out of
• DVCC settings appear to reset or behave unexpectedly
• VE.Bus alarms that weren't there before

My question for anyone who's already on v3.79 — did you have to manually re-enter your DVCC settings after updating? And did those of you running CANbus BMS (rather than VE.Bus BMS) see any difference in behaviour?

I've deliberately held off updating after a previous firmware version caused a minor headache with our absorption settings. There's something to be said for the old "if it ain't broke" approach, especially when you're relying on this kit miles from anywhere.

Anyone else sitting tight on an older firmware version, or have you taken the plunge and come out the other side unscathed?

@MarineVicky the v3.79 Multiplus II GX issues are well documented — Victron quietly pulled it and v3.80 is the one to grab from the VRM portal sharpish before your BMS throws a tantrum at 2am in a layby somewhere!

Key things to check:

• DVCC settings — v3.79 borked some BMS communication handshakes
• ESS assistant may need reloading after the update
• Make sure your VE.Bus firmware matches — mismatches cause the phantom low battery alarms

Had something similar on my van conversion when I jumped updates too eagerly on my Victron kit — the BMS was basically ghosted by the system and it was showing alarms for batteries that were at 90% 🙄

Flash to v3.80 via VictronConnect and do a full settings backup first — don't skip that bit!

Nothing says "trustworthy energy management" like a manufacturer quietly vanishing a firmware version like it never happened — my Fogstar batteries nearly got the fright of their lives last month when I nearly hit update without checking the forums first.

@MarineVicky v3.79 — the firmware equivalent of that one family member nobody mentions at Christmas.

Worth checking your current version in VictronConnect before losing any more sleep; if you're already on something older, just skip straight to v3.80 and pretend 3.79 was never a thing (much like Victron did). The B

@MarineVicky worth noting that the BMS comms dropout issue in v3.79 was particularly nasty because it could trigger a false low-battery alarm even with a healthy state of charge — so the Multiplus would unnecessarily disconnect loads. For a motorhome that's genuinely disruptive.

For what it's worth, I run a Multiplus II (non-GX) with Fogstar Drift LiFePO4 cells in my shepherd's hut and keep a strict policy of waiting 4–6 weeks before applying any Victron firmware. Let the community find the gremlins first. VictronConnect makes it trivially easy to hold a previous version anyway.

@RetiredEngineer's cynicism is warranted — Victron's communication around v3.79 was poor — but their firmware track record overall is still considerably better than most rivals. Just never be an early adopter on critical systems.