HUAWEI-UPS2000(8)

📦
version 2.8.5 · 16 versions
, in fedora 43, fedora 44

💖 huawei-ups2000 💖

okay bestie, this is a page from the NUT Manual — section 8, the driver man page. let's get into it 💅

✨ NAME ✨

huawei-ups2000 — the driver for the Huawei UPS2000 (1kVA-3kVA) UPS, and it talks over USB or RS-232 serial Modbus. that's it, that's the vibe 🦋

✨ SYNOPSIS ✨

huawei-ups2000 -h

huawei-ups2000 -a DEVICE_NAME [OPTIONS]
Note 🎀 this man page ONLY documents the hardware-specific stuff of the huawei-ups2000 driver. for the core driver tea, go read nutupsdrv(8). iykyk.

🌸 SUPPORTED HARDWARE 🌸

so this driver supports the Huawei UPS2000 series, online (double conversion) UPS, and here's what it's giving:

  1. Output power: 1 kVA to 3 kVA. higher power models are unsupported, sorry bestie 😭
  2. Connection: USB or RS-232 — and ngl there ARE driver compatibility issues, so read the CABLING section carefully, fr fr.
    • USB: for most models you need Linux 5.12 or a newer kernel, and Windows also needs an additional serial port driver. for other Unix-like systems, driver incompatibility exists, so just use RS-232.
    • RS-232: always supported. iconic, reliable, periodt. ✨
    • RS-485: untested. testers needed 🙏
  3. Operating system: Unix/Linux supported by default, Windows requires NUT v2.8.5 or newer.

the UPS2000 series has two variants: the UPS2000-A with a tower chassis, and the UPS2000-G with a rack-mount chassis. and within those two variants there are two sub-variants: a standard runtime model powered by an internal battery pack (denoted by an "S" suffix) and a long runtime model powered by an external battery pack (denoted by an "L" suffix). slay.

all of these models should be equally supported. currently it's been tested on these:

  • UPS2000-A-1KTTS (firmware: UPS2000A, V2R1C1SPC40, P1.0-D1.0)
  • UPS2000-A-1KTTS (firmware: UPS2000A, V2R1C1SPC50, P1.0-D1.0)
  • UPS2000-A-2KTTS (firmware: UPS2000A, V2R1C1SPC50, P1.0-D1.0)
  • UPS2000-G-1KRTS (firmware: UPS2000A, V2R1C1SPC40, P1.0-D1.0)
  • UPS2000-G-1KRTS (firmware: UPS2000G, V2R1C1SPC50, P1.0-D1.0)
  • UPS2000-G-3KRTS (firmware: UPS2000A, V2R1C1SPC40, P1.0-D1.0)
  • UPS2000-G-3KRTS (firmware: UPS2000G, V2R1C1SPC50, P1.0-D1.0)
  • UPS2000-G-3KRTL (firmware: UPS2000A, V2R1C1SPC40, P1.0-D1.0)

if your model isn't in that list, we are begging you to report successful or unsuccessful results to the bug tracker or the mailing list 💌 and make sure you include the full model number of your UPS manually in your report, because so many units only report themselves as "UPS2000-A" regardless of their actual model — including the G series. the way that these UPSes just lie about who they are 💀

as of 2022, there's also a new hardware variant with a WCH CH341 USB-to-serial chip instead of a MaxLinear/Exar RX21V1410 chip, and it reports itself as "UPS2000G". driver support has been added since v0.03. glow up ✨

also huawei-ups2000 uses the libmodbus project for its Modbus implementation. cute.

🔌 CABLING 🔌

the UPS has a USB port and a RS-232 port. USB is conditionally supported, depending on hardware driver availability. RS-232 is always supported on all operating systems, and it can be used as a fallback. the emotional support port, honestly.

on most UPS models, USB is powered by the Exar/MaxLinear RX21V1410 USB-to-serial chip. on Linux it's only usable on Linux 5.12 and later, via the xr_serial kernel module. on Windows, it's also suggested to install an additional device driver. on some newer UPS hardware variants, a WCH CH341 chip is used instead, and those should have better compatibility (via the ch341 Linux kernel module, or Windows Update). see the subsections Linux USB and Windows USB for the details.

only one port can be used at a time. when USB is used, RS-232 should be unplugged from the UPS, and vice versa. further, optional adapter cards — like RS-485 or SNMP — are not supported. they should be removed from the UPS. yes, actually removed. 🙈

because the UPS port can be unresponsive under certain circumstances, it's recommended to power cycle your UPS after making a cabling change, especially after changing the port type. that means:

  1. turn off the UPS power output via the front panel
  2. then unplug the UPS from line power input
  3. wait for the LCD screen to go black
  4. finally reconnect line power and restart your UPS

