Does this trigger do what I think/hope?

[sbessel]

I am looking to auto-unlock a door and am running into an issue where my event won't trigger.



use these constants;

Scott Home =100=Home
Scott Home =0=Away

What I think/need it to do is be TRUE if Scott Home is home/100 for no more than 5 minutes.

I am trying to trigger only if I am HOME/100 but not home for longer than 5 minutes.

I have tried all sorts of iterations but I am stumped and it is not working,
I posted all of the details in https://forums.homeseer.com/forum/ho...r-unlock-logic
but I am thinking I am completely off-base on my thinking of how EasyTrigger triggers

thanks,

Scott

[George]

Those are AND IF's. Where is your originating IF statement? The event will only trigger on an IF statement being true, then it evaluates the AND IF's.

[sbessel]

Those are AND IF's. Where is your originating IF statement? The event will only trigger on an IF statement being true, then it evaluates the AND IF's.

The IF works fine and is not the issue, my question was specific to the EasyTrigger portion.

[teladog01]

I am looking to auto-unlock a door and am running into an issue where my event won't trigger.

Your event doesn't trigger because these two conditions can never be true at the same time. One condition specifies the device value is 100, the other condition specifies the device value is NOT 100. How can that possibly ever be true?

Try using the Easy Trigger condition "This device's value has changed in the last 5 minutes" instead of the "has not been in range" condition.

[randy]

I am looking to auto-unlock a door and am running into an issue where my event won't trigger.



use these constants;

Scott Home =100=Home
Scott Home =0=Away

What I think/need it to do is be TRUE if Scott Home is home/100 for no more than 5 minutes.

I am trying to trigger only if I am HOME/100 but not home for longer than 5 minutes.

I have tried all sorts of iterations but I am stumped and it is not working,
I posted all of the details in https://forums.homeseer.com/forum/ho...r-unlock-logic
but I am thinking I am completely off-base on my thinking of how EasyTrigger triggers

thanks,

Scott

That condition will only be true if your virtual device has been at some value other than 100 for 5 minutes or longer. There may be other solutions, but I would start a timer when you get home with one event when your virtual device changes to Home. Then use the timer as a condition in your second event. This event starts my timer:



Starting a timer always sets it to 0 and starts it running.

Here is an example of the event to control the lock:

[sbessel]

Your event doesn't trigger because these two conditions can never be true at the same time. One condition specifies the device value is 100, the other condition specifies the device value is NOT 100. How can that possibly ever be true?

Try using the Easy Trigger condition "This device's value has changed in the last 5 minutes" instead of the "has not been in range" condition.

What I was assuming is that the first statement was true based on being home/100 for less than 5 minutes, if longer it would be false, is this an incorrect assumption?
Which is why I asked here hoping spud could help

I did take your suggestion and will test this later today:

I am not sure if this will have the same desired effect, but I am hopeful.

thanks,

Scott

[Uncle Michael]

Not knowing what your trigger is, this suggestion is a bit speculative, but have you considered the EasyTrigger Trigger "device was and becomes"?
That is, use the trigger: If Automation Virtual Scott Home Was Away and Becomes Home

[teladog01]

Not knowing what your trigger is, this suggestion is a bit speculative, but have you considered the EasyTrigger Trigger "device was and becomes"?
That is, use the trigger: If Automation Virtual Scott Home Was Away and Becomes Home

Of course the OP could use this trigger if they wanted, but the trigger is irrelevant. My understanding is that the crux of the question is how to trigger when home, but only when home for less than five minutes.

[randy]

Of course the OP could use this trigger if they wanted, but the trigger is irrelevant. My understanding is that the crux of the question is how to trigger when home, but only when home for less than five minutes.

Correct and the Easy Trigger solution he just implemented will do that well.

[sbessel]

I appreciate the feedback and I do have a working solution, but my real question was to spud as to the exact nature of this trigger.
It can be interpreted a couple of ways;
normal reading, right to left;
Is Scott not home and not home for for at least 5 minutes
programmer logic;
Is (Scott home for at least 5 minutes) NOT

The programmer method was what my brain is used to and what I assumed, but it appears not to work that way.
Because I am used to statements in parens that are tested and the NOT operator before negates the statement.

The first method makes no sense to me.

I am still hoping spud can come in with the real answer.

[spud]

The condition "has not been in range [X, Y] for at least 5 minutes" is true when the device's value has been either lower than X or greater than Y for at least 5 minutes

so I guess it's your first interpretation