UPS Tools

Advanced conf in clinet mode

dennypage — Sat, 25 Apr 2026 09:45:18 GMT

@Urbaman75 Taking shutdown actions based on OB is almost always a bad idea, especially with remote server/client. Just let NUT and the UPS manage things as intended based on LB.

NUT server - After power is turned back on, pfsense shut's down sockets without warning for no reason

dennypage — Mon, 09 Mar 2026 23:53:46 GMT

@DomV said in NUT server - After power is turned back on, pfsense shut's down sockets without warning for no reason: Because I think that this is the default value for this UPS. And I still really don't understand why with the pi it works correctly even with this setting. The default for low battery on APC UPSs is 10%. 97% would not make sense to use as a default setting on any UPS. As to the Pi, there are any number of configuration reasons that would result in a change of behavior. If you want to explore that further, I recommend the NUT Users mailing list.

UPS ups on battery - appers often now

netboy — Sun, 08 Mar 2026 22:47:54 GMT

@dennypage said in UPS ups on battery - appers often now: I have no idea. The information that has been provided is insufficient for me to offer any conclusion. fair enough - i am going to get rid of UPS and buy power station with UPS functionality

NUT and Goldenmate UPS

dennypage — Fri, 30 Jan 2026 23:45:01 GMT

@moosport said in NUT and Goldenmate UPS: Thank you @dennypage ! Welcome

pfSense 2.8.1, NUT 2.8.2_5 package, EcoFlow UPS

dennypage — Tue, 06 Jan 2026 17:41:16 GMT

@Rahzadan said in pfSense 2.8.1, NUT 2.8.2_5 package, EcoFlow UPS: Is there a way to upgrade NUT to a newer version in pfSense? I expect it will be updated in the next pfSense release cycle.

Docker container for nut server?

johnpoz — Thu, 09 Oct 2025 19:32:11 GMT

Well I got my synology to be monitored. But not having any luck getting win-nut working on my windows machine.. I found a later version that suppose to work 2.8.4, and it finds my ups via nut-scanner.. But can't seem to get it to run, says no listening interface, etc. etc.. I think just going to throw some money at it, I can get the personal panel version to show up in cloud, so just going to their cloud card, found on amazon for 68$ Their cloud interface is not horrible - and the cost is like 10$ a year for lic per ups, and if you buy a card you can get 3 year lic for 1 card.. The only unit I have that doesn't support the cloud card is the one behind my tv. But that is one I have linux working on, and can use cyberpowers software vs nut to connect it to the cloud. found a slick little docker, @netboy looks a bit more what I would like.. But - just going throw some money at vs dicking with the windows machine and nut. And just put them all up on the cloud. https://github.com/Brandawg93/PeaNUT

NUT fails to start after 2.7.2 -> 2.8.0 upgrade

dennypage — Sat, 26 Jul 2025 18:55:22 GMT

@jhg said in NUT fails to start after 2.7.2 -> 2.8.0 upgrade: Interesting. I would have thought the initial reboot, which occurred as part of the upgrade, would have done the trick, but it took a second reboot, just now, to get things working. Glad you have it sorted. There was no difference in the output of usbconfig show_ifdrv at any point -- before or after unplugging/replugging the USB cable, nor after rebooting. ... Question: What would tell me whether or not a driver was loaded? If there were an attached driver, it should have shown up with the show_ifdrv command. If you use the command and look at the other usb devices, I think they will show attached drivers. I don't expect to see a driver attached to the ups, because there is a quirk that tells the OS to ignore that device (and not attach a driver). Look for idVendor and idProduct in the above output. The Vendor ID for your device is 0764, which corresponds to Cyber Power Systems, and the Product ID for your device is 0601, which is registered as "PR1500LCDRT2U UPS" (don't sweat an exact match for the name). You can see the quirk with the following command: [25.07-RC][root@fw]/root: usbconfig dump_device_quirks | grep 0764 VID=0x0764 PID=0x0005 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_HID_IGNORE VID=0x0764 PID=0x0501 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_HID_IGNORE VID=0x0764 PID=0x0601 REVLO=0x0000 REVHI=0xffff QUIRK=UQ_HID_IGNORE [25.07-RC][root@fw]/root: Your device is third on the list. The HID_IGNORE quirk says to ignore the device and not attach a driver. @jhg said in NUT fails to start after 2.7.2 -> 2.8.0 upgrade: You might consider adding this resolution to the release notes for 2.8. LOL... sorry, I don't have input to the release notes (I don't work here). While I wrote and maintain various packages, including NUT, I'm still just a volunteer. Most packages are actually written by volunteers.

