Vertiv Liebert PSI5 (USB ID 10af:0002) - usbhid-ups fails with “Access denied (insufficient permissions)” on TrueNAS SCALE 25.10.4

TrueNAS General
1

Hi all,

I’m trying to configure a Vertiv Liebert PSI5 UPS on TrueNAS SCALE 25.10.4. My question is this:

Has anyone successfully configured a Vertiv Liebert PSI5 (USB ID 10af:0002) with TrueNAS SCALE 25.10.x?

Environment

  • TrueNAS SCALE 25.10.4

  • UPS: Vertiv Liebert PSI5

  • USB Vendor/Product ID: 10af:0002

  • Driver selected in the UI: Liebert ups 2 PowerSure PSA USB (usbhid-ups)

  • Port: auto

Symptoms

The UPS is detected by Linux:

  • lsusb -v reports:

    • Manufacturer: Vertiv Co.

    • Product: Liebert PSI5

    • Vendor/Product: 10af:0002

However: ‘upscale ups’ returns ‘Error: Driver not connected’

Running the driver manually as root: ‘sudo /lib/nut/usbhid-ups -a ups -DD’ produces:

Checking device 1 of 6 (10AF/0002)
Failed to open device (10AF/0002), skipping:
Access denied (insufficient permissions)

I have already verified usb cable is good. UPS works correctly when connected to a Mac. Linux detects the UPS. And, ups.conf is:

driver = usbhid-ups
port = auto

  • midclt call ups.config reports the expected configuration.

  • upsd and upsmon are running.

  • usbhid-ups immediately exits.

Additional observations

The shipped NUT udev rules contain entries for:

  • 10af:0001

  • 10af:0004

  • 10af:0008

>>>>but not for 10af:0002.

I also tested changing permissions on /dev/hidraw0 and /dev/hidraw1 (temporarily) and it did not change the behavior.

Thanks!

2

It may be that your ups is not supported by the nut version truenas uses, since the version is pretty out of date.
Edit:
yeah it seems your ups need nut version 2.8.2 and truenas uses 2.8.0

3

Thanks for looking into this. That aligns with what I’ve been seeing.

The UPS identifies as USB ID 10af:0002 (Vertiv Liebert PSI5), and TrueNAS SCALE 25.10.4 reports NUT 2.8.0.

During troubleshooting we confirmed:

  • Linux detects the device correctly.

  • usbhid-ups finds the device but fails to initialize it.

  • We ruled out cabling and general USB detection issues.

If PSI5 support was added in NUT 2.8.2, that would explain the behavior very well.

Do you know whether an updated NUT package is planned for a future TrueNAS release, or if there’s a recommended workaround in the meantime?

4

I hope that Truenas 26 gets an updated nut version, but I’d have to check if it really gets it

5

Someone using the beta checked which version truenas 26 uses and yes it gets an update, but sadly only to 2.8.1

6

You can try creating a configuration in /etc/udev/rules.d/50-upsnut.conf

with the following content:

SUBSYSTEM==“usb”, ATTR{idVendor}==“10af”, ATTR{idProduct}==“0002”, MODE=“0660”, GROUP=“nut”