1 hour ago, Rysz said:

This should now be fixed in today's plugin update; I also opened an upstream bug report for the driver:

https://github.com/networkupstools/nut/issues/3075

Thanks for the quick fix. Data is now showing again.

But the runtime is not now calculated I guess because the battery.runtime is not missing.

on previous releases this was needed in the config.

[ups]

driver = nutdrv_qx

port = auto

# If not in manual mode, put any additional settings below this line

default.battery.voltage.high = 40.40

default.battery.voltage.low = 31.20

default.battery.voltage.nominal = 36.0

runtimecal=300,100,600,50

Just now, SimonF said:

Thanks for the quick fix. Data is now showing again.

But the runtime is not now calculated I guess because the battery.runtime is not missing. on previous This was needed in the config.

[ups]

driver = nutdrv_qx

port = auto

# If not in manual mode, put any additional settings below this line

default.battery.voltage.high = 40.40

default.battery.voltage.low = 31.20

default.battery.voltage.nominal = 36.0

runtimecal=300,100,600,50

Yeah, this is due to the driver issue part - I'm hoping we can get this fixed in the backend soon as well.

P.S. Note that you can switch the NUT backend to "previous (2.8.3 stable)" for the previous version, which worked for you.

@SimonF If you are still on the default (2.8.4) backend can you try this fixed up driver?

Stop NUT, then put this file into /usr/libexec/nut (backup old one/overwrite) and chmod +x /usr/libexec/nut/nutdrv_qx.

Then start NUT again and please see if the problem still occurs or if it works now... let me know, thank you. 😀

nutdrv_qx

32 minutes ago, Rysz said:

Yeah, this is due to the driver issue part - I'm hoping we can get this fixed in the backend soon as well.

P.S. Note that you can switch the NUT backend to "previous (2.8.3 stable)" for the previous version, which worked for you.

I have removepkg for 2.8.4 and reinstalled 2.8.3 But can try the fix later.

7 minutes ago, SimonF said:

I have removepkg for 2.8.4 and reinstalled 2.8.3 But can try the fix later.

Thanks a lot, that would be great so we can get this fixed for all future versions also. 😉

14 minutes ago, Rysz said:

Thanks a lot, that would be great so we can get this fixed for all future versions also. 😉

The driver maybe compiled for a newer release. My machine is on 6.12

Sep  6 16:00:20 unraid rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Sep  6 16:00:20 unraid rc.nut: /usr/libexec/nut/nutdrv_qx: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /usr/libexec/nut/nutdrv_qx)

18 minutes ago, SimonF said:

The driver maybe compiled for a newer release. My machine is on 6.12

Sep  6 16:00:20 unraid rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Sep  6 16:00:20 unraid rc.nut: /usr/libexec/nut/nutdrv_qx: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /usr/libexec/nut/nutdrv_qx)

I'm very sorry, I forgot you're on the older OS version - this one should work.

nutdrv_qx

37 minutes ago, Rysz said:

I'm very sorry, I forgot you're on the older OS version - this one should work.

nutdrv_qx

Yes runtime is now being calculated with the patched driver.

Just now, SimonF said:

Yes runtime is now being calculated with the patched driver.

Thanks a lot for testing, I'll get the changes upstreamed so this will be fixed for future NUT versions. In the meantime you can use the older backend where this still worked or patch the file I gave you in manually.

5 minutes ago, Rysz said:

Thanks a lot for testing, I'll get the changes upstreamed so this will be fixed for future NUT versions. In the meantime you can use the older backend where this still worked or patch the file I gave you in manually.

Thanks for the help. This server rarely gets rebooted so will leave patched driver for now.

5 minutes ago, SimonF said:

Thanks for the help. This server rarely gets rebooted so will leave patched driver for now.

