7 minutes ago, Dwarfboysim said:

Hi,

I opened up a terminal in Unraid and got the following results

for the command: ls /dev/ttyUSB* I got "ls: cannot access '/dev/ttyUSB*': No such file or directory"

for the command: dmesg | grep tty I got "[ 0.288678] printk: legacy console [tty0] enabled"

any clues?

Thanks,

Dwarfboysim

I also tried: lsusb and it gave the below

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 001 Device 002: ID 0d9f:0002 Powercom Co., Ltd Black Knight PRO / WOW Uninterruptible Power Supply (Cypress HID->COM RS232)

Bus 001 Device 003: ID 0781:5567 SanDisk Corp. Cruzer Blade

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Thank you those who developed this Plugin, it works as advertised. Great Work !!!

Not many plugins, Dockers, or ... work without extra effort .....

Have a question ......

My sever has dual AC power supplies, and has two (2) UPS (UPS Model: Back-UPS NS 1500M2), one for each AC power supply. Is this plugin able to support more than one UPS?

If no, could this feature be added to any future development of this plug in?

Thank you !!!

Hi all,

there is a log generated while having power problems/cuts from my UPS and I would need help to understand what this means:

May 7 02:32:56 QNAP usbhid-ups[3710]: ups_status_set: seems that UPS [ups] is in OL+DISCHRG state now. Battery charge is currently 87. Is it calibrating (perhaps you want to set 'onlinedischarge_calibration' option)? Note that some UPS models (e.g. CyberPower UT series) emit OL+DISCHRG when in fact offline/on-battery (perhaps you want to set 'onlinedischarge_onbattery' option)

The UPS is a CP1500EPFCLCD (not UT series).

OL+DISCHRG means what? overload and discharge?

I'm asking because I'm trying to observe nasty power problems on my private source (off-grid-inverter) and have seen this entry in the server.log.

thanks in advance

noraid

Will NUT shutdown docker containers and VMs as part of the regular shutdown?

If not, is NUT Actions required?

[deleted]

Edited May 17May 17 by landS

I got fed up of replacing the sealed lead acid batteries every year and swaped those SLA batteries to Lithium iron phosphate batteries, the batteries do take longer time to charge but the backup has actually doubled, now the only problem is that the runtime and battery charge which my ups apc bg 1500 model reports is designed for lead acid battery so now since I'm using lithium batteries the runtime and battery charge % is wrongly reported so the function of safe shutdown cannot be used as it uses runtime and battery charge to decide when to shutdown. The only parameter which is correctly reported is the voltage so if NUT had an option to trigger voltage based shutdown it would be very helpful like triggering shutdown when voltage drops to 23v as 23v is the cliff point for LFP batteries below which the voltage rapidly falls.

35 minutes ago, drmetro said:

I got fed up of replacing the sealed lead acid batteries every year and swaped those SLA batteries to Lithium iron phosphate batteries, the batteries do take longer time to charge but the backup has actually doubled, now the only problem is that the runtime and battery charge which my ups apc bg 1500 model reports is designed for lead acid battery so now since I'm using lithium batteries the runtime and battery charge % is wrongly reported so the function of safe shutdown cannot be used as it uses runtime and battery charge to decide when to shutdown. The only parameter which is correctly reported is the voltage so if NUT had an option to trigger voltage based shutdown it would be very helpful like triggering shutdown when voltage drops to 23v as 23v is the cliff point for LFP batteries below which the voltage rapidly falls.

I see a other big problem when replacing Lead-Bat. to Li-Bat. for UPS. Keeping them constantly at 100% charging level is realy bad. I would say it is a security risk.

If you go for Li-Bat. then buy a UPS that is build for that.

On 5/15/2026 at 5:12 AM, landS said:

[deleted]

NUT will shutdown your containers and VMs as part of the regular shutdown.

It will not do that just because the system is on battery (prior to initiating shutdown).

If you want to do that you'd have to use the scripting hooks (in GUI configuration editor) or NUT Actions.

On 5/7/2026 at 1:44 AM, oakley4404 said:

Thank you those who developed this Plugin, it works as advertised. Great Work !!!

Not many plugins, Dockers, or ... work without extra effort .....

Have a question ......

My sever has dual AC power supplies, and has two (2) UPS (UPS Model: Back-UPS NS 1500M2), one for each AC power supply. Is this plugin able to support more than one UPS?

If no, could this feature be added to any future development of this plug in?

Thank you !!!

It's not supported in the GUI, but can be done in manual configuration mode.

It's been on the roadmap for a long while, but it's a large effort and not many are asking for it.

On 5/7/2026 at 8:04 AM, NoRaid99 said:

Hi all,

there is a log generated while having power problems/cuts from my UPS and I would need help to understand what this means:

