[Plugin] NUT v2 - Network UPS Tools - Page 79 - Plugin Support

October 26, 2025Oct 26

1 hour ago, JupiterAscending said:
Is this plugin compatible with Unraid 7.2 RC2?
I recently had to update my NAS to 7.2 so I could mount an NTFS drive.
I want to monitor my UPS from this machine, however I can't turn on NUT.
The syslog shows a bunch of errors.
UPS = CyberPower CP1500AVRLCD3 Intelligent LCD UPS System, 1500VA/900W

Please post the NUT debug package that's found in NUT Settings.

Quote

October 26, 2025Oct 26

I can do that. I wanted to confirm it wasn't just a UNRAID vs issue first. I guess your reply kind of answers that question.

Here's the zip. (nut-debug-20251026025244.zip)

nut-debug-20251026025244.zip

Thx

Edited October 26, 2025Oct 26 by JupiterAscending

Quote

October 26, 2025Oct 26

9 minutes ago, JupiterAscending said:
I can do that. I wanted to confirm it wasn't just a UNRAID vs issue first. I guess your reply kind of answers that question.
Here's the zip. (nut-debug-20251026025244.zip)
nut-debug-20251026025244.zip
Thx

I just checked with RC2 and the NUT software itself is fully functional.

Your system log has a lot of kernel USB subsystem errors, unrelated to NUT.

Power saving (e.g. powertop) or a kernel version compatibility problem with your hardware are possible causes.

These kind of problems can however also affect the connectivity of NUT with the UPS, even if not caused by NUT itself.

Quote

October 26, 2025Oct 26

3 minutes ago, Rysz said:
I just checked with RC2 and the NUT software itself is fully functional.
Your system log has a lot of kernel USB subsystem errors, unrelated to NUT.
Power saving (e.g. powertop) or a kernel version compatibility problem with your hardware are possible causes.
These kind of problems can however also affect the connectivity of NUT with the UPS, even if not caused by NUT itself.

Yeah I saw those...I thought maybe they were related to 7.2 RC2....I'm not technical enough to troubleshoot them. I guess I will have to wait until the final 7.2 comes out in the next few days/couple weeks & then see if those errors are still there....I don't have many apps installed (just "myspeed") as this old computer is filled with my old drives & used entirely as a backup NAS (xfs array) for my Windows Plex Server.

As far as data transfer loss, I guess in theory it's not much of an issue as the computer that would be transferring data to & from it would shutdown first (by it's UPS) in the event of a power outage canceling any transfers.....But even an idle computer still shouldn't be unceremoniously cut off from electricity....

ANYWAY, Thanks for looking at my problem for me

Quote

1

October 27, 2025Oct 27

I have an RPi running docker containers of NUT (upshift/nut-upsd:2.8.0) for each UPS I have in my UPS farm. Each UPS is exposed to an individual port for clients to hook on to and monitor - e.g. NAS, HA, etc.

However, I just can't seem to connect my UnRAID NAS (7.1.4) with the 2025.09.07 plugin to any of the NUT instances. my other non UnRAID clients are working and can see battery charge, voltage, etc..

My NUT Settings

