2 hours ago, SBlack08 said:

Hey everyone, I recently had to buy a new UPS. I decided on an "APC Back UPS BX – BX1200MI-GR."

Can anyone tell me why I keep getting these alerts? I didn't have that with my Green Cell UPS...

Thanks

nut-ups.dev nut-debug-20250816133125.zip

It's a known firmware issue with that series, please check this post for how to fix it:

1 hour ago, Rysz said:

It's a known firmware issue with that series, please check this post for how to fix it:

ah okay i have changed to preview build, but the changes in ups.conf aren't saved. I'll wait a night and see if the alerts continue.

2 hours ago, SBlack08 said:

ah okay i have changed to preview build, but the changes in ups.conf aren't saved. I'll wait a night and see if the alerts continue.

You need to put the changes on line 8 or later, they will persist if you follow the guide to the point.

Also you need to use the NUT Configuration Editor in NUT Settings (Web GUI) otherwise it won't work.

@Rysz Thanks for carrying Nut forward, it is an excellent UPS tool and it's hard to think of Unraid without it, so thank you.

I had a question I wanted to run by you, and it may just be noise in the logs... but something that has always irk'd me is whenever I update the plugin I see the verbose log as the update happens in Unraid, and I always see this:

Executing hook script: pre_plugin_checks
Checking for other installed NUT versions...
Making sure all existing NUT services are stopped (before install/upgrade)...
WARNING:
WARNING: The NUT installation script was not able to stop all NUT services gracefully.
WARNING: IN CASE OF PROBLEMS, please REBOOT YOUR SYSTEM to complete any upgrades.
WARNING:

I took a look at the code you're running on shutdown prior to update:

echo "Making sure all existing NUT services are stopped (before install/upgrade)..."
if [ -x /etc/rc.d/rc.nut ]; then
    if ! /etc/rc.d/rc.nut stop >/dev/null 2>&1; then
        echo "WARNING:"
        echo "WARNING: The NUT installation script was not able to stop all NUT services gracefully."
        echo "WARNING: IN CASE OF PROBLEMS, please REBOOT YOUR SYSTEM to complete any upgrades."
        echo "WARNING:"
    fi
    killall nut-poller >/dev/null 2>&1

So you're checking if /etc/rc.d/rc.nut exists and if it does then you run /etc/rc.d/rc/nut stop and check to see if it's return code $1, got it.

So on my system when I manually stop Nut, I get this:

root@TheArk:~# /etc/rc.d/rc.nut stop
Writing NUT configuration...
Updating permissions for NUT...
Checking if the NUT Runtime Statistics Module should be enabled...
Enabling the NUT Runtime Statistics Module...
Stopping the NUT services... 
Network UPS Tools upsmon 2.8.4 release
Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Can't open /var/run/nut/snmp-ups-CyberPower.pid: No such file or directory
Can't open /var/run/nut/snmp-ups-auto.pid either: No such file or directory

And because of the two lines at the end I end with a return code 1, not 0 even though Nut has stopped.

So I decided to look a little more this morning. Overall, I have a Cyberpower UPS that I use an RM Card to connect to, so Unraid is a slave connection to the RM Card over the network. I made sure this morning that the driver being used is snmp-ups (was usbhid-ups prior) though I think the driver isn't really at fault here.

If I look inside /var/run/nut when Nut is running, all I have is upsmon.pid. Is there a way to suppress these warnings/errors on shutdown so I get a clean return code $0?

Edited August 21, 2025Aug 21 by cybrnook

53 minutes ago, cybrnook said:

@Rysz Thanks for carrying Nut forward, it is an excellent UPS tool and it's hard to think of Unraid without it, so thank you.

I had a question I wanted to run by you, and it may just be noise in the logs... but something that has always irk'd me is whenever I update the plugin I see the verbose log as the update happens in Unraid, and I always see this:

