Had a few instances of the driver losing connection to my UPS, just saw this after a brief power bump (only a bump, not an outage):

APC Back-UPS RS 1350MS

Poll UPS [[email protected]] failed - Data stale

Restarting the NUT driver reconnects it properly and data is returned. Driver is 2.8.5 stable. Any ideas? unRAID 7.3.2 on a Supermicro chassis.

Maybe something to do with this? https://github.com/networkupstools/nut/issues/3487

Edited July 22Jul 22 by Nogami

Bug in UI

If slave ups named something like "ippon_ups" onsaving all, including _, will be truncated for ex. to ""ippon" so no status\info on page\widget. (or no connection at all if non-manual)

Screenshot

Screenshot Also HERE

Manual ovveriding in /boot/config/plugins/nut-dw/nut-dw.cfg works perfect, like

 sed -i 's/^NAME=.*/NAME="ippon_ups"/' /boot/config/plugins/nut-dw/nut-dw.cfg

Edited July 23Jul 23 by MERKATOR

I think I have a similar issue. Sometimes when I open up the dashboard I'll notice that there's a continuous loading icon showing on the UPS widget, not stats on battery or load. Restarting NUT instantly fixes it. I noticed my syslog is also swamped with NUT related warnings, see the attached screenshots. Any clue on how to fix this?

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 is 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.

12 minutes ago, MonadProxy said:

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 is 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.

It would shutdown completely, if in halfway, it mostly is shutdown problem, something stuck actually.

On 8/16/2025 at 3:58 PM, Rysz said:

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

On 8/16/2025 at 5:41 PM, 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.

After a lot of tweaking and experimenting, I created a script that automatically adds and saves the entries for me. This way, the values are no longer overwritten every time I restart the NUT service.

In the meantime, I also had to replace the UPS because the old one was defective. However, I bought the exact same model again (ups.model = Back-UPS BX1200MI).
But I’m still continuously getting the alarm messages... Any other solutions?

#!/bin/bash
cd /etc/nut && chattr -i ups.conf &&
cat > ups.conf <<'EOF'
[ups]
driver = usbhid-ups
port = auto
pollonly
lbrb_log_delay_sec = 3
lbrb_log_delay_without_calibrating
EOF
cat ups.conf && chattr +i ups.conf && lsattr ups.conf

Edited August 15Aug 15 by SBlack08

How i can connect a QNAP NAS with the UPS on the Unraid Server.
I used the Slave UPS Option in QNAP with the Unraid Server IP with the UPS.

The NUTS Mode is Netserver.

But what Configuration must i been set or configure for a correct Connection?