> On Oct 29, 2023, at 9:25 PM, Kelly Byrd <kb...@memcpy.com> wrote:
> 
> I have seen reports of folks claiming this just worked for them out of the 
> box,

Here you're referring to just making things work on Windows or macOS, right? I 
don't think it will be quite as simple with NUT, mostly because the NUT drivers 
are trying to expose all of the variables and commands, rather than just the 
simple shutdown bits.

I'm not sure where a generic HID PDC driver sits in the priority list at the 
moment, but IIRC the current driver is still fairly tightly coupled to the USB 
VID and resulting model-specific mappings. So once you get the permissions 
worked out, you would still need a new source file that maps the HID Usage 
"paths" to NUT variable names. It's one of those things that in hindsight, it 
would have been great to fall back to a generic mapping that just looks at the 
OB and LB bits, but real-world UPSes are messy, and we would have needed those 
model-specific mappings to be able to distinguish things like input and output 
voltage.

That said, if you change the VID/PID to something supported already, things 
just might work. The "Couldn't retrieve descriptors" is likely a result of the 
driver dropping root privileges, then not having enough permissions to write to 
the /dev/bus/usb node to request the HID descriptor. I don't know how your 
VID/PID got into the udev rules file - VID 2341 doesn't show up in the NUT Git 
source tree.

-- 
Charles Lepple
clepple@gmail


_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Reply via email to