[Nut-upsuser] Vertiv Liebert

[Jim Klimov]

On top of what Greg said, see if your udev.rules file provided by the NUT
package includes the vendorid:productid for your device. The
`ups.status:OB` (unless you're testing and it is really on battery) seems
like a short read of USB reports. Boosted driver debug may confirm it, like
`expected 900-something bytes but only got 33` or similar. Thos tends to
happen when the driver (or libusb on its behalf) can't exclusively access
the device - e.g. ifthe kernel holds it or has some other program attached.
The udev rules are one of mechanisms to manage these delegations.

Hope this helps,
Jim Klimov

On Sun, Apr 9, 2023, 02:29 Greg Troxel <gdt at lexort.com> wrote:

> Bruce Pleat via Nut-upsuser <nut-upsuser at alioth-lists.debian.net>
> writes:
>
> > Here's the (far less lengthy) output for the Vertiv Liebert:
> >
> > device.mfr: Vertiv Co
> > device.model: Liebert PSA5
> > device.serial: 22223106602D04C
> > device.type: ups
> > driver.name: usbhid-ups
> > driver.parameter.pollfreq: 30
> > driver.parameter.pollinterval: 2
> > driver.parameter.port: auto
> > driver.parameter.productid: 0002
> > driver.parameter.synchronous: no
> > driver.parameter.vendorid: 10AF
> > driver.version: 2.7.4
> > driver.version.data: Belkin/Liebert HID 0.17
> > driver.version.internal: 0.41
> > ups.mfr: Vertiv Co
> > ups.model: Liebert PSA5
> > ups.productid: 0002
> > ups.serial: 22223106602D04C
> > ups.status: OB
> > ups.vendorid: 10af
> >
> > As you can see, useful information is missing from the Liebert/Vertiv:
> > I'm running it connected to a Raspberry Pi 4B (latest patches applied
> > nightly), so I'd prefer to do it from there.
> >
> > Is there debugging I can do?
> > (I'm a NUT rookie and admit to finding the docs overwhelming.)
>
> I'm still sort of new, but:
>
>   Build nut from source and use that (the tip of master from it), rather
>   than whatever old code your OS provides.  2.7.4 is ancient and there
>   have been a ton of improvements since then.  I am not sure there is
>   anybody interested in helping you work on 2.7.4.
>
>   Run the driver with debugging flags to get verbose logging.   upsc
>   shows that variables you expect aren't there, and verbose logging will
>   give you some insight into what's happening.
>
>   See if other code, perhaps proprietary and even Windows, if you can
>   hold  your nose and suspend your free software ethics :-), will report
>   anything more.
>
>   Find the docs that show what is available via HID and read the driver
>   code to see if anything is missing.
>
> My guess is that your problem is one of:
>
>   something is going wrong and the device just isn't getting read.
>
>   The HID data structures do not line up between what nut expects and
>   the device provides
>
> and that upgrading to current nut is reasonably likely to avoid a lot of
> issues, even if it doesn't immediately work.  But it might.
>
> _______________________________________________
> 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/20230409/54e9efa9/attachment.htm>