Advanced Settings for Client to attach

kiekar — Sat, 26 Jul 2025 12:00:55 GMT

@provels Thanks for your reply and help. I'm now able to have unraid connect to the NUT server.

pfSense NUT Client-Mode

kiekar — Mon, 14 Jul 2025 22:45:20 GMT

@elvisimprsntr thanks for your suggestion. I will give it a try.

SNMP UPS inconsistent connection

Gertjan — Thu, 05 Jun 2025 13:02:33 GMT

@Laxarus said in SNMP UPS inconsistent connection: DNS failure is one of the suspects No need to keep the "suspect" waiting, as you can consult the proof right away. Go here : Status > System Logs > System > DNS Resolver and see if you can find : [image: 1749190942028-59c728e4-a985-4222-b07d-e0d394cb1ebb-image.png] If you find them, match the related time stamp info with the NUT UPS events (main system log). If they match, and it happens to often, get yourself this mission : Figure out why unbound restarts, then evaluate the conditions that made it restart. The final goal is (always) : make DNS as accessible as possible. For example : a default, "clean" pfSense install won't restart unbound for days, even weeks. Start plugging in and moving network cables into pfSense, or power down and power up devices attached to pfSense directly by cable, and every time packages get restarted. Install pfBlockerng and according its settings it can restart unbound many time per day. Depending how you use pfSense, what you've installed extra can make live hard for your DNS ... for yourself. Your mission as an admin : find the right balance.

Issues after upgrade to 2.8.0

dennypage — Thu, 05 Jun 2025 08:08:06 GMT

@JonesTech I recommend removing all the excess config you have put in. There are far too many copy/paste magic recipes for NUT on the internet that mislead people. The best approach with NUT is to start with the default configuration, and let NUT and your UPS take care of business as designed. You should only add directives to NUT if you are doing so to address a specific problem, and even then be very minimalist. And with every OS or NUT upgrade, you should retest/reconfirm that the directives are actually still necessary. ignorelb, while commonly recommended on the internet in various recipes derived from 10 or 15+ year old information, is almost always a very bad idea. It should ONLY be used if you have one of those very unfortunate old UPSs that declare Low Battery immediately on mains fail. On a modern UPS, you simply don't want to ignore the UPS saying "Hey, the battery is low, I'm about to shut down..." interruptonly is not pertinent to the initial connection of the driver, and should only be done if necessary to address constant disconnects with your UPS. Usually this is used to work around bugs in the USB or driver layer. If you do need to put this in, you should retest this with every OS or NUT upgrade to see if it is still required. Increasing pollinterval will make it longer before the system knows you are on battery. Almost certainly not what you want. override.battery.charge.warning has no meaning with the pfSense configuration. override.battery.charge.low will cause NUT to initiate a shutdown even though you have over a third of your run-time remaining. While this is a meaningful directive, are you sure this is what you want? And are you sure your UPS will work correctly this case?

ups shutdown pfsense after 30 seconds

dennypage — Tue, 03 Jun 2025 06:47:28 GMT

@firefox said in ups shutdown pfsense after 30 seconds: Could this be an incorrect setting in the SNMP card's graphical interface? I took the SNMP card from another UPS that is from the same manufacturer as my UPS. this is the model of my ups AON1500-2 this is the model of the ups i took the card from top v pro 6 When I connected the snmp card to the ups it seemed to recognize that it was a different ups I assume this is the same UPS as you were asking about last December? I do not have familiarity with that UPS manufacturer, so I really can't answer your question. You can either reach out to the manufacturer and ask them about NUT SNMP support for their UPSs, or go down the path of learning about SNMP and diagnose the issue yourself. Unless you happen to find someone with the exact same UPS and SNMP card, already working with NUT, this is going to require some effort. FWIW, the odds are that either the SNMP driver is incorrect, or the MIB is incorrect. For me, the first step would be to learn about the available MIBs, and begin exploring the SNMP interface with snmpwalk.

