Multiple Trigger Expressions

Do multiple trigger expressions ever turn false, or do you just use the true timestamp with the condition in repeat mode?

I have this condition as “LivingRoomOccupied” and once it turned true the first time, it hasn’t gone back to false, even though none of the sensors has been tripped in several hours…

(LRMotion or (LROccupancy @ 3 < 10:00) or (KitchenOccupancy @ 3 < 10:00))

I guess I should say I am expecting this condition to be true if the motion detector is currently active, or if one of the occupancy sensors has been tripped three times in the last 10 minutes…

[quote=“wilme2, post:1, topic:181327”]Do multiple trigger expressions ever turn false, or do you just use the true timestamp with the condition in repeat mode?

I have this condition as “LivingRoomOccupied” and once it turned true the first time, it hasn’t gone back to false, even though none of the sensors has been tripped in several hours…

(LRMotion or (LROccupancy @ 3 < 10:00) or (KitchenOccupancy @ 3 < 10:00))[/quote]

Your problem is in the “@ 3 < 10:00”

But for your knowledge its always a good idea when you get into this problem to make a few extra temporary conditions then split up your code.

Run threw your house a bit then come back and check the report to see which part is staying true and such. So in this case you can split this up in 3 conditions

test = LRMotion

test1 = LROccupancy @ 3 < 10:00

test2 = KitchenOccupancy @ 3 < 10:00

Anyways the way the test1 and test2 are written above once its true i don’t think it will turn false. Like saying
“after 5 min of a motion become true” there is no false written into it. You’ll have to rewrite it with an “and” or other trigger to get it to kick back to false after a delay or something like that.

Tell us what your trying to accomplish and we can come up with something.

That makes sense but

True for how long? there is no off time on this.

You motion will trip, then reset (built into the motion it’s self) so that will go true then go back false but the rest of the statement currently wont.

Anyways the way the test1 and test2 are written above once its true i don't think it will turn false.

Test 1 will go false if it took more than 10 minutes for the last 3 LROccupancy events.
So just wait 10 minutes … then trigger LROccupancy … Test 1 will turn false.

If you have battery powered Z-Wave motion sensors … you do not get very many events back from the sensor.
They default to a 5 minute window.
So if you make your first motion of the day … you will get a MOTION active event … If you continue to move around at least 1 motion each 5 minutes … you will never see another event from the motion detector … until there is no motion for a consecutive 5 minutes … then you will get a NO MOTION event.
So the @ operator with battery powered motion sensors is usually useless. This will work great with wired motion sensors connected to an alarm system.

What is your action? How long do you need the condition to be true? Does it have to be true for several min, Can it be true for a min or two?

This would work depending on what your goals are.

(LRMotion or ((LROccupancy @ 3 < 10:00) and (LROccupancy; Now < 00:30)) or ((KitchenOccupancy @ 3 < 10:00) and (KitchenOccupancy; Now < 00:30))

by adding “LROccupancy; Now < 00:30” to the end it will only be true for around 30 sec after the last time “LROccupancy” was true.

(LROccupancy @ 3 < 10:00) and (LROccupancy; Now < 00:30)

[quote=“RichardTSchaefer, post:5, topic:181327”]

Anyways the way the test1 and test2 are written above once its true i don’t think it will turn false.

Test 1 will go false if it took more than 10 minutes for the last 3 LROccupancy events.
So just wait 10 minutes … then trigger LROccupancy … Test 1 will turn false.[/quote]

Thanks for that info.

That was the part I was missing. Essentially I didn’t understand that the “@ 3 < 10:00” wasn’t the last ten minutes - but comparing the time between the last three motion active event timestamps against a 10 minute interval.

[quote=“RichardTSchaefer, post:5, topic:181327”]If you have battery powered Z-Wave motion sensors … you do not get very many events back from the sensor.
They default to a 5 minute window.
So if you make your first motion of the day … you will get a MOTION active event … If you continue to move around at least 1 motion each 5 minutes … you will never see another event from the motion detector … until there is no motion for a consecutive 5 minutes … then you will get a NO MOTION event.
So the @ operator with battery powered motion sensors is usually useless. This will work great with wired motion sensors connected to an alarm system.[/quote]

Actually using solar powered Leviton EnOcean occupancy sensors. They report once a minute as long as motion is detected. And then once when motion is no longer detected within the “OccupancyReset” time variable setting on the plug-in.

So my goal is to determine human presence on the second floor reliably - and not just from the cat wandering across the floor for his dinner.

So the Bosch tri-tech motion detector is very pet friendly and hence the cat can’t set it off at all - but it only covers a portion of the floor and requires major motion. The two Leviton EnOcean occupancy sensors, on the other hand, are easy to trip, register minor motion, and therefore the cat sets them off daily. But the cat rarely triggers more than once every few hours. So @ 3 < 10:00 should be a very good indicator a human is in that part of the floor and hence we need to light and heat/cool appropriately…

So right now I am here and so far it seems to meet my requirements - did I miss anything?

Condition MultipleKitchenOccupancy Repeat Yes KitchenOccupancy @ 3 < 10:00
Condition MultipleLROccupancy Repeat Yes LROccupancy @ 3 < 10:00
Condition SecondFloorOccupied Repeat Yes LRMotion or (MultipleLROccupancy; Now < 10:00) or (MultipleKitchenOccupancy; Now < 10:00)

I think you only need:

SecondFloorOccupied Repeat Yes LRMotion or MultipleLROccupancy or MultipleKitchenOccupancy

[quote=“RichardTSchaefer, post:10, topic:181327”]I think you only need:

SecondFloorOccupied Repeat Yes LRMotion or MultipleLROccupancy or MultipleKitchenOccupancy[/quote]

But based on what I read you say above, and my testing, the @ 3 < 10:00 conditions will stay true for hours - until the next active motion is NOT within the 10 minute interval…

Yep … but you have REPEAT set to true … So every time any of the conditions re-evaluates to true … it will trigger.