Executing hook script: pre_plugin_checks
Checking for other installed NUT versions...
Making sure all existing NUT services are stopped (before install/upgrade)...
WARNING:
WARNING: The NUT installation script was not able to stop all NUT services gracefully.
WARNING: IN CASE OF PROBLEMS, please REBOOT YOUR SYSTEM to complete any upgrades.
WARNING:

I took a look at the code you're running on shutdown prior to update:

echo "Making sure all existing NUT services are stopped (before install/upgrade)..."if [ -x /etc/rc.d/rc.nut ]; then
    if ! /etc/rc.d/rc.nut stop >/dev/null 2>&1; then
        echo "WARNING:"
        echo "WARNING: The NUT installation script was not able to stop all NUT services gracefully."
        echo "WARNING: IN CASE OF PROBLEMS, please REBOOT YOUR SYSTEM to complete any upgrades."
        echo "WARNING:"
    fi
    killall nut-poller >/dev/null 2>&1

So you're checking if /etc/rc.d/rc.nut exists and if it does then you run /etc/rc.d/rc/nut stop and check to see if it's return code $1, got it.

So on my system when I manually stop Nut, I get this:

root@TheArk:~# /etc/rc.d/rc.nut stop
Writing NUT configuration...
Updating permissions for NUT...
Checking if the NUT Runtime Statistics Module should be enabled...
Enabling the NUT Runtime Statistics Module...
Stopping the NUT services... 
Network UPS Tools upsmon 2.8.4 release
Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Can't open /var/run/nut/snmp-ups-CyberPower.pid: No such file or directory
Can't open /var/run/nut/snmp-ups-auto.pid either: No such file or directory

And because of the two lines at the end I end with a return code 1, not 0 even though Nut has stopped.

So I decided to look a little more this morning. Overall, I have a Cyberpower UPS that I use an RM Card to connect to, so Unraid is a slave connection to the RM Card over the network. I made sure this morning that the driver being used is snmp-ups (was usbhid-ups prior) though I think the driver isn't really at fault here.

If I look inside /var/run/nut when Nut is running, all I have is upsmon.pid. Is there a way to suppress these warnings/errors on shutdown so I get a clean return code $0?

Thanks for pointing this out — your observations are correct. The rc.d script is fairly old and generic, so the stop command attempts to stop everything it knows about. As a result, it tries to shut down all parts of the NUT ecosystem, even though in a slave mode setup there will never be any upsd or driver instances running. This leads to misleading “failure” messages when it attempts to stop processes that were never started. I’ll adjust this in upcoming updates to suppress these unnecessary warnings in such cases, while still attempting to stop everything to account for broken configuration states.

On 8/21/2025 at 4:46 PM, cybrnook said:

@Rysz Thanks for carrying Nut forward, it is an excellent UPS tool and it's hard to think of Unraid without it, so thank you.

I had a question I wanted to run by you, and it may just be noise in the logs... but something that has always irk'd me is whenever I update the plugin I see the verbose log as the update happens in Unraid, and I always see this:

Executing hook script: pre_plugin_checks
Checking for other installed NUT versions...
Making sure all existing NUT services are stopped (before install/upgrade)...
WARNING:
WARNING: The NUT installation script was not able to stop all NUT services gracefully.
WARNING: IN CASE OF PROBLEMS, please REBOOT YOUR SYSTEM to complete any upgrades.
WARNING:

I took a look at the code you're running on shutdown prior to update:

echo "Making sure all existing NUT services are stopped (before install/upgrade)..."if [ -x /etc/rc.d/rc.nut ]; then
    if ! /etc/rc.d/rc.nut stop >/dev/null 2>&1; then
        echo "WARNING:"
        echo "WARNING: The NUT installation script was not able to stop all NUT services gracefully."
        echo "WARNING: IN CASE OF PROBLEMS, please REBOOT YOUR SYSTEM to complete any upgrades."
        echo "WARNING:"
    fi
    killall nut-poller >/dev/null 2>&1

