Re: nut UPS shutdown issue after nut upgrade 2.8.2 -> 2.8.4

On 3/28/26 4:58 PM, Łukasz Michalski wrote:

I think that it is safer to alter nut-driver@valkyrie_ups.service. It is autogenerated by enumerator from /etc/nut/ups.conf entries.

As for pollonly flag, it is an usbhid-ups config flag, so you have to add it to your ups section in /etc/nut/ups.conf.

Thank you will give this a shot if another comm loss and force shutdown occurs. I found the proper syntax that I was scratching my head about. Since it's a single flag, it's = enabled, e.g. pollonly = enabled in my [upsname] section of ups.conf. -- David C. Rankin, J.D.,P.E.