Make multiple motion sensors behave like a single sensor?

[mocelet]

Maybe after a restart of the hub could be an issue too, haven’t tested.

In that case we go back to having a single remains as best solution, for that, either create a rule in Rules API like @orangebucket mentioned, or use the virtual switch approach which is also a single ramains rule and won’t have those problems plus the other routines will look cleaner.

[orangebucket (Graham)]

@mocelet

Maybe after a restart of the hub could be an issue too, haven’t tested.

Me neither, but a good thought.

If I wanted a Routines based solution I’d probably be using four, along with a virtual (or real) device (switch or motion sensor) that is set to only send events on change of state (although preconditions in the Routines would be an alternative safeguard). One to activate the virtual device if any motion sensor was active. One to deactivate the virtual device if all the motion sensors are inactive. One to turn the lights on the virtual device is active. One to turn the lights off if the virtual device has been inactive for x minutes.

I like to separate out the nuts and bolts of the detection of motion from actions I take if motion is detected and when using Routines I feel the need to make it really clear.

[Declankh]

Yep, i have this setup too. No need for virtual switches. It’s a nice example of de Morgans law.

[mocelet]

@orangebucket

since starting the Routine (saving or enabling)

@mocelet

Maybe after a restart of the hub could be an issue too

I’ve just tested it for research sake and wasn’t able to replicate it:

• Disabling and enabling the rule doesn’t affect, I triggered one sensor without triggering the other one and the routine triggered after 1 minute of no motion which is the time I set.
• Then I thought, the rule already existed, maybe the state of that remains is kept until updated. So I deleted the routine and created a new one. Triggered just one of the sensors, and the routine triggered after 1 minute of no motion.
• Then I restarted the hub, just out of curiosity, again, triggering only one of the sensors. The routine run after 1 minute of no motion.

So maybe there’s no reliability difference between using one “for X minutes” or two “for X minutes” in the same routine.

[TapioX]

@mocelet

Actually @HalD , @h0ckeysk8er and @raed.jarrar are correct, there’s no need for the virtual switch at all!

I wasn’t very confident about the behaviour of the “for 5 minutes” so I’ve tested it and looks like it works.

The generated rule “stays for 5 minutes” translates to a remains condition with latching: true, not really sure how this modifier affects the remains behaviour but seems like that’s what makes it work in this case. I guess the latch is what makes it stay in that condition so even if both sensors meet the condition at different times it will trigger the routine. Without the latch, I guess, the routine would not work.

There are hidden features in SmartThings routines. This latching is not visible anywhere, not even in AWA logic (only in JSON).

@Declankh

It’s a nice example of de Morgans law.

It’s good that there are also logic experts among us.

[Declankh]

@TapioX

It’s good that there are also logic experts among us.

_______​.