If you have time and could check one more thing, just to be 100% sure:
When you disable runtimecal (just comment out with #) can you confirm that battery.runtime is no longer in variable table?

6 minutes ago, Rysz said:

If you have time and could check one more thing, just to be 100% sure:
When you disable runtimecal (just comment out with #) can you confirm that battery.runtime is no longer in variable table?

Yes if I comment out the line runtime does not show in the output.

14 hours ago, SimonF said:

Yes if I comment out the line runtime does not show in the output.

The fix for your driver is now included in the "preview" backend that's part of today's update.

Does NUT for Unraid support multiple UPSes connected to the two redundant power supplies on my R510?

Hello,

I'm seeing a lot of this in the log:

Sep 21 20:43:00	homelabserver	usbhid-ups[7379]:	nut_libusb_get_interrupt: No such device (it may have been disconnected)	Drive Related
Sep 21 20:42:57	homelabserver	usb_manager:	Info: rc.usb_manager Autoconnect No Mapping found CPS_VP1600ELCD /dev/bus/usb/001/026 001 026 port 1-10.2	Drive Related
Sep 21 20:42:57	homelabserver	usb_manager:	Info: rc.usb_manager usb_add CPS_VP1600ELCD /dev/bus/usb/001/026 001 026	Drive Related
Sep 21 20:42:57	homelabserver	kernel:	hid-generic 0003:0764:0501.0016: hiddev97,hidraw4: USB HID v1.10 Device [CPS VP1600ELCD] on usb-0000:00:14.0-10.2/input0	Drive Related
Sep 21 20:42:56	homelabserver	kernel:	usb 1-10.2: new low-speed USB device number 26 using xhci_hcd	Drive Related
Sep 21 20:42:56	homelabserver	usb_manager:	Info: rc.usb_manager Removed 001/025 vm: nostate 001 025	Drive Related
Sep 21 20:42:56	homelabserver	usb_manager:	Info: rc.usb_manager Device Match 001/025 vm: 001 025	Drive Related
Sep 21 20:42:56	homelabserver	usb_manager:	Info: rc.usb_manager usb_remove CPS_VP1600ELCD /dev/bus/usb/001/025 001 025	Drive Related
Sep 21 20:42:56	homelabserver	kernel:	usb 1-10.2: USB disconnect, device number 25	Drive Related
Sep 21 20:42:56	homelabserver	kernel:	usb 1-10-port2: disabled by hub (EMI?), re-enabling...	Drive Related

Any idea if I can fix this?

On 9/21/2025 at 8:53 PM, Soulplayer said:

Hello,

I'm seeing a lot of this in the log:

Sep 21 20:43:00	homelabserver	usbhid-ups[7379]:	nut_libusb_get_interrupt: No such device (it may have been disconnected)	Drive Related
Sep 21 20:42:57	homelabserver	usb_manager:	Info: rc.usb_manager Autoconnect No Mapping found CPS_VP1600ELCD /dev/bus/usb/001/026 001 026 port 1-10.2	Drive Related
Sep 21 20:42:57	homelabserver	usb_manager:	Info: rc.usb_manager usb_add CPS_VP1600ELCD /dev/bus/usb/001/026 001 026	Drive Related
Sep 21 20:42:57	homelabserver	kernel:	hid-generic 0003:0764:0501.0016: hiddev97,hidraw4: USB HID v1.10 Device [CPS VP1600ELCD] on usb-0000:00:14.0-10.2/input0	Drive Related
Sep 21 20:42:56	homelabserver	kernel:	usb 1-10.2: new low-speed USB device number 26 using xhci_hcd	Drive Related
Sep 21 20:42:56	homelabserver	usb_manager:	Info: rc.usb_manager Removed 001/025 vm: nostate 001 025	Drive Related
Sep 21 20:42:56	homelabserver	usb_manager:	Info: rc.usb_manager Device Match 001/025 vm: 001 025	Drive Related
Sep 21 20:42:56	homelabserver	usb_manager:	Info: rc.usb_manager usb_remove CPS_VP1600ELCD /dev/bus/usb/001/025 001 025	Drive Related
Sep 21 20:42:56	homelabserver	kernel:	usb 1-10.2: USB disconnect, device number 25	Drive Related
Sep 21 20:42:56	homelabserver	kernel:	usb 1-10-port2: disabled by hub (EMI?), re-enabling...	Drive Related

Any idea if I can fix this?

This is related to your USB connection (so either the server's or UPS bus or the cable itself).

Easiest would be to try another cable or another USB port (2.0 ports usually are more stable).

Otherwise more tricky to "solve", see here:

https://forums.unraid.net/topic/60217-plugin-nut-v2-network-ups-tools/?&do=findComment&comment=1350269

In general with such things, unless something doesn't work, I'd probably just ignore the log messages myself.

Hello,
I purchased the new USB 120W DC UPS for the Ugreen NAS 4800 Plus. But can't get it to work with the NUT tools plugin.
I have all the cables correctly plugged in, but none of the drivers work for it. I have tried them all, but NUT does not see the UPS and fails to start the service. I contacted Ugreen for drivers, but they said they don't support Unraid, and just gave me drivers for their UGOS. I have no clue how to even use these drivers. Will there be an update for in this plugin for this new UPS? or any help in how I can get the software to see this driver?

Hello,

Currently using UnRAID UPS service 'Settings > UPS Settings' with an APC & CyberPower UPS connected via USB... I cannot be certain if this leverages NUT?

Example:




Recently have been looking into Unifi's UPS offerings, which features the ability to run as a NUT Server

Example:

1. Being the Unifi UPS has the ability to run as a NUT server would that mean that any other device (UnRAID Server, etc.) would become a slave to the UPS/NUT server?

2. Currently considering a replacement UPS device and looking at the Unifi UPS variants -- Curious if this plugin is compatible with the Unifi UPS as it is newer on the market and if this plugin has Unifi UPS driver compatibility?

3. Would the 'Settings > UPS Settings' service be required to be disabled before installing this plugin?

If anyone has any feedback on this inquiry it would be greatly appreciated before dropping the money on Unifi's UPS

Looking forward to the feedback.

Thank you :-)

Edited October 9, 2025Oct 9 by bombz

6 hours ago, bombz said:

I cannot be certain if this leverages NUT?

It doesn't, if you want NUT you don't set up/disable the built-in thing but install the NUT plugin and set it up.

Edited October 9, 2025Oct 9 by Kilrah

3 hours ago, Kilrah said:

It doesn't, if you want NUT you don't set up/disable the built-in thing but install the NUT plugin and set it up.

Appreciate the feedback. I assumed as the Unifi UPS are newer that driver support would be limited. Hope in the future the clients will have driver support to allow these UPS to be leveraged.

In the mean time, may consider setting up all UPS on a NUT server (via Pi) and have NAS 01 and NAS 02 setup as clients to leverage them accordingly as the current setup is one (1) UPS per one (1) NAS... will have to think on some deployment planning.

On 10/9/2025 at 7:22 AM, bombz said:

Appreciate the feedback. I assumed as the Unifi UPS are newer that driver support would be limited. Hope in the future the clients will have driver support to allow these UPS to be leveraged.

In the mean time, may consider setting up all UPS on a NUT server (via Pi) and have NAS 01 and NAS 02 setup as clients to leverage them accordingly as the current setup is one (1) UPS per one (1) NAS... will have to think on some deployment planning.

Just wanted to let you know that I was able to get the Unfi Tower UPS NUT server working with this plugin.

1) The Unifi interface is confusing.
2) I had to do manual setup of the upsmon.conf file.