May 7 02:32:56 QNAP usbhid-ups[3710]: ups_status_set: seems that UPS [ups] is in OL+DISCHRG state now. Battery charge is currently 87. Is it calibrating (perhaps you want to set 'onlinedischarge_calibration' option)? Note that some UPS models (e.g. CyberPower UT series) emit OL+DISCHRG when in fact offline/on-battery (perhaps you want to set 'onlinedischarge_onbattery' option)

The UPS is a CP1500EPFCLCD (not UT series).

OL+DISCHRG means what? overload and discharge?

I'm asking because I'm trying to observe nasty power problems on my private source (off-grid-inverter) and have seen this entry in the server.log.

thanks in advance

noraid

OL+DISCHRG usually means on battery or calibrating, some UPS like to expose it like that.

The flags allow NUT to show the UPS as OB (on battery) or CAL (calibrating) instead when in this state.

It ultimately depends on what your UPS is really doing when it's in this state, then you decide on which flag to use.

@Rysz

Okay, thank you for the explanation.

Never have seen this before. Still seems to be a bit strange to me when the UPS reports "OB or CAL" while a power interruption. Who, if not the UPS itself knows what happened?

7 minutes ago, NoRaid99 said:

@Rysz

Okay, thank you for the explanation.

Never have seen this before. Still seems to be a bit strange to me when the UPS reports "OB or CAL" while a power interruption. Who, if not the UPS itself knows what happened?

The UPS does know, it's just that this specific UPS series may report it differently than (most) others so the driver doesn't know what to do. 😉

In any case, if you don't have a power outage at that time - it's calibrating, if you do - it's on battery, and either of the flags tell the driver what's what.

On 5/15/2026 at 1:22 PM, NoRaid99 said:

I see a other big problem when replacing Lead-Bat. to Li-Bat. for UPS. Keeping them constantly at 100% charging level is realy bad. I would say it is a security risk.

If you go for Li-Bat. then buy a UPS that is build for that.

Hi , no the Li-batteries are actually not charged 100% , because the APC ups charger charges only upto 13.6v and than cuts off automatically and Li- batteries need 14.8v to be said as 100% charged the Li batteries are just 85 to 90% charged .

Good point.

And what about the cut off voltage?

Anyway, personally I wouldn't do it.

edit:

-like this they never get balanced!!!

-perhaps the Max. Continuous Discharge Current is not high enought

-perhaps the Recommended charging current is not set to the right value and could be to high

-possibly the lead-bat. gets charged sometimes with more then the 13.6V. Usualy 14.2V would be the voltage to keep lead-bat. at charge level.

Edited May 17May 17 by NoRaid99

4 hours ago, NoRaid99 said:

-like this they never get balanced!!!

They should unless they have a shitty BMS

4 hours ago, NoRaid99 said:

-perhaps the Max. Continuous Discharge Current is not high enought

You need to choose the correct size/rating obviously

4 hours ago, NoRaid99 said:

-perhaps the Recommended charging current is not set to the right value and could be to high

Again check ratings, but lead acid charge from UPSes is way slower than anything Li can handle (usually your UPS will need 12h+ to recharge)

4 hours ago, NoRaid99 said:

-possibly the lead-bat. gets charged sometimes with more then the 13.6V. Usualy 14.2V would be the voltage to keep lead-bat. at charge level.

Still less than LiFe

There are plenty of Li-Fe batteries that are meant to be used as direct replacement for lead acid batteries.

Edited May 17May 17 by Kilrah

22 hours ago, Kilrah said:

They should unless they have a shitty BMS

Don't think so.

If the cells do not get charged up to 100% some times, there will be no satisfactory balancing. At least 3.5-3.55V per cell is needed for this to even start the process.

And it needs as well a minimum amount of Amps to realise a effective balancing. Here I see as well a problem with the low charging current used for the small lead acid bateries used in UPS.

22 hours ago, Kilrah said:

There are plenty of Li-Fe batteries that are meant to be used as direct replacement for lead acid batteries.

That is marketing speak. Lead-acid-bat can never be the the same like LiFe-bat. and only can be replaced with compromises. They are basically different and are coosen by purpose.

It is like running your diesel car with sunflower oil. Just don't do it, if you don't know exactly what you are doing.

Edited May 18May 18 by NoRaid99

2 hours ago, NoRaid99 said:

If the cells do not get charged up to 100% some times, there will be no satisfactory balancing. At least 3.5-3.55V per cell is needed for this to even start the process.

All are depends on system design, there are no correct or wrong. You can design continue balancing also fine. The key point are when balancing start, how much power will waste, that's why you will found balancing start in above conditions for old type balancer.

Balance current are depends on cell voltage different and the max current of the balancer support, unless you have boost circuit to speed up that process.

3 hours ago, NoRaid99 said:

It is like running your diesel car with sunflower oil. Just don't do it, if you don't know exactly what you are doing.

