This is a known limitation with many presence sensors: they only ever send one event, telling you when they have detected someone. But they don’t send you an event to tell you “nothing is happening now over here!”.
With Apilio, you can add a timeout to your PIR condition to make sure that you are using data that is recent. This is like adding a way to make the sensor “false”, even if the sensor is not capable of sending this information How to setup time constraints for Conditions: delays and timeouts
Here’s an example where we use a PIR sensor with a timeout to only turn on a light for a while after someone has been detected:
Let me know if this is similar to your Logicblock! Thanks!
@Anna, correct me if I am wrong but the timeout countdown starts the first time the sensor reports TRUE, and does NOT re-start again when there is a “re-update”
That means that, if you set the timeout to, let’s say, 1 minute, and you want to take an action when that happens (e.g. turn off lights), then that action may be triggered even if there is still motion in place.
An option would be needed (idea for @pebneter! ) in conditions to set wether the timeout countdown should be reset upon a reupdate.
Obviously, if all @rljkoster needs is to detect movement (e.g. for alarm purposes), then the timeout approach may work. If lack of movement needs to be detected, then my recommendation is to buy new motion sensors (I’ve already gone through that).
Update: This is how it actually works according to @Anna, so no problem here.
) in conditions to set wether the timeout countdown should be reset upon a reupdate.
Update: This is how it actually works according to 
Thanks for letting us know