I have an automation in the new app to activate Armed (Stay) in STHM if between the hours of 10 PM and 4 AM there is no motion is detected by any of my five motion sensors for 30 minutes. The problem is that if I go to bed before 10 PM, the automation doesn’t get triggered. It needs motion to first …

I know this isn’t the answer you want, but I had the same problem and this worked for me: Move your start time back to 8pm (or a time guaranteed to be before you’ll ever go to bed).

Yes, I was going to do that, but it’s not uncommon for us to be watching a movie and sitting motionless on the couch at that time, so I was afraid that the automation would get triggered prematurely. If I were to change the start time to an earlier time and increase the motionless period, then it wo…

What if, instead of using a period of time, you ran automations to set a flag at 10pm and clear it at 4am, and then ANDed your motion sensors with the state of that flag? The flag could be a virtual switch being toggled to on or off, or you could set a virtual motion sensor to no motion at night an…

Confirm I have the same problem. I addressed it by tuning the window as mentioned elsewhere. If this behavior is as described on this thread, the “no motion” automation is implemented incorrectly. Instead of looking for a “no motion” message in the time window, it needs to look for the absence of a…

Exactly right. It should be looking for the absence of a “motion detected” event instead of looking for a “no motion” event, which is actually a motion stopped event. This appears to be operating the way that it does in the Smart Lighting smartapp, which looks for a “motion stopped” event as a trigg…

I know this won’t be the answer that anyone wants to hear, but “motion stopped“ is a sensor event reported by the sensor. That means the system doesn’t have to monitor it for the whole period: When the sensor determines that motion stopped (after a motion detected event) it sends a message to the hu…

I understand what you’re saying, but I don’t think it needs to continuously poll. It just needs to set a timer (not an actual timer, but schedule the action to happen in an hour), so that if a new “motion detected” event does not occur with that time, then it executes the action when the time runs o…

The beginning of a time period doesn’t act as a trigger, only a filter. Exact time can act as a trigger. You’ll probably need to two automations: one for exact time and one for time period.

Correct me if I’m wrong, but I seem to remember a tutorial that explained how this “problem” will be solved using the new rules API. Does anyone know when the new rules API goes live?

[image] tleroy: Correct me if I’m wrong, but I seem to remember a tutorial that explained how this “problem” will be solved using the new rules API. Does anyone know when the new rules API goes live? It’s live now, but it’s still in development: FAQ: Getting Started with the new Rules API

"Motionless duration" doesn't arm STHM if motion stopped before the time period

SmartApps & Automations

JDRoberts September 13, 2020, 11:59pm 11

It’s live now, but it’s still in development:

FAQ: Getting Started with the new Rules API

Topic		Replies	Views
FAQ: Why “after no motion” doesn’t work the way you think it will FAQ migration2020	6	2344	January 6, 2021
Automation: why does it not work? (Ignores no motion condition) SmartApps & Automations	7	626	April 10, 2021
No Motion automation SmartApps & Automations	3	603	April 14, 2022
[SOLVED] Period of Time + No Motion Automation not working after migrating to new smartthings SmartApps & Automations	6	1176	January 12, 2021
Automation Motionless Duration Longer than 1 Hour? SmartApps & Automations	2	557	September 16, 2020

"Motionless duration" doesn't arm STHM if motion stopped before the time period

Related topics