Request to support my ups device us3000

[S_R]

UPS is not powering off on command

Is this an endless loop that runs until /etc/killpower exists, executing upsdrvctl shutdown every second? Is this the alternate shutdown command in the ups config? Should I be able to simulate /lib/nut/usbhid-ups -a ups -k via command line? That doesn’t seem to work, coming back with the Can't claim USB device [051d:0002]@0/0: Entity not found error.

I currently use docker nut compatible with compatible use. It can shut down, but I can’t realise UPS shutdown. Because the system shuts down, the docker container stops and can’t realise the shutdown of nps itself.

nut-docker.zip

[S_R]

The built-in version 2.8.0 is too low. Request an update.

[squirrel627]

@S_R There’s a recently opened forum thread to request an update to NUT. You can vote on it if it’s important to you. Everyone gets a certain amount of votes.

Update NUT to the latest version

Problem/Justification Some popular APC UPS models throw bogus warnings with the current NUT version (2.8.0). I can’t include links, but a discussion and detailed explanation of the problem can be found at Network UPS Tools’ “nut” Github repo, under the issue #2347. A fix was shipped in NUT 2.8.3 Impact Wrong UPS warnings will no longer appear Please update the NUT version to 2.8.3 or later in the next release of TrueNAS Scale to fix this issue. The UPS models affected (APC Back-UPS BXxxxxM…

[JohnEL]

I have the same problem

[LarsR]

The nut version only gets updated when the Debian base gets updated. Even truenas 26 only updates nut to 2.8.1… if you need even newer versions you may have to wait over a year…

[pmh]

FreeBSD has 2.8.5