Hello, I have an openups2 ups. It works very well with nut, except two things: 1) It keeps sending a 'libusb_get_string: invalid argument' message to the log; 2) It does not report any command. Following http://nut-upsdev.alioth.debian.narkive.com/bmJyFFkO/libusb-get-string-invalid-argument, I was able to fix the error message using the attached patch. I do not know how ot fix the second point, but it is not really important (it could be convenient). Regards, Alphonse. -------------- next part -------------- A non-text attachment was scrubbed... Name: nut-openups.patch Type: text/x-patch Size: 919 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20170721/259cbb5a/attachment.bin>
On Jul 21, 2017, at 3:21 PM, Alphonse <alphsteiner at gmail.com> wrote:> > Hello, > I have an openups2 ups. It works very well with nut, except two things: > 1) It keeps sending a 'libusb_get_string: invalid argument' message to the log; > 2) It does not report any command. > > Following http://nut-upsdev.alioth.debian.narkive.com/bmJyFFkO/libusb-get-string-invalid-argument, I was able to fix the error message using the attached patch.Thanks for the patch. For reference, what does the rest of the "upsc" output look like for this device?> I do not know how ot fix the second point, but it is not really important (it could be convenient).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)
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.mfr.date: battery.runtime: 3932100 battery.temperature: 36.79 battery.type: 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, Alphonse.
>> 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)This is weird (for me): I have added the 'explore' option into the ups configuration, and restarted the driver, but now it tells that the device is offline! It is back to normal without this option. I have attached the requested log. -------------- next part -------------- A non-text attachment was scrubbed... Name: usbhid-ups-openups2.log.gz Type: application/gzip Size: 2980 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20170722/23c4178e/attachment.bin>