So you're checking if /etc/rc.d/rc.nut exists and if it does then you run /etc/rc.d/rc/nut stop and check to see if it's return code $1, got it.

So on my system when I manually stop Nut, I get this:

root@TheArk:~# /etc/rc.d/rc.nut stop
Writing NUT configuration...
Updating permissions for NUT...
Checking if the NUT Runtime Statistics Module should be enabled...
Enabling the NUT Runtime Statistics Module...
Stopping the NUT services... 
Network UPS Tools upsmon 2.8.4 release
Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release
Can't open /var/run/nut/snmp-ups-CyberPower.pid: No such file or directory
Can't open /var/run/nut/snmp-ups-auto.pid either: No such file or directory

And because of the two lines at the end I end with a return code 1, not 0 even though Nut has stopped.

So I decided to look a little more this morning. Overall, I have a Cyberpower UPS that I use an RM Card to connect to, so Unraid is a slave connection to the RM Card over the network. I made sure this morning that the driver being used is snmp-ups (was usbhid-ups prior) though I think the driver isn't really at fault here.

If I look inside /var/run/nut when Nut is running, all I have is upsmon.pid. Is there a way to suppress these warnings/errors on shutdown so I get a clean return code $0?

This is now fixed with the next update and you should see its effects after that (so the update after the next update).

The reason you won't see it with this (next) update is because the rc.d script needs to update with the new changes first.

Here's how I addressed this in the end, if you're curious: https://github.com/desertwitch/NUT-unRAID/commit/ef2f38f

Using priview 2.8.4

Have strange issue, now was power off our area, so waited 5 min for shutdown, but this was happened and about almost 10min was message sended to my main pc by WinNUT-Client (85% for ups battery).

But have 5 min on battey in settings and this was working befor.

23 minutes ago, Masterwishx said:

Using priview 2.8.4

Have strange issue, now was power off our area, so waited 5 min for shutdown, but this was happened and about almost 10min was message sended to my main pc by WinNUT-Client (85% for ups battery).

But have 5 min on battey in settings and this was working befor.

Nothing was changed with the shutdown logic in the plugin, is there anything in the logs?

38 minutes ago, Rysz said:

there anything in the logs?

I will check when power will be on again :)

3 hours ago, Rysz said:

is there anything in the logs?

it seems should work fine but something happened in the way and took more that 300sec ?

Also got message from WinNUT Client about 85% battery instead of 5min that was usual before, seems becouse missed on time shutdown...

Aug 26 20:17:01 Myserver upsmon[9557]: UPS [email protected] on battery
Aug 26 20:17:01 Myserver xnut-notify-hooks.sh: ONBATT commands are now executing in background...
Aug 26 20:17:01 Myserver nut-notify: [Eaton9E2000i] UPS is on battery. The system will shutdown in 300 seconds.
Aug 26 20:23:06 Myserver xnut-notify-hooks.sh: ONBATT_SHUTDOWN commands are now executing in background...
Aug 26 20:23:06 Myserver nut-notify: [Eaton9E2000i] UNRAID is being gracefully shutdown from a UPS power event.
Aug 26 20:24:14 Myserver upsmon[9557]: Signal 10: User requested FSD
Aug 26 20:24:14 Myserver upsd[9554]: Client [email protected] set FSD on UPS [Eaton9E2000i]
Aug 26 20:24:30 Myserver upsmon[9557]: Host sync timer expired, forcing shutdown
Aug 26 20:24:30 Myserver upsmon[9557]: Executing automatic power-fail shutdown
Aug 26 20:24:30 Myserver upsmon[9557]: Auto logout and shutdown proceeding
Aug 26 20:24:38 Myserver rc.nut: Backing up last 200KB of NUT service logs to USB...

Edited August 26, 2025Aug 26 by Masterwishx

On 8/25/2025 at 9:11 AM, Rysz said:

This is now fixed with the next update and you should see its effects after that (so the update after the next update).

