Announcement

Collapse
No announcement yet.

Event Execution Delay Measurement Script discussion

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

  • Event Execution Delay Measurement Script discussion

    Where can I find the title'd discussion?

    I'd like to add a suggestion to update the associated device's last update time so I know at a glance the event is running properly.

    Also, what is required in order for the colored bars to appear? Which type of virtual device is required? I have 3 different virtual devices, virtual, virtual.1, and virtual.2. Virtual.1 did not seem to work properly as that one does not have an on/off button, and virtual.2 kind of worked, but regular plain virtual seemed to work best.
    huggy_d1

    Automating made easy

  • #2
    Event Delay Detection script can be found here: http://board.homeseer.com/showthread.php?t=155454

    Originally posted by huggy_d1 View Post
    Where can I find the title'd discussion?

    I'd like to add a suggestion to update the associated device's last update time so I know at a glance the event is running properly.

    Also, what is required in order for the colored bars to appear? Which type of virtual device is required? I have 3 different virtual devices, virtual, virtual.1, and virtual.2. Virtual.1 did not seem to work properly as that one does not have an on/off button, and virtual.2 kind of worked, but regular plain virtual seemed to work best.
    I didn't start a discussion thread. Didn't expect much discussion. Actually, I really didn't expect much attention at all. I'll link this thread.
    The colored bars? Do you mean the graphs? I just use J0n00VDGraphing to track the Delay device. I use a "Virtual" for the device. Gives me the option to turn it on or off for logging. It could be any type I suppose.

    Originally, I was updating the Device Last Change time only when one of the logging thresholds had been exceeded. Unfortunately, hs.SetDeviceValue seems to update the Device Time; so it's not possible to do that now.

    I'm going to look at the logging. No need of the html tags there. Simple fix.
    Last edited by Wadenut; August 19th, 2012, 08:52 AM.
    Real courage is not securing your Wi-Fi network.

    Comment


    • #3
      V1.03 fixes a problem with detection of delays greater than one second (the very reason this script was written).

      I do have one remaining concern.
      If event execution delays exceed 60 seconds, and the script is run at minute 59 for instance, it will probably not report properly at that time, as it has no idea in which minute the event actually was scheduled to be triggered. I may need to resort to a system variable to circumvent this. I want to avoid using an INI or other file for storage, as this would only increase execution time.
      Real courage is not securing your Wi-Fi network.

      Comment


      • #4
        Downloaded and installed on HSPro and HS Standard V.58 machines.

        Thanks Greg!

        As I was updating got the TTS warning and see this in the log. Just copying and pasting the new vb script via VNC did this on the HS Pro machine. Heard the warning right afterwards not doing anything. (2:31:04 PM).

        8/19/2012 2:26:47 PM Event Delay Currently 47.515 seconds [Delta: 46.586] Scripts running: Event Delay Check.vb
        8/19/2012 2:26:47 PM Warning Events seem to be delayed. Current delay is 47.515 seconds.Scripts running: Event Delay Check.vb
        8/19/2012 2:26:48 PM Event Delay Currently 48.14 seconds [Delta: 0.625] Scripts running: Event Delay Check.vb
        8/19/2012 2:26:48 PM Warning Events seem to be delayed. Current delay is 48.14 seconds.Scripts running: Event Delay Check.vb
        8/19/2012 2:27:08 PM Event Delay Currently 8.937 seconds [Delta: -39.203] Scripts running: Event Delay Check.vb
        8/19/2012 2:31:04 PM Event Delay Currently 4.393 seconds [Delta: 4.334] Scripts running: Event Delay Check.vb
        8/19/2012 2:32:00 PM Event Delay Currently 0.061 seconds [Delta: -4.332] Scripts running: Event Delay Check.vb
        Then I heard the TTS again.

        Ah seeing an event now on HS Pro box. (only one right now). I am not understanding though why I am seeing the huge delays now where as before I did not see them.

        8/19/2012 2:31:20 PM Event Delay Currently 20.593 seconds [Delta: 20.531] Scripts running: Event Delay Check.vb
        8/19/2012 2:31:20 PM Warning Events seem to be delayed. Current delay is 20.593 seconds.Scripts running: Event Delay Check.vb
        8/19/2012 2:31:21 PM Event Delay Currently 21.546 seconds [Delta: 0.953] Scripts running: Event Delay Check.vb
        8/19/2012 2:31:21 PM Warning Events seem to be delayed. Current delay is 21.546 seconds.Scripts running: Event Delay Check.vb,custom_cnn_headlines.txt
        8/19/2012 2:32:00 PM Event Delay Currently 0.062 seconds [Delta: -21.484] Scripts running: Event Delay Check.vb
        8/19/2012 2:33:09 PM Event Delay Currently 9.015 seconds [Delta: 8.953] Scripts running: Event Delay Check.vb
        8/19/2012 2:34:00 PM Event Delay Currently 0.062 seconds [Delta: -8.953] Scripts running: Event Delay Check.vb
        8/19/2012 2:35:55 PM Event Delay Currently 55.937 seconds [Delta: 55.875] Scripts running: Event Delay Check.vb
        8/19/2012 2:35:55 PM Warning Events seem to be delayed. Current delay is 55.937 seconds.Scripts running: Event Delay Check.vb
        8/19/2012 2:36:08 PM Event Delay Currently 8.921 seconds [Delta: -47.016] Scripts running: Event Delay Check.vb
        8/19/2012 2:37:00 PM Event Delay Currently 0.062 seconds [Delta: -8.859] Scripts running: Event Delay Check.vb
        8/19/2012 2:38:00 PM Event Delay Currently 0.062 seconds [Delta: 0] Scripts running: Event Delay Check.vb
        8/19/2012 2:39:08 PM Event Delay Currently 8.921 seconds [Delta: 8.859] Scripts running: Event Delay Check.vb
        8/19/2012 2:41:04 PM Event Delay Currently 4.218 seconds [Delta: -4.703] Scripts running: Event Delay Check.vb
        Nothing really except for one on the HS Standard box.

        8/19/2012 2:31:04 PM Event Delay Currently 4.393 seconds [Delta: 4.334] Scripts running: Event Delay Check.vb
        8/19/2012 2:32:00 PM Event Delay Currently 0.061 seconds [Delta: -4.332] Scripts running: Event Delay Check.vb
        8/19/2012 2:33:00 PM Event Delay Currently 0.069 seconds [Delta: 0.008] Scripts running: Event Delay Check.vb
        8/19/2012 2:34:00 PM Event Delay Currently 0.062 seconds [Delta: -0.007] Scripts running: Event Delay Check.vb
        8/19/2012 2:35:00 PM Event Delay Currently 0.07 seconds [Delta: 0.008] Scripts running: Event Delay Check.vb
        8/19/2012 2:36:00 PM Event Delay Currently 0.048 seconds [Delta: -0.022] Scripts running: Event Delay Check.vb
        8/19/2012 2:37:00 PM Event Delay Currently 0.072 seconds [Delta: 0.024] Scripts running: Event Delay Check.vb
        8/19/2012 2:38:00 PM Event Delay Currently 0.065 seconds [Delta: -0.007] Scripts running: Event Delay Check.vb
        8/19/2012 2:39:00 PM Event Delay Currently 0.057 seconds [Delta: -0.008] Scripts running: Event Delay Check.vb
        8/19/2012 2:40:00 PM Event Delay Currently 0.081 seconds [Delta: 0.024] Scripts running: Event Delay Check.vb
        8/19/2012 2:41:00 PM Event Delay Currently 0.059 seconds [Delta: -0.022] Scripts running: Event Delay Check.vb
        8/19/2012 2:42:00 PM Event Delay Currently 0.051 seconds [Delta: -0.008] Scripts running: Event Delay Check.vb
        8/19/2012 2:43:00 PM Event Delay Currently 0.06 seconds [Delta: 0.009] Scripts running: Event Delay Check.vb
        Last edited by Pete; August 19th, 2012, 02:44 PM.
        - Pete

        Auto mator
        Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
        Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

        X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

        Comment


        • #5
          Anyone else have issues downloadng?

          I keep getting invalid attachment.

          --Dan
          Tasker, to a person who does Homeautomation...is like walking up to a Crack Treatment facility with a truck full of 3lb bags of crack. Then for each person that walks in and out smack them in the face with an open bag.

          Comment


          • #6
            I'll re-upload it.
            Meantime there is another potential problem if delays are > 60 seconds. I'm working on the system variable to deal with both issues.
            Real courage is not securing your Wi-Fi network.

            Comment


            • #7
              Dan,

              I just checked and I can download it.

              Greg,

              I am seeing multiple delays but for whatever reason its not showing me the events causing the delays on the HS Pro machine.

              Changed the speak warning to 50 seconds for the time being.
              - Pete

              Auto mator
              Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
              Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

              X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

              Comment


              • #8
                I am seeing many delay warnings.

                Just to test I disabled Malware Malabytes and AVG just to see if anything changes. It doesn't make sense that I am seeing so many delays with the running events; even though I cannot see the events right now causing the delays.
                - Pete

                Auto mator
                Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
                Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

                X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                Comment


                • #9
                  I don't think it's going to be possible to track delays greater than 60 seconds. The reason for this is that there is simply no way to determine exactly when the script should have run. Even if I store the last run time in a variable, any existing delay greater than a minute is going to multiply the error each time the script runs.

                  Now, that being said, I welcome anyone to run with this and try to solve this problem.
                  Real courage is not securing your Wi-Fi network.

                  Comment


                  • #10
                    Watching a bit and with AV and Malware off checking not seeing over 60 seconds of a delay now.

                    I still don't see what events though are causing the delays; so instead just did a search on the event last to match the time.

                    Did find a CheaperRFID event - disabled plugin for now. Also disabled BLRFid for now for kicks.
                    Last edited by Pete; August 19th, 2012, 05:06 PM.
                    - Pete

                    Auto mator
                    Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
                    Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

                    X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                    Comment


                    • #11
                      Pretty interesting. My highest delta occurred during a ZWave poll, which failed:
                      Attached Files
                      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


                      • #12
                        OK, I've solved one problem.
                        I'll have to rewrite the doc a bit before posting.

                        Now (and I've tested this), the maximum reliably reported delay will be anything less than the run frequency.
                        For instance:
                        If the script is run once per minute, the max delay will be 59.999 seconds.
                        If run every two minutes, the max will be 119.999 seconds.
                        At five minutes, 299.999 seconds.
                        And so on.

                        I still want to try to do something about running before the hour, with a delay that extends past the hour.

                        Any thoughts?
                        Real courage is not securing your Wi-Fi network.

                        Comment


                        • #13
                          v1.04 is up. It solves the >60 sec delay problem and includes the updated doc.
                          Real courage is not securing your Wi-Fi network.

                          Comment


                          • #14
                            Will give it a try.

                            With the RFID plugins disabled, AV and Malware checking this is what I see now:

                            8/19/2012 6:12:00 PM Event Delay Currently 0.062 seconds [Delta: -2.359] Scripts running: Event Delay Check.vb
                            8/19/2012 6:13:00 PM Event Delay Currently 0.062 seconds [Delta: 0] Scripts running: Event Delay Check.vb
                            8/19/2012 6:14:00 PM Event Delay Currently 0.062 seconds [Delta: 0] Scripts running: Event Delay Check.vb
                            8/19/2012 6:16:02 PM Event Delay Currently 2.859 seconds [Delta: 2.797] Scripts running: Event Delay Check.vb
                            8/19/2012 6:16:02 PM Event Delay Currently 2.937 seconds [Delta: 0.078] Scripts running: Event Delay Check.vb
                            8/19/2012 6:17:00 PM Event Delay Currently 0.046 seconds [Delta: -2.891] Scripts running: Event Delay Check.vb
                            8/19/2012 6:18:00 PM Event Delay Currently 0.062 seconds [Delta: 0.016] Scripts running: Event Delay Check.vb
                            8/19/2012 6:19:00 PM Event Delay Currently 0.062 seconds [Delta: 0] Scripts running: Event Delay Check.vb
                            8/19/2012 6:21:01 PM Event Delay Currently 1.5 seconds [Delta: 1.438] Scripts running: Event Delay Check.vb
                            8/19/2012 6:21:02 PM Event Delay Currently 2.046 seconds [Delta: 0.546] Scripts running: Event Delay Check.vb
                            8/19/2012 6:22:00 PM Event Delay Currently 0.062 seconds [Delta: -1.984] Scripts running: Event Delay Check.vb
                            8/19/2012 6:23:00 PM Event Delay Currently 0.046 seconds [Delta: -0.016] Scripts running: Event Delay Check.vb
                            - Pete

                            Auto mator
                            Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
                            Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

                            X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                            Comment


                            • #15
                              Thank-you for the update Greg.

                              Redoing MythTV box and playing with a couple of Jogglers (totally disassembled now).....wife interrupted said endeavors with dinner.....

                              .... still want to try to do something about running before the hour, with a delay that extends past the hour.
                              Would that mean using another variable?

                              I'm still unable to see the events causing the delays. I did have one just now into the 44 second mark; FTP to my ISP; did the manual search of events to find it.

                              8/19/2012 7:26:44 PM Event Delay Currently 44.468 seconds [Delta: 44.422] Scripts running: Event Delay Check.vb
                              8/19/2012 7:26:44 PM Warning Events seem to be delayed. Current delay is 44.468 seconds.Scripts running: Event Delay Check.vb
                              8/19/2012 7:26:44 PM Event Delay Currently 44.687 seconds [Delta: 0.218999999999994] Scripts running: Event Delay Check.vb
                              8/19/2012 7:26:44 PM Warning Events seem to be delayed. Current delay is 44.687 seconds.Scripts running: Event Delay Check.vb
                              Last edited by Pete; August 19th, 2012, 07:43 PM.
                              - Pete

                              Auto mator
                              Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
                              Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

                              X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                              Comment

                              Working...
                              X