UPS Not Detected by Your Computer: How to Fix It

Most likely cause: the cable or the port

When a UPS shows no sign of life on the computer side (no battery icon, nothing in device lists, the software says "no UPS found"), the fault is usually physical. Three culprits cover most cases:

• Wrong cable in an RJ45-style port. Many APC units, and some other brands, have a data port that looks like an Ethernet jack. It is not Ethernet. It carries USB or serial signals on a manufacturer-specific pinout, and only the matching cable works.
• A charge-only or damaged USB cable. If the UPS has a standard USB-B (printer-style) or USB-C port, any data-capable cable should work, but some cheap cables only carry power.
• A hub, KVM, dock or front-panel port in the way. UPS units enumerate as low-speed HID devices, and some hubs, KVM switches and docks don't pass them through reliably.

The fix is usually to find the original cable (or the exact replacement listed in the manual), plug it into a rear USB port wired directly to the motherboard, and power-cycle the connection. If the UPS still doesn't appear, the problem is software, and the diagnostic flow below narrows it down.

Diagnostic flow, in order

Work through these checks in order. The early steps are quick, risk-free and resolve most cases; skip ahead only once a step clearly passes.

1. Confirm the UPS is on and finished starting. Most units only talk over USB while switched on. A UPS that shut itself off after a long outage, or is mid self-test, may not enumerate.
2. Identify the data port and the right cable. Check the rear panel and manual. If the port is RJ45-shaped, you need the manufacturer's USB-to-RJ45 (or serial-to-RJ45) cable for that model. A DB9 serial port needs the vendor's serial cable, and a generic null-modem cable is often wired differently.
3. Plug directly into the computer. Use a rear USB port, not a hub, monitor USB port, KVM, docking station or front-panel header. On older PCs, a USB 2.0 port is sometimes more reliable than a USB 3 port for HID devices.
4. Look for the device at the OS level (commands below). If the OS sees a USB device from the UPS vendor, the cable and port are fine and the problem is software.
5. Remove competing software. Make sure only one program (vendor app, apcupsd, or NUT) is trying to own the UPS.
6. Check permissions and drivers on Linux and NAS systems, where the monitoring daemon often runs as an unprivileged user.
7. Reset the communication path. Unplug the USB cable for 30 seconds, reconnect, and if needed power-cycle the UPS with the load safely shut down first. Some units also have a firmware update that fixes communication bugs.

Symptom, cause and fix

Windows

On a working setup, Windows shows a battery icon in the notification area (even on a desktop) and lists the UPS in Device Manager under Batteries as something like "HID UPS Battery", with a matching entry under Human Interface Devices. The exact names vary by brand.

• No battery entry at all: the cable, port or UPS is the problem. Try another port and cable before anything else.
• Entry with a warning icon: right-click, uninstall the device, unplug the USB cable, wait, and reconnect so Windows reloads its built-in driver.
• Battery shows but the vendor app can't find the UPS: reinstall the app with the UPS connected, and remove other UPS tools. In practice, PowerChute or PowerPanel coexist with the Windows battery driver but not with a second monitoring package.
• Drops out after sleep: in Power Options, disable USB selective suspend, and in Device Manager clear "Allow the computer to turn off this device to save power" on the USB root hub the UPS uses.

Windows can shut down on its own at a critical battery level once it sees the UPS. See Windows UPS shutdown settings for configuring that, and PowerChute and PowerPanel for the vendor tools.

macOS

macOS supports HID UPS units natively. When one is connected, a UPS section appears in the battery or energy settings, with options to shut down after a set time on UPS power or at a remaining-charge threshold. The exact location has moved between macOS versions, so if you don't see it, search System Settings for "UPS".

To confirm the hardware link, open System Information and look under USB. If the UPS vendor appears there but no UPS options show up, the unit may not present a standard HID power interface; check the vendor's Mac support. If it does not appear under USB, go back to the cable and port. Details are in macOS UPS settings.

Linux, NAS and homelab servers

Start at the bottom of the stack and work up:

# Does the kernel see a USB device from the UPS vendor?
lsusb

# Watch for it when you replug the cable
sudo dmesg -w

# NUT: probe for supported USB UPS units and suggest a config
sudo nut-scanner -U

If lsusb shows nothing new when you plug the cable in, no software change will help: it is the cable, port or UPS. If it shows the device, the remaining issues are almost always one of these:

Two daemons fighting over one device

