On 11/11/2025 at 10:33 AM, mcreekmore said:

I case anyone else is having trouble with their Unifi UPS, here are my settings

So helpful, thank you! I was trying forever to get login credentials working and the logs reported a successful login, but kept saying "Current power value: 1" and the plugin didn't report successfully finding the UPS in the unraid GUI at all. Glad it's working without login creds! Within unraid, it seems like you can put anything for user/pass, but there does need to be something (cant be blank).

One difference on my end is that I did enable static IP for the UPS instead of DHCP though

I have an issue with NUT and a CP1500PFCLCD UPS.

When power goes out, it correctly detects it and sends an "On Battery" email. Then, when it hits the power threshold, it sends a "UPS System Shutdown" email... and then it seemingly just turns the UPS itself off rather than shutting down Unraid. When I turn everything back on, Unraid reports an unclean shutdown, runs a parity check, etc.

The UPS definitely isn't running out of power before it can shutdown Unraid - I can hit the power button after this whole thing while the power is still out and it will come back on with plenty of power to spare for the lower power items plugged in alongside Unraid.

"Disable UPS Power after Shutdown" is set to "No", so I can't figure out what's going on.

I've attached my diagnostics, but it only has a log since it was rebooted for whatever reason, so here's the log from right before the unclean shutdown:

Nov 13 14:19:34 Tollana upsmon[26481]: UPS [email protected] on battery
Nov 13 14:19:34 Tollana nut-notify[2096]: is now handling ONBATT
Nov 13 14:19:34 Tollana nut-notify[2096]: [ups] UPS is on battery. The system will shutdown when the UPS battery charge reaches 30%.
Nov 13 14:19:34 Tollana nut-notify[2096]: Executing user's hook script for ONBATT (as non-blocking)...
Nov 13 14:19:34 Tollana nut-notify[2096]: Sending OS notifications...
Nov 13 14:19:34 Tollana xnut-notify-hooks.sh[2096]: ONBATT commands are now executing in background...
Nov 13 14:19:34 Tollana sSMTP[2116]: Creating SSL connection to host
Nov 13 14:19:34 Tollana sSMTP[2116]: SSL connection using TLS_AES_256_GCM_SHA384
Nov 13 14:19:37 Tollana sSMTP[2116]: Sent mail for [email redacted] (221 2.0.0 closing connection af79cd13be357-8b2af043045sm186308885a.39 - gsmtp) uid=0 username=root outbytes=771
Nov 13 14:19:37 Tollana nut-notify[2096]: Shutdown criteria are now being monitored...
Nov 13 14:23:29 Tollana usbhid-ups[26446]: nut_libusb_get_report: Input/Output Error
Nov 13 14:23:31 Tollana usbhid-ups[26446]: 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!
Nov 13 14:25:37 Tollana nut-notify[2096]: Shutdown criteria are now met, proceeding with shutdown...
Nov 13 14:25:37 Tollana nut-notify[2096]: [ups] UNRAID is being gracefully shutdown from a UPS power event.
Nov 13 14:25:37 Tollana nut-notify[2096]: Executing user's hook script for ONBATT_SHUTDOWN (as non-blocking)...
Nov 13 14:25:37 Tollana nut-notify[2096]: Sending OS notifications...
Nov 13 14:25:37 Tollana xnut-notify-hooks.sh[2096]: ONBATT_SHUTDOWN commands are now executing in background...
Nov 13 14:25:37 Tollana sSMTP[13075]: Creating SSL connection to host
Nov 13 14:25:37 Tollana sSMTP[13075]: SSL connection using TLS_AES_256_GCM_SHA384
Nov 13 14:25:39 Tollana sSMTP[13075]: Sent mail for [email redacted] (221 2.0.0 closing connection af79cd13be357-8b2aeeb1487sm188836585a.19 - gsmtp) uid=0 username=root outbytes=756
Nov 13 14:25:39 Tollana nut-notify[2096]: Setting FSD (= point of no return)...
Nov 13 14:25:39 Tollana upsmon[26481]: Signal 10: User requested FSD
Nov 13 14:25:39 Tollana upsd[26478]: Client [email protected] set FSD on UPS [ups]
Nov 13 14:25:39 Tollana upsmon[26481]: Executing automatic power-fail shutdown
Nov 13 14:25:39 Tollana nut-notify[2096]: is now exiting from handling ONBATT
Nov 13 14:25:39 Tollana upsmon[26481]: Auto logout and shutdown proceeding

