similar to: Question on EATON UPS

Laurent Taieb via Nut-upsuser wrote on 3/9/23 9:25 AM: > > Hi NUT Users, > > One of my APC UPS is having battery issue and apparently we cannot > change battery in that UPS. (not super green?) > > I have purchased an EATON UPS and added the ref in ups.conf > > When restarting the driver, I got this error > > >0.030612[D2] Checking device 2 of 10 (0463/FFFF)

The "unknown" fields mean the driver did not get that piece of information from libusb. In case of Manufacturer/Product which are unknown in the later post, but known in the first, I suppose you had another driver running, or the kernel still owned it (udev misbehavior, not handing it off after reconnections, etc.) and so exclusive access was not given to the new (currently reporting)

Sounds like some other program is holding the port. Have you stopped other NUT drivers for the device (e.g. via auto-resuscitating services) before starting this one? Does udev, ugen or similar facility have the configuration to hand off this device to NUT run-time user? (BTW, if you are now testing a custom build - was it configured to use same accounts as pre-packaged variant)? On Fri, Mar 24,

Thanks Larry, I tried. Got the following traces and the driver doesn?t start. 1.036797 [D2] - VendorID: 0463 1.036812 [D2] - ProductID: ffff 1.036826 [D2] - Manufacturer: unknown 1.036840 [D2] - Product: unknown 1.036872 [D2] - Serial Number: unknown 1.036912 [D2] - Bus: 002 1.036942 [D2] - Device: unknown 1.036965 [D2] - Device

On Thursday, March 9th, 2023 at 8:34 AM, Dan Langille via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: >> The UPS has been defined in ups.conf as: >> >> [myups3] >> >> driver : usbhid-ups >> >> port = auto >> >> vendorid = 0463 >> >> productid = ffff >> >> desc = "5S" >> >> bus

Also, just in case - are you in a virtualized environment? Is there (intentional or not) USB pass-through to the UPSes? My hint is, we had cases where a host or guest grabbed the device but it was not apparent from the part of system running NUT. Jim On Fri, Mar 24, 2023, 23:23 Jim Klimov <jimklimov+nut at gmail.com> wrote: > Sounds like some other program is holding the port. Have

Cheers, Trying to wrap my head around an issue discussed in https://github.com/networkupstools/nut/issues/1925 The gist of it is that despite the usbhid-ups driver running as `root` and seeing most of the regular run-time info, in the initial device search it fails to find basic matching info points - the device vendor, product and sernum strings: ```` 0.289953 [D2] Device does not match

Cheers, Trying to wrap my head around an issue discussed in https://github.com/networkupstools/nut/issues/1925 The gist of it is that despite the usbhid-ups driver running as `root` and seeing most of the regular run-time info, in the initial device search it fails to find basic matching info points - the device vendor, product and sernum strings: ```` 0.289953 [D2] Device does not match

I?m making some progress I believe? I switched off and switched on the UPS further to the laptop having started the daemon and I?m not getting the same error message which is probably due to the server working in the background still locking the device I think the daemon starts but gets into an infinite loop and doesn?t finish and hand back control. Here are the updated traces I got by

I think having this logic buried within libhid/libusb (libusb:libusb_open(), line 179 to 206) is ultimately a mistake, albeit one that I am probably responsible for. Would it make sense to confine libhid to low-level operations, and leave the decision of trying to reopen vs. retrying to open to the high-level driver, in this case usbhid-ups? I envision that the code in usbhid-ups:reconnect_ups()

Hello all, I think I've found the "regression" in Belkin/Liebert USB HID support which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was actually caused by a bug fix: practically the only functional difference per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()` to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <

Hello all, I think I've found the "regression" in Belkin/Liebert USB HID support which worked for NUT v2.7.4 and reports zero voltages in 2.8.0 -- it was actually caused by a bug fix: practically the only functional difference per `git diff v2.7.4..v2.8.0 drivers/belkin-hid.c` is a change from `abs()` to `fabs()` in order-of-magnitude comparisons like `if( abs(value - 1e-7) <

Apologies for the long post. I'm trying to include what I hope are the relevant bits (output of lsusb -v and usbhid-ups) Long term goal: I've got a DIY UPS that I would like to get working with my QNAP NAS (which uses Linux and NUT underneath the hood) Immediate short-term problem: I can't get past running usbhid-ups on Ubuntu 23.10 with an Arduino Leonardo. I have an Arduino Micro