On Jun 19, 2019, at 4:16 PM, David Zomaya wrote:
>
>> “I think a range of IDs (even with a few exceptions for the older units)
>> would be sufficient. The ideal scenario is that the range is somewhat
>> future-proof, so a version of NUT from this year can properly identify next
>> year's UPS. If not, we still have manual ways for users to add their
>> idProduct to ups.conf and the udev files, but as you can imagine, that is
>> frustrating for a new user.”
>
> Almost everything we make now is PDC compliant, so we should at least be able
> to do this. We’re looking into something easy to identify in the output of
> lsusb –v though since that could help with legacy support.
>
As you probably saw with lsusb, some of the output is not shown when not
running as root (it does not look up descriptors, for instance, including
string descriptor). One value that should always be available is
"wDescriptorLength". PDC-compliant UPSes need several hundred bytes in the HID
descriptor, whereas the proprietary protocols are just describing an 8-byte
buffer (or similar).
(I'm still noodling over the 42-usb-hd-pm.rules file - not sure why the
stop/start cycle is necessary, because the logs indicated that the driver is
reconnecting.)
_______________________________________________
Nut-upsdev mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