The reason you won't see it with this (next) update is because the rc.d script needs to update with the new changes first.

Here's how I addressed this in the end, if you're curious: https://github.com/desertwitch/NUT-unRAID/commit/ef2f38f

Thanks for this. At first I was sad as you are already stating, I saw the error message again during upgrade. But then it clicked that it was still using the older logic one more time..... and I assumed that NEXT update should be clean. Thanks for driving that point home.

11 hours ago, Masterwishx said:

it seems should work fine but something happened in the way and took more that 300sec ?

Also got message from WinNUT Client about 85% battery instead of 5min that was usual before, seems becouse missed on time shutdown...

Aug 26 20:17:01 Myserver upsmon[9557]: UPS [email protected] on battery
Aug 26 20:17:01 Myserver xnut-notify-hooks.sh: ONBATT commands are now executing in background...
Aug 26 20:17:01 Myserver nut-notify: [Eaton9E2000i] UPS is on battery. The system will shutdown in 300 seconds.
Aug 26 20:23:06 Myserver xnut-notify-hooks.sh: ONBATT_SHUTDOWN commands are now executing in background...
Aug 26 20:23:06 Myserver nut-notify: [Eaton9E2000i] UNRAID is being gracefully shutdown from a UPS power event.
Aug 26 20:24:14 Myserver upsmon[9557]: Signal 10: User requested FSD
Aug 26 20:24:14 Myserver upsd[9554]: Client [email protected] set FSD on UPS [Eaton9E2000i]
Aug 26 20:24:30 Myserver upsmon[9557]: Host sync timer expired, forcing shutdown
Aug 26 20:24:30 Myserver upsmon[9557]: Executing automatic power-fail shutdown
Aug 26 20:24:30 Myserver upsmon[9557]: Auto logout and shutdown proceeding
Aug 26 20:24:38 Myserver rc.nut: Backing up last 200KB of NUT service logs to USB...

It does look like everything worked, as far as the shutdown sequence is concerned.

Does your system have little CPU or maybe it was under extreme resource pressure when this happened?

Because it's weird it took more than a minute longer to start shutdown (6m) and then another full minute to set FSD (7m).

If you had even more delay after FSD (after the last log line) maybe the array took long to stop due to running services (resource pressure)?

2 hours ago, Rysz said:

It does look like everything worked, as far as the shutdown sequence is concerned.

Does your system have little CPU or maybe it was under extreme resource pressure when this happened?

Because it's weird it took more than a minute longer to start shutdown (6m) and then another full minute to set FSD (7m).

If you had even more delay after FSi5 14D (after the last log line) maybe the array took long to stop due to running services (resource pressure)?

Strange, CPU = i5-14400 , ZFS Snapshot script Finished at: 20:09:05

Have no other scripts at this time but maybe some container load was involved here ...

2025-08-26T20:09:05+03:00 MyServer ZFS_SnapShot: All Done

I identified a couple of potential edge-case issues in the shutdown logic, which should be resolved in the latest update.

A lot of the shutdown script was mostly unchanged legacy code, I've refactored and modernised it with additional safeguards.

I still receiving this error after 2 - 3 days run on my unraid server. Only fix here is to reboot the undrai server.

Can't reboor NUT driver:

Writing NUT configuration...
Updating permissions for NUT...
Checking if the NUT Runtime Statistics Module should be enabled...
Disabling the NUT Runtime Statistics Module...
Stopping the NUT services...
Network UPS Tools upsmon 2.8.3 release
Network UPS Tools upsd 2.8.3 release
Network UPS Tools upsdrvctl - UPS driver controller 2.8.3 release
Stopping /var/run/nut/nutdrv_qx-ups.pid failed, retrying harder: Success
Network UPS Tools upsdrvctl - UPS driver controller 2.8.3 release
Network UPS Tools 2.8.3 release - Generic Q* USB/Serial driver 0.42
USB communication driver (libusb 1.0) 0.50
No supported devices found. Please check your device availability with 'lsusb'
and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'subdriver', 'vendorid' and 'productid'
options specified. Please refer to the man page for details about these options
(man 8 nutdrv_qx).