(

I get an error when trying to create the NUT debug package :(

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

)

Network UPS Tools Backend: nut-2.8.4-x86_64-1stable.ssl31
Network UPS Tools Backend Switch: default (2.8.4 stable)
Start Network UPS Tools Service: Yes
Enable USB Power Management Override: No
Enable Rule-Based Syslog Filters: No 
Redirection for NUT Service Logs: Default (to Syslog)
Persist Redirected Logs on Reboot: No
Enable Manual Configuration: Yes
UPS Name: nutups

And the only CONF file I've changed is upsmon.conf to

MONITOR [email protected]:34493 1 demonrik nutserver slave
SHUTDOWNCMD "/sbin/poweroff"
POWERDOWNFLAG "/etc/nut/no_killpower"
NOTIFYCMD "/usr/sbin/nut-notify"
NOTIFYFLAG ONBATT SYSLOG+EXEC
NOTIFYFLAG ONLINE SYSLOG+EXEC
NOTIFYFLAG REPLBATT SYSLOG+EXEC

With no DEBUG_MIN in the upsmon.conf it looks like it has trouble accessing.

Oct 27 08:47:41 INX-NAS4 rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Oct 27 08:47:41 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-nut-srvr.pid: No such file or directory
Oct 27 08:47:41 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-auto.pid either: No such file or directory
Oct 27 08:56:16 INX-NAS4 ool www[1823930]: /usr/local/emhttp/plugins/nut-dw/scripts/start
Oct 27 08:56:17 INX-NAS4 rc.nut: Writing NUT configuration...
Oct 27 08:56:18 INX-NAS4 rc.nut: Updating permissions for NUT...
Oct 27 08:56:18 INX-NAS4 rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Oct 27 08:56:18 INX-NAS4 rc.nut: Disabling the NUT Runtime Statistics Module...
Oct 27 08:56:19 INX-NAS4 rc.nut: Network UPS Tools upsmon 2.8.4 release
Oct 27 08:56:19 INX-NAS4 rc.nut: UPS: [email protected]:34493 (secondary) (power value 1)
Oct 27 08:56:19 INX-NAS4 rc.nut: Using power down flag file /etc/nut/no_killpower
Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Startup successful
Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Warning: running as one big root process by request (upsmon -p)
Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Login on UPS [[email protected]:34493] failed - got [ERR ACCESS-DENIED]

setting 'DEBUG_MIN 6' it looks like it has same access issue - however it does appear to read some stats

Oct 27 08:59:00 INX-NAS4 rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Oct 27 08:59:00 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-nut-srvr.pid: No such file or directory
Oct 27 08:59:00 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-auto.pid either: No such file or directory
Oct 27 08:59:03 INX-NAS4 rc.nut: Network UPS Tools upsmon 2.8.4 release
Oct 27 08:59:03 INX-NAS4 rc.nut: UPS: [email protected]:34493 (secondary) (power value 1)
Oct 27 08:59:03 INX-NAS4 rc.nut: Using power down flag file /etc/nut/no_killpower
Oct 27 08:59:03 INX-NAS4 rc.nut:    0.000023#011[D1:1830988] debug level is '6'
Oct 27 08:59:03 INX-NAS4 rc.nut:    0.000028#011[D1:1830988] will use a shutdown command (SHUTDOWNCMD): '/sbin/poweroff'
Oct 27 08:59:03 INX-NAS4 rc.nut:    0.000029#011[D1:1830988] will use custom notification command (NOTIFYCMD): '/usr/sbin/nut-notify'
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Startup successful
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Warning: running as one big root process by request (upsmon -p)
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] Saving PID 1830989 into /var/run/nut/upsmon.pid
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] Trying to connect to UPS [[email protected]:34493]
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Login on UPS [[email protected]:34493] failed - got [ERR ACCESS-DENIED]
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D3:1830989] Current power value: 1
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D3:1830989] Minimum power value: 1
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D4:1830989] Beginning 5-sec delay between main loop cycles
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] 5-sec delay between main loop cycles finished, took 5.000160
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D2:1830989] pollups: [email protected]:34493
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / status
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / buzzword
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / X-buzzword
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D2:1830989] parse_status: [OL DISCHRG]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] parsing: [OL]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] ups_on_line: [email protected]:34493 (first time)
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] parsing: [DISCHRG]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] Known and ignored status token: [DISCHRG]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Handled 2 status tokens
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Current power value: 1
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Minimum power value: 1
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] Beginning 5-sec delay between main loop cycles

i.e. it clearly sees on this UPS (an APC BGM2200B-GR) it's OL and DISCHARGing.

But no update of any details anywhere on UnRAID

I do see the upsnotify failure and also have that backend issue creating the debug package and wonder if it's some permission setting somewhere gone wrong.

I have tried removing and reinstalling the plugin several times on 2 different UnRAID NASes with identical results and am not even sure where to look next.

Any help on getting this working greatly appreciated.

Quote

October 27, 2025Oct 27

7 hours ago, demonrik said:

I have an RPi running docker containers of NUT (upshift/nut-upsd:2.8.0) for each UPS I have in my UPS farm. Each UPS is exposed to an individual port for clients to hook on to and monitor - e.g. NAS, HA, etc.

However, I just can't seem to connect my UnRAID NAS (7.1.4) with the 2025.09.07 plugin to any of the NUT instances. my other non UnRAID clients are working and can see battery charge, voltage, etc..

My NUT Settings