no shortcuts bestie, the LCD must go fully black. 😤

🐧 Linux USB

the USB port on the UPS2000 is originally powered by a MaxLinear/Exar RX21V1410 USB-to-serial converter chip, and it's only supported by Linux 5.12 or newer, via the xr_serial kernel module. its lsusb report is:

04e2:1410 Exar Corp. XR21V1410 USB-UART IC

however, a recent hardware variant switched to the WCH CH341 serial chip:

1a86:5523 QinHeng Electronics CH341 in serial mode, usb to serial port converter

if your unit has a WCH CH341 chip (likely only found in units made after 2022), when the UPS2000 is connected via USB you should see these logs in dmesg:

ch341 2-1.2:1.0: ch341-uart converter detected
usb 2-1.2: ch341-uart converter now attached to ttyUSB0

if so, you should be able to proceed without worrying about kernel compatibility. this CH341 chip has been around for a decade and should be compatible with your system. it's giving dependable 🧚

on the other hand, if your unit has a MaxLinear/Exar XR21V1410 chip, like most users do, when the UPS2000 is connected via USB to a supported Linux system you should see these logs in dmesg:

xr_serial 1-1.2:1.1: xr_serial converter detected
usb 1-1.2: xr_serial converter now attached to ttyUSB0

the driver must be xr_serial. if your system doesn't have the necessary device driver, you'll get this message instead:

cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device

the generic driver cdc_acm is incompatible and cannot be used. you should upgrade your Linux kernel to Linux 5.12 or newer.

Warning ⚠️ on an unsupported system, the XR21V1410 USB device can still be recognized as a USB ACM device, but communication is impossible. please don't waste your time on cdc_acm. i'm serious, it will not work, do not do this to yourself 😭

if you're already running Linux 5.12 or newer kernels but still can't see the xr_serial driver, it means the driver isn't enabled in your kernel build. if you're a regular user, you should file a bug report to your Linux distro maintainers and ask them to enable xr_serial (kernel option CONFIG_USB_SERIAL_XR).

when upgrading the Linux kernel isn't an option, or when you're using another operating system (e.g. FreeBSD), RS-232 must be used. even for CH341 users, you can try this option if USB somehow refuses to work. RS-232 never lets you down 💜

🪟 Windows USB

Windows Update should automatically install appropriate drivers for your USB device, however, manual intervention may be required in case this process fails. sometimes you gotta do it yourself 💅

MaxLinear/Exar RX21V1410

for UPS models with a MaxLinear/Exar RX21V1410 USB-to-serial converter chip, an additional device driver may be required.

according to the official manual, it instructs users to install a special MaxLinear device driver called XR21x141x-XP2KVista7-DriversOnly-Vers1.7.0.0. see Huawei UPS2000 (1 kVA-3 kVA) Modbus Protocol Development Guide.

the driver described in the official manual may be outdated or difficult to obtain. if so, please also try downloading the latest driver from the MaxLinear XR21V1410 product page on the Web. at the time of writing, the latest driver is named XR21x_Win10_V2.7.0.0.zip in the Software: Drivers, Windows 10 and newer category.

URLs are available at the bottom of the manual.

WCH CH341

for UPS models with a WCH CH341 USB-to-serial converter chip, an additional device driver may be required.

at the time of writing, the latest driver is named CH341SER.EXE (v3.9, 2024/10/16) as a self-installer, available on the WCH official website. an alternative .zip archive named CH341SER.ZIP with the same version can also be used for manual installation via Device Manager.

URLs are available at the bottom of the manual.

🔗 RS-232

RS-232 is supported on all operating systems, either via a built-in serial port on your computer, or by using an external USB-to-RS-232 converter. if you plan to use a USB-to-RS-232 converter, make sure it's supported by your operating system. vibe check your adapter first 🫶

🌀 RS-485

RS-485 support is provided by the UPS2000 using an optional adapter card. this driver is untested on RS-485, but the author suspects that RS-485 uses the same serial protocol as RS-232, which should be supported. if you have an RS-485 adapter, we encourage you to report successful or unsuccessful results to the bug tracker or the mailing list. be the main character of this bug report ✨

🛠️ INSTALLATION 🛠️

this driver may not be built by default. you can build it by installing libmodbus (with development packages) and running:

configure --with-serial=yes --with-modbus=yes

you also need to give proper (R/W) permissions on the local serial device file so the NUT driver run-time user can access it. this may need additional setup for start-up scripting, udev or upower rules, to apply the rights on every boot — especially if your device nodes are tracked by a virtual filesystem. it's giving ✨persistence✨