Driver failed to start (exit status=1)

How to fix this? Other super master root command I can use to force an reboot without reboot unraid every 2 - 3 day? :)
I have also tried "default 2.8.4 stable"

Edited September 5, 2025Sep 5 by uCoreX

I installed Network UPS Tools (NUT) by desertwitch from Community Applications and rebooted my server.

Now it won't boot up. Do I just disable the plugin on the usb stick?

4 hours ago, waymon said:

I installed Network UPS Tools (NUT) by desertwitch from Community Applications and rebooted my server.

Now it won't boot up. Do I just disable the plugin on the usb stick?

You can just delete the respective .plg file in /boot/config/plugins. It would be interesting to know what problem you're having exactly and where it gets stuck though, as this problem has never occured to any other users before.

10 hours ago, Rysz said:

You can just delete the respective .plg file in /boot/config/plugins. It would be interesting to know what problem you're having exactly and where it gets stuck though, as this problem has never occured to any other users before.

Thanks. I removed the plugin and still not booting. All I did is install the plugin, it told me to restart. So I click the 'restart' button in unraid. And now it looks as if the machine isnt even getting to the usb boot. I see the logo for a hot second and then its just black. If I tap my power button it turns off. Normally I have to hold it.

Its like the machine is stuck in the reboot mode or something....

10 minutes ago, waymon said:

Thanks. I removed the plugin and still not booting. All I did is install the plugin, it told me to restart. So I click the 'restart' button in unraid. And now it looks as if the machine isnt even getting to the usb boot. I see the logo for a hot second and then its just black. If I tap my power button it turns off. Normally I have to hold it.

Its like the machine is stuck in the reboot mode or something....

I'm not sure what you did, but the plugin doesn't tell you to reboot. Try to boot into safe mode, which will disable all plugins. If that doesn't work - it's not a plugin related issue. If that works - uninstall any plugins one by one to see which one causes the issue.

39 minutes ago, Rysz said:

I'm not sure what you did, but the plugin doesn't tell you to reboot. Try to boot into safe mode, which will disable all plugins. If that doesn't work - it's not a plugin related issue. If that works - uninstall any plugins one by one to see which one causes the issue.

It definitely said, that the change will take place once I reboot. It was like the 2nd or 3rd field on the plugins page.
I got the machine to boot. Not sure what happened but when I rebooted the computer my USB was not first in the boot order....odd.

Will try NUT again! Thanks!

Edit-

Edited September 5, 2025Sep 5 by waymon

16 minutes ago, waymon said:

It definitely said, that the change will take place once I reboot. It was like the 2nd or 3rd field on the plugins page.
I got the machine to boot. Not sure what happened but when I rebooted the computer my USB was not first in the boot order....odd.

Will try NUT again! Thanks!

Edit-

Ah, I see what you mean now. A reinstall or reboot is only required if you change the NUT backend using that setting where it says that. I'm glad that you got it working again, regardless.

@Rysz Hi,

I have updated to the latest NUT plugin version all looks ok but its failing to retreive values.

Sep 6 08:59:26 unraid rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release

Sep 6 08:59:26 unraid rc.nut: Network UPS Tools 2.8.4 release - Generic Q* USB/Serial driver 0.45

Sep 6 08:59:26 unraid rc.nut: USB communication driver (libusb 1.0) 0.50

Sep 6 08:59:50 unraid rc.nut: Using protocol: Megatec 0.08

Sep 6 08:59:50 unraid rc.nut: Autodetected 1 as number of battery packs [36/40.20]

Sep 6 08:59:50 unraid nutdrv_qx[46374]: Autodetected 1 as number of battery packs [36/40.20]