Obviously it's important that Unraid shutdown cleanly, but I'd also like the UPS to stay on for the other devices connected to it to be up as long as possible. Any thoughts?

nut-debug-20251113155602.zip

Edited November 14, 2025Nov 14 by taniith
Remove diagnostics file as issue was resolved.

50 minutes ago, taniith said:

I have an issue with NUT and a CP1500PFCLCD UPS.

When power goes out, it correctly detects it and sends an "On Battery" email. Then, when it hits the power threshold, it sends a "UPS System Shutdown" email... and then it seemingly just turns the UPS itself off rather than shutting down Unraid. When I turn everything back on, Unraid reports an unclean shutdown, runs a parity check, etc.

The UPS definitely isn't running out of power before it can shutdown Unraid - I can hit the power button after this whole thing while the power is still out and it will come back on with plenty of power to spare for the lower power items plugged in alongside Unraid.

"Disable UPS Power after Shutdown" is set to "No", so I can't figure out what's going on.

I've attached my diagnostics, but it only has a log since it was rebooted for whatever reason, so here's the log from right before the unclean shutdown:

Nov 13 14:19:34 Tollana upsmon[26481]: UPS [email protected] on battery
Nov 13 14:19:34 Tollana nut-notify[2096]: is now handling ONBATT
Nov 13 14:19:34 Tollana nut-notify[2096]: [ups] UPS is on battery. The system will shutdown when the UPS battery charge reaches 30%.
Nov 13 14:19:34 Tollana nut-notify[2096]: Executing user's hook script for ONBATT (as non-blocking)...
Nov 13 14:19:34 Tollana nut-notify[2096]: Sending OS notifications...
Nov 13 14:19:34 Tollana xnut-notify-hooks.sh[2096]: ONBATT commands are now executing in background...
Nov 13 14:19:34 Tollana sSMTP[2116]: Creating SSL connection to host
Nov 13 14:19:34 Tollana sSMTP[2116]: SSL connection using TLS_AES_256_GCM_SHA384
Nov 13 14:19:37 Tollana sSMTP[2116]: Sent mail for [email redacted] (221 2.0.0 closing connection af79cd13be357-8b2af043045sm186308885a.39 - gsmtp) uid=0 username=root outbytes=771
Nov 13 14:19:37 Tollana nut-notify[2096]: Shutdown criteria are now being monitored...
Nov 13 14:23:29 Tollana usbhid-ups[26446]: nut_libusb_get_report: Input/Output Error
Nov 13 14:23:31 Tollana usbhid-ups[26446]: 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!
Nov 13 14:25:37 Tollana nut-notify[2096]: Shutdown criteria are now met, proceeding with shutdown...
Nov 13 14:25:37 Tollana nut-notify[2096]: [ups] UNRAID is being gracefully shutdown from a UPS power event.
Nov 13 14:25:37 Tollana nut-notify[2096]: Executing user's hook script for ONBATT_SHUTDOWN (as non-blocking)...
Nov 13 14:25:37 Tollana nut-notify[2096]: Sending OS notifications...
Nov 13 14:25:37 Tollana xnut-notify-hooks.sh[2096]: ONBATT_SHUTDOWN commands are now executing in background...
Nov 13 14:25:37 Tollana sSMTP[13075]: Creating SSL connection to host
Nov 13 14:25:37 Tollana sSMTP[13075]: SSL connection using TLS_AES_256_GCM_SHA384
Nov 13 14:25:39 Tollana sSMTP[13075]: Sent mail for [email redacted] (221 2.0.0 closing connection af79cd13be357-8b2aeeb1487sm188836585a.19 - gsmtp) uid=0 username=root outbytes=756
Nov 13 14:25:39 Tollana nut-notify[2096]: Setting FSD (= point of no return)...
Nov 13 14:25:39 Tollana upsmon[26481]: Signal 10: User requested FSD
Nov 13 14:25:39 Tollana upsd[26478]: Client [email protected] set FSD on UPS [ups]
Nov 13 14:25:39 Tollana upsmon[26481]: Executing automatic power-fail shutdown
Nov 13 14:25:39 Tollana nut-notify[2096]: is now exiting from handling ONBATT
Nov 13 14:25:39 Tollana upsmon[26481]: Auto logout and shutdown proceeding

Obviously it's important that Unraid shutdown cleanly, but I'd also like the UPS to stay on for the other devices connected to it to be up as long as possible. Any thoughts?

