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

    NUT disconnects: Eaton SMART1500LCD

    Scheduled Pinned Locked Moved
    UPS Tools
    4
    31
    1.5k
    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.
    • H
      hspindel @pfsense4ever
      last edited by

      @pfsense4ever
      Please read through all the discussion above.

      I got the UPS to connect by adding RUN_AS_USER root to Additional configuration lines for upsmon.conf. However, @dennypage says in this discussion that adding a USB quirk is a better solution. Still working on that.

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

        [Wrong thread, sorry]

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

          @hspindel said in NUT disconnects: Eaton SMART1500LCD:

          My best guess at the line to install the quirk is:

          hw.usb.quirk.0="0x09ae 0x2012 0x0000 0xffff UQ_HID_IGNORE"

          But I am not at all confident I got that right. How does it look?

          Looks good to me.

          You can test without having to reboot by using this command:

          usbconfig add_dev_quirk_vplh 0x09ae 0x2012 0x0000 0xffff UQ_HID_IGNORE

          followed by disconnect and reconnect of the USB cable.

          There is a usbconfig option to show the attached driver if any. IIRC, it's show_ifdrv. Run it before and after the disconnect/reconnect and you should see that after there is no attached driver. Alternatively, you can simply try to start NUT (without root) to see if it works.

          Note that using usbconfig to install the quirk is temporary and will not survive a reboot. So assuming it works, you will want to install it properly in /boot/loader.conf.local.

          1 Reply Last reply Reply Quote 0
          • dennypageD dennypage referenced this topic on
          • dennypageD
            dennypage
            last edited by dennypage

            Please see here regarding testing of the new pfSense NUT package. I would appreciate any help you can offer. Thanks!

            [Note that the new package addresses the crash issue after successful start, but does not have anything regarding the quirk issue that prevents initial start]

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

              @hspindel Can you confirm that the quirk did in fact work? I'd like to use this as an example in a post I am doing explaining creating quirks. Thanks.

              H 2 Replies Last reply Reply Quote 0
              • H
                hspindel @dennypage
                last edited by

                @dennypage said in NUT disconnects: Eaton SMART1500LCD:

                @hspindel Can you confirm that the quirk did in fact work? I'd like to use this as an example in a post I am doing explaining creating quirks. Thanks.

                When I have a chance to test it, I will be happy to post the results. Been rather busy. :-)

                1 Reply Last reply Reply Quote 0
                • H
                  hspindel @dennypage
                  last edited by

                  @dennypage said in NUT disconnects: Eaton SMART1500LCD:

                  @hspindel Can you confirm that the quirk did in fact work? I'd like to use this as an example in a post I am doing explaining creating quirks. Thanks.

                  Mostly good results. Thank you for all the help.

                  1. The changes I had previously made to the NUT configuration were:

                  Extra Arguments to driver (optional)
                  interruptonly

                  Additional configuration lines for upsmon.conf
                  RUN_AS_USER root

                  Additional configuration lines for ups.conf
                  user=root
                  pollinterval=10

                  1. I deleted all of the above changes except pollinterval. Rebooted the pfSense router and verified that UPS connection did not work (as expected, wanted to make sure I was testing from a baseline).

                  2. Created the file /boot/loader.conf.local with contents:

                  hw.usb.quirk.0="0x09ae 0x2012 0x0000 0xffff UQ_HID_IGNORE"

                  1. Rebooted the pfSense router and was able to verify that the UPS was correctly monitored by NUT. Pulled the UPS power cord a couple times to verify that NUT detected that and it was handled correctly.

                  2. Left the configuration running. After about five minutes, NUT loses connection to the UPS. Only thing that fixed that was:

                    Extra Arguments to driver (optional): interruptonly

                  3. With the interruptonly flag present, the UPS connection is once again stable without need for setting root access. However,@dennypage mentioned above that this is not a good solution due to a memory corruption issue in the USB reconnect code (libusb). I am not seeing any problems and at present don't have a another solution that works.

                  4. Verified that with interruptonly present, NUT still responds correctly to unplugging and replugging the UPS.

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

                    @hspindel said in NUT disconnects: Eaton SMART1500LCD:

                    Excellent job creating the quirk!

                    Left the configuration running. After about five minutes, NUT loses connection to the UPS. Only thing that fixed that was:

                    Extra Arguments to driver (optional): interruptonly

                    Is this with the 2.8.0_2 package, or the new 2.8.1 package?

                    H 1 Reply Last reply Reply Quote 0
                    • H
                      hspindel @dennypage
                      last edited by

                      @dennypage said in NUT disconnects: Eaton SMART1500LCD:

                      @hspindel said in NUT disconnects: Eaton SMART1500LCD:

                      Excellent job creating the quirk!

                      Left the configuration running. After about five minutes, NUT loses connection to the UPS. Only thing that fixed that was:

                      Extra Arguments to driver (optional): interruptonly

                      Is this with the 2.8.0_2 package, or the new 2.8.1 package?

                      I am running 2.8.0_2. The package manager for pfSense+ doesn't list a 2.8.1 upgrade available.

                      This is on a Netgate 8200.

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

                        @hspindel said in NUT disconnects: Eaton SMART1500LCD:

                        I am running 2.8.0_2. The package manager for pfSense+ doesn't list a 2.8.1 upgrade available.

                        Please see the Call for testing here. I would appreciate it if you could give it a spin. Thanks.

                        H 1 Reply Last reply Reply Quote 0
                        • H
                          hspindel @dennypage
                          last edited by hspindel

                          @dennypage said in NUT disconnects: Eaton SMART1500LCD:

                          @hspindel said in NUT disconnects: Eaton SMART1500LCD:

                          I am running 2.8.0_2. The package manager for pfSense+ doesn't list a 2.8.1 upgrade available.

                          Please see the Call for testing here. I would appreciate it if you could give it a spin. Thanks.

                          TLDR: v2.8.1 so far is working well.

                          Documenting everything I encountered in case it helps anyone else.

                          1. Had a heckuva time finding the nut-devel-2023.10.07_1 package. Could not find it on Redmine. Unfortunately, didn't write down where I eventually found it. For future writeups, a direct link to the package would likely be helpful. Also, note that the full package name I found is amd64_nut_devel-2023.10.07_1.pkg. (Of course, this is hardware-specific - I am running on a Netgate 8200).

                          1. I downloaded the package to my PC. Had another heckuva time transferring the package to the pfSense router. Could not get ftp to work - ftp said "file not found." This was with both a Windows ftp server and a Linux ftp server tried with multiple login credentials. Eventually solved this problem by installing a tftp server on pfSense and a tftp client on Windows. File successfully transferred with tftp.

                          2. Using the pfSense GUI, I deleted the interruptonly flag.

                          3. Using the pfSense GUI, I stopped the UPS service.

                          4. SSH into pfSense+. Uninstalled NUT with pkg remove -fy nut. No problems seen.

                          5. Installed new NUT with pkg install -fy /tmp/amd64_nut-devel-2023.10.07_1.pkg. Only problem seen was I initially forgot the "amd64" in front of the name. Once I got the name right, the package installed without issue.

                          6. Back to the pfSense GUI, I started the UPS service. After a short time, the UPS service came up fine.

                          7. Pulled power and restored power to the UPS. Verified that the UPS service handled this correctly - no problems seen.

                          8. Noticed that the pfSense+ GUI still reports the nut package version as 2.8.0_2. Not particularly worried about that - just reporting it.

                          9. Without the interruptonly flag, v2.8.0_2 would disconnect and reconnect approximately every five minutes. v.2.8.1 has now been running for about 90 minutes with no issues seen. Will leave this running at least overnight, but it seems to be that v2.8.1 (along with the previously installed quirk) has fixed the issues I've seen.

                          Thank you very much to @dennypage for the excellent support in getting this working.

                          H 1 Reply Last reply Reply Quote 2
                          • H
                            hspindel @hspindel
                            last edited by hspindel

                            @dennypage
                            To further follow up: v.2.8.1 worked overnight with no issues! Just pulled power and reconnected as a final test, and NUT responded as expected.

                            dennypageD 1 Reply Last reply Reply Quote 1
                            • dennypageD
                              dennypage @hspindel
                              last edited by

                              @hspindel Excellent. Thank you for helping test.

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S stephenw10 moved this topic from pfSense Packages on
                              • First post
                                Last post