Victron Battery Compatibility (2026): The Three Tiers & the DVCC Test

There is a piece of advice circulating on Victron pages that costs installers real money: that if a battery isn’t on Victron’s tested list, it can’t talk to the system, so you should fall back to a shunt and monitor it like a dumb pack. That is not what Victron says. Victron’s own battery compatibility page states plainly that many third-party batteries not on the list are compatible, that using them is permitted under warranty, and that Victron supplies its battery protocol specification to those manufacturers on request. Off-list and off-comms are two different things. This guide sorts Victron battery compatibility into the three tiers that actually exist, and explains the one BMS behaviour that decides whether a battery talks cleanly or throws phantom alarms for a week.

Quick answer: Victron runs an open battery ecosystem with three tiers of compatibility. Tier 1 is the roughly 28 brands Victron has tested and documented (Pylontech, BYD B-Box, Dyness, Pytes, BSLBATT, Discover AES, BattleBorn, SimpliPhi, Freedom Won, Sunwoda and others), giving plug-and-play managed operation. Tier 2 is third-party batteries not on that list: Victron confirms these are compatible, permitted under warranty, and supported through your supplier, and they run the same full closed-loop control as Tier 1 provided the BMS follows Victron’s protocol. Tier 3 is DIY and self-build BMS setups (123SmartBMS, Batrium, REC), which Victron supports only in a limited way. Managed batteries connect over BMS-Can (CANBus) to a GX device such as the Cerbo GX, which then runs DVCC. The single most useful test of whether a battery is genuinely managed: when the pack fills, its BMS must reduce the Charge Voltage Limit (CVL). A BMS that only clamps the Charge Current Limit (CCL) instead will trigger overvoltage and overload warnings that look like inverter faults but aren’t.

Victron Battery Compatibility: The Three Tiers

Victron does not publish a single approved-or-rejected list. It publishes a tested list and then, separately, a policy for everything else, and the gap between those two documents is where most of the confusion on this topic lives. Sorted properly, there are three tiers, and only the third one is genuinely limited.

Tier structure derived from Victron Energy’s official Battery Compatibility page (victronenergy.com/live, last modified 16 March 2026), which lists tested batteries, states the warranty and support position for non-listed third-party batteries, and separately documents DIY/self-build BMS products. Brand coverage changes between revisions. Check the current page for your specific model.

The practical takeaway is the boundary between Tier 2 and Tier 3, not between Tier 1 and Tier 2. A Tier 2 battery is not a compromise version of a Tier 1 battery. It runs the same closed loop, reports the same state of charge, accepts the same DVCC control. What you give up by being off the tested list is Victron’s own documentation and Victron’s own support desk for that specific pack, which is precisely why Victron’s wording puts the responsibility on the supplier. If your supplier can’t hand you the pairing parameters, that’s a supplier problem, not a protocol problem.

The DVCC/CVL Test: What “Managed” Actually Means

A managed battery is one whose BMS tells the Victron system what to do, not one that merely reports numbers. The battery publishes four values over BMS-Can: Charge Voltage Limit, Charge Current Limit, Discharge Current Limit and State of Charge — and the GX device uses them to drive the whole system through DVCC (Distributed Voltage and Current Control). That is the difference between a battery that is monitored and a battery that is in charge.

This is where a real, checkable test lives. Victron’s compatibility documentation flags a specific failure pattern it sees repeatedly from third-party and DIY BMS designs, and it’s worth quoting the mechanism precisely, because it explains a class of fault that gets misdiagnosed as an inverter problem:

The related failure is a BMS that blocks charge or discharge current outright, or sets CCL to zero when the pack is full. Victron reports that this triggers confusing alarms, including the inverter/charger reporting overload conditions under almost no load. Installers then spend hours chasing a fault that isn’t there, find the inverter works perfectly on the bench, and only later discover the cause was the battery’s BMS logic.

So when you evaluate a battery for a Victron system, the question to put to the supplier is not “is it compatible?” — everyone says yes. It is: does the BMS taper by reducing CVL as the pack approaches full, and does it avoid setting CCL to zero at 100%? A supplier who understands the question is a supplier whose battery will commission cleanly. One who doesn’t understand it is telling you something useful.

“Not on the List” Does Not Mean “No Communication”

Victron explicitly permits third-party batteries that aren’t on its tested list, under warranty, and provides its battery protocol specification to those manufacturers on request. This is the single most misreported fact about Victron compatibility, and getting it wrong leads people to buy the wrong thing or to cripple a perfectly capable battery.

