I have setup 2 routines and they seem to be doing odd things and was hoping someone could give me advice. I have a motion sensor where id like to track when someone is in the room for an extended period of time (not a simple walk through) and create an action. I’ve created a second routine where if there is no motion in that room for a period of time, another action is taken. Here’s what I wrote and what is actually happening.
- Motion in the Room: If Motion Sensor detects Motion and the status is for 5 min… kick of routine.
- No Motion in the Room: If the Motion Sensor does not detect motion and the status is for 30 min, kick off another routine.
Here is my problem: The motion sensor is “activated” when someone walks in but not long enough so the first routine is not kicked off. However, the second routine sees that the motion sensor stopped detection action for longer than 30 min… so it actually kicks off the second routine (even though the first never actually kicked off).
Hope that makes sense. Any suggestions?
Brand and model of the motion sensor that you are using? Different ones have different options for this kind of use case. 
Im currently using Ecobee EB-RSE3PK2 which were provided with the ecobee thermostat. The reason I’m still using them is that both ecobee recognizes temp and motion with it AND SmartThings also sees them for motion.
I could use the newer ecobee sensors but I think I’d have the same challenge. I also have other Motion sensors I could use Samsung SmartThings GP-U999SJVLBAA… but would lose the ecobee integration.
Yes, that makes sense, it is the motion active and inactive events that start the Routines running.
As you are using Routines I would suggest you need to have the first routine set a flag of some sort when it actually runs it’s action, and then use that flag being set as an extra condition for the second routine. If there isn’t already something suitable happening (like a light or switch being turned on), then perhaps have the first routine set a virtual switch on when it runs and have the second routine clear it.
Ecobee sensors keep motion active for 35 minutes after motion is detected
1 Like
Also you can use other temperature/motion sensors to control ecobee sith SmartThings routines. Opposite integration
1 Like
Ecobee really doesn’t control anything in my house… I just use their sensors because they came along with the thermostat. The only thing I find useful in ecobee is the “follow me” functionality. For example, one ac unit covers 5 rooms and I have an ecobee sensor in each with each reporting to the thermostat its temp. It’s algorithm determines which rooms are occupied by the sensors remotely places and only uses the occupied ones to calculate an avg temp. Ex. If all sensors report 80 degrees except the two rooms I’m using reporting 75… then the thermostat says it’s 75. That’s neat so I left it enabled.
I think I’ll figure out the flag concept… never heard of it but I like the idea of a virtual flag I can tickle on off. Have to check that out. Clearly my house is requiring me to become smarter as it does.
The 35 min threshold is also something I never knew. Setting any check less than that is pointless. On top of that here is usually a buffer of 1-2 min overhead I thought I already accounted for. Thanks for this tidbit.
The ecobee sensors were specifically designed for use with a thermostat, so they make their window longer because that extends the battery life. Basically the more reports a sensor sends, the more battery it uses up.
Most motion sensors intended for home automation other than thermostats have a “cool down“ of three minutes as a default. Some can be set to check more often, but that will use up the battery faster. So it depends on the details of what you’re trying to do as to what’s the best match to the purpose.
1 Like