Nut & Powerware/Eaton 5110 problem: package needs patch?

  • Hello all,

    just upgraded from 1.2 to 2.0.1 and installed the latest nut package, since I got an Eaton/Powerware 5110 USB UPS.

    The problem is that there is no mention of this on the web interface. However, the model is clearly supported:

    # grep 5110 /usr/local/etc/nut/driver.list
    "Powerware"     "PW5110"        ""      "bcmxcp_usb"

    Indeed, if I manually change /usr/local/etc/nut/ups.conf to:

    # cat /usr/local/etc/nut/ups.conf

    then nut starts up just fine, information is clearly displayed in the pfsense interface etc:

    # /usr/local/etc/rc.d/ start
    starting upscode2
    Network UPS Tools - UPS driver controller 2.2.2
    Network UPS Tools - BCMXCP UPS driver 0.14 (2.2.2)
    Warning: This is an experimental driver.
    Some features may not function correctly.
    Model = POWERWARE UPS    700VA
    Firmware = Cont:00.50 Inve:01.50
    Shutdown delay =  120 seconds
    Shutdown delay longer than battery capacity when Low Battery warning is given. (max 60 seconds)
    starting upsd
    Network UPS Tools upsd 2.2.2
    listening on port 3493
    Connected to UPS [eaton5110]: bcmxcp_usb-eaton5110
    starting upsmon
    Network UPS Tools upsmon 2.2.2
    UPS: eaton5110@localhost (master) (power value 1)
    Using power down flag file /etc/killpower

    Unfortunately, contents of ups.conf are lost after a reboot.  :-[

    Can the maintainer of the port provide some patching here? Or, is there any alternative, with a minimal tinkering of pfsense, preferably with a "clean" solution, to have my ups.conf "stick"?

  • Until you can get an fix to the package, you can edit /usr/local/pkg/ and change how this package generates conf.

    This way every time you apply, your changes will be in conf file.

    Don`t forget to create a backup file outside from /usr/local/pkg folder before start editing it.

    cp /usr/local/pkg/ /root

  • Thanks, that did the trick!

    Is there something else I can do to communicate this request for change to the package communicator, to have this solved for the next nut package version?

  • You can create an account at github and pull your file change request to Fix this package.

Log in to reply