On 25 Jul, Charles Lepple wrote: > Even if you can use the start-and-stop pwrstatd trick, all of the > values reported by the usbhid-ups debug messages are in the > vendor-specific 0xFF00 range, and so we would need to create mappings > between them and the NUT variable names. (Note that pwrstatd says your > computer is on utility power, but nut says "OB" - on battery.)
I was just looking through the specs and there isn't a claim that this particular model is USB HID-compliant ... _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