nut-debug-20251113155602.zip

I'm pretty sure this is the battery that's no longer able to hold the charge, 30% is quite low. Many older batteries voltage will collapse under load even when showing sufficient charge. You can test this by e.g. connecting a lamp or some other non-critical appliance and see when the UPS really loses power vs. the charge it says. If could also be a low charge threshold that kills the power, if there is such a setting (if the UPS has a screen, check the manual). But I highly suspect this is the battery and Unraid cannot fully shutdown before the voltage collapses.

6 hours ago, Rysz said:

I'm pretty sure this is the battery that's no longer able to hold the charge, 30% is quite low. Many older batteries voltage will collapse under load even when showing sufficient charge. You can test this by e.g. connecting a lamp or some other non-critical appliance and see when the UPS really loses power vs. the charge it says. If could also be a low charge threshold that kills the power, if there is such a setting (if the UPS has a screen, check the manual). But I highly suspect this is the battery and Unraid cannot fully shutdown before the voltage collapses.

Ah, ok that does make sense. Thank you.

So it sounds like in the short term I should increase the threshold to something higher than 30%. Maybe 50-60%. And in the long term either new new UPS or a new battery for this one.

Thanks!

I can confirm that NUT is working perfect with this CyberPower UPS CP1500PFCLCD. So it must be a setting problem.

6 hours ago, taniith said:

So it sounds like in the short term I should increase the threshold to something higher than 30%. Maybe 50-60%. And in the long term either new new UPS or a new battery for this one.

Sometimes better to go with "time on battery". I.e. if the outage lasted more than 30 seconds it's unlikely to come back up, so initiate shutdown.

Yes I agree, "time on battery" is much more reliable.

"runtime left" is very vage because it depends too much to the SOH of the battery.

2 hours ago, Kilrah said:

Sometimes better to go with "time on battery". I.e. if the outage lasted more than 30 seconds it's unlikely to come back up, so initiate shutdown.

I agree with this and it's less reliant on information from the UPS during the outage.

Would anyone have managed to get an APC Smart-UPS X 3000 with an AP9631 management card (latest firmware upon all) working with APC modbus driver? Modbus is enabled on port 502 on the AP9631 however I've been able to get NUTS working with it.

Thanks.

Has anyone gotten Ecoflow power stations to function as a proper UPS in Unraid yet? The comments from earlier in the year had unsuccessful results

Which one? AFAIK they work as such (prefer the actual UPS versions that have faster switching times) but they have no data reporting so can't automate anything

56 minutes ago, Kilrah said:

Which one? AFAIK they work as such (prefer the actual UPS versions that have faster switching times) but they have no data reporting so can't automate anything

The recent ones that advertise 10ms UPS switchover times, like the Delta 3 or River 3 Plus. So they can't automatically shut down a server by sending the right signal via USB?

Update: from what I read, the older Delta 3 doesn't support it but the Delta 3 Plus should support NAS functions, but I don't know if they can work with NUT / Unraid:
"A nice extra on the Delta 3 plus is NAS server support and HID communication functions. ... NAS server support and HID communication functions will prevent data loss when using it with your computer. It will send a prompt to the server when the battery is almost dead to save data before shutting down."

Edited November 22, 2025Nov 22 by shawn

Hi everyone !

Since I didn't have much luck with my Wohrle UPS, I decided to switch :)

I bought an AEG Protect D 1000, but it turns out it uses the same software 😭

It is detected as a Liebert device (06da:0003) using nutdrv_qx.