You will find guides — including one currently ranking near the top for this search — that describe non-listed batteries as operating “without direct communication with Victron inverters,” and then recommend a SmartShunt as the workaround. For a genuinely unmanaged battery, that advice is fine: a shunt is exactly the right tool for a pack with no comms. Applied as a blanket rule to all off-list batteries, it is wrong, and it quietly downgrades a Tier 2 battery into a Tier 3 installation.

The difference matters because closed-loop control is not a luxury feature. Without it you lose temperature-aware charge limits, BMS-driven current control, and a true state of charge coming from the battery’s own coulomb counting rather than an inferred estimate. On an off-grid system where the “% remaining” figure decides whether the generator starts, that is a meaningful downgrade.

“No Communication” on Victron: How to Triage It

Most “no communication” faults on a Victron system are bus and configuration problems, not compatibility problems. Work through these in order before concluding the battery is incompatible. The fault is usually upstream of the pack.

1. Is the battery on BMS-Can, not the wrong CAN port? A GX device has more than one CAN interface, and the services differ between them. The managed-battery service belongs on BMS-Can. Confirm the port and confirm the CAN bus profile is set to the speed the battery expects (500 kbit/s is typical for LFP BMS profiles; check the battery’s documentation for the exact value).
2. Is the bus terminated at both ends? CAN needs a terminator at each physical end of the bus. One missing terminator produces exactly the symptom people report as “it worked for a minute then dropped”: intermittent, load-dependent comms failure that looks like a firmware bug.
3. Is the cable pinout right? RJ45 connectors are the standard trap here. A battery-brand CAN cable and a generic Ethernet patch cable look identical and are not electrically the same. Pinouts differ between battery brands; using the wrong cable gives you a link light and no data.
4. Is DVCC enabled, and is the battery selected as the controlling monitor? With DVCC off, the GX won’t act on the battery’s limits even if it can see them. Check that the battery is set as the system’s battery monitor rather than a shunt that’s silently taking priority.
5. Is the GX firmware current? Victron adds and refines battery driver support in Venus OS releases. An older firmware may simply not carry the driver for a newer pack.
6. Only then: is it the BMS logic? If comms are established but you’re seeing overvoltage or phantom overload alarms, you are likely looking at the CVL-versus-CCL behaviour described above rather than a wiring fault.

Steps 2 and 3 between them account for the large majority of these calls. It is almost never the inverter.

Which Victron Products Take a Managed Battery

Managed battery integration on Victron runs through a GX device, not through the inverter directly. The inverter/charger does the power conversion; the GX device is what speaks BMS-Can to the battery and distributes control to everything else on the system.

The design implication is straightforward: if closed-loop control matters to you, budget for a GX device from the start. A MultiPlus and a managed battery without a GX in between is a system that cannot run DVCC, no matter how good the battery’s BMS is.

Scaling Up: Parallel Batteries and Temperature Limits

When you stack multiple battery modules, the GX device should still see one battery, not several. This is the question that comes up as soon as a system grows past a single module, and it changes what you need to ask the supplier.

Rack-mounted LFP modules are typically wired in parallel for power and then daisy-chained on a separate internal communication link, with one module configured as master. The master aggregates the pack’s values and presents a single set of limits and a single state of charge to the GX device over BMS-Can. From Venus OS’s point of view there is one battery with a larger capacity, which is what you want: several packs each publishing their own competing Charge Voltage Limit to the same bus is a configuration problem, not a feature.

What this means practically is that the number of modules you can run in one bank is a property of the battery’s BMS, not of the Victron system. Ask the supplier for the maximum supported parallel count and the addressing method before you size the bank, because retrofitting a module into a chain that has hit its limit is an expensive discovery. It is also worth confirming that the modules must be the same model and ideally a similar age; mixing capacities or generations in one chain is where balance problems start.

What Victron’s Open Ecosystem Gives You

It is worth naming the strategic difference here, because it is the reason Victron dominates the off-grid and marine end of this market. Victron’s position is that the battery protocol specification is available to manufacturers on request, that non-listed third-party batteries are permitted under warranty, and that the tested list is a convenience rather than a gate. Compare that with the closed end of the market, where an inverter accepts only the manufacturer’s own packs and third-party batteries are locked out by design, the trade-off we broke down in our guide to Sungrow battery compatibility.

An open platform costs you something. You take on the integration work, you need a supplier who can produce pairing parameters, and you carry more responsibility for verifying the pack. What you get in return is leverage: you can specify the battery on capacity, warranty, cycle life and price rather than accepting whatever the inverter brand sells. Over a system’s life that is usually the larger number. The same open-platform logic drives the other systems in this cluster: Growatt, GoodWe and Deye — and if you’re still choosing between architectures, start with low voltage versus high voltage home batteries.

Common Mistakes With Victron Battery Compatibility

Frequently Asked Questions