Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    NUT + CPS EC650LCD not working

    Scheduled Pinned Locked Moved UPS Tools
    7 Posts 4 Posters 829 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      bigagt
      last edited by

      Hello,
      I'm on pfSense 2.7.2 running on a Protectli Vault 4, attempting to use nut 2.8.2_1 with my new CPS EC650LCD.

      This doesn't seem to be working out of the box, and I can't find an indication as to where it's failing.

      I did start pumping "user=root" into the driver args to resolve this error:
      usbhid-ups[42439]: writepid: fopen /var/db/nut/usbhid-ups-EC650LCD.pid: Permission denied

      Once I started using "user=root" that error went away, but it still is not loading the service properly. The "UPS Status" page says:
      "Status Alert: The UPS requires attention"

      When I go to Status->Services->nut, the service is not active. Attempting to activate it spins for a few seconds, then just returns to inactive. In the System Logs, it just says:
      php-fpm[379]: /nut_settings.php: Starting service nut
      usbhid-ups[48657]: Startup successful

      Running usbconfig gives me the following output:
      ugen0.1: <Intel XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
      ugen0.1.0: uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1>
      ugen0.2: <CPS EC650LCD> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (50mA)

      Any advice that you can give to further troubleshoot would be much appreciated!

      E 1 Reply Last reply Reply Quote 0
      • E
        elvisimprsntr @bigagt
        last edited by elvisimprsntr

        @bigagt

        I have an APC connected to pfSense and a CPS connected to a Linux desktop client.

        I added user=root for similar errors in a previous CE NUT release.

        Screenshot 2025-04-17 at 5.22.04 AM.png

        usbconfig 
        
        ugen0.1: <Intel XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
        ugen0.2: <vendor 0x214b USB2.0 HUB> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA)
        ugen0.3: <American Power Conversion Back-UPS XS 1500M FW:947.d11 .D USB FW:d11> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (2mA)
        

        Run nut-scanner to confirm NUT can detect the UPS

        nut-scanner 
        
        Scanning USB bus.
        No start IP, skipping SNMP
        Scanning XML/HTTP bus.
        No start IP, skipping NUT bus (old connect method)
        Scanning NUT simulation devices.
        Scanning NUT bus (avahi method).
        Error sending Eaton <SCAN_REQUEST/> to <broadcast>, #1/3
        Failed to create Avahi client: Daemon not running
        Error sending Eaton <SCAN_REQUEST/> to <broadcast>, #2/3
        Error sending Eaton <SCAN_REQUEST/> to <broadcast>, #3/3
        [nutdev1]
        	driver = "usbhid-ups"
        	port = "auto"
        	vendorid = "051D"
        	productid = "0002"
        	product = "Back-UPS XS 1500M FW:947.d11 .D USB FW:d11"
        	serial = "3B2125X60993"
        	vendor = "American Power Conversion"
        	bus = "000"
        	device = "003"
        	busport = "001"
        
        

        See what usbdump shows.

        usbdump -d ugen0.3 # <- ugen0.2 in your case.
        
        06:01:38.926816 usbus0.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
        06:01:38.927034 usbus0.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
        06:01:38.927058 usbus0.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
        06:01:38.927285 usbus0.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
        06:01:38.927307 usbus0.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
        06:01:38.927411 usbus0.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
        06:01:38.927435 usbus0.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
        06:01:38.927656 usbus0.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=12,IVAL=0,ERR=0
        06:01:38.927692 usbus0.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
        06:01:38.927908 usbus0.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
        06:01:38.927948 usbus0.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
        06:01:38.928158 usbus0.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
        06:01:38.928190 usbus0.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
        06:01:38.928404 usbus0.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
        

        Try polling the UPS using the upsc command

        upsc apcups # <- UPS Name. Default is upsmon.  Yours might be EC650LCD based on your post.
        
        battery.charge: 99
        battery.charge.low: 10
        battery.charge.warning: 50
        battery.date: 2001/09/25
        battery.mfr.date: 2021/06/23
        battery.runtime: 3663
        battery.runtime.low: 120
        battery.type: PbAc
        battery.voltage: 27.3
        battery.voltage.nominal: 24.0
        device.mfr: American Power Conversion
        device.model: Back-UPS XS 1500M
        device.serial: 3B2125X60993  
        device.type: ups
        driver.debug: 0
        driver.flag.allow_killpower: 0
        driver.name: usbhid-ups
        driver.parameter.pollfreq: 30
        driver.parameter.pollinterval: 2
        driver.parameter.port: auto
        driver.parameter.synchronous: auto
        driver.state: quiet
        driver.version: 2.8.1.1
        driver.version.data: APC HID 0.100
        driver.version.internal: 0.52
        driver.version.usb: libusb-1.0.0 (API: 0x1000102)
        input.sensitivity: medium
        input.transfer.high: 139
        input.transfer.low: 88
        input.transfer.reason: input voltage out of range
        input.voltage: 122.0
        input.voltage.nominal: 120
        ups.beeper.status: enabled
        ups.delay.shutdown: 20
        ups.firmware: 947.d11 .D
        ups.firmware.aux: d11     
        ups.load: 11
        ups.mfr: American Power Conversion
        ups.mfr.date: 2021/06/23
        ups.model: Back-UPS XS 1500M
        ups.productid: 0002
        ups.realpower.nominal: 900
        ups.serial: 3B2125X60993  
        ups.status: OL CHRG
        ups.test.result: No test initiated
        ups.timer.reboot: 0
        ups.timer.shutdown: -1
        ups.vendorid: 051d
        
        
        B 1 Reply Last reply Reply Quote 0
        • B
          bigagt @elvisimprsntr
          last edited by

          @elvisimprsntr Thanks for the reply!

          running nut-scanner fails:

          ld-elf.so.1: Shared object "libssl.so.30" not found, required by "nut-scanner"
          

          usbdump -d ugen0.2
          Output attached.
          usbdump.txt

          E GertjanG 2 Replies Last reply Reply Quote 0
          • E
            elvisimprsntr @bigagt
            last edited by elvisimprsntr

            @bigagt

            What does the /usr/lib folder contain?

            /usr/lib: ls -lart libssl*
            -r--r--r--  1 root wheel  612912 Jun 28  2023 libssl.so.111
            -r--r--r--  1 root wheel  695488 Dec  6  2023 libssl.so.30
            lrwxr-xr-x  1 root wheel      12 Dec  6  2023 libssl.so -> libssl.so.30
            -r--r--r--  1 root wheel 3959538 Dec  6  2023 libssl.a
            
            

            Try -U option

            nut-scanner -U
            
            1 Reply Last reply Reply Quote 0
            • GertjanG
              Gertjan @bigagt
              last edited by

              @bigagt said in NUT + CPS EC650LCD not working:

              ld-elf.so.1: Shared object "libssl.so.30" not found, required by "nut-scanner"

              That's not good at all.
              nut-scanner, and probably all of the nut binaries, will fail.
              Messages like "Shared object "libssl.so.30" not found" mean that the installed package is to 'new' or your pfSense kernel version is to old ^^
              Can you upgrade to the way newer 2.8.0 Beta ? as its out for weeks now, and from what I can see here on the forum, it's quiet good / stable / usable.

              I'm using :
              f2681246-8fe1-47d2-ad6e-3eaed3f1c60b-image.png

              but that's with the latest pfSense Plus third (latest as of today) beta version.
              That version, and the latest "2.8.0" have much in common.

              nut-scanner -U
              give me :

              [25.03-BETA][root@pfSense.bhf.tld]/root: nut-scanner -U
              Scanning USB bus.
              [nutdev-usb1]
                      driver = "usbhid-ups"
                      port = "auto"
                      vendorid = "051D"
                      productid = "0002"
                      product = "Back-UPS XS 700U   FW:924.Z5 .I USB FW:Z5"
                      serial = "3BX926X61525"
                      vendor = "American Power Conversion"
                      # bus = "000"
                      # device = "002"
                      # busport = "003"
              

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

              1 Reply Last reply Reply Quote 0
              • dennypageD
                dennypage
                last edited by

                You have a mismatch between the OS (pfSense) and the installed nut package. Be sure to have the right version selected in updates, then remove and re-install the nut package.

                B 1 Reply Last reply Reply Quote 0
                • B
                  bigagt @dennypage
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.