Cheers, Looking at the `vendorid=0x10af` -- the usbhid-ups subdriver `belkin-hid` has the best chance here (being the only one to mention it).
The `productid=0x0002` is indeed not mentioned in `drivers/belkin-hid.c` so probably nobody encountered it before and/or tested a hotfix to PR it into NUT upstream. Since the NUT release v2.8.1, the `usbhid-ups` should support a `subdriver` config option, so you can try it with devices whose IDs are not compiled into the binary program. If you don't have it packaged but are comfortable building from source, the github NUT wiki has some pointers about "in-place" builds to test from the build area and later optionally install to override what the distro package delivers. Jim On Mon, Dec 4, 2023, 13:15 tim Goins via Nut-upsuser < nut-upsuser@alioth-lists.debian.net> wrote: > Replaced ups with a new Liebert UPS and it seems the device may not be > known to nut. Below is output of lsusb: > ID 10af:0002 Liebert Corp. PowerSure PST UPS > > Sent from Outlook <http://aka.ms/weboutlook> > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