Sep 6 08:59:50 unraid nutdrv_qx[46374]: No charge time specified, using built in default [43200 seconds]

Sep 6 08:59:50 unraid rc.nut: No charge time specified, using built in default [43200 seconds]

Sep 6 08:59:50 unraid rc.nut: No idle load specified, using built in default [10.0 %]

Sep 6 08:59:50 unraid nutdrv_qx[46374]: No idle load specified, using built in default [10.0 %]

Sep 6 08:59:51 unraid nutdrv_qx[46374]: Listening on socket /var/run/nut/nutdrv_qx-ups

Sep 6 08:59:51 unraid rc.nut: Listening on socket /var/run/nut/nutdrv_qx-ups

Sep 6 08:59:51 unraid nutdrv_qx[48431]: Startup successful

Sep 6 08:59:52 unraid rc.nut: Network UPS Tools upsd 2.8.4 release

Sep 6 08:59:52 unraid rc.nut: listening on 0.0.0.0 port 3493

Sep 6 08:59:52 unraid upsd[48497]: listening on 0.0.0.0 port 3493

Sep 6 08:59:52 unraid upsd[48497]: Connected to UPS [ups]: nutdrv_qx-ups

Sep 6 08:59:52 unraid upsd[48497]: Found 1 UPS defined in ups.conf

Sep 6 08:59:52 unraid rc.nut: Connected to UPS [ups]: nutdrv_qx-ups

Sep 6 08:59:52 unraid rc.nut: Found 1 UPS defined in ups.conf

Sep 6 08:59:52 unraid nutdrv_qx[48431]: sock_connect: enabling asynchronous mode (auto)

Sep 6 08:59:52 unraid upsd[48498]: Startup successful

Sep 6 08:59:52 unraid rc.nut: Network UPS Tools upsmon 2.8.4 release

Sep 6 08:59:52 unraid rc.nut: UPS: [email protected] (primary) (power value 1)

Sep 6 08:59:52 unraid rc.nut: Using power down flag file /etc/nut/no_killpower

Sep 6 08:59:52 unraid upsmon[48501]: Startup successful

Sep 6 08:59:52 unraid upsmon[48501]: Warning: running as one big root process by request (upsmon -p)

Sep 6 08:59:52 unraid upsd[48498]: User [email protected] logged into UPS [ups]

Diags attached.

nut-ups (1).dev nut-debug-20250906091234.zip

11 minutes ago, SimonF said:

@Rysz Hi,

I have updated to the latest NUT plugin version all looks ok but its failing to retreive values.

Sep 6 08:59:26 unraid rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release

Sep 6 08:59:26 unraid rc.nut: Network UPS Tools 2.8.4 release - Generic Q* USB/Serial driver 0.45

Sep 6 08:59:26 unraid rc.nut: USB communication driver (libusb 1.0) 0.50

Sep 6 08:59:50 unraid rc.nut: Using protocol: Megatec 0.08

Sep 6 08:59:50 unraid rc.nut: Autodetected 1 as number of battery packs [36/40.20]

Sep 6 08:59:50 unraid nutdrv_qx[46374]: Autodetected 1 as number of battery packs [36/40.20]

Sep 6 08:59:50 unraid nutdrv_qx[46374]: No charge time specified, using built in default [43200 seconds]

Sep 6 08:59:50 unraid rc.nut: No charge time specified, using built in default [43200 seconds]

Sep 6 08:59:50 unraid rc.nut: No idle load specified, using built in default [10.0 %]

Sep 6 08:59:50 unraid nutdrv_qx[46374]: No idle load specified, using built in default [10.0 %]

Sep 6 08:59:51 unraid nutdrv_qx[46374]: Listening on socket /var/run/nut/nutdrv_qx-ups

Sep 6 08:59:51 unraid rc.nut: Listening on socket /var/run/nut/nutdrv_qx-ups

Sep 6 08:59:51 unraid nutdrv_qx[48431]: Startup successful