(

I get an error when trying to create the NUT debug package :(

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

)

Network UPS Tools Backend: nut-2.8.4-x86_64-1stable.ssl31
Network UPS Tools Backend Switch: default (2.8.4 stable)
Start Network UPS Tools Service: Yes
Enable USB Power Management Override: No
Enable Rule-Based Syslog Filters: No 
Redirection for NUT Service Logs: Default (to Syslog)
Persist Redirected Logs on Reboot: No
Enable Manual Configuration: Yes
UPS Name: nutups

And the only CONF file I've changed is upsmon.conf to

MONITOR [email protected]:34493 1 demonrik nutserver slave
SHUTDOWNCMD "/sbin/poweroff"
POWERDOWNFLAG "/etc/nut/no_killpower"
NOTIFYCMD "/usr/sbin/nut-notify"
NOTIFYFLAG ONBATT SYSLOG+EXEC
NOTIFYFLAG ONLINE SYSLOG+EXEC
NOTIFYFLAG REPLBATT SYSLOG+EXEC

With no DEBUG_MIN in the upsmon.conf it looks like it has trouble accessing.

Oct 27 08:47:41 INX-NAS4 rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Oct 27 08:47:41 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-nut-srvr.pid: No such file or directory
Oct 27 08:47:41 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-auto.pid either: No such file or directory
Oct 27 08:56:16 INX-NAS4 ool www[1823930]: /usr/local/emhttp/plugins/nut-dw/scripts/start
Oct 27 08:56:17 INX-NAS4 rc.nut: Writing NUT configuration...
Oct 27 08:56:18 INX-NAS4 rc.nut: Updating permissions for NUT...
Oct 27 08:56:18 INX-NAS4 rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Oct 27 08:56:18 INX-NAS4 rc.nut: Disabling the NUT Runtime Statistics Module...
Oct 27 08:56:19 INX-NAS4 rc.nut: Network UPS Tools upsmon 2.8.4 release
Oct 27 08:56:19 INX-NAS4 rc.nut: UPS: [email protected]:34493 (secondary) (power value 1)
Oct 27 08:56:19 INX-NAS4 rc.nut: Using power down flag file /etc/nut/no_killpower
Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Startup successful
Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Warning: running as one big root process by request (upsmon -p)
Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Login on UPS [[email protected]:34493] failed - got [ERR ACCESS-DENIED]

setting 'DEBUG_MIN 6' it looks like it has same access issue - however it does appear to read some stats

Oct 27 08:59:00 INX-NAS4 rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Oct 27 08:59:00 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-nut-srvr.pid: No such file or directory
Oct 27 08:59:00 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-auto.pid either: No such file or directory
Oct 27 08:59:03 INX-NAS4 rc.nut: Network UPS Tools upsmon 2.8.4 release
Oct 27 08:59:03 INX-NAS4 rc.nut: UPS: [email protected]:34493 (secondary) (power value 1)
Oct 27 08:59:03 INX-NAS4 rc.nut: Using power down flag file /etc/nut/no_killpower
Oct 27 08:59:03 INX-NAS4 rc.nut:    0.000023#011[D1:1830988] debug level is '6'
Oct 27 08:59:03 INX-NAS4 rc.nut:    0.000028#011[D1:1830988] will use a shutdown command (SHUTDOWNCMD): '/sbin/poweroff'
Oct 27 08:59:03 INX-NAS4 rc.nut:    0.000029#011[D1:1830988] will use custom notification command (NOTIFYCMD): '/usr/sbin/nut-notify'
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Startup successful
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Warning: running as one big root process by request (upsmon -p)
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] Saving PID 1830989 into /var/run/nut/upsmon.pid
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] Trying to connect to UPS [[email protected]:34493]
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Login on UPS [[email protected]:34493] failed - got [ERR ACCESS-DENIED]
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D3:1830989] Current power value: 1
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D3:1830989] Minimum power value: 1
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D4:1830989] Beginning 5-sec delay between main loop cycles
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] 5-sec delay between main loop cycles finished, took 5.000160
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D2:1830989] pollups: [email protected]:34493
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / status
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / buzzword
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / X-buzzword
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D2:1830989] parse_status: [OL DISCHRG]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] parsing: [OL]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] ups_on_line: [email protected]:34493 (first time)
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] parsing: [DISCHRG]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] Known and ignored status token: [DISCHRG]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Handled 2 status tokens
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Current power value: 1
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Minimum power value: 1
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] Beginning 5-sec delay between main loop cycles

i.e. it clearly sees on this UPS (an APC BGM2200B-GR) it's OL and DISCHARGing.

But no update of any details anywhere on UnRAID

I do see the upsnotify failure and also have that backend issue creating the debug package and wonder if it's some permission setting somewhere gone wrong.

I have tried removing and reinstalling the plugin several times on 2 different UnRAID NASes with identical results and am not even sure where to look next.

Any help on getting this working greatly appreciated.

Please try to spin up all your array disks and try the debug package generation again.

By any chance, is the UPS server you're trying to connect to running on a UniFi UPS?

I'm not sure about your exact setup though, what happens when you run in command-line:

upsc [email protected]:34493

Quote

October 27, 2025Oct 27

8 hours ago, demonrik said:

I have an RPi running docker containers of NUT (upshift/nut-upsd:2.8.0) for each UPS I have in my UPS farm. Each UPS is exposed to an individual port for clients to hook on to and monitor - e.g. NAS, HA, etc.

However, I just can't seem to connect my UnRAID NAS (7.1.4) with the 2025.09.07 plugin to any of the NUT instances. my other non UnRAID clients are working and can see battery charge, voltage, etc..

My NUT Settings