MONITOR "Unifi_Id"@[Tower_IP_Addess]:[Tower_Port] 1 user userpass slave
Example
MONITOR [email protected]:3493 1 nutuser nutpass slave

Additionally I had to uncheck the box labeled "login credential" in Unifi because even though it says non UI devices will need to log in with a credential, it seems like unchecking the box make it not require a password at all. Additionally I wasn't able to get it to accept my user / password even if I checked the box and set it in this plugin and the unfi the same, probly because of an issue with the upsd.users file on the tower. (Was not able to trouble shoot this further.) So the user ans userpass part of the monitor line might not be required... not sure.

Anyway doing the manual setup + unchecking the box allowed me to get a connection with the remote Unifi Tower UPS established.

Also I'm new to this plugin so I'm not sure how to configure the NUT plugin to shutdown the server when the UPS Tower signals a power loss or whatever... but hey step one solved right?

Edited October 14, 2025Oct 14 by gundamguy

34 minutes ago, gundamguy said:

Just wanted to let you know that I was able to get the Unfi Tower UPS NUT server working with this plugin.

1) The Unifi interface is confusing.
2) I had to do manual setup of the upsmon.conf file.

MONITOR "Unifi_Id"@[Tower_IP_Addess]:[Tower_Port_3493] 1 user userpass slave
Example
MONITOR [email protected]:3493 1 nutuser nutpass slave