In fact, charging different battery are dealing on current / voltage, that's not proper comparison.

Hi, I've been using the NUT plugin for a while and have noticed that the UPS doesn't turn off after the server shuts down! It's set to do so. Have I missed something? Screenshots attached.

Thanks, Tim

Does your UPS support this switch-off function after auto shutdown the server?

1 minute ago, NoRaid99 said:

Does your UPS support this switch-off function after auto shutdown the server?

Yes, in the manual, it of course refers to Powershute for Windows!

Just curious, I've installed the app, and each morning I'm finding NUT has shutdown my UNRAID Server. I don't see anything that might be causing it, was curious if anyone might have any idea's

I noticed this flag is set to 0 could this be why the UPS doesn't switch off? If so shouldn't the GUI change the flag setting?

driver.flag.allow_killpower

0

@MothyTim In my setting this is at zero as well and shutdown of the UPS is working.

edit:

sorry that I can't really help you.

Maybe there is something to find in the logs, when you cut power and see what gets logged.

Or have a try with driver 2.8.4

edit2:

May 28 16:03:24 QNAP ool www[2808853]: /usr/local/emhttp/plugins/nut-dw/scripts/start
May 28 16:03:25 QNAP rc.nut: Writing NUT configuration...
May 28 16:03:28 QNAP rc.nut: Updating permissions for NUT...
May 28 16:03:28 QNAP rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
May 28 16:03:28 QNAP rc.nut: Disabling the NUT Runtime Statistics Module...
May 28 16:03:29 QNAP rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
May 28 16:03:29 QNAP rc.nut: Network UPS Tools 2.8.4 release - Generic HID driver 0.67
May 28 16:03:29 QNAP rc.nut: USB communication driver (libusb 1.0) 0.50
May 28 16:03:29 QNAP rc.nut: Using subdriver: CyberPower HID 0.84
May 28 16:03:29 QNAP rc.nut: Defaulting 'pollfreq' to 12 for CPS devices
May 28 16:03:29 QNAP usbhid-ups[2812862]: Defaulting 'pollfreq' to 12 for CPS devices
May 28 16:03:29 QNAP usbhid-ups[2812862]: You may want to set 'pollonly' flag on CPS devices
May 28 16:03:29 QNAP rc.nut: You may want to set 'pollonly' flag on CPS devices
May 28 16:03:29 QNAP usbhid-ups[2812862]: Listening on socket /var/run/nut/usbhid-ups-ups
May 28 16:03:29 QNAP rc.nut: Listening on socket /var/run/nut/usbhid-ups-ups
May 28 16:03:29 QNAP usbhid-ups[2812864]: Startup successful
May 28 16:03:30 QNAP rc.nut: Network UPS Tools upsd 2.8.4 release
May 28 16:03:30 QNAP rc.nut: listening on 0.0.0.0 port 3493
May 28 16:03:30 QNAP upsd[2812898]: listening on 0.0.0.0 port 3493
May 28 16:03:30 QNAP upsd[2812898]: Connected to UPS [ups]: usbhid-ups-ups
May 28 16:03:30 QNAP rc.nut: Connected to UPS [ups]: usbhid-ups-ups
May 28 16:03:30 QNAP usbhid-ups[2812864]: sock_connect: enabling asynchronous mode (auto)
May 28 16:03:30 QNAP upsd[2812898]: Found 1 UPS defined in ups.conf
May 28 16:03:30 QNAP rc.nut: Found 1 UPS defined in ups.conf
May 28 16:03:30 QNAP upsd[2812899]: Startup successful
May 28 16:03:30 QNAP rc.nut: Network UPS Tools upsmon 2.8.4 release
May 28 16:03:30 QNAP rc.nut: UPS: [email protected] (primary) (power value 1)
May 28 16:03:30 QNAP rc.nut: Using power down flag file /etc/nut/killpower
May 28 16:03:30 QNAP upsmon[2812902]: Startup successful

Thats the normal log from unraid when starting nut service, maybe you find something missing at yours.

edit3:

WARNING:

In most cases it is sufficient to configure NUT using the GUI for the smoothest possible user experience.

Any changing the configuration directly can have unexpected side effects, use 'Reset Config' in case of problems.

Have you checked the debug file? NUT Debug Package (.zip)

In my setup upsmon.conf.txt shows POWERDOWNFLAG "/etc/nut/killpower"

I guess driver.flag.allow.killpower will be set just in time when needed as variable.

The description for the command: Tell the driver daemon to initiate UPS shutdown; should be unlocked with driver.flag.allow_killpower option or variable setting.

Edited May 28May 28 by NoRaid99

@NoRaid99 Thanks for the info. I'll check through it all and post back!

after i updated to 7.3.1 from 7.2.x NUT stoped working for me from time to time.

my syslog is full of this:

Jun  2 11:00:01 Unraid-1 move: mover: started
Jun  2 11:00:01 Unraid-1 move: mover: finished
Jun  2 11:47:32 Unraid-1 usbhid-ups[12652]: nut_libusb_get_interrupt: Input/Output Error
Jun  2 11:47:34 Unraid-1 usbhid-ups[12652]: Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Jun  2 11:47:51 Unraid-1 upsd[12656]: Data for UPS [UnraidUPS] is stale - check driver
Jun  2 11:47:56 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale
Jun  2 11:47:56 Unraid-1 upsmon[12659]: Communications with UPS [email protected] lost
Jun  2 11:48:01 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale
Jun  2 11:48:06 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale
Jun  2 11:48:11 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale
Jun  2 11:48:16 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale
Jun  2 11:48:21 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale

Syslog and nut debug is attched.

unraid-1-syslog-20260602-1110.zip nut-debug-20260602131115.zip

47 minutes ago, sonic6 said:

after i updated to 7.3.1 from 7.2.x NUT stoped working for me from time to time.

my syslog is full of this:

Jun  2 11:00:01 Unraid-1 move: mover: started
Jun  2 11:00:01 Unraid-1 move: mover: finished
Jun  2 11:47:32 Unraid-1 usbhid-ups[12652]: nut_libusb_get_interrupt: Input/Output Error
Jun  2 11:47:34 Unraid-1 usbhid-ups[12652]: Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Jun  2 11:47:51 Unraid-1 upsd[12656]: Data for UPS [UnraidUPS] is stale - check driver
Jun  2 11:47:56 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale
Jun  2 11:47:56 Unraid-1 upsmon[12659]: Communications with UPS [email protected] lost
Jun  2 11:48:01 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale
Jun  2 11:48:06 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale
Jun  2 11:48:11 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale
Jun  2 11:48:16 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale
Jun  2 11:48:21 Unraid-1 upsmon[12659]: Poll UPS [[email protected]] failed - Data stale

Syslog and nut debug is attched.

unraid-1-syslog-20260602-1110.zip nut-debug-20260602131115.zip

If it's after an update, it's usually kernel (USB driver) related, check this post for information:

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

can anyone help me configure my ups ugreen US3000 ,i have already updated the firmware of it and in the nut config added the lines mentioned in previous posts but it still does not get recognized. please find the debug log and screenshots of my settings in nut below.

nut-debug-20260609082354.zip

Edited June 9Jun 9 by Ruubdoy

In the last few weeks (I think it started since updating to Unraid 7.3.1 from 7.2.4) the connection to the UPS stops working after few days, if I try to stop the NUT service and start it again the following error is shown in the log:

Jun 10 11:30:53 Tower ool www[729600]: /usr/local/emhttp/plugins/nut-dw/scripts/start
Jun 10 11:30:54 Tower rc.nut: Writing NUT configuration...
Jun 10 11:30:56 Tower rc.nut: Updating permissions for NUT...
Jun 10 11:30:56 Tower rc.nut: Adding UDEV lines to rc.6 for NUT...
Jun 10 11:30:56 Tower rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Jun 10 11:30:56 Tower rc.nut: Disabling the NUT Runtime Statistics Module...
Jun 10 11:30:57 Tower rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.5 release
Jun 10 11:30:57 Tower rc.nut: Network UPS Tools 2.8.5 release - Generic HID driver 0.71
Jun 10 11:30:57 Tower rc.nut: USB communication driver (libusb 1.0) 0.53
Jun 10 11:31:03 Tower rc.nut: Driver exited abnormally
Jun 10 11:31:03 Tower kernel: usbhid-ups[736883]: segfault at 7ffc148c9000 ip 0000000000414f3d sp 00007ffc148c4f80 error 4 in usbhid-ups[14f3d,403000+27000] likely on CPU 0 (core 0, socket 0)
Jun 10 11:31:03 Tower kernel: Code: 44 24 38 ff d0 85 c0 0f 8f 06 05 00 00 83 7d 00 01 7e 13 48 8d 35 2b 55 02 00 bf 02 00 00 00 31 c0 e8 07 db 00 00 49 83 c5 04 <45> 8b 65 00 8b 45 00 45 85 e4 78 f0 83 f8 01 0f 8e 3b ff ff ff 31
Jun 10 11:31:04 Tower kernel: usb 3-2: USB disconnect, device number 3
Jun 10 11:31:04 Tower kernel: usb 3-2: new full-speed USB device number 4 using xhci_hcd
Jun 10 11:31:07 Tower kernel: hid-generic 0003:0463:FFFF.0005: hiddev96,hidraw2: USB HID v1.10 Device [EATON 5E] on usb-0000:2c:00.3-2/input0

I never had errors with this UPS after it stops working the only way to fix it is to reboot Unraid, any idea how to debug this issue?