Announcement

Collapse
No announcement yet.

Problem with Timers Not Being Evaluated Correctly

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

  • Problem with Timers Not Being Evaluated Correctly

    Just ramping up on HS3 and loving it! But this timer business has me stumped.

    Please take a look at this and tell me what I'm doing wrong. The idea is that I have two driveway motion sensors that reset a timer when triggered. I use these timers to understand when an event occurred and then use the difference between the timer values to understand if it is an arrival or departure event. The arrive and depart events will trigger at the same time seeming to ignore the "Comparison between 2 device values is true" expression.

    The debug log shows timer 58 (Driveway Sensor Motion Timer 2) being reset to 0 at 1:32:06
    The log then shows timer 56 (Driveway Sensor Motion Timer 1) being reset to 0 at 1:32:09 at the same time the "Driveway Alarm Event - Arrive" event triggered.
    But the "Comparison between 2 device values is true" also requires timer 56 to be greater than timer 58, which it is not.
    So, why is this being triggered?

    Any help would be appreciated. Thanks!

    I will add that there is an option set for this event to not rerun for 30 seconds.


    Click image for larger version

Name:	ScreenHunter 156.png
Views:	17
Size:	47.9 KB
ID:	1282399Click image for larger version

Name:	ScreenHunter 158.png
Views:	17
Size:	109.0 KB
ID:	1282398Click image for larger version

Name:	ScreenHunter 159.png
Views:	17
Size:	417.2 KB
ID:	1282400Click image for larger version

Name:	ScreenHunter 161.png
Views:	41
Size:	73.7 KB
ID:	1282397


    Current Date/Time: 2/3/2019 2:15:25 PM
    HomeSeer Version: HS3 Pro Edition 3.0.0.500
    Operating System: Microsoft Windows Server 2019 Standard - Server
    System Uptime: 1 Day 18 Hours 9 Minutes 42 Seconds
    IP Address: 192.168.1.12
    Number of Devices: 221
    Number of Events: 34
    Available Threads: 1023
    HSTouch Enabled: True
    Event Threads: 32
    Event Trigger Eval Queue: 0
    Event Trigger Priority Eval Queue: 0
    Device Exec Queue: 0
    HSTouch Event Queue: 0
    Email Send Queue: 0
    Anti Virus Installed:
    In Virtual Machine: Yes
    Enabled Plug-Ins
    3.1.3.33206: Blue-Iris
    3.0.0.56: EasyTrigger
    1.2.0.72: Life360
    0.0.0.45: Pushover 3P
    3.0.6413.20219: UltraNetCam3
    3.0.1.252: Z-Wave
    Last edited by drewp001; February 4th, 2019, 08:07 PM. Reason: Trying agin to add images.

  • #2
    Your attachments are not visible to me, but I do this a slightly different way. When each sensor is tripped it runs an event that turns on a virtual device, then turns it off again after a reasonable delay. It also runs another event that checks to see if the virtual device corresponding to the other sensor is on. If it is then the vehicle triggered the other sensor first.
    Mike____________________________________________________________ __________________
    HS3 Pro Edition 3.0.0.548

    HW: Stargate | NX8e | CAV6.6 | Squeezebox | PCS | WGL 800RF, Rain8Net+ | RFXCOM | QSE100D | Vantage Pro | Green-Eye | X10: XTB-232, -IIR | Edgeport/8 | Way2Call | Ecobee3

    Comment


    • #3
      Thanks UM, may have to give that a look!

      I did get this to work be replacing the "if timer less than value" with what you see below. Seems like there is is timing issue where the time will be reset to less than 30 which will trigger the event but the value presented to the next expression is still the old value. Pretty sure this is a bug, but I realize that my trigger usage may have been less than ideal to start since I had to use the "Cannot Re-Run For:" option set to 30 seconds to not get repeating triggers.

      Click image for larger version

Name:	ScreenHunter 165.png
Views:	17
Size:	37.1 KB
ID:	1282405

      Comment

      Working...
      X