Announcement

Collapse
No announcement yet.

ACPUPSD Plug-in for HS2

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    ACPUPSD Plug-in for HS2

    Attached is the APCSUPSD plug-in for HS2. The APCUPSD allows HS2 to monitor multiple APC UPS devices. Each monitored UPS device must be running apcupsd (http://www.apcupsd.org). The plugin will communicate with apcupsd via a TCP/IP connection. The primary features:
    • Monitors local UPS or UPS attached to remote computers
    • Monitor up to 5 ups services
    • Retrieves UPS information for APCUPSD software which must be running on target computes
    • HS2 devices for each monitored UPS
    • Event triggers
    • Event actions
    • Trend chart of power line voltage, load and battery charge

    Compatibility
    This plugin requires HS2 Version 2.3 or higher.

    Version History
    Version 1.4.2.2
    • Initial version posted to Forum

    Attached is the ZIP of the files to install. To install, run the MSI included in the zip file and for new installation only, copy the ini file from the zip file to the config folder in the HS2 installation.

    Post any questions, comments, or issues with the APCUPSD plug-in in the discussion thread (here: http://board.homeseer.com/showthread.php?p=1112974 ).
    Attached Files
    Last edited by pcp; March 28, 2014, 07:01 AM.

    #2
    HS2 UPS Devices
    Attached Files

    Comment


      #3
      UPS Monitoring
      Attached Files

      Comment


        #4
        HS2 UPS Triggers
        Attached Files

        Comment


          #5
          Got this plugin installed and working.
          When using the 'Low Battery Charge Trigger', at what charge value does that trigger? and is it adjustable?
          Dick
          HS PRO 2.5.0.81, WinXP, IE8, Shuttle XS35V3, 2.13GHz, 4GB, 40GB SSD drive, AC-RF2, ADIOcelot, Message Server, TI103, SNEVL CID, pjcOutlook, MCSTemperature, Powertrigger, BLBackup, BLFloorplan, BLIcon, BLOccupied, BLRadar, BLRfid, BLLogMonitor, ACPUPSD, UltraECM, WeatherXML & Stipus' script connector. 500+ devices, 260+ events, 1-wire weather station + temp/humidity sensors & Oregon Scientific temp & humidity sensors & 2 Brultech ECM-1240s

          Comment


            #6
            The thresholds are in the configuration of the specific ups. There is s trigger threshold and a reset threshold (cannot re-trigger before reaching the reset threshold).

            Comment


              #7
              Originally posted by pcp View Post
              The thresholds are in the configuration of the specific ups. There is s trigger threshold and a reset threshold (cannot re-trigger before reaching the reset threshold).
              To verify, if I set the 'low battery charge trigger' and 'low battery charge reset' to 30 and 50 respectively an event using the 'low battery charge trigger' would trigger if the battery charge went below 30 and could not trigger again until it returned to above 50? Right??
              Using this sounds like the right trigger to begin a sequence of events to gracefully shut things down when the power has gone out. Does that sound right?
              Dick
              HS PRO 2.5.0.81, WinXP, IE8, Shuttle XS35V3, 2.13GHz, 4GB, 40GB SSD drive, AC-RF2, ADIOcelot, Message Server, TI103, SNEVL CID, pjcOutlook, MCSTemperature, Powertrigger, BLBackup, BLFloorplan, BLIcon, BLOccupied, BLRadar, BLRfid, BLLogMonitor, ACPUPSD, UltraECM, WeatherXML & Stipus' script connector. 500+ devices, 260+ events, 1-wire weather station + temp/humidity sensors & Oregon Scientific temp & humidity sensors & 2 Brultech ECM-1240s

              Comment


                #8
                Yes that is correct.

                I do not remember and will need to double check if it applies to the HS2 version of the plugin, the value of the device tracking the remaining time is the number of remaining seconds (well as said double check). and you trigger on this device value as well. Just another option.

                Comment


                  #9
                  Originally posted by pcp View Post
                  Yes that is correct.

                  I do not remember and will need to double check if it applies to the HS2 version of the plugin, the value of the device tracking the remaining time is the number of remaining seconds (well as said double check). and you trigger on this device value as well. Just another option.
                  Were you able to check on this?
                  Dick
                  HS PRO 2.5.0.81, WinXP, IE8, Shuttle XS35V3, 2.13GHz, 4GB, 40GB SSD drive, AC-RF2, ADIOcelot, Message Server, TI103, SNEVL CID, pjcOutlook, MCSTemperature, Powertrigger, BLBackup, BLFloorplan, BLIcon, BLOccupied, BLRadar, BLRfid, BLLogMonitor, ACPUPSD, UltraECM, WeatherXML & Stipus' script connector. 500+ devices, 260+ events, 1-wire weather station + temp/humidity sensors & Oregon Scientific temp & humidity sensors & 2 Brultech ECM-1240s

                  Comment


                    #10
                    Not yet but plan tonight. If you view the device properties in hs2 and has a nonzero value it should be time time span in seconds

                    Comment


                      #11
                      I checked. The device value of the remaining time is not set to the value in seconds, only the device string is set. Use the triggers as you already planned.

                      Comment

                      Working...
                      X