Additionally I had to uncheck the box labeled "login credential" in Unifi because even though it says non UI devices will need to log in with a credential, it seems like unchecking the box make it not require a password at all. Additionally I wasn't able to get it to accept my user / password even if I checked the box and set it in this plugin and the unfi the same, probly because of an issue with the upsd.users file on the tower. (Was not able to trouble shoot this further.) So the user ans userpass part of the monitor line might not be required... not sure.

Anyway doing the manual setup + unchecking the box allowed me to get a connection with the remote Unifi Tower UPS established.

This is killer information!!

Appreciate this post. Currently looking at the Unifi UPS, waiting for the rack mount UPS to release. However haven't looked into battery replacements for these device yet (make, model, process, etc.)

Will keep your post noted for when the day and time comes.

Thank you again!

Edit:

As I wasn't sure if Unifi UPS could be ran as a slave (which you confirmed) my thought was to run it stand-alone to only leverage my unifi devices.

Edited October 14, 2025Oct 14 by bombz

Hello,

Just purchased an Eaton 9PX and the driver doesn't seem to load when connected via USB. I've tried different USB ports, cables, motherboards (2nd Unraid server), 2.82 through to preview builds of NUT. Attached debug file.

I wanted to check if there's anything I can or should do to get this working before I get a network card for this unit.

nut-debug-20251019122507.zip

8 hours ago, lowsanity said:

Hello,

Just purchased an Eaton 9PX and the driver doesn't seem to load when connected via USB. I've tried different USB ports, cables, motherboards (2nd Unraid server), 2.82 through to preview builds of NUT. Attached debug file.

I wanted to check if there's anything I can or should do to get this working before I get a network card for this unit.

nut-debug-20251019122507.zip

Thank you for the detailed debug package with debug level increased.

I'm not sure what to make of your issue, although Eaton devices are usually well supported in NUT.

I've logged an upstream issue with the NUT software package developers, and will investigate myself also:
https://github.com/networkupstools/nut/issues/3136

I'll let you know if I have any news, hopefully we'll get this resolved for you, as soon as possible.

On 9/29/2025 at 12:37 AM, Dwsomers said:

Hello,
I purchased the new USB 120W DC UPS for the Ugreen NAS 4800 Plus. But can't get it to work with the NUT tools plugin.
I have all the cables correctly plugged in, but none of the drivers work for it. I have tried them all, but NUT does not see the UPS and fails to start the service. I contacted Ugreen for drivers, but they said they don't support Unraid, and just gave me drivers for their UGOS. I have no clue how to even use these drivers. Will there be an update for in this plugin for this new UPS? or any help in how I can get the software to see this driver?

Appreciate it if developers could respond. Will this hardware be included in an upcoming version update of NUT?
Also, is there any way I can assist with troubleshooting?