Problem with Timers Not Being Evaluated Correctly

[drewp001]

Please take a look at this and tell me what I'm doing wrong in this example below. The below event will run when resetting timer 2 before timer 1 and it should not. The comparison acts as if it is being ignored.



Current Date/Time: 2/3/2019 2:46:44 PM
HomeSeer Version: HS3 Pro Edition 3.0.0.500
Operating System: Microsoft Windows Server 2019 Standard - Server
System Uptime: 1 Day 18 Hours 41 Minutes 1 Second
IP Address: 192.168.1.12
Number of Devices: 223
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

[sparkman]

Your attachment is not showing, but instead shows:

{"data-align":"none","data-size":"full","data-attachmentid":1282039}

[drewp001]

Odd, image attached again, hopefully.

[randy]

The problem may be that timer devices are a representation of actual timers and there is a delay in their being updated. Your first two conditions use actual timers and the third uses the HS Devices. When you reset timer 2, the second condition becomes instantly true, but the HS device used in the comparison may lag by more than a second. The HS devices were only added so that you can look at time values, but they are not designed to be used as Triggers or Conditions in Events. Because of the overhead they cause, I have deleted all of my HS timer devices except those that I want to see in HSTouch or the Device Manager.

If you watch a timer Device in Device Manager, you will see that they usually jump 2 or more seconds at a time.

[drewp001]

Yep, okay, makes sense, thanks! But "A Timers Value Is" is an option in the triggers list so I thought it should be good. I have reworked it to also require a state change in addition to timer value and it is good now, so supports your explanation.

[randy]

Yep, okay, makes sense, thanks! But "A Timers Value Is" is an option in the triggers list so I thought it should be good. I have reworked it to also require a state change in addition to timer value and it is good now, so supports your explanation.

"A Timers Value Is" is good because it uses an actual timer, Counters-Timers Timer 1 used in the Easy Trigger comparison is a representation of an actual timer.

[drewp001]

So an Easy Trigger bug/limitation.Good to know, thanks!

[randy]

So an Easy Trigger bug/limitation.Good to know, thanks!

No, not an Easy Trigger bug or problem, it is an issue with HomeSeer Timer Devices. Spud's plug-in only deals with HS devices and can only react to devices. Since those devices have latency from the actual timers and Easy Trigger only deals with devices it has no way of dealing with the difference between an actual timer (which is not a device) and the HS device representing the timer.

[drewp001]

Understood, Thank You!