<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On Dec 16, 2018, at 6:07 PM, James <<a href="mailto:bjlockie@lockie.ca" class="">bjlockie@lockie.ca</a>> wrote:<div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class="">Which driver is this?<br class=""></blockquote><br class=""></div></div></blockquote>...<br class=""><blockquote type="cite" class=""><div class=""><div class="">device.mfr: CPS<br class="">device.model: UPS CP850AVRLCD<br class="">device.type: ups<br class="">driver.name: usbhid-ups<br class=""></div></div></blockquote><br class=""></div><div>For a USB HID PDC (Power Device Class) UPS like this, "ups.test.result" comes straight from the spec:</div><div><br class=""></div><div><a href="https://github.com/networkupstools/nut/blob/v2.7.4/drivers/usbhid-ups.c#L383-L392" class="">https://github.com/networkupstools/nut/blob/v2.7.4/drivers/usbhid-ups.c#L383-L392</a></div><div><br class=""></div><div><a href="https://www.usb.org/document-library/power-device-class-document-10" class="">https://www.usb.org/document-library/power-device-class-document-10</a> page 26</div><br class=""><div class="">It is possible to check around for other status bits, but if they are non-standard, mapping them back to useful names might be difficult.</div><div class=""><br class=""></div><div class="">I think it would be useful to have a debug dump from before and after replacing the battery, if you have the time. Basically, you can kill the driver out from under NUT ("killall usbhid-ups" as root), then restart it with "-DDD". If your system uses paths similar to Debian/Ubuntu, it will be something like this:</div><div class=""><br class=""></div><div class=""># /lib/nut/usbhid-ups -a desktop_ups -DDD 2>&1 | tee /tmp/CP850AVRLCD.debug.old-battery.txt</div><div class=""><br class=""></div><div class="">Let it run for a few seconds, and once it starts looping, you can kill it with Ctrl-C. If the log is larger than a few kB, please gzip it before sending.</div><div class=""><br class=""></div><div class="">You can start the driver again with "/lib/nut/usbhid-ups -a desktop_ups", or by restarting the whole NUT service if things are not looking right.</div></body></html>