Announcement

Collapse
No announcement yet.

Event Execution Delay Measurement Script

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

  • Event Execution Delay Measurement Script

    Poor mans HS2Sentry.

    From time to time, Event execution by Homeseer may become delayed due to uncontrolled resource management by HS, plugins, scripts or external influences.
    This script is capable of detecting this situation and taking action before the system becomes unuseable. This is useful under HS Standard where no software watchdog (HS2Sentry) exists as well as under HSPRO as an aid in analysing potential problems.

    Full documentation is in the ZIP.

    Features:
    Tracks event execution delay times in a Device String and Value.
    Optionally logs all activity controlled by the device status.
    Optionally logs warnings if execution time is greater than an independently set threshold.
    Optionally speaks a warning if execution time is greater than an independently set threshold.
    Optionally attempts to force a system restart if execution time is greater than an independently set threshold.

    Discussion can be found here: http://board.homeseer.com/showthread.php?t=155468
    Attached Files
    Last edited by Wadenut; November 19th, 2014, 12:39 PM.
    Real courage is not securing your Wi-Fi network.

  • #2
    Up and running here, Wadenut. What deltas are you and others getting?
    HS3Pro Running on a Raspberry Pi3
    64 Z-Wave Nodes, 168 Events, 280 Devices
    UPB modules via OMNI plugin/panel
    Plugins: Z-Wave, BLRF, OMNI, HSTouch, weatherXML, EasyTrigger
    HSTouch Clients: 3 Android, 1 Joggler

    Comment


    • #3
      Normally, I see about +/-1 ms. But when HS starts having problems, I've seen as much as +/-600 ms, and a gradual increase in ex times.

      I'm glad such a simple script can be of use to others.
      Real courage is not securing your Wi-Fi network.

      Comment


      • #4
        Update: v1.02 html tags are no longer written as text to the GUI log.
        Real courage is not securing your Wi-Fi network.

        Comment


        • #5
          1.05 has no functional improvments.
          Simply replaced Writelogex with Writelog for the benefit of those running older versions of Homeseer.
          Real courage is not securing your Wi-Fi network.

          Comment


          • #6
            v1.08 is posted above.
            Additional functions are described within the included documentation.
            Thanks go to Jon00 for his useful suggestions.
            Real courage is not securing your Wi-Fi network.

            Comment


            • #7
              v1.08.01
              Fixed a small bug.
              If graphing only was selected in v1.08, the calculated Min/Max values would be incorrect (=0).
              These values are also optionally provided as part of the graphing process (Jon00VDGraphing) and so were removed from the resulting device string.
              If TrackDV is selected, the Min/Max values are calculated and included withing the device strings.
              Real courage is not securing your Wi-Fi network.

              Comment


              • #8
                v1.12
                Fixed a couple of bugs no-one happened to notice.
                Moved configuration to an INI file
                Added several options.

                Will now detect delays in excess of the trigger period.


                I stongly suggest reading the included documentation prior to using, especially if upgrading from a previous version.
                Real courage is not securing your Wi-Fi network.

                Comment


                • #9
                  v1.12.1
                  - Fixes a small bug where the minimum delay time might become negative. This has occurred when the event frequency or the TriggerFrequency parameter in the configuration file are altered in vivo.
                  - Trigger Frequency is moved from the configuration to become a parameter to the running script. This makes altering the run frequency a one step process. Existing events will need to be modified as a result.
                  There should be no need for existing users to replace the configuration file. The old TriggerFrequency parameter in the Config section is now obsolete and can be removed if desired.

                  Full documentation has been updated accordingly.

                  This is a mod I've been using for some time now, but had forgotten to post.
                  Real courage is not securing your Wi-Fi network.

                  Comment

                  Working...
                  X