similar to: Centos 6.1, BNT400AP and immediate shutdown of ups

I have the same issue of incorrect output voltage being reported by usbhid-ups, as run on NAS4Free (FreeBSD). UPS is as shown below. There is a thread on this list from 2014 that has these same issues, apparently never addressed by any of the later usbhid-ups releases. I?m using 2.7.3. The value I am especially concerned with is the output voltage; if ANY thing should be right on the report, it?s

On Oct 11, 2016, at 10:07 PM, Daniel Shields wrote: > > No joy. Reverted. A wrong number for the udev rules file would prevent the driver from starting at all due to permissions errors. It is possible that 52 and 62 are currently in the acceptable range. > > From: Daniel Shields <grungelizard9 at hotmail.com> > Sent: Tuesday, October 11, 2016 9:19 PM > To: nut-upsuser

Package: logcheck Version: 1.2.63 Severity: minor Tags: patch Hi, There was recently a modification to filter acpid stuffs. But there are still things not filtered by logcheck. When I unplugg, then plug back my battery, I get following notifications: System Events =-=-=-=-=-=-= Nov 8 21:41:31 morpork acpid: received event "ac_adapter AC0 00000080 00000000" Nov 8 21:41:31 morpork

Hello, No ttyUSB* device under /dev however the new driver has detected the UPS, the nut services are able to start, just "upsc -l ups" sais unknown error and doesn't return any information. Could be due to the driver unable to detect number of battery packs as reported by the nut-driver.service startup? How can I fix that? root at omv:~# systemctl status nut-driver.service●

Here are a series of my recent changes to NUT. The first few in the set are primarily little fixes and improvements. In among those are a few for .gitignore files which of course you can ignore for SVN, and there's one for a commit to a generated file which of course should not be tracked in any VCS. Then there are a couple or three to do with generating the header files used by