Announcement

Collapse
No announcement yet.

Lost Delayed Action Event Triggers

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

    Lost Delayed Action Event Triggers

    Has anybody been losing delayed action event triggers? I have been using the following event for testing my Schlage door lock:

    Click image for larger version

Name:	2019-05-08_10-20-49.jpg
Views:	210
Size:	44.1 KB
ID:	1303534
    Most of the time this event runs exactly as expected. The HS3 log snippet below shows that the test event triggered at 30 seconds after the hour, as expected, and the door was unlocked (first event action), as expected. However, the second event action (to relock the door after a 10 second delay) was never triggered.

    Click image for larger version

Name:	2019-05-08_10-33-58.jpg
Views:	67
Size:	57.1 KB
ID:	1303535
    This event ran as expected for several hourly iterations both before and after the one in question. It is noted (but probably irrelevant) that the failed iteration is the first one of a new calendar day. I stipulate, but don't know how to demonstrate, that I wasn't doing anything to cancel scheduled events.

    Help, anyone?

    Current Date/Time: 5/8/2019 10:58:11 AM
    HomeSeer Version: HS3 Pro Edition 3.0.0.500
    Linux version: Linux hometrollerSEL 3.16.0-031600-generic #201408031935 SMP Sun Aug 3 23:56:17 UTC 2014 i686 i686 i686 GNU/Linux System Uptime: 11 Days 14 Hours 14 Minutes 22 Seconds
    IP Address: 127.0.0.1
    Number of Devices: 232
    Number of Events: 79
    Available Threads: 199
    HSTouch Enabled: True
    Event Threads: 0
    Event Trigger Eval Queue: 0
    Event Trigger Priority Eval Queue: 0
    Device Exec Queue: 0
    HSTouch Event Queue: 0
    Email Send Queue: 0

    Enabled Plug-Ins
    1.0.0.148: Arduino Plugin
    3.0.19.0: BLLock
    1.0.1.0: BLTEDPro
    1.3.7.0: Device History
    3.0.0.63: EasyTrigger
    3.0.2.20: OMNI
    3.0.1.248: Z-Wave
Working...
X