Orion XS shown as non-BMS-managed

Had this exact headache with my tiny house setup last winter — Victron NG bank feeding an Orion XS, and the damn thing showing as "non-BMS-managed" in VRM no matter what I tried with the VE.Smart networking.

The core problem worth discussing: if your BMS needs to pull the plug on charging during a low-cell event, does the Orion XS actually respect that signal reliably, or are we just hoping for the best?

In my case I've got a Fogstar Drift LiFePO4 bank, and the BMS should be talking to the Cerbo GX, which should be telling the Orion to stand down — but that chain of "shoulds" makes me deeply uncomfortable when real money is at stake.

Few things I'd genuinely like to know from people who've cracked this:

• Are you using the remote on/off wire as a hard cutoff from the BMS rather than relying on networked logic?
• Has anyone successfully got the Orion XS to show as BMS-managed in VRM, or is that just cosmetic?
• Does the Orion XS even need to be BMS-managed if the Cerbo is handling load/charge disconnect properly upstream?

The boat use-case (isolating a starter battery from the main bank) is basically identical to what a lot of us are doing with vehicle alternators or secondary battery circuits in off-grid rigs, so this isn't niche territory.

Curious whether anyone's actually stress-tested this or just crossed their fingers like I have.

@ROW_OffGrid been there with my motorhome setup — the key thing people miss is that the Orion XS needs to receive BMS data directly via VE.Smart networking, but if your BMS isn't a Victron Smart Battery Sense or a compatible Victron-branded unit, it simply won't propagate the right data objects across the network.

What BMS are you actually running? If it's a third-party unit (Daly, JK, etc.) you'll need a Cerbo GX or similar acting as the bridge — the Orion XS then reads BMS-managed status via the GX device rather than VE.Smart directly.

Check in VRM under the Orion XS device settings whether "BMS controlled" is toggled on manually as a workaround — it's buried under the advanced tab and easy to overlook.

@ROW_OffGrid one thing worth checking that's often overlooked: the Orion XS distinguishes between receiving BMS data passively via VE.Smart networking and actually being directly connected to a compatible BMS via VE.Bus or a dedicated BMS signal wire. VRM will only show "BMS-managed" when it's getting a genuine charge-enable/disable signal from the BMS itself, not just voltage telemetry floating around the network.

On my narrowboat I solved this by running a proper two-wire remote on/off connection from the BMS's charge-enable output directly to the Orion XS remote port, alongside the VE.Smart networking. Both are needed simultaneously in most configurations.

Also worth confirming your firmware is current — there were specific fixes in the Orion XS firmware around v1.06 addressing exactly this VRM reporting issue. Check the Victron changelog before assuming it's a wiring problem.

@ROW_OffGrid had the same issue on my boat last year. Worth checking your VE.Bus BMS is actually publishing its allow-to-charge signal across the network — not just connected. In VictronConnect, pull up the BMS device and confirm the "allow to charge" and "allow to discharge" flags are actively toggling.

Also double-check the Orion XS firmware — there was a specific version that introduced proper BMS-managed mode recognition. Anything below that and it'll just show as non-managed regardless of your network config.

Mine sorted itself after a firmware update plus power-cycling the entire network in the right sequence: BMS first, then the Orion XS last.

Good shout from @DevonDweller on the passively-vs-actively managed distinction — that caught me out on my own van build last spring.

One thing nobody's mentioned yet: firmware version matters enormously here. I had the exact same "non-BMS-managed" status stuck on my Orion XS until I updated it via VictronConnect. Pre-v1.08 firmware had a known bug where BMS data was being received over VE.Smart but not properly acknowledged in the charger's logic tree.

Also worth checking — if you're running a Lynx Smart BMS, make sure it's set as the network master in VE.Smart, not your MPPT. I'd accidentally let the SmartSolar take that role and the Orion was essentially ignoring the BMS signals entirely.

Pull the firmware version first before chasing wiring rabbits — saved me several hours of unnecessary head-scratching.

@ROW_OffGrid one thing that tripped me up on my narrowboat build — the Orion XS also needs to be on the same VE.Smart network as the BMS, not just a VE.Smart network. Sounds obvious but I had two separate networks running simultaneously (one for my MPPT, one I'd set up earlier for testing) and the Orion was quietly joining the wrong one. Check under Bluetooth settings → VE.Smart networking on the Orion itself and confirm the network name matches exactly what your BMS is broadcasting. Renamed mine to something unambiguous and it resolved immediately. Also worth double-checking firmware — Victron pushed an update last year that specifically addressed BMS status reporting on the XS, and running mismatched firmware across devices on the same network causes all sorts of weird ghost states in VRM.