• APCUPSD: How to power off UPS

    Moved
    4
    0 Votes
    4 Posts
    3k Views
    S

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

  • PHP Error with apcupsd.widget

    Moved
    3
    0 Votes
    3 Posts
    1k Views
    C

    @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

  • nut/usb issue with 23.01-RELEASE

    Moved
    2
    0 Votes
    2 Posts
    969 Views
    dennypageD

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

  • NUT Package upssched setup

    Moved
    14
    0 Votes
    14 Posts
    2k Views
    dennypageD

    @gwaitsi said in NUT Package upssched setup:

    @dennypage i already have it working

    Congratulations. Super cool.

  • NUT server on Pfsense

    Moved
    5
    0 Votes
    5 Posts
    1k Views
    dennypageD

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

  • question about apcupsd

    Moved
    2
    0 Votes
    2 Posts
    851 Views
    jimpJ

    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.

  • APC UPS Daemon service help configure

    Moved
    21
    0 Votes
    21 Posts
    2k Views
    dennypageD

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

  • Configuring APCUPSD

    Moved
    24
    0 Votes
    24 Posts
    10k Views
    dennypageD

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

  • Multiple UPS with Apcupsd and/or NUT

    Moved
    4
    0 Votes
    4 Posts
    2k Views
    occamsrazorO

    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.

  • ApcUPSD Config

    Moved
    2
    0 Votes
    2 Posts
    998 Views
    V

    @studmuffin1134
    Check out the apcupsd manual.

    My UPS is connected via USB to pfSense, even it has a network card inside. This works flawlessly.

  • NUT upssched

    Moved
    14
    0 Votes
    14 Posts
    5k Views
    M

    I managed to get my config working :)
    I thought that I share it here so maybe someone will find it useful.

    My UPS Settings:

    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.

  • Edit NUT config files?

    Moved
    6
    0 Votes
    6 Posts
    2k Views
    dennypageD

    @furom Most welcome

  • Nut Setup

    Moved
    3
    0 Votes
    3 Posts
    1k Views
    RyanMR

    @dennypage I thought I had tried the unplug/re-plug the USB cable, but I probably didn't after installing the nut package. Anyways, I am up and running and everything looks good with my slaves. Thanks.

  • Network UPS Tools Package Running

    Moved
    5
    1 Votes
    5 Posts
    2k Views
    dennypageD

    @jonathanlee Yes, the NUT folk have done a very good job at supporting a wide variety of UPS systems.

  • Cant get NUT working with a APC ups plugged in with USB

    Moved
    3
    0 Votes
    3 Posts
    2k Views
    dennypageD

    @sjbates2283 said in Cant get NUT working with a APC ups plugged in with USB:

    In case someone else comes across this, use the apcupsd package instead

    In the context of the issue posted, this is not an appropriate recommendation.

    In case someone else comes across this, the issue above was that there is a common FreeBSD permission issue with usb UPS ports the first time the UPS is attached to the system. This can be addressed by rebooting the system, or by simply unplugging and re-plugging the usb connection.

    I expect that the OP figured this out pretty quickly. Lots of references to this in the NUT help thread.

  • Network UPS Tools Memory Used ??

    Moved
    6
    0 Votes
    6 Posts
    2k Views
    JonathanLeeJ

    @netblues Yes spot on. We learned this also in Python programming class. I agree the some URLBlacklists are massive and just eat memory, makes me wonder if they use some hybrid form of Stacks, Queues, or ArrayLists. Shalla list on my Netgate 2100 Max did not have the same issues that the other blacklists are creating, Shallalist was rather large also just not as big as the others. Thanks for the reply happy Easter.

  • apcupsd

    Moved
    6
    0 Votes
    6 Posts
    3k Views
    R

    @jasonmicron If the documentation is on docs.netgate.com you can file an update request in our redmine at https://redmine.pfsense.org

  • How to reliably stop NUT from setting biweekly UPS calibration?

    Moved
    1
    0 Votes
    1 Posts
    552 Views
    No one has replied
  • NUT and APC Smart UPS 750 RM USB

    Moved
    4
    0 Votes
    4 Posts
    2k Views
    B

    @serbus Thank you so much this just saved me.

Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.