Nut upsuser - Dec 2020 - [EXTERNAL] Re: This Liebert device (10af:0002) is not supported. Newer Lithium PSI5 device.

I added the 'productid = 0002' line to my ups.conf and get this new
output:

sudo /sbin/upsdrvctl start

Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
Can't claim USB device [10af:0002]: could not detach kernel driver from
interface 0: Operation not permitted
Driver failed to start (exit status=1)

Anything else I can try?


—
Lucas Keipper
IT Consultant & Owner
LMK Consulting
(980) 621-6728
lmkconsulting.net <http://www.lmkconsulting.net>


On Thu, Dec 10, 2020 at 6:03 PM Joe Reid <jreid at vnet.net> wrote:
> [networkups]
>          driver = usbhid-ups
>          port = auto
>          desc = "Network Closet UPS"
>          productid = 0002
>
> is what's in my ups.conf
>
>
> On 12/10/2020 2:44 PM, Lucas Keipper wrote:
> > Hi there. I have a new Liebert Vertiv PSI5 Lithium UPS connected to my
> > Ubuntu 18.04 box via USB that I am trying to configure with NUT. This
> > device is not on the HCL, but should be pretty similar to the  PSI
> > 1440 USB which uses the usbhid-ups driver. (or I'm completely
wrong,
> > but it's a similar product family...)
> >
> > I know it's not officially supported, but if someone would like to
use
> > me as the guinea pig for the correct driver settings then I'm open
to
> > some additional testing.
> >
> > ups.conf entry:
> > [VertivPSI5-lithium]
> >    driver = usbhid-ups
> >    port = auto
> >
> > "sudo /sbin/upsdrvctl start" outputs the below:
> >
> > Network UPS Tools - UPS driver controller 2.7.4
> > Network UPS Tools - Generic HID driver 0.41 (2.7.4)
> > USB communication driver 0.33
> > This Liebert device (10af:0002) is not (or perhaps not yet) supported
> > by usbhid-ups. Please make sure you have an up-to-date version of NUT.
If
> > this does not fix the problem, try running the driver with the
> > '-x productid=0002' option. Please report your results to the
NUT user's
> > mailing list <nut-upsuser at lists.alioth.debian.org
> > <mailto:nut-upsuser at lists.alioth.debian.org>>.
> >
> > How do I "run the driver with -x ..."? I've tried adding
it to the end
> > of the command line and adding it to the ups.conf file, but neither
work.
> >
> > I have updated the system via apt.
> >
> > NUT version is: 2.7.4-5.1ubuntu2
> >
> > Thanks!
> >
> > —
> > Lucas Keipper
> > IT Consultant & Owner
> > LMK Consulting
> > (980) 621-6728
> > lmkconsulting.net <http://www.lmkconsulting.net>
> >
> > _______________________________________________
> > Nut-upsuser mailing list
> > Nut-upsuser at alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
>
> --
> joe
>
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20201211/49c72ab3/attachment.html>

> Can't claim USB device [10af:0002]: could not detach kernel driver from
interface 0: Operation not permitted
> Driver failed to start (exit status=1)

> Anything else I can try?
Maybe adding a udev rule like:

# /etc/udev/rules.d/90-nut-ups.rules
ACTION=="add", \
SUBSYSTEM=="usb", \
ATTR{idVendor}=="10af", ATTR{idProduct}=="0002", \
MODE="0660", GROUP="nut"

Be sure to reboot or reload Udev rules after

Credit to AskUbuntu https://askubuntu.com/a/276637 for initially helping me
figure this out.


Thank you,
David Zomaya
Tripp Lite


________________________________
 This message is for the addressee's use only. It may contain confidential
information. If you receive this message in error, please delete it and notify
the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no
responsibility for viruses which may infect an email sent to you from Tripp Lite
and which damage your electronic systems or information. It is your
responsibility to maintain virus detection systems to prevent damage to your
electronic systems and information.