Talk:Network UPS Tools

Can't claim USB device error

Excellent guide, the comment on permission and requiring /etc/udev/rules.d/50-ups.rules was exactly the problem installing the latest version from AUR. I would vote for Arch packaging NUT again as it is essential for all but APC compatibles UPSs that use apcupsd. David C. Rankin, J.D.,P.E. -- Rankin Law Firm, PLLC (talk) 04:34, 13 May 2019 (UTC)

Your vote will have counted for it re-joining the repo soon-ish afterwards. Unfortunately, the other issues on this talk page shows the article needs updating, because configuration changed. Let's hope someone takes the initiative. Nothing to edit without using it. --Indigo (talk) 18:06, 20 September 2026 (UTC)

Change in systemd units after update to NUT 2.8.0

This might just be an issue with my config, but it appears that after updating to 2.8.0 nut-server.service can no longer start the appropriate nut-driver by itself:

• nut-driver.service is gone, and one must instead manually run nut-driver-enumerator.service which creates the needed nut-driver@.service link (wanted by the new nut-driver.target).
• There's also nut-driver-enumerator.path which monitors /etc/nut/ups.conf and runs the service when it's changed.
• Finally, there's a new nut.target which pulls the server and monitor services as well as the new driver target.

--FeralHedgehog (talk) 18:19, 2 May 2022 (UTC)

Needs revision

I have just installed 2.8.0 and the guidance given is no longer correct. The comment above by FeralHedgehog helped me to get it going but someone with good knowledge of systemd & NUT needs to redo the wiki page with some explanation as to what the various .service & .target files do . If I get time I might give it a go, but don't count on it! Vario (talk) 08:57, 9 June 2022 (UTC)

Starting on boot

I had trouble getting NUT (v2.8.0) to start on boot when enabling the units in this guide. Starting those units manually one by one did work. I disabled all of them and enabled just nut.target and nothing else, and that seems start NUT correctly when rebooting. I guess that's the way it's supposed to work now in 2.8.0(?).

--Zebibit (talk) 17:51, 5 September 2022

NUT-Monitor

The section about NUT-Monitor in the AUR should be modified or removed. NUT-Monitor is now packaged with Network UPS Tools. The nut and nut-monitor packages should also have their conflicts updated to prevent concurrent installation. Heidegger (talk) 15:55, 10 December 2023 (UTC)

This conflict may not exist for everyone. I know that I have the git version of NUT v. 2.8.1.r249.g0ea95a760-1 and it does provide NUT-Monitor. Heidegger (talk) 16:52, 10 December 2023 (UTC)

Configure MODE if you want delayed power off

I was struggling to make NUT power down my UPS after system shutdown so that "dumb" devices like my wifi AP would not drain the remaining battery (aka delayed power off / shutdown.return).

After spending way too much time on this I realized that the /usr/lib/systemd/system-shutdown/nutshutdown script does nothing if MODE in /etc/nut/nut.conf is set to none (the default). The guide does not mention nut.conf at all, so make sure to set MODE to whatever makes sense for your setup. Irminsul (talk) 18:25, 19 September 2026 (UTC)