Rysz

The settings are greyed out because NUT is running (you'd need to stop NUT to change them). Why the load doesn't display I'm not sure, nothing was changed in the backend that would cause this. If reverting back to 2.8.0 also doesn't change this (the load missing), it's likely not caused by the backend, but the UPS - can you try connecting your UPS on a different USB port?

Welcome!

I've just pushed an update with a fixed backend for your issue. Please do as follows: Stop NUT on your UNRAID if running. Set "Network UPS Tools Backend Switch:" to "default (recent master)" in NUT Settings Click on "Apply" button to save the changed backend setting. Update the NUT plugin to version 2023.10.24 Make sure "Network UPS Tools Backend:" now says: "nut-2.8.0-x86_64-12master.ssl11" Start NUT, should work now. 🙂

Nothing was changed on that, do you have the correct CMDSCRIPT directive in your upssched.conf? Anything in the logs, particularly when starting up NUT?

I've just identified and been able to reproduce this as a bug in the backend in the relatively rare situation of a not 100% correctly treated ONLINE state in combination with a network loss. I've reported this to the upstream backend developer and hopefully we'll see a fix for this ASAP. In the meantime, you can switch to the release/legacy backend, if those work for you: Sorry for the inconvenience - I'll post here as soon as this is fixed in the "default (recent master)" backend.

Thanks for reporting back, this is indeed the battery self test, we've luckily been able to fix the APC shutdown issue in the "default (recent master)" backend also since your report. So you can stay on 2.8.0 stable if it works well for you or update NUT and switch back to "default (recent master)". 🙂

Yes, that's the affected series. The old NUT used the legacy 2.7.4 backend (and had a range of problems on its own unfortunately). If you choose the NUT stable or legacy backends you'll only get the GUI updates when updating NUT but the backend will always stay on the chosen backend (if that's what you want 🙂)

This is unfortunately a known bug in the NUT backend that happens when some APC devices do their bi-monthly battery self tests. Switching to stable or legacy backend has fixed the problem for the other users affected and a fix for this from the NUT backend developers is on the way. I'm guessing you also have an APC device?

POLLFREQ 5 This is what you'd put in upsmon.conf on UNRAID via the NUT configuration editor in the GUI. You might need to "Reset Config" since yours seems broken somehow. The other lines (from the post) are only for the server the UPS is physically connected to.

I'd try another USB port and see if the problem persists, such logs have been occurring for other users where USB ports or cables died.

See this post for the values:

Sorry, no idea about the Docker version of NUT - that one's not maintained by me.

"Kill UPS Power" selbst bewirkt nur das Ausschalten der USV (und des Batteriestroms zu den Geräten) nach dem Herunterfahren des Servers. Wenn der Netzstrom wieder da ist, sollte sich die USV dann wieder einschalten und der Server (wenn im BIOS so eingerichtet) wieder hochfahren. Ist also ein Zusammenspiel von mehreren Faktoren mit der grundlegenden Voraussetzung dass die USV selbst das Herunterfahren unterstützt.

Die "Kill UPS Power" Funktion wird leider nicht von allen USV Geräten unterstützt, je nach Hersteller und Modell.

Nice work and thanks for posting it here - nice to see this working and incorporated into another script. 🙂

Mit deinen Einstellungen und Werten wird das sichere Herunterfahren im Falle eines Stromausfalls auf jeden Fall funktionieren. 🙂

Eaton USV funktionieren meist sehr gut mit NUT, liegt daran dass NUT einige Zeit von Eaton mitentwickelt und gesponsert wurde. Freut mich aber trotzdem, dass es bei dir gut funktioniert! 🙂

Bei UPS Power and Load Display Settings (auf Manual) kannst du die Normwerte deiner USV einstellen. Damit sollten dir dann alle deiner fehlenden Werte außer "Runtime Left" berechnet und angezeigt werden. Obwohl dir auch bereits jetzt die notwendigen Werte für die Funktion von NUT selbst angezeigt werden. Die fehlenden Werte sind primär optischer Natur (im GUI), muss man also nicht zwingend für die NUT-Funktionen haben. Einzig den Shutdown Mode: "Runtime Left" kannst du mangels "Runtime Left" Wert halt nicht verwenden. Der ist aber ohnehin nicht empfehlenswert, also einfach "Battery Level" oder "Time on Battery" verwenden. Dass die Batterieladung immer auf 100% steht ist nicht ungewöhnlich und sollte auch so sein (ist bei mir auch so). Du kannst ja einmal testen ob NUT funktioniert bzw. die Batterieladung fällt wenn du z.B. testweise mal den Strom abstellst. Ansonsten kannst du noch probieren (ob dir dann mehr Werte angezeigt werden): Network UPS Tools Backend Switch: stable (2.8.0 stable) UPS Driver: nutdrv_qx Mach halt vorher einen Screenshot deiner jetzigen Einstellungen, damit du notfalls wieder zum Ist-Zustand kannst.

I've just updated the plugin, the new version includes that setting. 🙂

Where and how does the NUT server (the one not on UNRAID) show you the wrong runtime? Usually the NUT server just reports back the raw values from the UPS and doesn't interpret them somehow (on other Linux distributions), so where are you seeing the wrong value on your RPi? Regarding UNRAID, since a few users have asked for this already I'll implement a switch between seconds and minutes reported for UPS runtime in the next update.

I've read about this a couple of times in the bug tracker of NUT (backend) so far and, as I understood it, this behaviour essentially boils down to the USB driver's implementation in the Linux kernel in combination with that specific USB controller on either the server, the UPS device or both - so this is something that can't really be influenced much from the NUT side of things. What's always worth attempting is changing the USB port or USB cable, some users have reported connection losses and such I/O-errors because they were using a bad USB port or USB cable. Over-polling is indeed sometimes an issue with some UPS, there are some ups.conf settings you can tune: Just make sure to put them in the safe-zone (below line 12, marked with the red arrow): pollinterval = The status of the UPS will be refreshed after a maximum delay which is controlled by this setting. This is normally 2 seconds. This setting may be useful if the driver is creating too much of a load on your monitoring system or network. pollfreq = Set polling frequency for full updates, in seconds. Compared to the quick updates performed every "pollinterval" (the latter option is described in ups.conf(5)), the "pollfreq" interval is for polling the less-critical variables. The default value is 30 (in seconds). synchronous = By enabling the synchronous flag (value = yes), the driver will wait for data to be consumed by upsd, prior to publishing more. This can be enabled either globally or per driver. The default of auto acts like no (i.e. asynchronous mode) for backward compatibility of the driver behavior, until communications fail with a "Resource temporarily unavailable" condition, which happens when the driver has many data points to send in a burst, and the server can not handle that quickly enough so the buffer fills up. I've used the default values in my screenshot, you'll need to play around with different values to see the difference - please let us know if it had any positive effect on your problem.

OK die Einstellungen sehen soweit einmal gut aus. Kannst du unter UPS Driver versuchen ob die USV mit blazer_usb statt nutdrv_qx erkannt wird? Ansonsten einfach morgen nochmal beide Treiber (nutdrv_qx und blazer_usb) mit den zwei anderen Backends (legacy 2.7.4 und stable 2.8.0) probieren. Alternativ gerne auch nochmal mit einem anderen USB Port versuchen.

Das sind die APC USV Einstellungen, hier musst du "Starte APC UPS Daemon" auf Nein einstellen. NUT und der APC UPS Daemon können nicht gleichzeitig laufen, das sind zwei verschiedene Programme. Wird deine USV jetzt unter "NUT Settings" erkannt und läuft NUT ? Alle Informationen und Einstellungen zur USV laufen dann ausschließlich über die "NUT Settings" Seite.

In dem Menü musst du eben den Treiber nutdrv_qx (2te Stelle im Menü auswählen) Du musst das System nicht neustarten, du musst nur in dem UPS Driver Menü nutdrv_qx auswählen. Und dann versuchen NUT zu starten... 🙂

Da muss es ein Dropdown-Menü geben, das wird sogar auf deinem Screenshot angezeigt: Ansonsten mal mit einem anderen Browser versuchen, falls sich da kein Menü ausklappen lässt...