Announcement

Collapse
No announcement yet.

Event triggered manually, cannot re run for x minutes

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

  • rjh
    replied
    I am no ready to put out an official Beta, but if you need this fix, the Windows installer for 455 is here:

    http://homeseer.com/updates3/SetupHS3_3_0_0_455.msi

    Leave a comment:


  • rprade
    replied
    Originally posted by mikee123 View Post
    When there is a newer release version, will I get the prompt to update still (as I am on a beta) ?
    Yes, as long as "Check for HS3 Update at Startup" is enabled in setup. It just looks for a higher version than what is installed at startup, regardless of whether you are running a beta or release version.

    Leave a comment:


  • mikee123
    replied
    When there is a newer release version, will I get the prompt to update still (as I am on a beta) ?

    Leave a comment:


  • rprade
    replied
    Yes .455 is a beta. It is at https://homeseer.com/updates3/SetupHS3_3_0_0_455.msi

    I can confirm it is fixed. I just enabled my test events again

    Click image for larger version

Name:	Capture.PNG
Views:	1
Size:	49.8 KB
ID:	1197447

    The script:
    Code:
    Sub Main(Parm As Object)
        hs.WriteLog("Trace", "Event Test 1 ran")
        hs.triggerevent("Test 2")
    end sub
    And here are the log results

    Jul-09 12:04:48 PM Trace Event Test 1 ran
    Jul-09 12:03:48 PM Trace Event Test 1 ran
    Jul-09 12:02:48 PM Trace Event Test 1 ran
    Jul-09 12:02:48 PM Trace Test 2 Event Ran
    Jul-09 12:01:48 PM Trace Event Test 1 ran
    Jul-09 12:00:48 PM Trace Event Test 1 ran
    Jul-09 11:59:48 AM Trace Event Test 1 ran
    Jul-09 11:58:48 AM Trace Event Test 1 ran
    Jul-09 11:57:48 AM Trace Event Test 1 ran
    Jul-09 11:57:48 AM Trace Test 2 Event Ran
    Jul-09 11:56:48 AM Trace Event Test 1 ran
    Jul-09 11:55:48 AM Trace Event Test 1 ran
    Jul-09 11:54:48 AM Trace Event Test 1 ran
    Jul-09 11:53:48 AM Trace Event Test 1 ran
    Jul-09 11:52:48 AM Trace Event Test 1 ran
    Jul-09 11:52:48 AM Trace Test 2 Event Ran
    Jul-09 11:51:48 AM Trace Event Test 1 ran
    Jul-09 11:50:48 AM Trace Event Test 1 ran
    Jul-09 11:49:48 AM Trace Event Test 1 ran
    Jul-09 11:48:48 AM Trace Event Test 1 ran
    Jul-09 11:47:48 AM Trace Event Test 1 ran
    Jul-09 11:47:48 AM Trace Test 2 Event Ran
    Jul-09 11:46:48 AM Trace Event Test 1 ran
    Jul-09 11:45:48 AM Trace Event Test 1 ran
    Jul-09 11:44:48 AM Trace Event Test 1 ran
    Jul-09 11:43:48 AM Trace Event Test 1 ran
    Jul-09 11:42:48 AM Trace Event Test 1 ran


    As you can see, the 5 minute "Cannot Re-Run For:" is now respected when called by a script. It was already respected when called from another Event or launched from the Event Management page.

    Thank you Rich
    Last edited by rprade; July 9th, 2018, 01:05 PM.

    Leave a comment:


  • mikee123
    replied
    Thats good. I'll try over the next few days. I guess .455 is a beta ?

    Leave a comment:


  • rjh
    replied
    This is fixed in HS3 build 3.0.0.455. Calling hs.TriggerEvent now honors the "cannot re-run for X # minutes" setting.

    Leave a comment:


  • mikee123
    replied
    There should be an easy workaround, for the time being at least, I have created another event which runs the event originally triggered by the script. The script does run the event which runs the original event. That way, the event which cannot re run for x minutes is triggered by another event. So that should work...

    Leave a comment:


  • rprade
    replied
    Originally posted by zwolfpack View Post
    Could it be that triggering from scripting function works differently that triggering solely thru event engine?
    I thought of the same thing and you are correct. The scripting call hs.TriggerEvent apparently will run a second event regardless of the "Cannot Re-Run" setting. In the test I outlined above I changed the triggering of the second event to a script and both events run once a minute, even though the second event is set to Cannot Re-Run for 5 minutes. I sent Rich an email letting him know the specifics of this issue.

    Leave a comment:


  • zwolfpack
    replied
    Could it be that triggering from scripting function works differently that triggering solely thru event engine?
    event is triggered by a script command: hs.TriggerEvent("AC close bedroom windows") every 3 minutes

    Leave a comment:


  • rprade
    replied

    Jun-30 6:20:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:19:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:19:04 PM Event Event Trigger "HomeSeer Demo Test 2"
    Jun-30 6:18:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:17:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:16:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:15:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:14:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:14:04 PM Event Event Trigger "HomeSeer Demo Test 2"
    Jun-30 6:13:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:12:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:11:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:10:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:09:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:09:04 PM Event Event Trigger "HomeSeer Demo Test 2"
    Jun-30 6:08:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:07:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:06:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:05:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:04:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:04:04 PM Event Event Trigger "HomeSeer Demo Test 2"
    Jun-30 6:03:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:02:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:01:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 6:00:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 5:59:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-30 5:59:04 PM Event Event Trigger "HomeSeer Demo Test 2"

    Leave a comment:


  • mikee123
    replied
    For me the cannot re run for x minutes does not work. Sometimes it seems to stop execution of the event, other times its still running. I am trying to find a pattern, so far I havent. After the event triggered, (I have a cannot re run for 10 minutes), I triggered a manual run. It did not run. I clicked run again, and it triggered. That was within 2 minutes of the event running. Before that I noticed, the event run every 3 minutes, even though cannot run for 10 minutes is selected. The event is triggered by a script command: hs.TriggerEvent("AC close bedroom windows") every 3 minutes

    Jun-30 22:10:38 Event Event Trigger "Notifications TTS AC close bedroom windows"
    Jun-30 22:10:38 Event Event Notifications TTS AC close bedroom windows triggered by the event page 'Run' button.
    Jun-30 22:10:26 Event Event Notifications AC close bedroom windows triggered by the event page 'Run' button.
    Jun-30 22:07:27 Event Event Trigger "Notifications AC close bedroom windows"
    Jun-30 22:04:27 Event Event Trigger "Notifications AC close bedroom windows"
    Jun-30 22:01:27 Event Event Trigger "Notifications AC close bedroom windows"
    Jun-30 21:58:27 Event Event Trigger "Notifications AC close bedroom windows"
    Jun-30 21:55:27 Event Event Trigger "Notifications AC close bedroom windows"
    Jun-30 21:52:27 Event Event Trigger "Notifications AC close bedroom windows"

    .
    Attached Files

    Leave a comment:


  • rprade
    replied

    Leave a comment:


  • rprade
    replied
    Maybe it is possible the second event will run again when called from a different event. I didn’t test that. I will do so later today. I’ll set up a third event that calls the second and see what happens.

    Leave a comment:


  • S-F
    replied
    Odd. I have a situation that occurs every single day where this isn't the case. When I get home as determined by my phone connecting to the wi-fry network a manually run event is called. Then it is called again when I enter my PIN at the door. Without fail the even runs twice. This happens EVERY SINGLE DAY! The secondary event wakes my PC and fires up the browser and a few other applications. By the time I sit down at the computer there are two instances of all of these applications running. It's a PITA. It wasn't an issue with my older PC as it booted faster so by the time I was entering my PIN at the door it would already be up and running and a condition of the secondary event is that my PC not be running but the newer PC is a little more industrial/commercial and takes a lot longer to boot.

    Leave a comment:


  • rprade
    replied
    Originally posted by S-F View Post
    This is not the case for a manually triggered event that's called from another event. The cannot re-run for is not respected. I filed a bug report on this a little over a year ago. I'm sure nobody at HST cares. I'm not sure if it's the same for a script though.
    Hmm. It worked when I first tested it several years ago. I did confirm that it is respected when the event is manually run from the events page before posting above.

    Just to confirm what you are reporting, I set up these two Events. Test 2 cannot be rerun for 1 minute.

    Click image for larger version