Sep 6 08:59:52 unraid rc.nut: Network UPS Tools upsd 2.8.4 release

Sep 6 08:59:52 unraid rc.nut: listening on 0.0.0.0 port 3493

Sep 6 08:59:52 unraid upsd[48497]: listening on 0.0.0.0 port 3493

Sep 6 08:59:52 unraid upsd[48497]: Connected to UPS [ups]: nutdrv_qx-ups

Sep 6 08:59:52 unraid upsd[48497]: Found 1 UPS defined in ups.conf

Sep 6 08:59:52 unraid rc.nut: Connected to UPS [ups]: nutdrv_qx-ups

Sep 6 08:59:52 unraid rc.nut: Found 1 UPS defined in ups.conf

Sep 6 08:59:52 unraid nutdrv_qx[48431]: sock_connect: enabling asynchronous mode (auto)

Sep 6 08:59:52 unraid upsd[48498]: Startup successful

Sep 6 08:59:52 unraid rc.nut: Network UPS Tools upsmon 2.8.4 release

Sep 6 08:59:52 unraid rc.nut: UPS: [email protected] (primary) (power value 1)

Sep 6 08:59:52 unraid rc.nut: Using power down flag file /etc/nut/no_killpower

Sep 6 08:59:52 unraid upsmon[48501]: Startup successful

Sep 6 08:59:52 unraid upsmon[48501]: Warning: running as one big root process by request (upsmon -p)

Sep 6 08:59:52 unraid upsd[48498]: User [email protected] logged into UPS [ups]

Diags attached.

nut-ups (1).dev nut-debug-20250906091234.zip

Can you check the PHP logs? I've never seen this before, it should only happen for a HTTP or PHP issue. Which OS version are you running?

6 minutes ago, Rysz said:

Can you check the PHP logs? I've never seen this before, it should only happen for a HTTP or PHP issue. Which OS version are you running?

Should have checked there.

Stack trace:

#0 /usr/local/emhttp/plugins/nut-dw/include/nut_status.php(111): round('')

#1 {main}

[06-Sep-2025 09:30:38 Europe/London] TypeError: round(): Argument #1 ($num) must be of type int|float, string given in /usr/local/emhttp/plugins/nut-dw/include/nut_footer.php:53

Stack trace:

#0 /usr/local/emhttp/plugins/nut-dw/include/nut_footer.php(53): round('')

#1 /usr/local/emhttp/plugins/nut-dw/include/nut_footer.php(106): nut_format_time('', 'seconds')

#2 {main}

[06-Sep-2025 09:30:38 Europe/London] TypeError: round(): Argument #1 ($num) must be of type int|float, string given in /usr/local/emhttp/plugins/nut-dw/include/nut_status.php:111

Stack trace:

#0 /usr/local/emhttp/plugins/nut-dw/include/nut_status.php(111): round('')

#1 {main}

currently 6.12.5 on this machine.

3 hours ago, SimonF said:

Should have checked there.

Stack trace:

#0 /usr/local/emhttp/plugins/nut-dw/include/nut_status.php(111): round('')

#1 {main}

[06-Sep-2025 09:30:38 Europe/London] TypeError: round(): Argument #1 ($num) must be of type int|float, string given in /usr/local/emhttp/plugins/nut-dw/include/nut_footer.php:53

Stack trace:

#0 /usr/local/emhttp/plugins/nut-dw/include/nut_footer.php(53): round('')

#1 /usr/local/emhttp/plugins/nut-dw/include/nut_footer.php(106): nut_format_time('', 'seconds')

#2 {main}

[06-Sep-2025 09:30:38 Europe/London] TypeError: round(): Argument #1 ($num) must be of type int|float, string given in /usr/local/emhttp/plugins/nut-dw/include/nut_status.php:111

Stack trace:

#0 /usr/local/emhttp/plugins/nut-dw/include/nut_status.php(111): round('')

#1 {main}

currently 6.12.5 on this machine.

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