apcupsd and NUT both want exclusive access to the UPS. Install one. On desktop distributions, the power management service may also read the UPS through the kernel's HID driver; that usually coexists, but if you suspect it, check which processes have the device open.

Permissions

NUT drivers run as an unprivileged user and rely on udev rules that grant access to known UPS vendor and product IDs. Distribution packages ship these rules, but a hand-built install, a new model not yet in the rules, or a container may lack them. The symptom is a permissions error in the driver log while lsusb shows the device fine.

Wrong driver

Most HID units use NUT's usbhid-ups driver. Some inexpensive units are not HID at all: they present a USB-to-serial chip and speak a simple serial protocol, which in NUT typically means the nutdrv_qx family. A few older Tripp Lite models use their own driver. The NUT hardware compatibility list is the authority here. A minimal HID entry looks like this:

[myups]
    driver = usbhid-ups
    port = auto
    desc = "Rack UPS"

For apcupsd with a USB-connected APC unit, the usual settings are UPSCABLE usb, UPSTYPE usb, and a blank DEVICE line so it autodetects. Full walkthroughs: Network UPS Tools (NUT) and apcupsd.

Appliance NAS systems

Synology, TrueNAS and Unraid use NUT or apcupsd under the hood, but you configure them through the web UI. If the NAS doesn't see the UPS, try every USB port on the NAS (some front ports are meant for storage) and confirm the model on the NAS vendor's compatibility list. See Synology, TrueNAS and Unraid setup guides.

Serial vs USB: an often-missed mismatch

Some UPS models, especially rack and tower business units, offer both a USB port and a serial port, or a single RJ45-style port that can do either depending on the cable. A serial cable plugged into a USB-to-serial adapter will not make the UPS appear as a USB HID device; the software must be set up for serial (a COM port or /dev/ttyS//dev/ttyUSB device) and the right protocol. Conversely, configuring apcupsd or NUT for USB when the cable is serial produces "no UPS found" forever.

Older APC Smart-UPS serial links use a specific signaling cable, and a generic straight-through or null-modem cable can, on some models, send a signal the UPS interprets as a shutdown command. If you are not certain a cable is the correct part, don't experiment on a UPS powering production equipment.

Virtual machines and USB passthrough

Passing the UPS's USB device through to one VM (on Proxmox, ESXi or similar) works, but it is fragile and backwards. The host is the thing that actually needs to shut down last, and passthrough tends to break when the device re-enumerates, the host reboots, or the USB bus numbering changes. If you do pass it through, map it by vendor and product ID rather than by physical port.

The more robust design is to connect the UPS to the hypervisor host, run a NUT server there, and have each VM (and other machines on the network) run a NUT client. The host then shuts guests down in order before powering off itself. Proxmox UPS shutdown covers this pattern in detail, and UPS for a homelab server covers the hardware side.

Network management cards

A UPS with a network management card is detected over the network, not USB. If monitoring software can't see it:

• Confirm the card has an IP address (DHCP lease or the address set in its setup utility) and that you can reach its web page.
• Check that the protocol your software uses (SNMP v1/v3, or the vendor's own protocol) is enabled on the card, with matching community strings or credentials.
• On some models, the card and the USB or serial port can't both be used for full monitoring at the same time, or the card takes priority. Check the UPS manual if you need both.

More in network management cards and SNMP.

Brand notes (check your manual)

• APC: many Back-UPS and Smart-UPS models use an RJ45-style data port that requires APC's own USB or serial cable for that model family. Some newer units add a standard USB port. See the APC lineup.
• CyberPower: most consumer and small-business models use a standard USB-B port and HID. Some units have a reputation in the NUT community for needing gentler polling; the NUT documentation notes model-specific workarounds.
• Eaton: most current small units are standard HID over USB-B; larger models may also offer serial and card slots.
• Tripp Lite: most current models are HID; some older models use a protocol that needs a different NUT driver.
• Budget and no-name units: some have no data port, or a USB port that is a USB-serial bridge rather than HID. If the box doesn't mention operating system shutdown support, assume limited compatibility.

When it isn't worth fixing

If the UPS passes a second-machine test with no detection, you've tried the correct cable, and its firmware is current, the communication board may be faulted. On a unit that is otherwise protecting power correctly, a network-capable UPS or a different monitoring approach may be cheaper than a repair. If the unit also has other problems, such as a replace battery light that won't clear or short runtime, weigh that into the decision. A UPS that can't signal a shutdown still rides through short outages, but on a server or NAS without graceful shutdown, a long outage ends in a hard power loss. That's the whole reason to get this link working.