[Plugin] NUT v2 - Network UPS Tools

Please install Network UPS Tools (NUT) by desertwitch from Community Applications. The older plugins (including the one in the first post of this topic) are deprecated/now unsupported.

Please read before installing NUT

Recommended by Rysz

Rysz

January 8, 20242 yr

If you are using "powertop", this is known to cause instabilities with some UPS (changing the auto-hibernation of USB devices). If not, continue reading... USB connectivity problems (data staleness, timeouts, ...) are incredibly hard if not impossible to diagnose remotely. They can stem from a multitude of factors because of the many parts involved in the equation (USB cable, port, bus, driver, implementation, ...). Common reasons have included broken USB cables (could attempt new US

USB connection instabilities, timeouts and staleness

Recommended by Rysz

Rysz

December 5, 20241 yr

That APC BX series is known to suffer from this (what we believe to be) firmware issue and we've put patches in place to suppress this unwanted behaviour on the UPS side. Here's how you can set it up: Go to NUT Settings. Set Network UPS Tools Backend Switch to preview (latest build). Apply settings and either reinstall NUT or reboot the machine. Confirm the Network UPS Tools Backend now has "master" in the name. Using the NUT Configuration Editor (in NUT Setti

APC BX series issues & solution

Recommended by Rysz

October 31, 2025Oct 31

1 minute ago, dalben said:
Dunno then. All I can tell you is that on 7.1.4 (I think) it worked. After the upgrade to 7.2 it didn't.
The console errors show its trying to pull data https://servername and it fails. I edit the command in dev mode to http://servernane and it works. When I go via caddy reverse proxy to the https URL, it works.
Thats about the extent of my technical knowledge.

We'll have to see if more reports surface with users updating to 7.2.

NUT code paths haven't changed and are all relative, so no assumptions about protocol/port are made.

What's more is, it works for me on 7.2. over HTTP also... so perhaps something on your end (browser, proxy...)?

Quote

Replies 2.1k
Views 456.3k
Created 8 yr8 yr
Last Reply 5 hr5 hr

Popular Days

Posted Images

October 31, 2025Oct 31

I'm working on a client side mitigation of the UniFi protocol problems, hopefully I'll have good news with the next update to get these UPS functional for you all.

Quote

October 31, 2025Oct 31

After updating everything was working fine with NUT plugin until I noticed this on the footer.

Before the upgrade to 7.2.0 the footer was exactly that but the NUT data was on the left, not on the right.

Is it possible to put it back where it was before the upgrade?

Regards from Portugal!

Quote

November 1, 2025Nov 1

15 hours ago, Rysz said:
We'll have to see if more reports surface with users updating to 7.2.
NUT code paths haven't changed and are all relative, so no assumptions about protocol/port are made.
What's more is, it works for me on 7.2. over HTTP also... so perhaps something on your end (browser, proxy...)?

I did a bit more digging around and it does seem to be my end. Edge gives me this behaviour. Edge incognito, Chrome and Chrome Incognito display the correct behavior. I'll keep hunting at my end until it's sorted. Just odd it only started happening after the 7.2 upgrade

Quote

November 1, 2025Nov 1

6 hours ago, PetabyteLDA said:
After updating everything was working fine with NUT plugin until I noticed this on the footer.
Before the upgrade to 7.2.0 the footer was exactly that but the NUT data was on the left, not on the right.
Is it possible to put it back where it was before the upgrade?
Regards from Portugal!

Unfortunately not, I also like it better on the left but plugin developers were asked to put it on the right (the other plugin you're having probably wasn't updated for the new OS version yet).

Quote

November 1, 2025Nov 1

On 10/29/2025 at 1:31 PM, demonrik said:
look forward to the update.
appreciate you looking

The latest update allows adding the port to the IP address in GUI settings, please try and report back if it works.

18 hours ago, enJOyIT said:
runs on the standard 3493 port
Maybe the plugin uses the wrong authentification mechanism?
The windows NUT tool runs fine and can connect.

On 10/21/2025 at 2:12 PM, dam_j said:
Hey,
I´m trying to get the new Ubuiqiti Tower UPS connected.
Only configuration it has is enabling the internal NUT-Server and config a user which i have done.
In the NUT Plugin i configure it as slave and give the Ip, user, password.
After i start the plugin i don´t get any errors in the log but i also get no read from the ups.
I can ping the UPS just fine from the unraid server.
LOG says:
Oct 21 14:10:44 TEST rc.nut: Writing NUT configuration...
Oct 21 14:10:45 TEST rc.nut: Updating permissions for NUT...
Oct 21 14:10:45 TEST rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Oct 21 14:10:45 TEST rc.nut: Disabling the NUT Runtime Statistics Module...
Oct 21 14:10:46 TEST rc.nut: Network UPS Tools upsmon 2.8.4 release
Oct 21 14:10:46 TEST rc.nut: UPS: [email protected] (secondary) (power value 1)
Oct 21 14:10:46 TEST rc.nut: Using power down flag file /etc/nut/no_killpower
Oct 21 14:10:46 TEST upsmon[608694]: Startup successful
Oct 21 14:10:46 TEST upsmon[608694]: Warning: running as one big root process by request (upsmon -p)
And thats it. Anything more that i can try?
Thanks in advance

On 10/22/2025 at 10:26 PM, AngryHyena said:
I'm having issues with my UniFi UPS as well. I ran that command and I couldn't get it to connect unless I added the port I used as a socket at the end of the IP, so I'd have to do something like upsc [email protected]:123 otherwise I got a connection refused. It only works if I have the credentials disabled.
Is there a way in the manual config to point to a hostname or at least add the socket on the end of the IP?

I've added a UniFi workaround in the latest update, please try and report back if it works.

If using a custom port - the latest update allows adding the port to the IP address in GUI settings (if not the default of 3493).

Quote

November 1, 2025Nov 1

Recently purchased an Eaton 3S850B 3S Gen2 UPS, and have tried all drivers available in the NUT plugin config, but to no avail.

When trying to start the NUT server:

Nov 1 08:20:53 FWLONNAS01 rc.nut: Writing NUT configuration...

Nov 1 08:20:55 FWLONNAS01 rc.nut: Updating permissions for NUT...

Nov 1 08:20:55 FWLONNAS01 rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...

Nov 1 08:20:55 FWLONNAS01 rc.nut: Disabling the NUT Runtime Statistics Module...

Nov 1 08:20:56 FWLONNAS01 rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release

Nov 1 08:20:56 FWLONNAS01 rc.nut: Network UPS Tools 2.8.4 release - Generic HID driver 0.67

Nov 1 08:20:56 FWLONNAS01 rc.nut: USB communication driver (libusb 1.0) 0.50

Nov 1 08:20:56 FWLONNAS01 rc.nut: No matching HID UPS found

Nov 1 08:20:56 FWLONNAS01 rc.nut: Driver failed to start (exit status=1)

Debug package is unable to be provided:

ERROR: The NUT Debug Package Generation Script has failed - no response from the bash backend.

Quote

November 1, 2025Nov 1

Just now, flashback said:
Recently purchased an Eaton 3S850B 3S Gen2 UPS, and have tried all drivers available in the NUT plugin config, but to no avail.
When trying to start the NUT server:
Nov 1 08:20:53 FWLONNAS01 rc.nut: Writing NUT configuration...
Nov 1 08:20:55 FWLONNAS01 rc.nut: Updating permissions for NUT...
Nov 1 08:20:55 FWLONNAS01 rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Nov 1 08:20:55 FWLONNAS01 rc.nut: Disabling the NUT Runtime Statistics Module...
Nov 1 08:20:56 FWLONNAS01 rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Nov 1 08:20:56 FWLONNAS01 rc.nut: Network UPS Tools 2.8.4 release - Generic HID driver 0.67
Nov 1 08:20:56 FWLONNAS01 rc.nut: USB communication driver (libusb 1.0) 0.50
Nov 1 08:20:56 FWLONNAS01 rc.nut: No matching HID UPS found
Nov 1 08:20:56 FWLONNAS01 rc.nut: Driver failed to start (exit status=1)
Debug package is unable to be provided:
ERROR: The NUT Debug Package Generation Script has failed - no response from the bash backend.

Can you try raising the UPS Driver (not NUT Monitor!) Debug Level to 6 and post the syslog output?

Quote

November 1, 2025Nov 1

2 minutes ago, Rysz said:
Can you try raising the UPS Driver (not NUT Monitor!) Debug Level to 6 and post the syslog output?

Sure!

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.000000 [D1:1845439] debug level is '6'

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.000038 [D5:1845439] send_to_all: SETINFO driver.debug "6"

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.000046 [D5:1845439] send_to_all: SETFLAGS driver.debug RW NUMBER

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.001953 [D1:1845439] Succeeded to become_user(root): now UID=0 GID=0

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.001988 [D1:1845439] Signalling UPS [ups]: driver.exit (quietly, no fuss if no driver is running or responding)

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002007 Can't open /var/run/nut/usbhid-ups-ups: No such file or directory

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002011 [D1:1845439] Request for other driver to exit returned code -1

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002026 [D1:1845439] Socket dialog with the other driver instance (may be absent) failed: No such file or directory

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002039 [D1:1845439] PID file /var/run/nut/usbhid-ups-ups.pid not found; stat() returned -1: No such file or directory

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002073 [D1:1845439] Saving PID 1845439 into /var/run/nut/usbhid-ups-ups.pid

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002118 [D5:1845439] send_to_all: SETINFO device.type "ups"

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002127 [D5:1845439] send_to_all: SETINFO driver.state "init.device"

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002130 [D1:1845439] upsdrv_initups (non-SHUT)...

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002134 [D2:1845439] Initializing an USB-connected UPS with library libusb-1.0.28 (API: 0x0100010A) (NUT subdriver name='USB communication driver (libusb 1.0)' ver='0.50')

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.003483 [D2:1845439] Checking device 1 of 3 (1D6B/0003)

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024415 [D1:1845439] nut_libusb_open: invalid libusb bus number 0

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024711 [D2:1845439] - VendorID: 1d6b

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024721 [D2:1845439] - ProductID: 0003

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024725 [D2:1845439] - Manufacturer: Linux 6.12.24-Unraid xhci-hcd

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024729 [D2:1845439] - Product: xHCI Host Controller

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024732 [D2:1845439] - Serial Number: 0000:00:14.0

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024736 [D2:1845439] - Bus: 002

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024739 [D2:1845439] - Bus Port: unknown

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024743 [D2:1845439] - Device: 001

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024747 [D2:1845439] - Device release number: 0612

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024750 [D2:1845439] Trying to match device

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024758 [D2:1845439] match_function_subdriver (non-SHUT mode): matching a device...

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024794 [D2:1845439] match_function_subdriver (non-SHUT mode): failed to match a subdriver to vendor and/or product ID

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024800 [D2:1845439] Device does not match - skipping

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024987 [D2:1845439] Checking device 2 of 3 (0781/5583)

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026407 [D2:1845439] - VendorID: 0781

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026422 [D2:1845439] - ProductID: 5583

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026426 [D2:1845439] - Manufacturer: USB

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026429 [D2:1845439] - Product: SanDisk 3.2Gen1

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026432 [D2:1845439] - Serial Number: 0101b24fa2eae5d36e6c56ab524c516452170f58879cc6bda7b0381660b92b2df4ee00000000000000000000166bb2aaff8647008355810725b3666a

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026437 [D2:1845439] - Bus: 001

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026440 [D2:1845439] - Bus Port: 003

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026443 [D2:1845439] - Device: 006

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026446 [D2:1845439] - Device release number: 0100

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026448 [D2:1845439] Trying to match device

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026453 [D2:1845439] match_function_subdriver (non-SHUT mode): matching a device...

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026461 [D2:1845439] match_function_subdriver (non-SHUT mode): failed to match a subdriver to vendor and/or product ID

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026464 [D2:1845439] Device does not match - skipping

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026482 [D2:1845439] Checking device 3 of 3 (1D6B/0002)

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026513 [D1:1845439] nut_libusb_open: invalid libusb bus number 0

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026688 [D2:1845439] - VendorID: 1d6b

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026696 [D2:1845439] - ProductID: 0002

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026699 [D2:1845439] - Manufacturer: Linux 6.12.24-Unraid xhci-hcd

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026702 [D2:1845439] - Product: xHCI Host Controller

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026705 [D2:1845439] - Serial Number: 0000:00:14.0

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026708 [D2:1845439] - Bus: 001

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026711 [D2:1845439] - Bus Port: unknown

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026713 [D2:1845439] - Device: 001

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026716 [D2:1845439] - Device release number: 0612

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026719 [D2:1845439] Trying to match device

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026723 [D2:1845439] match_function_subdriver (non-SHUT mode): matching a device...

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026729 [D2:1845439] match_function_subdriver (non-SHUT mode): failed to match a subdriver to vendor and/or product ID

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026732 [D2:1845439] Device does not match - skipping

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026750 [D2:1845439] libusb1: No appropriate HID device found

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026754 No matching HID UPS found

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026767 [D5:1845439] send_to_all: SETINFO driver.state "cleanup.exit"

Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026773 [D1:1845439] upsnotify: failed to notify about state NOTIFY_STATE_STOPPING: no notification tech defined, will not spam more about it

Nov 1 08:30:27 FWLONNAS01 rc.nut: Driver failed to start (exit status=1)

Quote

November 1, 2025Nov 1

1 minute ago, flashback said:
Sure!
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.000000 [D1:1845439] debug level is '6'
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.000038 [D5:1845439] send_to_all: SETINFO driver.debug "6"
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.000046 [D5:1845439] send_to_all: SETFLAGS driver.debug RW NUMBER
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.001953 [D1:1845439] Succeeded to become_user(root): now UID=0 GID=0
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.001988 [D1:1845439] Signalling UPS [ups]: driver.exit (quietly, no fuss if no driver is running or responding)
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002007 Can't open /var/run/nut/usbhid-ups-ups: No such file or directory
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002011 [D1:1845439] Request for other driver to exit returned code -1
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002026 [D1:1845439] Socket dialog with the other driver instance (may be absent) failed: No such file or directory
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002039 [D1:1845439] PID file /var/run/nut/usbhid-ups-ups.pid not found; stat() returned -1: No such file or directory
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002073 [D1:1845439] Saving PID 1845439 into /var/run/nut/usbhid-ups-ups.pid
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002118 [D5:1845439] send_to_all: SETINFO device.type "ups"
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002127 [D5:1845439] send_to_all: SETINFO driver.state "init.device"
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002130 [D1:1845439] upsdrv_initups (non-SHUT)...
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.002134 [D2:1845439] Initializing an USB-connected UPS with library libusb-1.0.28 (API: 0x0100010A) (NUT subdriver name='USB communication driver (libusb 1.0)' ver='0.50')
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.003483 [D2:1845439] Checking device 1 of 3 (1D6B/0003)
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024415 [D1:1845439] nut_libusb_open: invalid libusb bus number 0
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024711 [D2:1845439] - VendorID: 1d6b
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024721 [D2:1845439] - ProductID: 0003
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024725 [D2:1845439] - Manufacturer: Linux 6.12.24-Unraid xhci-hcd
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024729 [D2:1845439] - Product: xHCI Host Controller
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024732 [D2:1845439] - Serial Number: 0000:00:14.0
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024736 [D2:1845439] - Bus: 002
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024739 [D2:1845439] - Bus Port: unknown
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024743 [D2:1845439] - Device: 001
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024747 [D2:1845439] - Device release number: 0612
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024750 [D2:1845439] Trying to match device
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024758 [D2:1845439] match_function_subdriver (non-SHUT mode): matching a device...
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024794 [D2:1845439] match_function_subdriver (non-SHUT mode): failed to match a subdriver to vendor and/or product ID
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024800 [D2:1845439] Device does not match - skipping
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.024987 [D2:1845439] Checking device 2 of 3 (0781/5583)
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026407 [D2:1845439] - VendorID: 0781
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026422 [D2:1845439] - ProductID: 5583
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026426 [D2:1845439] - Manufacturer: USB
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026429 [D2:1845439] - Product: SanDisk 3.2Gen1
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026432 [D2:1845439] - Serial Number: 0101b24fa2eae5d36e6c56ab524c516452170f58879cc6bda7b0381660b92b2df4ee00000000000000000000166bb2aaff8647008355810725b3666a
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026437 [D2:1845439] - Bus: 001
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026440 [D2:1845439] - Bus Port: 003
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026443 [D2:1845439] - Device: 006
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026446 [D2:1845439] - Device release number: 0100
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026448 [D2:1845439] Trying to match device
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026453 [D2:1845439] match_function_subdriver (non-SHUT mode): matching a device...
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026461 [D2:1845439] match_function_subdriver (non-SHUT mode): failed to match a subdriver to vendor and/or product ID
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026464 [D2:1845439] Device does not match - skipping
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026482 [D2:1845439] Checking device 3 of 3 (1D6B/0002)
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026513 [D1:1845439] nut_libusb_open: invalid libusb bus number 0
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026688 [D2:1845439] - VendorID: 1d6b
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026696 [D2:1845439] - ProductID: 0002
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026699 [D2:1845439] - Manufacturer: Linux 6.12.24-Unraid xhci-hcd
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026702 [D2:1845439] - Product: xHCI Host Controller
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026705 [D2:1845439] - Serial Number: 0000:00:14.0
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026708 [D2:1845439] - Bus: 001
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026711 [D2:1845439] - Bus Port: unknown
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026713 [D2:1845439] - Device: 001
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026716 [D2:1845439] - Device release number: 0612
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026719 [D2:1845439] Trying to match device
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026723 [D2:1845439] match_function_subdriver (non-SHUT mode): matching a device...
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026729 [D2:1845439] match_function_subdriver (non-SHUT mode): failed to match a subdriver to vendor and/or product ID
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026732 [D2:1845439] Device does not match - skipping
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026750 [D2:1845439] libusb1: No appropriate HID device found
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026754 No matching HID UPS found
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026767 [D5:1845439] send_to_all: SETINFO driver.state "cleanup.exit"
Nov 1 08:30:27 FWLONNAS01 rc.nut: 0.026773 [D1:1845439] upsnotify: failed to notify about state NOTIFY_STATE_STOPPING: no notification tech defined, will not spam more about it
Nov 1 08:30:27 FWLONNAS01 rc.nut: Driver failed to start (exit status=1)

It doesn't seem to see your UPS at all, what happens when you click here:

Quote

November 1, 2025Nov 1

Just now, Rysz said:
It doesn't seem to see your UPS at all, what happens when you click here:

Interesting.

NUT Scanner is now searching for UPS devices...

#####################################################

NO DEVICES FOUND

Quote

November 1, 2025Nov 1

2 minutes ago, flashback said:
Interesting.

NUT Scanner is now searching for UPS devices...
#####################################################
NO DEVICES FOUND

Can you try on another USB port (2.0 ones usually work better), anything else in logs when you plug in/out the USB cable?

Did you try with another USB cable perhaps?

Quote

November 1, 2025Nov 1

6 minutes ago, Rysz said:
Can you try on another USB port (2.0 ones usually work better), anything else in logs when you plug in/out the USB cable?
Did you try with another USB cable perhaps?

There's only 1 USB A input on the NAS unfortunately, I'd otherwise have to try the USB C port perhaps with an adaptor?

FYI, plugged into my laptop:

Ignore the load, I only just installed it, it's now showing 27W.

Edited November 1, 2025Nov 1 by flashback

Quote

November 1, 2025Nov 1

FYI on my old Synology NAS it detects straight away:

I'll go and grab a USB drive and plug that in and see whether Unraid sees it.

Quote

November 1, 2025Nov 1

Can you try updating to the latest NUT plugin (2025.11.01a) and try generating a debug package in NUT settings for me now?

With the UPS connected please, I hope the generation works for you now (it may take up to 2 minutes, so be patient... 😉)

Quote

November 1, 2025Nov 1

6 minutes ago, Rysz said:
Can you try updating to the latest NUT plugin (2025.11.01a) and try generating a debug package in NUT settings for me now?
With the UPS connected please, I hope the generation works for you now (it may take up to 2 minutes, so be patient... 😉)

Amazing. It's now working! What was the issue?

Proof of life:

Edited November 1, 2025Nov 1 by flashback

Quote

November 1, 2025Nov 1

Just now, flashback said:
Amazing. It's now working! What was the issue?

The UPS is working...? I haven't changed anything in that regard, so maybe just a lucky coincidence.

If the UPS drops or doesn't get recognised in the future, it may be the hardware combination with that kernel version.

Some users had luck getting a cheap USB hub and seeing if that plays better than direct connection of the UPS to the motherboard.

Quote

November 1, 2025Nov 1

2 minutes ago, Rysz said:
The UPS is working...? I haven't changed anything in that regard, so maybe just a lucky coincidence.
If the UPS drops or doesn't get recognised in the future, it may be the hardware combination with that kernel version.
Some users had luck getting a cheap USB hub and seeing if that plays better than direct connection of the UPS to the motherboard.

'tis indeed, how unusual.

Key Value Key Value

battery.charge 100 battery.charge.low 20

battery.runtime 4320 battery.type PbAc

device.mfr EATON device.model Eaton 3S 850

device.serial Blank device.type ups

device.usb.version USB driver.debug 0

driver.flag.allow_killpower 0 driver.name usbhid-ups

Quote

November 1, 2025Nov 1

Just now, flashback said:
'tis indeed, how unusual.
Key Value Key Value
battery.charge 100 battery.charge.low 20
battery.runtime 4320 battery.type PbAc
device.mfr EATON device.model Eaton 3S 850
device.serial Blank device.type ups
device.usb.version USB driver.debug 0
driver.flag.allow_killpower 0 driver.name usbhid-ups

Well, glad it works for you now, some UPS also like to take a bit of time to get recognised...

But Eaton is generally the best (supported) choice for NUT (and UPS too in my personal opinion)...

Feel free to report back if you run into any problems later down the line... 😊

Quote

November 1, 2025Nov 1

49 minutes ago, Rysz said:

The latest update allows adding the port to the IP address in GUI settings, please try and report back if it works.
I've added a UniFi workaround in the latest update, please try and report back if it works.
If using a custom port - the latest update allows adding the port to the IP address in GUI settings (if not the default of 3493).

51 minutes ago, Rysz said:

The latest update allows adding the port to the IP address in GUI settings, please try and report back if it works.
I've added a UniFi workaround in the latest update, please try and report back if it works.
If using a custom port - the latest update allows adding the port to the IP address in GUI settings (if not the default of 3493).

It seems to work now without any problems, it's just not possible to use authentication.

I needed to fill in some "fake" details in NUT, but after that it started to run perfectly fine.

Edited November 1, 2025Nov 1 by Runaljod

Quote

November 1, 2025Nov 1

1 minute ago, Runaljod said:

It seems to work now without any problems, it's just not possible to use authentication.

I needed to fill in some "fake" details in NUT, but after that it started to run perfectly fine.

Glad to hear, can you also take a screenshot of the variable table that's in NUT Settings now?
You can blank out the serial number, I just want to check which variables get exposed now.

Quote

November 1, 2025Nov 1

7 minutes ago, Rysz said:
Well, glad it works for you now, some UPS also like to take a bit of time to get recognised...
But Eaton is generally the best (supported) choice for NUT (and UPS too in my personal opinion)...
Feel free to report back if you run into any problems later down the line... 😊

That would be a long time indeed, as it's been connected for 2 weeks! ;)

I wonder if unplugging/replugging seemed to sort it. Anyway, all good and thanks for the swift help.

Quote

November 1, 2025Nov 1

8 minutes ago, Rysz said:
Glad to hear, can you also take a screenshot of the variable table that's in NUT Settings now?
You can blank out the serial number, I just want to check which variables get exposed now.

Of course!

Quote

November 1, 2025Nov 1

Thank you @Rysz !

It's working for me aswell.

Quote

November 3, 2025Nov 3

Hello,

Sadly even after the update (thanks for that) my Unifi ups still doesn´t work.

Anything else i can try?

Quote

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Followers

Go to topic listing

Replies 2.1k
Views 456.3k
Created 8 yr8 yr
Last Reply 5 hr5 hr

[Plugin] NUT v2 - Network UPS Tools

Featured Replies

Top Posters In This Topic

Popular Days

Most Popular Posts

SimonF

SimonF

Rysz

Posted Images

Join the conversation

Top Posters In This Topic

Popular Days

Most Popular Posts

SimonF

SimonF

Rysz

Posted Images

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)