Motion Light Control Help

[fstbusa]

This is what I have set up now. I guess I don’t understand how the Task Cancellation Policy works then. The way I follow the logic on this, the lights will come on when the sensor sees motion.(nothing can cancel them coming on when it sees motion because of the TCP). Then 3 min after the sensor goes active the lights will turn off unless the sensor goes inactive with no motion for a short time and is “re-activated”.

I figured I would want a TCP set on the Wait so it would reset the timer if the sensor went active again.

[bobbles]

Change it so that the wait and the turn off is directly under the turn on.
Then delete the else.

[fstbusa]

Please explain how this won’t turn off the lights 3 min after they turn on if motion never stops. The only way I see the timer being reset is if motion stops and the sensor becomes active again.

Is active not the same as motion detected?

[bobbles]

Because you have set TCP to never.
This means that the tasks will never cancel whenever the motion becomes inactive.
Also the way it works is when motion is detected again within the 3 minute countdown, everything resets. So when motion goes inactive again it restarts.
So in theory if you keep moving around the light will stay on.
EDIT : If you enable trace facility you can watch the timer counting down and resetting with motion.

[fstbusa]

I’ll give it a try and see how it works. Thanks.

[bobbles]

Is active not the same as motion detected?

Active or Inactive is a condition.
Changes To is a trigger.

Here is a description of them.

Conditions and Triggers: The difference?

as new users join the community, we expect that at some point many new users will ask this question. so, heres a quick note. conditions: if there are NO triggers in a piston, webcore checks the conditions to decide which events that piston should be subscribed to. if there are triggers in that piston, webcore does NOT subscribe to the events the conditions refer to. triggers: if there are triggers in a piston webcore ONLY checks the triggers to …

[fstbusa]

Watching the trace, the timer stopped counting as soon as the sensor stopped reporting motion but it appeared to run correctly and shut the slights off after 3 min. I’ll do some more testing to see if the lights shut off while motion is occurring(which is the problem I have been having in the past)

[Danabw]

Where do you set TCP?

NVM…found it.

[fstbusa]

after messing with this for a while… still having the lights turn off on me. I’m thinking its the sensor going dead and not registering motion.

[bobbles]

Look in the recently tab for the motion sensor, that should tell you if it is detecting motion or not.

[fstbusa]

I’ve looked there… I blame this Fibaro sensor… it always has hiccups… main page says motion is detected but the “recently” tab says no motion. Lights sometimes come on and sometimes not. Always needs a battery pull to reset it and correct it.

[bobbles]

What version is the sensor?
Pre V3.2 or V3.2.
What DH are you using?
This could also affect what is happening.

[fstbusa]

V3.2 or V3.2.

v3.2
This is the handler I’m using.
https://drive.google.com/file/d/1ZyoxKu5B9VAI-V9HW6ow5F-TzUHzLH8U/view?usp=sharing

[bobbles]

Well it’s not that then.
Could you post a screen shot of your piston again.
Make sure it has the code so I can import and test with my setup.

[fstbusa]

For example. This morning I was leaving for work and I saw the sensor flash as to pick up motion and the lights didn’t come on. I checked the app and the DH said the sensor was detecting motion but under the “recent” tab indicated NO motion.

I’m thinking it has to do with the DH or device and not the piston.

[bobbles]

Can you do a screenshot of the parameter settings for the device?

[fstbusa]

Assuming this is what you meant.

[bobbles]

I’ve just compared your parameters with mine and there are some that are different but I don’t think that should matter.
Perhaps you could put your sensor into config mode, press button b 3 times and the led will go blue, and then push the config button in the device in the ST app.
Just to give it another boot up the backside.

I really don’t understand why it’s not working. Do you have another sensor you could try with to prove it?

[bobbles]

You could try doing it this way.
Completely different way but works just as well.

Or perhaps set it up using Smart Lighting. This will also prove if it is working as it should.

[fstbusa]

I’ll give it a shot… based on what I’m seeing in the logs and what I see in the app… I don’t think its the piston causing the issue. The sensor is not reporting motion consistently even though it says its detected motion.