pfSense -> pfSense NUT connection issues

dennypage — Mon, 02 Jun 2025 09:24:32 GMT

@AngryAnt said in pfSense -> pfSense NUT connection issues: I had explicited the firewall allow rules to the NUT port only Yes, that is appropriate. The allow example really should have had a destination port like so: [image: 1748973560467-screenshot-2025-06-03-at-10.56.00-resized.png]

apcupsd causes restart

Vancejo1 — Sun, 25 May 2025 23:43:54 GMT

@viragomann Yes it definitely is rebooting, but not immediately. I was able to try it 3 more times before putty quit responding. Here is what shows in putty... Select function number: 10 This test instructs the UPS to perform a battery calibration operation and reports the result when the process completes. The battery level must be at 100% and the load must be at least 10% to begin this test. Battery level is 100% -- OK Load level is 14% -- OK Clearing previous self test result...CLEARED The battery calibration should automatically end when the battery level drops below about 25%. This process can take minutes or hours, depending on the size of your UPS and the load attached. Initiating battery calibration...INITIATED Waiting for calibration to complete... To abort the calibration, press ENTER. CALIBRATION COMPLETED Result of last self test: ABORTED Test kill UPS power Perform self-test Read last self-test result View/Change battery date View manufacturing date View/Change alarm behavior View/Change sensitivity View/Change low transfer voltage View/Change high transfer voltage Perform battery calibration Test alarm View/Change self-test interval Q) Quit Select function number: 10 This test instructs the UPS to perform a battery calibration operation and reports the result when the process completes. The battery level must be at 100% and the load must be at least 10% to begin this test. Battery level 99% is insufficient to run test. Test kill UPS power Perform self-test Read last self-test result View/Change battery date View manufacturing date View/Change alarm behavior View/Change sensitivity View/Change low transfer voltage View/Change high transfer voltage Perform battery calibration Test alarm View/Change self-test interval Q) Quit Select function number: 10 This test instructs the UPS to perform a battery calibration operation and reports the result when the process completes. The battery level must be at 100% and the load must be at least 10% to begin this test. Battery level 99% is insufficient to run test. Test kill UPS power Perform self-test Read last self-test result View/Change battery date View manufacturing date View/Change alarm behavior View/Change sensitivity View/Change low transfer voltage View/Change high transfer voltage Perform battery calibration Test alarm View/Change self-test interval Q) Quit Select function number: 10 This test instructs the UPS to perform a battery calibration operation and reports the result when the process completes. The battery level must be at 100% and the load must be at least 10% to begin this test.

NUT Remote Access Stopped Working After Migration from CW 2.7.2 to 2.8.0-BETA

jeffry.maynard — Tue, 13 May 2025 16:59:26 GMT

@dennypage I added back in the listen directive and removed the port forward. Seems to work well also. Not sure why my arp table got mussed, but I guess that can happen.

NUT + CPS EC650LCD not working

bigagt — Wed, 16 Apr 2025 16:41:00 GMT

Thanks, all! Upgrading to the latest pfSense Beta fixed it!

NUT suddenly stops working every app. 6 minutes

j.koopmann — Fri, 28 Mar 2025 08:48:16 GMT

@dennypage said in NUT suddenly stops working every app. 6 minutes: Okay, that is entertaining to say the least. Does "66da6bc012db26058161" happen to be the locally generated password for local-monitor? I have not the slightest idea! Never seen this before!!!! Rest: Will be delighted to do so! Thanks for the instructions.

Linefeed in pfSense email notifications (with Network UPS Tools)

Gertjan — Wed, 22 Jan 2025 22:09:15 GMT