Name:	Capture.PNG
Views:	1
Size:	41.9 KB
ID:	1197261

    I manually triggered test 1 at 5:41:54 and test 2 ran. I ran test 1 a second time within 5 seconds at 5:42:04 and test 2 did not run. These log entries are in reverse chronological order, but they confirm that test 2 only ran once, the first time event 1 was run. After a couple of minutes at 5:44:21 test 1 would run test 2 test 2 again.

    Jun-26 5:44:26 PM Event Deleting event after run: "Delayed Actions Vanity Lights (Delayed Action)"
    Jun-26 5:44:26 PM Event Event Trigger "Delayed Actions Vanity Lights (Delayed Action)"
    Jun-26 5:44:21 PM Event Event Trigger "HomeSeer Demo Test 2"
    Jun-26 5:44:21 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-26 5:44:21 PM Event Event HomeSeer Demo Test 1 triggered by the event page 'Run' button.
    Jun-26 5:42:04 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-26 5:42:04 PM Event Event HomeSeer Demo Test 1 triggered by the event page 'Run' button.
    Jun-26 5:41:59 PM Event Deleting event after run: "Delayed Actions Vanity Lights (Delayed Action)"
    Jun-26 5:41:59 PM Event Event Trigger "Delayed Actions Vanity Lights (Delayed Action)"
    Jun-26 5:41:57 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-26 5:41:57 PM Event Event HomeSeer Demo Test 1 triggered by the event page 'Run' button.
    Jun-26 5:41:54 PM Event Event Trigger "HomeSeer Demo Test 2"
    Jun-26 5:41:54 PM Event Event Trigger "HomeSeer Demo Test 1"
    Jun-26 5:41:54 PM Event Event HomeSeer Demo Test 1 triggered by the event page 'Run' button.

    It appears to be working as I described here. How is it not working for you?

    Leave a comment:

Working...
X