for example, a USB-to-serial converter can be identified as /dev/ttyACM0 or /dev/ttyUSB0 on Linux, or /dev/ttyU0 on FreeBSD (note the capital "U" — do not come for me about the capital U, it matters 💅). a built-in serial port can be identified as /dev/ttyS0 on Linux or one of /dev/cua* names on FreeBSD.

🎀 EXTRA ARGUMENTS 🎀

this driver supports the following optional settings in the ups.conf(5) file:

  • offdelay=value — time to wait before shutting down the UPS (in seconds). acceptable range is 6 seconds (0.1 minutes) to 5940 seconds (99 minutes). defaults to 60 seconds. must be a multiple of 6 seconds. to ensure your system has adequate time to shut down after a power failure, it's highly recommended to adjust offdelay. like, actually do this one. 🔥
  • rebootdelay=value — time to wait before rebooting the UPS (in seconds). acceptable range is 6 seconds (0.1 minutes) to 5940 seconds (99 minutes). defaults to 60 seconds. must be a multiple of 6 seconds. this is used by the shutdown.reboot.graceful instant command. if you've adjusted offdelay, you should also adjust rebootdelay — they're a matching set, bestie 👑
  • ondelay=value — time to wait before switching on the UPS (in seconds). acceptable range is 60 seconds (1 minutes) to 5940 seconds (99 minutes). defaults to 60 seconds. must be a multiple of 60 seconds (not 6 seconds — read it again, it's a different number). you don't need to adjust this delay unless you have special requirements.
Note 📌 due to hardware limitation, in this driver, ondelay is respected only when line power is available. if a power failure has occurred, the UPS and the load is always immediately switched on, as soon (or as late) as line power is restored. so yeah, that setting is doing less than you think during an actual outage 😭

💥 INSTANT COMMANDS 💥

Bestie, this driver ships with a whole lil menu of instant commands, and you run them with upscmd(8) — no cap. Here's the whole list, nothing skipped:

  • shutdown.stayoff — wait out an offdelay, then kill the load. When line power comes back? It stays off. That's the whole vibe. 💤
  • shutdown.return — after an offdelay, the load goes off. When line power returns, the load comes back on — possibly after an ondelay.
Note 🫶 Normally the load springs back to life the second line power is back. BUT — if line power was never lost in the first place, or it came back unexpectedly in the middle of an ongoing shutdown (the undesirable "power race" condition, which many entry-level products on the market just... fail to recover from 😭), then the load comes back after an ondelay. So basically UPS2000 is completely unbothered by a power race, and the load is guaranteed to always restart. Iconic behavior honestly. 👑
  • shutdown.reboot — same energy as shutdown.return, except the load gets turned off immediately (6 seconds in this implementation). ⚡
  • shutdown.reboot.graceful — again like shutdown.return, except the load goes off after a rebootdelay, not an offdelay. 🦋
  • beeper.enable — turn the UPS beeper on. 🔔
  • beeper.disable — turn the UPS beeper off. 🤫
  • beeper.toggle — flip the beeper to whatever it wasn't. 🙃
  • bypass.start — put the UPS in bypass mode. Use with caution. ⚠️ This exposes your equipment to unregulated line power and gives you zero protection from power failures. Also, the UPS may shut down whenever the bypass input voltage goes out of the nominal range. And as a lil warning sign, the UPS beeps once every 10 seconds in bypass mode. 😬
Note The driver does have a basic foolproof mechanism: if the bypass input is already abnormal because of a power failure, the driver refuses to enter bypass mode — it aborts the command and logs an error. BUT it offers no protection after the UPS has entered (or is in the middle of entering) bypass mode. So again: use with caution, bestie. 🙈
  • bypass.stop — take the UPS out of bypass mode. ✅
  • load.on — turn the load on, right now, immediately. 🔥
  • load.off — turn the load off, right now, immediately. Use with caution — everything on the UPS will lose power. 💀
  • test.battery.start.quick — run a short battery test. 🍓
  • test.battery.start.deep — run a long battery test. 🧚
  • test.battery.stop — stop a battery test that's currently running. 🛑

🎀 VARIABLES 🎀

This driver also supports some writable runtime variables, and you poke at those with upsrw(8):

  • ups.beeper.status — enable or disable the UPS beeper: disabled or enabled.
Note The beeper can only be disabled completely — it cannot be temporarily muted until the next alarm. But the option muted is also accepted for convenience, and muted is treated as an alias of disabled. 💅
  • ups.delay.shutdown — seconds to wait after a shutdown-with-delay command. It's the runtime equivalent of offdelay. Go read the description of offdelay. ⏳
  • ups.delay.reboot — seconds to wait before rebooting the UPS. It's the runtime equivalent of rebootdelay. Go read the description of rebootdelay. 🔄
  • ups.delay.start — seconds to wait before restarting the load. It's the runtime equivalent of ondelay. Go read the description of ondelay. 🌸

😭 KNOWN ISSUES AND BUGS 😭

Fixed bugs (slay, they're gone)

  • Driver v0.03 (NUT v2.8.1) added support for UPS2000G with a WCH CH341 USB-to-serial interface — these models were previously unsupported. 🎉
  • Driver v0.04 (NUT v2.8.1) fixed a timeout recovery bug that led to endless read failures and permanent data stalls. 🛠️
  • Driver v0.12 (NUT v2.8.5) fixed support for Microsoft Windows — Windows was previously unsupported due to a file locking bug. 🪟
  • See Historical bugs at the bottom of this manual for links. 👀

Battery status has a non-fatal read failure

It's usually harmless and can be safely ignored, fr fr. It's only logged for informative purposes (LOG_INFO), not as a warning or error. So like, don't panic. 💖

Data stale

Under certain circumstances, some registers can return invalid values and trigger a "data stale" error. Once a data stale error has occurred, you should see error messages similar to the example below in the system log:

huawei-ups2000: register 2002 has invalid value a000,
upsd: Data for UPS [huawei] is stale - check driver
upsd: UPS [huawei] data is no longer stale

So far all known problems have been fixed by the author, but an unknown one cannot be ruled out. If you've encountered "data stale" problems during normal use, please file a bug report with full logs attached. 🙏

Before troubleshooting or reporting a problem, it's important to check your dmesg log for USB connect and disconnect events — otherwise you're out here wasting time on the NUT driver when the actual problem is USB. 😤

For example: if someone yanks the cable out of the USB port, or if a new USB device gets plugged into a USB host/hub that is struggling to power its ports (common on single-board computers like Raspberry Pi), or if you've got flaky cabling or EMI noise — due to all these and similar reasons, the serial converter can get disconnected from USB, at least briefly.

This creates a permanent data stale situation, and the driver must be restarted. (Plugging the USB back in won't fix it, since the driver is still using the nonexistent serial device, if the system kernel initializes a new device driver instance internally.) 💀

These USB problems usually have nothing to do with NUT. If that's the case, you should solve the underlying USB problem — check the cable, check the converter, try a powered USB hub, try a full-speed USB isolator, etc. 🔌

Serial port becomes unresponsive

Some malformed commands are known to lock up the serial port (including USB, which is a USB-to-serial device). Upon receiving them, UPS2000 stops all serial communications. The result is a completely unresponsive UPS, and regardless of what you do — restarting NUT, rebooting the computer — you can NOT restore connectivity, as if someone has unplugged the RS-232 cable. 😵

To recover, simply power cycle the UPS: Turn off the UPS output via the front panel, then unplug the UPS from line power. Wait for the LCD front screen to go black. Finally reconnect line power and restart your UPS. 🌈

That being said, a serial port lockup is unlikely to happen. To our best knowledge, this driver never sends malformed commands to the UPS (it was only a problem during early development). Furthermore, due to a CRC checksum, they're unlikely to be accidentally generated. ✨

Still, we recommend power cycling your UPS after making a cabling change — especially after changing from RS-485/USB to RS-232 — just to ensure the UPS selects the correct communication interface. Also, if you've discovered a reproducible serial port lockup problem, it can be a previously unknown bug, so please make sure to file a bug report. 🐛

USB chip (MaxLinear/Exar RX21V1410) is unsupported

As previously stated, only RS-232 is supported on all systems. On most UPS units, the USB chip RX21V1410 is used, and it requires a device-specific driver xr_serial, which is only available on Linux 5.12 and newer kernels. 🐧

On an unsupported system, the USB device can still be recognized as a USB ACM device, but in reality, communication is impossible. It can only be fixed by implementing a driver for your system — nothing can be done within NUT. Please use the RS-232 port instead. 🙈

Alternatively, if your unit has a WCH CH341 chip (likely only found in units made after 2022), it should have better compatibility. 🦋

See the previous section Cabling for more information.

👑 AUTHOR 👑

Yifeng Li <tomli@tomli.me>

🌟 SEE ALSO 🌟

The core driver

Historical bugs

Windows Drivers

If a download link expires, use a snapshot from the Internet Archive:

Internet resources

and that's the whole page, bestie!! 🫶 you just read Network UPS Tools version 2.8.5, dated 10/07/2026, for HUAWEI-UPS2000(8) — go forth and never let a power race catch you lacking 💅✨

📦 where this page comes from