I have the CyberPower 1100va AVR...didn't had any issues. Thank you all for sharing the advance setting, mine is done.

@renegade, @provels You're welcome

@azdeltawye said in How to configure NUT for Tripp Lite UPS using SNMP: This sounds like it is way above my knowledge level. I've never heard of snmpwalk. Is that something I could run on a raspberry Pi? In all honesty, I was hoping for some kind of cookbook procedure from someone who had successfully set this up... I'll probably just have to wait for the Local USB fix, hopefully in the next version of NUT... Yes, I would expect that you can run it on a Pi assuming you have SNMP installed. Example: snmpwalk -v 1 -c public 192.168.1.1 Where 'public' is the name of the SNMP community, and '192.168.1.1' is the IP address of the UPS. As to the local USB situation, there is an easy workaround discussed here, or an updated binary available here.

@dominikhoffmann: My Smart-UPS has a USB-B jack. Connecting a standard USB-A-to-USB-B cable to the white USB jack on my Netgate 1100 allows apcupsd to communicate with the UPS.

@viragomann ill give it a shot... thanks

@dominikhoffmann said in Interact with APC UPC via apcupsd or nut?: Which package should I use to interface my pfSense box to a UPS? apcupsd or nut? Assume the UPS is one from APC. If you are looking at single host with an attached UPS, either package is a fine choice. Matter of preference. If you are looking to coordinate shutdown of multiple machines, NUT would be the preference.

Yesterday, I reinstalled my apcupsd and now my widget is working again.

@bchan there is a checkbox setting “Kill on Power Fail” already, is that not working?

@michaellacroix I'm getting the same line 130 error. I've seen reports of a similar error but different line. You might update what you are seeing on redmine. https://redmine.pfsense.org/issues/13970

@shaffergr https://forum.netgate.com/topic/102959/nut-package/970

@gwaitsi said in NUT Package upssched setup: @dennypage i already have it working Congratulations. Super cool.

@ewok2 There is a users mailing list, a developers mailing list, and an IRC channel, all on that page.

IIRC it returns everything the UPS reports to it over the interface, so it's possible the UPS itself isn't sending back the data, though what you do see there doesn't seem to be data from the UPS but meta information from apcupsd. You might try different driver settings to see if any others work and have data. It's also possible there may be a firmware update for the UPS that fixes the issue but that's not something the package can do or tell you.

@firefox USB-HID is the standard UPS protocol for USB. It is supported by a wide range of manufacturers. Here is a link to the NUT usbhid-ups driver page which should give you an idea of how widespread it is. Here is a link to the APC document describing their implementation. In short, if it's not HID compliant, neither APCUPSD or NUT using the usbhid-ups driver is going to work with it over usb. There are a couple of other usb based drivers offered by NUT, but these tend to be more unusual these days. See the NUT hardware compatibility list here for more info. I do see a couple of Advice UPSs on the list--they use the blazer_usb driver. You might give that a try. If that doesn't work, I think you are out of luck.

@occamsrazor One other thing you are going to run into... the QNAP uses a hard coded value for username and password (admin/123456). These hard coded values will be in conflict with the generated admin settings for NUT on pfSense. To get around this, you will need to change the configuration on the QNAP by hand to use the values you add on pfSense (post 2 referenced above). You will likely need to repeat this change whenever the OS on the QNAP is updated.

Sorry for the delayed reply, the answers are appreciated. Sounds like it is a no-go and that's OK. It wasn't a big deal but would have been nice to have it on pfSense but I'll see what other devices I have that I could install NUT on.

@studmuffin1134 Check out the apcupsd manual. My UPS is connected via USB to pfSense, even it has a network card inside. This works flawlessly.

I managed to get my config working :) I thought that I share it here so maybe someone will find it useful. My UPS Settings: [image: 1662927666331-services-ups-settings-final-c.png] /usr/local/etc/nut/upssched.conf -rw-r--r-- 1 root wheel 630 Sep 11 21:29 upssched.conf CMDSCRIPT /usr/local/bin/upssched-cmd # Command pipe and lock-file PIPEFN /var/db/nut/upssched.pipe LOCKFN /var/db/nut/upssched.lock # Send alerts immediately on change in line power AT ONBATT * EXECUTE onbatt AT ONLINE * EXECUTE onpower # Send alerts immediately if low battery limit is reached AT LOWBATT * EXECUTE onlowbatt # (Optional) Silence the beeper after 2 minutes AT ONBATT * START-TIMER mute_beeper 120 AT ONLINE * CANCEL-TIMER mute_beeper # Shutdown after 5 minutes on battery (5 * 60 = 300) AT ONBATT * START-TIMER onbatt_shutdown 300 # Cancel timer if power's restored AT ONLINE * CANCEL-TIMER onbatt_shutdown /usr/local/bin/upssched-cmd -r-xr-xr-x 1 root wheel 1411 Sep 11 21:29 upssched-cmd #!/bin/sh # START: User-specific settings # UPS_USERNAME="local-admin" UPS_PASSWORD="some-pass" UPS_LINK="CP1300_UPS@localhost" # END # START: Battery info # STATUS=$( upsc $UPS_LINK ups.status ) CHARGE=$( upsc $UPS_LINK battery.charge ) CHMSG="[$STATUS]:$CHARGE%" # END logger -i -t upssched-cmd Calling upssched-cmd $1 case $1 in onbatt) # make sure beeper is enabled upscmd -u ${UPS_USERNAME} -p ${UPS_PASSWORD} ${UPS_LINK} beeper.enable # alert message="$UPS_LINK, $CHMSG - Power outage, on battery" ;; onlowbatt) message="$UPS_LINK, $CHMSG - Power battery low - shutdown now!" ;; onpower) message="$UPS_LINK, $CHMSG - Power restored" ;; mute_beeper) message="(2) minute limit exceeded, muting beeper" upscmd -u ${UPS_USERNAME} -p ${UPS_PASSWORD} ${UPS_LINK} beeper.mute ;; onbatt_shutdown) message="$UPS_LINK, $CHMSG - Triggering shutdown after (5) minutes on battery" /usr/local/sbin/upsmon -c fsd ;; replace_batt) message="Quick self-test indicates battery requires replacement" ;; *) message="Unrecognized command: $1" /usr/bin/logger -i -t upssched-cmd $message exit 1 ;; esac /usr/bin/logger -i -t upssched-cmd $message /usr/local/pkg/nut/nut_email.php $message exit 0 The reason why my original config didn't work (upssched not starting) was caused by wrong AT declarations. I had to change them from AT notifytype UPS-name EXECUTE command to AT notifytype * EXECUTE command I'm not sure why I can't use specific UPS name (CP1300_UPS@localhost in my case) as it is recommended approach but otherwise upssched doesn't work. Regarding the offdelay and ondelay parameters in Extra Arguments to driver field. Initially I set them to offdelay=120 and ondelay=180 but it wasn't working as expected. After 120 seconds UPS was turning off but 60 seconds later (180 - 120) it was turning back on again while still being on battery power. I had to set ondelay=0 to prevent UPS from turning on until line power was restored.