[Nut-upsdev] Openups patch proposal

Alphonse alphsteiner at gmail.com
Sat Jul 22 13:13:58 UTC 2017

Charles Lepple a écrit :
> Thanks for the patch. For reference, what does the rest of the "upsc" 
> output look like for this device? 
Here it is:

$ upsc openups2
Init SSL without certificate database
battery.capacity: 100
battery.charge: 100
battery.charge.low: 5
battery.charge.warning: 20
battery.current: 0.000
battery.runtime: 3932100
battery.temperature: 36.79
battery.voltage: 10.13
device.mfr: Mini-Box.Com
device.model: OPEN-UPS2
device.serial: LI-ION
device.type: ups
driver.flag.maxreport: enabled
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.productid: d005
driver.parameter.synchronous: no
driver.parameter.vendorid: 04d8
driver.version: 2.7.4
driver.version.data: openUPS HID 0.4
driver.version.internal: 0.41
input.current: 0.000
input.voltage: 12.08
output.current: 0.000
output.voltage: 12.04
ups.mfr: Mini-Box.Com
ups.model: OPEN-UPS2
ups.productid: d005
ups.serial: LI-ION
ups.status: OL
ups.vendorid: 04d8

Note that there is still a 'libusb_get_string: Invalid argument' message 
into the log, but only when starting or resuming the system.

> I don't think that the firmware supported commands when this sub-driver was written. It is certainly something we can check for, using the "explore" mode mentioned in the driver man page: http://networkupstools.org/docs/man/usbhid-ups.html (please stop after 30-60 seconds, and gzip the output)
I'll try that as soon as possible.
Thanks for your consideration,

More information about the Nut-upsdev mailing list