Designed & made in France
🚚 All orders placed before September 27 have been shipped. We are now preparing the next orders (September 27, 28…). We will do our very best to deliver as quickly as possible.
LV-HUB8 min readBy the Pylon-Monitor teamUpdated

Pylontech LV-HUB: wiring, firmware and troubleshooting

One inverter, up to six groups of Pylontech batteries, and a small hub in between with its own firmware. What it does, how it is wired and started, what goes wrong when its firmware is out of date β€” and how to keep an eye on every group.

The short answer. The LV-HUB is the box that lets one inverter talk to up to six groups of Pylontech batteries. It has its own firmware, separate from the batteries', and an outdated one shows up as groups or modules missing, an address count that does not match the real number of racks, or an inverter that only sees part of the system β€” Pylontech's own troubleshooting answer for that last one is "upgrade the LV-HUB". The update is done through the hub's debug port with BatteryView, by an installer.

What the LV-HUB does β€” and when you need one

A single Pylontech stack β€” a "group" or "pile" in Pylontech's manuals β€” has one master battery that speaks for every battery behind it, up to 16 of them. Above that, or when the batteries are split into several stacks, each group has its own master, and an inverter can only listen to one battery voice on its CAN port. The LV-HUB solves that: it collects the CAN data of every group and hands the inverter a single, combined stream.

PointWhat Pylontech's manual says
Groups per hubUp to 6 battery groups
Batteries per groupUp to 16 US2000C, US3000C, US5000 or UP5000
Link to the inverterCAN, from the hub's CAN OUT port
Firmware updatesThrough the hub's RS232 port, marked "Debug"
RS485 instead of CANWith C-series and US5000 batteries, several groups on RS485 do not need an LV-HUB β€” the battery manual describes that wiring
Old and new batteriesWhen older US2000 modules share a system with US2000C, the manual uses an LV-HUB with each US2000C as the master of its own group

What the hub does not do: charge or balance anything. Every battery's BMS still protects and balances its own fifteen cells. The hub only carries information β€” which is exactly why its firmware matters: if it carries it badly, the inverter makes decisions on the wrong numbers.

How a system with an LV-HUB is wired

  1. Inside each group, the batteries are chained as usual: Link port 1 of one battery to Link port 0 of the next.
  2. The masters of the groups are chained to each other: the B/RS485 port of one master to the A/CAN port of the next group's master; the last master's B/RS485 stays empty.
  3. The A/CAN port of the first group's master goes to one of the hub's numbered ports, with the special cable from Pylontech's kit β€” a standard network cable does not work there.
  4. On the hub, CAN IN is linked to port 0, and CAN OUT goes to the inverter's CAN port.

The start-up order matters too. The hub's own address switches must read 000001, every battery's address switches stay at their default, and each group master is switched on in turn. When the first group's master has beeped three times β€” every group online β€” only that master's address switch is changed to 0100, the hub cable is connected, and the hub is switched on: it beeps, and its four green LEDs show the number of groups it sees, in binary. Many "my hub doesn't see everything" cases are this sequence done in the wrong order β€” worth redoing before suspecting the firmware.

Why the hub firmware matters

The hub's firmware decides how the groups are counted and addressed, how their values are combined, and how much detail is passed on to the inverter. Installers on Victron's community forum have documented the differences between versions well:

Pylontech's manual names the symptom that matters most: when the number of address assignments does not match the actual number of racks, its fix is to check the cabling, restart the whole system β€” and upgrade the LV-HUB.

Symptoms of an LV-HUB problem, and what to check first

What you seeCheck firstThen
The hub's status LED flashes red, or it shows fewer groups than you haveThe start-up sequence, the hub address (000001), the first master's switch (0100), the special cableHub firmware
The inverter shows fewer batteries than installedGroup cabling between masters (B/RS485 to A/CAN, last one empty)Hub firmware, then each battery's firmware
Address allocation errorCables in the right ports β€” Link ports inside a group, RS485/CAN between mastersHub firmware
No communication with the inverter at allThe inverter cable (CAN OUT, correct pinout on the inverter side), the hub's powerYour inverter's battery settings
One group consistently takes less current or ends at a different chargeDC cabling and fuses of that groupThe battery firmware of that group β€” see our firmware mismatch guide

The last line is the one nobody sees from the inverter, because the hub hands over a single combined state of charge. It is also the one that tells you the most about the long-term health of a large system.

How the LV-HUB firmware is updated

Like the batteries, the hub is updated with Pylontech's BatteryView on a Windows laptop, through the hub's RS232 "Debug" port, using the file supplied by Pylontech or your distributor.

Monitoring a multi-group system with Pylon-Monitor

Pylon-Monitor reads a group through its master's Console port β€” every battery of that group, every cell, up to 16 batteries. In a system with several groups, each group has its own master and its own Console port, so one Pylon-Monitor per group gives you every battery of the whole system. All of them can be linked to the same free account, each with its own name ("Group 1", "Garage rack"…), and you switch from one to the other on the online dashboard.

Pylon-Monitor dashboard comparing the batteries of a Pylontech stack side by side
Batteries compared side by side: charge, health, cycles, temperature and cell spread of every module β€” figures the inverter never receives behind a hub.

That is precisely the view the LV-HUB takes away from the inverter: each group's own charge, current, temperatures and cells, and each battery's BMS firmware β€” so a group that lags behind, or a battery on an odd release, stands out. To be clear about the limits: Pylon-Monitor reads the batteries, not the hub, so it does not show the LV-HUB's own firmware version; that one is read with BatteryView on the hub's debug port.

For the wiring of a single stack, see our parallel batteries guide; for the inverter link itself, the CAN, RS485 and Console guide; and for the alarm codes, the error codes guide.

Frequently asked questions

What is the Pylontech LV-HUB?
A CAN communication hub that joins up to 6 groups of Pylontech low-voltage batteries β€” up to 16 US2000C, US3000C, US5000 or UP5000 per group β€” into one data stream for the inverter. It does not charge or balance anything: each battery's BMS still does that.
Do I need an LV-HUB for two stacks of Pylontech batteries?
Not always. Pylontech's manual states that with C-series and US5000 batteries, several groups on RS485 do not need an LV-HUB. It is used for multi-group systems on CAN, and when older US2000 modules share a system with US2000C.
How do I know which LV-HUB firmware I have?
Connect a laptop with BatteryView to the hub's RS232 port marked "Debug". The version is not passed on through the batteries, so a battery monitor β€” Pylon-Monitor included β€” cannot show it.
What are the symptoms of outdated LV-HUB firmware?
Groups or modules missing on the inverter, an address count that does not match the number of racks, a Victron GX without per-module detail, or only 16 batteries shown in a larger system. Check the start-up sequence and cabling first, then update the hub.
How is the LV-HUB firmware updated?
With Pylontech's BatteryView on a Windows laptop, through the hub's Debug port, with a proper USB-to-RS232 cable and the file from Pylontech or your distributor. Do not cut the power during the update; if it stalls, contact the distributor.
Can Pylon-Monitor monitor a system with an LV-HUB?
Yes, one Pylon-Monitor per group, each on its group master's Console port, all linked to the same free account. You see every battery and cell of every group β€” the detail the hub does not pass on to the inverter.

One Pylon-Monitor per group, one free account: every battery and every cell of a multi-group Pylontech system, on the online dashboard.

Order now β€” €59 One-off purchase, €59 all in β€” no VAT, no subscription.