(

I get an error when trying to create the NUT debug package :(

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

)

Network UPS Tools Backend: nut-2.8.4-x86_64-1stable.ssl31
Network UPS Tools Backend Switch: default (2.8.4 stable)
Start Network UPS Tools Service: Yes
Enable USB Power Management Override: No
Enable Rule-Based Syslog Filters: No 
Redirection for NUT Service Logs: Default (to Syslog)
Persist Redirected Logs on Reboot: No
Enable Manual Configuration: Yes
UPS Name: nutups

And the only CONF file I've changed is upsmon.conf to

MONITOR [email protected]:34493 1 demonrik nutserver slave
SHUTDOWNCMD "/sbin/poweroff"
POWERDOWNFLAG "/etc/nut/no_killpower"
NOTIFYCMD "/usr/sbin/nut-notify"
NOTIFYFLAG ONBATT SYSLOG+EXEC
NOTIFYFLAG ONLINE SYSLOG+EXEC
NOTIFYFLAG REPLBATT SYSLOG+EXEC

With no DEBUG_MIN in the upsmon.conf it looks like it has trouble accessing.

Oct 27 08:47:41 INX-NAS4 rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Oct 27 08:47:41 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-nut-srvr.pid: No such file or directory
Oct 27 08:47:41 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-auto.pid either: No such file or directory
Oct 27 08:56:16 INX-NAS4 ool www[1823930]: /usr/local/emhttp/plugins/nut-dw/scripts/start
Oct 27 08:56:17 INX-NAS4 rc.nut: Writing NUT configuration...
Oct 27 08:56:18 INX-NAS4 rc.nut: Updating permissions for NUT...
Oct 27 08:56:18 INX-NAS4 rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Oct 27 08:56:18 INX-NAS4 rc.nut: Disabling the NUT Runtime Statistics Module...
Oct 27 08:56:19 INX-NAS4 rc.nut: Network UPS Tools upsmon 2.8.4 release
Oct 27 08:56:19 INX-NAS4 rc.nut: UPS: [email protected]:34493 (secondary) (power value 1)
Oct 27 08:56:19 INX-NAS4 rc.nut: Using power down flag file /etc/nut/no_killpower
Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Startup successful
Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Warning: running as one big root process by request (upsmon -p)
Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Login on UPS [[email protected]:34493] failed - got [ERR ACCESS-DENIED]

setting 'DEBUG_MIN 6' it looks like it has same access issue - however it does appear to read some stats

Oct 27 08:59:00 INX-NAS4 rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Oct 27 08:59:00 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-nut-srvr.pid: No such file or directory
Oct 27 08:59:00 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-auto.pid either: No such file or directory
Oct 27 08:59:03 INX-NAS4 rc.nut: Network UPS Tools upsmon 2.8.4 release
Oct 27 08:59:03 INX-NAS4 rc.nut: UPS: [email protected]:34493 (secondary) (power value 1)
Oct 27 08:59:03 INX-NAS4 rc.nut: Using power down flag file /etc/nut/no_killpower
Oct 27 08:59:03 INX-NAS4 rc.nut:    0.000023#011[D1:1830988] debug level is '6'
Oct 27 08:59:03 INX-NAS4 rc.nut:    0.000028#011[D1:1830988] will use a shutdown command (SHUTDOWNCMD): '/sbin/poweroff'
Oct 27 08:59:03 INX-NAS4 rc.nut:    0.000029#011[D1:1830988] will use custom notification command (NOTIFYCMD): '/usr/sbin/nut-notify'
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Startup successful
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Warning: running as one big root process by request (upsmon -p)
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] Saving PID 1830989 into /var/run/nut/upsmon.pid
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] Trying to connect to UPS [[email protected]:34493]
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Login on UPS [[email protected]:34493] failed - got [ERR ACCESS-DENIED]
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D3:1830989] Current power value: 1
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D3:1830989] Minimum power value: 1
Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D4:1830989] Beginning 5-sec delay between main loop cycles
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] 5-sec delay between main loop cycles finished, took 5.000160
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D2:1830989] pollups: [email protected]:34493
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / status
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / buzzword
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / X-buzzword
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D2:1830989] parse_status: [OL DISCHRG]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] parsing: [OL]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] ups_on_line: [email protected]:34493 (first time)
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] parsing: [DISCHRG]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] Known and ignored status token: [DISCHRG]
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Handled 2 status tokens
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Current power value: 1
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Minimum power value: 1
Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] Beginning 5-sec delay between main loop cycles

i.e. it clearly sees on this UPS (an APC BGM2200B-GR) it's OL and DISCHARGing.

But no update of any details anywhere on UnRAID

I do see the upsnotify failure and also have that backend issue creating the debug package and wonder if it's some permission setting somewhere gone wrong.

I have tried removing and reinstalling the plugin several times on 2 different UnRAID NASes with identical results and am not even sure where to look next.

Any help on getting this working greatly appreciated.

On another look... is your UPS name wrong? You're monitoring "nut-srvr", but your UPS name is "nutups"?

If you're monitoring "nut-srvr", the UPS name must also be "nut-srvr" - otherwise the GUI won't show the values.

Quote

October 28, 2025Oct 28

Hi,

I have a problem with my UPS and unraid since I updated to version 7. The issue appear when I have a power outage or when I start the server from power off state, when I restart the server all runs fine. When this happen I have the following log:

Oct 27 09:43:48 hpnas rc.nut: Writing NUT configuration...

Oct 27 09:43:49 hpnas rc.nut: Updating permissions for NUT...

Oct 27 09:43:49 hpnas rc.nut: Adding UDEV lines to rc.6 for NUT...

Oct 27 09:43:49 hpnas rc.nut: Adding UPS shutdown lines to rc.6 for NUT...

Oct 27 09:43:50 hpnas rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...

Oct 27 09:43:50 hpnas rc.nut: Disabling the NUT Runtime Statistics Module...

Oct 27 09:43:51 hpnas rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release

Oct 27 09:43:51 hpnas rc.nut: Network UPS Tools 2.8.4 release - Generic HID driver 0.67

Oct 27 09:43:51 hpnas rc.nut: USB communication driver (libusb 1.0) 0.50

Oct 27 09:43:51 hpnas rc.nut: No matching HID UPS found

Oct 27 09:43:51 hpnas rc.nut: Driver failed to start (exit status=1

The config is correct but UPS is not foud. I look in syslog and find this log:

Oct 27 09:42:36 hpnas kernel: usb 3-1.6: new low-speed USB device number 4 using ehci-pci

Oct 27 09:42:36 hpnas kernel: hid-generic 0003:06DA:FFFF.0001: hiddev96,hidraw0: USB HID v1.00 Device [PPC Offline UPS] on usb-0000:00:1a.0-1.6/input0

Oct 27 09:42:36 hpnas kernel: usb 3-1.6: USB disconnect, device number 4

Oct 27 09:42:36 hpnas kernel: usb 3-1.6: new low-speed USB device number 5 using ehci-pci

Oct 27 09:42:36 hpnas kernel: hid-generic 0003:06DA:FFFF.0002: hiddev96,hidraw0: USB HID v1.00 Device [PPC Offline UPS] on usb-0000:00:1a.0-1.6/input0

Oct 27 09:42:36 hpnas kernel: usb 3-1.6: USB disconnect, device number 5

Oct 27 09:42:40 hpnas kernel: usb 3-1.6: new low-speed USB device number 6 using ehci-pci

Oct 27 09:42:40 hpnas kernel: hid-generic 0003:06DA:FFFF.0003: hiddev96,hidraw0: USB HID v1.00 Device [PPC Offline UPS] on usb-0000:00:1a.0-1.6/input0

Oct 27 09:42:54 hpnas kernel: usb 3-1.6: USB disconnect, device number 6

UPS is constantly connecting and disconnecting!! I think this happens since I updated to Unraid 7.0.

Now If I manually start the plugin when UPS is connected it runs as expected

Oct 27 09:52:33 hpnas rc.nut: Writing NUT configuration...

Oct 27 09:52:35 hpnas rc.nut: Updating permissions for NUT...

Oct 27 09:52:35 hpnas rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...

Oct 27 09:52:35 hpnas rc.nut: Disabling the NUT Runtime Statistics Module...

Oct 27 09:52:36 hpnas rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release

Oct 27 09:52:36 hpnas rc.nut: Network UPS Tools 2.8.4 release - Generic HID driver 0.67

Oct 27 09:52:36 hpnas rc.nut: USB communication driver (libusb 1.0) 0.50

Oct 27 09:52:36 hpnas rc.nut: Using subdriver: Phoenixtec/Liebert HID 0.41

Oct 27 09:52:37 hpnas rc.nut: Listening on socket /var/run/nut/usbhid-ups-salicru

Oct 27 09:52:38 hpnas rc.nut: Network UPS Tools upsd 2.8.4 release

Oct 27 09:52:38 hpnas rc.nut: listening on 0.0.0.0 port 3493

Oct 27 09:52:38 hpnas rc.nut: Connected to UPS [salicru]: usbhid-ups-salicru

Oct 27 09:52:38 hpnas rc.nut: Found 1 UPS defined in ups.conf

Oct 27 09:52:38 hpnas rc.nut: Network UPS Tools upsmon 2.8.4 release

Oct 27 09:52:38 hpnas rc.nut: UPS: [email protected] (primary) (power value 1)

Oct 27 09:52:38 hpnas rc.nut: Using power down flag file /etc/nut/killpower

Would be possible to implement some sort of retry drive loading? or waiting until UPS is connected before drive loading?

Thanks in advance

Best Regards

Quote

October 28, 2025Oct 28

6 hours ago, yonesmit said:
Hi,
I have a problem with my UPS and unraid since I updated to version 7. The issue appear when I have a power outage or when I start the server from power off state, when I restart the server all runs fine. When this happen I have the following log:
Oct 27 09:43:48 hpnas rc.nut: Writing NUT configuration...
Oct 27 09:43:49 hpnas rc.nut: Updating permissions for NUT...
Oct 27 09:43:49 hpnas rc.nut: Adding UDEV lines to rc.6 for NUT...
Oct 27 09:43:49 hpnas rc.nut: Adding UPS shutdown lines to rc.6 for NUT...
Oct 27 09:43:50 hpnas rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Oct 27 09:43:50 hpnas rc.nut: Disabling the NUT Runtime Statistics Module...
Oct 27 09:43:51 hpnas rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Oct 27 09:43:51 hpnas rc.nut: Network UPS Tools 2.8.4 release - Generic HID driver 0.67
Oct 27 09:43:51 hpnas rc.nut: USB communication driver (libusb 1.0) 0.50
Oct 27 09:43:51 hpnas rc.nut: No matching HID UPS found
Oct 27 09:43:51 hpnas rc.nut: Driver failed to start (exit status=1
The config is correct but UPS is not foud. I look in syslog and find this log:
Oct 27 09:42:36 hpnas kernel: usb 3-1.6: new low-speed USB device number 4 using ehci-pci
Oct 27 09:42:36 hpnas kernel: hid-generic 0003:06DA:FFFF.0001: hiddev96,hidraw0: USB HID v1.00 Device [PPC Offline UPS] on usb-0000:00:1a.0-1.6/input0
Oct 27 09:42:36 hpnas kernel: usb 3-1.6: USB disconnect, device number 4
Oct 27 09:42:36 hpnas kernel: usb 3-1.6: new low-speed USB device number 5 using ehci-pci
Oct 27 09:42:36 hpnas kernel: hid-generic 0003:06DA:FFFF.0002: hiddev96,hidraw0: USB HID v1.00 Device [PPC Offline UPS] on usb-0000:00:1a.0-1.6/input0
Oct 27 09:42:36 hpnas kernel: usb 3-1.6: USB disconnect, device number 5
Oct 27 09:42:40 hpnas kernel: usb 3-1.6: new low-speed USB device number 6 using ehci-pci
Oct 27 09:42:40 hpnas kernel: hid-generic 0003:06DA:FFFF.0003: hiddev96,hidraw0: USB HID v1.00 Device [PPC Offline UPS] on usb-0000:00:1a.0-1.6/input0
Oct 27 09:42:54 hpnas kernel: usb 3-1.6: USB disconnect, device number 6
UPS is constantly connecting and disconnecting!! I think this happens since I updated to Unraid 7.0.
Now If I manually start the plugin when UPS is connected it runs as expected
Oct 27 09:52:33 hpnas rc.nut: Writing NUT configuration...
Oct 27 09:52:35 hpnas rc.nut: Updating permissions for NUT...
Oct 27 09:52:35 hpnas rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Oct 27 09:52:35 hpnas rc.nut: Disabling the NUT Runtime Statistics Module...
Oct 27 09:52:36 hpnas rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Oct 27 09:52:36 hpnas rc.nut: Network UPS Tools 2.8.4 release - Generic HID driver 0.67
Oct 27 09:52:36 hpnas rc.nut: USB communication driver (libusb 1.0) 0.50
Oct 27 09:52:36 hpnas rc.nut: Using subdriver: Phoenixtec/Liebert HID 0.41
Oct 27 09:52:37 hpnas rc.nut: Listening on socket /var/run/nut/usbhid-ups-salicru
Oct 27 09:52:38 hpnas rc.nut: Network UPS Tools upsd 2.8.4 release
Oct 27 09:52:38 hpnas rc.nut: listening on 0.0.0.0 port 3493
Oct 27 09:52:38 hpnas rc.nut: Connected to UPS [salicru]: usbhid-ups-salicru
Oct 27 09:52:38 hpnas rc.nut: Found 1 UPS defined in ups.conf
Oct 27 09:52:38 hpnas rc.nut: Network UPS Tools upsmon 2.8.4 release
Oct 27 09:52:38 hpnas rc.nut: UPS: [email protected] (primary) (power value 1)
Oct 27 09:52:38 hpnas rc.nut: Using power down flag file /etc/nut/killpower
Would be possible to implement some sort of retry drive loading? or waiting until UPS is connected before drive loading?
Thanks in advance
Best Regards

This is not related to NUT, but rather to the kernel USB subsystem (so the kernel version in combination with your hardware).

There's not much to do on the NUT side, because with such instabilities, even if it retries initial connections, it'll fail again eventually.

I'd try another USB port (maybe a 2.0 one) or worst case downgrade the OS/wait for an Unraid OS version with a newer kernel version...

Quote

October 28, 2025Oct 28

23 hours ago, Rysz said:
On another look... is your UPS name wrong? You're monitoring "nut-srvr", but your UPS name is "nutups"?
If you're monitoring "nut-srvr", the UPS name must also be "nut-srvr" - otherwise the GUI won't show the values.

I had it the same first - then changed it to something else just in case.

Changed it back and no success in updating the GUI

On 10/27/2025 at 5:15 PM, Rysz said:
Please try to spin up all your array disks and try the debug package generation again.
By any chance, is the UPS server you're trying to connect to running on a UniFi UPS?
I'm not sure about your exact setup though, what happens when you run in command-line:
upsc [email protected]:34493

I spun up the disks and get a new details

cp: cannot create regular file '/tmp/nut-debug/unraid-version.txt': No such file or directory
cp: cannot create regular file '/tmp/nut-debug/PLUGIN/nut-dw.plg.txt': No such file or directory

And no - is not a UniFi - is an APC UPS

Running the command line looks good

# upsc [email protected]:34493
battery.charge: 100
battery.charge.low: 66
battery.mfr.date: 1980/01/01
battery.runtime: 1105
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.7
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Back-UPS BGM2200B-GR
device.serial: 9B2428A19235
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: auto
driver.version: 2.8.0
driver.version.data: APC HID 0.98
driver.version.internal: 0.47
driver.version.usb: libusb-1.0.24 (API: 0x1000108)
input.sensitivity: medium
input.transfer.high: 298
input.transfer.low: 176
input.transfer.reason: input voltage out of range
input.voltage: 236.0
input.voltage.nominal: 230
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 481600G5-481700G2
ups.load: 21
ups.mfr: American Power Conversion
ups.mfr.date: 2024/07/16
ups.model: Back-UPS BGM2200B-GR
ups.productid: 0002
ups.realpower.nominal: 1320
ups.serial: 9B2428A19235
ups.status: OL DISCHRG
ups.test.result: Done and passed
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d

Quote

October 28, 2025Oct 28

On 7/19/2025 at 1:16 PM, EricB said:
Thank you so much for your guidance. I'm attaching the LOG file. What's great about sending to file, and not to monitor, is that I do NOT see the blip... at least I don't see it in the Unraid Notification bell. I had something like 300 notifications yesterday :)
Let me know if I can provide anything else to you. Many thanks for your help!nut.log

Hey @EricB, did you ever hear back on this? I just upgraded from an old APC to the Goldenmate 2000VA 2025 Version as well with USB NAS data port for my Unraid Server and networking equipment. I installed the plugin to monitor any power outages but don't see a lot of information...no load information or anything really...All I get is Battery percentage and runtime left with stays at zero...I assume it will calculate runtime when on Battery. Do you get any additional info, and if so, what did you do?

Edited October 28, 2025Oct 28 by TheRandy

Quote

October 29, 2025Oct 29

15 hours ago, demonrik said:

I had it the same first - then changed it to something else just in case.

Changed it back and no success in updating the GUI

I spun up the disks and get a new details

cp: cannot create regular file '/tmp/nut-debug/unraid-version.txt': No such file or directory
cp: cannot create regular file '/tmp/nut-debug/PLUGIN/nut-dw.plg.txt': No such file or directory

And no - is not a UniFi - is an APC UPS

Running the command line looks good

# upsc [email protected]:34493
battery.charge: 100
battery.charge.low: 66
battery.mfr.date: 1980/01/01
battery.runtime: 1105
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 27.7
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Back-UPS BGM2200B-GR
device.serial: 9B2428A19235
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: auto
driver.version: 2.8.0
driver.version.data: APC HID 0.98
driver.version.internal: 0.47
driver.version.usb: libusb-1.0.24 (API: 0x1000108)
input.sensitivity: medium
input.transfer.high: 298
input.transfer.low: 176
input.transfer.reason: input voltage out of range
input.voltage: 236.0
input.voltage.nominal: 230
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: 481600G5-481700G2
ups.load: 21
ups.mfr: American Power Conversion
ups.mfr.date: 2024/07/16
ups.model: Back-UPS BGM2200B-GR
ups.productid: 0002
ups.realpower.nominal: 1320
ups.serial: 9B2428A19235
ups.status: OL DISCHRG
ups.test.result: Done and passed
ups.timer.reboot: 0
ups.timer.shutdown: -1
ups.vendorid: 051d

Thanks for the information, I think I traced this issue to a specific GUI settings problem.

I'll add a custom "Port" setting, as part of the next update to NUT, which should resolve the issue.

The problem is that the GUI assumes the default NUT port at the moment, which the user should be able to change.

Quote

October 29, 2025Oct 29

3 hours ago, Rysz said:
Thanks for the information, I think I traced this issue to a specific GUI settings problem.
I'll add a custom "Port" setting, as part of the next update to NUT, which should resolve the issue.
The problem is that the GUI assumes the default NUT port at the moment, which the user should be able to change.

look forward to the update.

appreciate you looking

Quote

October 29, 2025Oct 29

On 10/28/2025 at 7:02 AM, Rysz said:
This is not related to NUT, but rather to the kernel USB subsystem (so the kernel version in combination with your hardware).
There's not much to do on the NUT side, because with such instabilities, even if it retries initial connections, it'll fail again eventually.
I'd try another USB port (maybe a 2.0 one) or worst case downgrade the OS/wait for an Unraid OS version with a newer kernel version...

I know it's not related to NUT plugin, even not related to NUT. The problem is with the kernel unraid is using, but I was suggesting that may be you could add to plugin some retries when loading the driver fails.... more people can have this issue and will not find a solution.

Meanwhile, on my side, I fixed with a script that retries it.....

Best Regards,

nut-autofix.sh

syslog.log

Edited October 29, 2025Oct 29 by yonesmit

Quote

October 29, 2025Oct 29

Hello @Rysz

It's maybe an early ping but can you take a little look at my request on the previous page ?
I hope I didnt bothered you..

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

Thank you 😌

Edited October 29, 2025Oct 29 by Furlings

Quote

October 31, 2025Oct 31

Not sure if this has already been reported or not. Upgraded to 7.2 today. NUT seems to work fine

but the dashboard tile never loads. It's been like that for about 4 hours now. I have disabled it and re-enabled it without much luck.

Quote

October 31, 2025Oct 31

9 minutes ago, dalben said:
Not sure if this has already been reported or not. Upgraded to 7.2 today. NUT seems to work fine

but the dashboard tile never loads. It's been like that for about 4 hours now. I have disabled it and re-enabled it without much luck.

It works for me:

Please check in your browser console and the PHP Settings (Tools => PHP Settings => View Log) if there's any issues.

Quote

October 31, 2025Oct 31

19 minutes ago, Rysz said:
It works for me:
Please check in your browser console and the PHP Settings (Tools => PHP Settings => View Log) if there's any issues.

OK, looking at those logs I worked out what it is.

Connect to Unraid Web UI with HTTPS and all is good. When I connect with HTTP I get the Please wait message. When I'm at home I normally hit http://servername to reach the Web UI. The Dashboard tile seem to hardcode https://url when trying to pull data rather than use what, which fails when someone is accessing without a cert.

From my console I see the gpustat has the same issue.

Quote

October 31, 2025Oct 31

Connecting to my new Unifi UPS doesn't work:

Oct 31 12:17:42 unraid upsmon[407139]: Poll UPS [[email protected]] failed - Unknown error
Oct 31 12:17:42 unraid upsmon[407139]: Communications with UPS [email protected] lost

NUT Server is working, tested it with https://github.com/nutdotnet/WinNUT-Client/releases/tag/v2.2.8719

my settings:

Any ideas?

Quote

October 31, 2025Oct 31

1 hour ago, dalben said:

OK, looking at those logs I worked out what it is.

Connect to Unraid Web UI with HTTPS and all is good. When I connect with HTTP I get the Please wait message. When I'm at home I normally hit http://servername to reach the Web UI. The Dashboard tile seem to hardcode https://url when trying to pull data rather than use what, which fails when someone is accessing without a cert.

From my console I see the gpustat has the same issue.

The plugin uses relative paths, and I'm also accessing over HTTP (as I'm sure many others do), so I think this is maybe your browser enforcing SSL on these (sub-)requests?

Quote

October 31, 2025Oct 31

2 minutes ago, enJOyIT said:
Connecting to my new Unifi UPS doesn't work:
Oct 31 12:17:42 unraid upsmon[407139]: Poll UPS [[email protected]] failed - Unknown error
Oct 31 12:17:42 unraid upsmon[407139]: Communications with UPS [email protected] lost
NUT Server is working, tested it with https://github.com/nutdotnet/WinNUT-Client/releases/tag/v2.2.8719
my settings:
Any ideas?

Is the server running on a specific port?

Quote

October 31, 2025Oct 31

1 hour ago, Rysz said:
Is the server running on a specific port?

runs on the standard 3493 port

Maybe the plugin uses the wrong authentification mechanism?

The windows NUT tool runs fine and can connect.

Quote

October 31, 2025Oct 31

3 minutes 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.

I just saw this is a UniFi UPS, these currently seem to have a non-compliant implementation of the NUT protocol.

It seems to work for some users without authentication enabled on the NUT server side, so maybe you can try that...

Windows NUT works because it queries a few individual variables, as opposed to our full variable dump.

A compliant NUT server must implement both individual variable queries and full dump queries, theirs doesn't seem to.

Unfortunately this is a problem on the vendor side, so nothing I can do from my point of view.

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

https://community.ui.com/releases/UniFi-UPS-1-4-13/fdd23b70-1191-4bc1-8485-d85c41a3a510

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

https://community.ui.com/questions/UniFi-UPS-sends-incorrect-responses-in-NUT-protocol/7f862573-eda4-4180-a987-0aca1233ee8a#answer/a857cb90-866a-4db0-9f8a-9e1dab1af14a

Quote

1

October 31, 2025Oct 31

ah, ok.

thank you!

Quote

October 31, 2025Oct 31

3 hours ago, Rysz said:
The plugin uses relative paths, and I'm also accessing over HTTP (as I'm sure many others do), so I think this is maybe your browser enforcing SSL on these (sub-)requests?

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.

Quote

[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)