Currently, I only get the raw voltage (2.32) and the OL status... No battery percentage or runtime/load info :(

Is there any chance of getting this to work properly, or will I have to resign myself to manually forcing parameters to simulate the battery percentage ?

Thanks a lot !

Here's the driver : https://www.generex.de/partners/oem/2/software/upsman/update

nut-debug-20251129155035.zip

Edited November 29, 2025Nov 29 by Furlings

Are there any plans of supporing the new Ubiquiti UPS or is this already available as a custom configuration? When searching the network, it is not found.

2 hours ago, swipbox said:

Are there any plans of supporing the new Ubiquiti UPS or is this already available as a custom configuration? When searching the network, it is not found.

https://forums.unraid.net/topic/60217-plugin-nut-v2-network-ups-tools/page/80/#findComment-1587572

https://forums.unraid.net/topic/60217-plugin-nut-v2-network-ups-tools/page/82/#findComment-1589967

On 12/12/2025 at 4:49 PM, Rysz said:

https://forums.unraid.net/topic/60217-plugin-nut-v2-network-ups-tools/page/80/#findComment-1587572

https://forums.unraid.net/topic/60217-plugin-nut-v2-network-ups-tools/page/82/#findComment-1589967

Thanks. I am able to connect now, but it is not retrieving any informaiton.

 

Only error i get in the log is this:

 

I have changed the ID to match the username, and now i don't get the error anymore. But the Unraid server does still not retrieve any information. Its says retrieving information for a short amount of time, and then returns to the same screen again with no data in the dashboard

Post a screenshot of the UniFi UPS Settings (in UniFi web interface) and the NUT debug package (can be found in NUT Settings in Unraid web interface).

4 minutes ago, Rysz said:

Post a screenshot of the UniFi UPS Settings (in UniFi web interface) and the NUT debug package (can be found in NUT Settings in Unraid web interface).

here you go

Edited December 15, 2025Dec 15 by swipbox

40 minutes ago, swipbox said:

here you go

nut-debug-20251215112659.zip

Please try to set it up exactly as in the screenshot (except for IPs):
https://forums.unraid.net/topic/60217-plugin-nut-v2-network-ups-tools/page/82/#findComment-1589967

You need to disable "login credential" as both screenshots show, this is likely the issue here.

Then for the username and password in Unraid NUT just use "slaveuser" and "12345" or something (some bogus values, but not same as UPS name).

On 11/11/2025 at 4:33 PM, mcreekmore said:

I case anyone else is having trouble with their Unifi UPS, here are my settings

Thanks. Now it works.

I recently purchased a CyberPower UPS (CP1500PFCRM2U) and got it hooked up to one of my Unraid boxes for testing. All seems to work good, except that the UPS powers back on immediately after powering off (post graceful shutdown of the Unraid box) prior to power being restored. Sequence of events:

• Cut power to the circuit the UPS is on

• Unraid NUT is configured to perform shutdown after 1min on battery, this works fine, Unraid gracefully shuts down

• After graceful shut down, NUT is configured to power off the UPS, this works as well. UPS gives a 60sec countdown and shuts down:
  

• Immediately after the UPS turns off, it goes into start up mode with another 60sec count down, then turns on as if power was restored (it was not):
  

Feels like I'm missing a setting somewhere. Anyone have any suggestions?

Current NUT config:

Edited January 3Jan 3 by 6stringdesigns

After more digging through the NUT repo, seems this is a CyberPower specific issue, particularly with the ups.delay.start default value in the driver config. Default value is 60 and anything greater than zero seems to cause this issue. To resolve, in the plugin's config, set Enable Manual Configuration to for UPS Driver, then add a new line with ondelay = 0. Save the config then restart NUT. UPS will then behave correctly after it's turned off: will only turn back on after power is restored.

Ref: https://github.com/networkupstools/nut/issues/578

Edited January 7Jan 7 by 6stringdesigns

since a few days I see every day messages on my unraid-server like this:

UPS Status: 14-01-2026 08:15

Notice [QNAP] NUT: [[email protected]] UPS On Line
UPS is online, any planned shutdowns were cancelled.

it is a single message and there was no power cut or interrupt before to cancell any started automations.

how can I find out, what the cause for this was, if it is a problem with nuts?

@Rysz btw in settings for the "UPS Name", the Unraid App Config UI wont let us use underscores even though the NUT server settings will. Workaround is to rename the server of course but that sucks :(

I just noticed something recently but I did not have time to document it with logs and I will have to wait for a power outage to happen again in order to re-create this scenario:

When a power outage occurs and NUT sends the shutdown signal to the server, if the power suddenly comes back, it does not go through with the shut down and aborts it.

The problem if it happens midway is that you will end up with a server that cancelled the shutdown operation, has drives that are spun down and others not, same for the containers.

It would be nicer if when the shut down signal is sent by the plugin during a power outage, it would go through completely even if the power comes back during the procedure (happens a lot for regions with small outages) and leave it to the user.

That way we could avoid completely having a 'half running server' that stopped it's shutdown process mid procedure and could cause other problems.

Another issue I always had is also that the signal is never sent to my windows machine through WinNUT even if it says that I am connected and everything is fine and dandy but I guess that's another story for another day.

Thanks in advance if someone has any clue.