How in new routines? Motion turn on and then turn off after motion stops

Do the new routines have something similar?

The old smart lighting had functionality which was turn on with motion, then turn off with time after no motion

Takes two routines…

When motion is detected,
Do such and such.

When motion sensor: no detection
For whatever time you set it to
Do such and such

1 Like

Hey thanks. I just set it up.

Does anyone know what the rules are for local or cloud.

It seems if I add time to the rule, like no motion for 1 minute it goes cloud.

Is that correct?

Im sure many people in this community can tell you what to do and exactly how to do it, but honestly, what your doing now is the best thing to be doing.

Keep experimenting with the routines and you’ll keep figuring it out.

Experiment with moving your motion sensors around (physically) or grouping them with combination preconditions of motion/no motion instead of time before Off.

I spent 6mos. moving motion sensors around in my home to get them exactly how I wanted motion/no motion triggers to fire when entering/exiting rooms during certain time periods or anytime.

Your cats are going to be your hurdle, just like mine was my wife.

1 Like

I might be wrong, but I don’t think you need 2 routines…at least not how I do it. Here is a routine I use that “turns off” after a set amount of time automatically.

Also, routines–if able to run locally, will tell you with either the note at the bottom of this one or in the list, it will have a little “house” with checkmark.

1 Like

Isn’t yours a timer that always turns off after the set amount of time? So it’s always on for two minutes or always on for five minutes or whatever?

I believe @professordave is looking for something that will turn off after 2 minutes of no motion. So if a person is walking around in the area for 20 minutes, it would turn off after 22 minutes. If a person is walking around in the area for four minutes, it would turn off after six minutes. That’s different than what you suggested. but maybe I’m wrong.

1 Like

@JDRoberts Thank you for explaining this so well!

I was unsure of how to describe what I was looking for

1 Like

Currently if you say no motion after x minutes the routine will be executed in the cloud. The following is an example.

1 Like

I migrated all of my Smart Lighting Routines to (Automation) Routines a while back just like this using one Routine since the light will stay on as long as there is continued triggering motion resetting the Turn Off timeout clock just like Smart Lighting did, and it runs local just like Smart Lighting did.

Note that if your have constant motion where the motion sensor never goes to no motion, then the light turns off after the set Turn Off value.

If there is another motion active event then the timers will be reset. Whether that requires an intermediate inactive (no motion) detection depends on whether the device repeatedly reports motion and whether the integration only reports changes of state.

So it doesn’t robustly implement the classic scenario the OP asked about, but it may be close enough in some situations.

1 Like

@JDRoberts and @orangebucket - your explanations make sense…I think the sensor has always changed state to “no motion”, so I’ve never realized that it could shut off with continued motion.

1 Like

Did that change at some point? My smart home setup is currently a mess since we just moved so I can’t test, but I seem to remember when the turn off after X minutes was added directly to the action then it was a wait statement and would run even if the condition was triggered again.

1 Like

I thought exactly that but I tested a Routine this morning and it was definitely resetting the timer. I wouldn’t rule out a cloud v local difference though.

2 Likes

I think it’s changed multiple times with none of the changes announced or documented. :thinking:

Certainly there have been a lot of forum reports of the “this used to work” variety.

3 Likes

Always keeping us on our toes :smirk:

3 Likes