@rdibley said in Linefeed in pfSense email notifications (with Network UPS Tools): So one more question: if most people don't use the Advanced section (and the users.conf is blank), how does a secondary system connect to the primary? Is it that most people don't define a user/password for monitoring, but that the primary is just open to any secondary system that might want to connect? I'm using it [image: 1738134876715-b852fa0b-7f4c-4461-8c73-3867487db57f-image.png] The third entry is for my Synology NAS : And the NAS side : [image: 1738134981361-c67da02f-ce7a-456c-a7e1-fede22ed4b6b-image.png] and done. I've also installed "Windows NUT Client" on two PC's nearby. Example : PC 1 with user name "pcrecep1" and password "secret1" : [image: 1738135091751-e41ec81d-1698-431f-98f9-17e142c93132-image.png] Works fine also. So I've 4 devices protected with one big 1000 VA APC UPS, where pfSense is the NUT 'server' as it has a USB cabled UPS hooked up to it, and now 4 devices are controlled by this UPS instead of one.

NUT upscmd ERR ACCESS-DENIED

jhg — Tue, 07 Jan 2025 22:23:50 GMT

Never mind, figured it out. I don't seem to be able to delete the post however.

Trying to run the following (or any upscmd command)

[2.7.2-RELEASE][admin@janus.jhmg.pvt]/root: upscmd -w -u admin cyberpower-1500 test.battery.start.quick
Password: ["admin" user's login password]
Unexpected response from upsd: ERR ACCESS-DENIED

I found the post showing where to look for the upsd.users file, and it does contain an entry for the "admin" user, but the password seems to be a hash

[2.7.2-RELEASE][admin@janus.jhmg.pvt]/root: cat /usr/local/etc/nut/upsd.users
[admin]
password=[160-bit hex string]
actions=set
instcmds=all
...

I tried all combinations of userid (admin, root) and password (actual password, hex string from upsd.users) but they all produce the same result.

How do I run upscmd?

Manage two UPS

zkab — Sat, 21 Dec 2024 12:25:38 GMT

@dennypage I will go for your suggested solution: UPS 1: pfSense as NUT server and the rest as NUT clients UPS 2: one system attached to the UPS as the NUT server and the others as NUT clients Since I don't have enough knowledge of NUT I guess I will be back several time to this forum. Thanks for you gudelines and Merry Christmas !!!

How do I connect the UPS to pfsense? If it is possible ?

dennypage — Sat, 07 Dec 2024 14:24:03 GMT

@firefox Glad you got it working

ONLINE LOW BATTERY message

dennypage — Tue, 15 Oct 2024 01:06:56 GMT

@netboy Glad you got it sorted.

Apcupsd: Battery age 23 Years 9 Months 8 Days?

DominikHoffmann — Wed, 09 Oct 2024 04:10:55 GMT

@jrey: Very helpful! Thank you very much!

Just to inform that APC model Back-UPS BX 1500BI-BR works perfectly

mcury — Thu, 01 Aug 2024 17:40:35 GMT

Just to add that I was able to set the following settings in this APC, by: Extra Arguments to driver (optional): offdelay=60 ondelay=180 waitbeforereconnect=30 Note: waitbeforereconnect=30 is important since the driver sometimes loses connectivity with NUT. Additional configuration lines for ups.conf maxretry=3 retrydelay=10 Shell: Check the admin password: (You don't need to set an admin user in upsd.users file), the password changes, so you need to check every time you are going to make a change. cat /usr/local/etc/nut/upsd.users Checking defaults: upsrw -l ups Changing values: upsrw -s battery.charge.low ups Username (root): admin Password: Enter new value for battery.charge.low: 50 OK upsrw -s battery.runtime.low ups Username (root): admin Password: Enter new value for battery.runtime.low: 1500 OK If you receive the following error after boot, with or without user=root in ups.conf : UPS [ups]: connect failed: Connection failure: Connection refused Then, install shellcmd and use the following script as shellcmd: #!/bin/sh sleep 60 /usr/local/sbin/pfSsh.php playback svc stop nut sleep 20 /usr/local/sbin/pfSsh.php playback svc start nut sleep 5 exit 1 done

Configuring NUT help?

dennypage — Mon, 22 Jul 2024 20:15:44 GMT

@beardedguy You are welcome.