Help With Motion Sensor Piston

[philly33flyers]

1) Give a description of the problem
I have a pistion that I created for a motion sensor to turn on a light but lately it’s been very random with it’s actions. Sometimes it will turn the light on and then immediately off and sometimes it will work properly.

2) What is the expected behaviour?
Switch 5 is the light that I want to control with Motion Sensor 1. Basically if there is motion then Switch 5 turns on UNLESS any of Switch 3, Switch 4, or Outlet 1 are on. I then want Switch 5 to turn off when motion has been inactive for 60 seconds or if any of Switch 3, Switch 4 or Outlet 1 is turned on. I also only want all of this to happen between 9pm and 7am.

3) What is happening/not happening?
I thought my piston was pretty good, but it appears not to be based on the behavior I’m getting with random firing and inconsistent results.

**4) Post a Green Snapshot of the piston![image|45x37]

5) Attach logs after turning logging level to Full
(PASTE YOUR LOGS HERE THEN HIGHLIGHT ALL OF THE LOGS AND CLICK ON THE </> ICON TO FORMAT THEM CORRECTLY)

[jkp]

Missed motion events; outage?

Hi Guys, Recently, I’ve noticed some of my motion events are delayed or missed completely. It looks like I can see the events in ST’s logs, but they either aren’t making it webcore, or something else is wrong. I thought it was something I was doing wrong, but then I saw a post on the ST community forum. Are there any issues impacting the performance of webcore over the past few days? Possibly unrelated: It did seem that there was a complete ST outage about a week ago, and I think that’s whe…

Webcore Missing Motion.inactive Messages

1) Give a description of the problem Starting a few weeks ago, Webcore started missing some motion.inactive messages from SmartThings. This is causing my “stays inactive” triggers to never trigger. The motion.inactive events are showing up consistently in the SmartThings IDE. I’ve tried restarting the hub, rewriting my pistons to make them as simple as possible. Pausing all non-essential pistons, changing batteries, etc. Because the motion.inactive events are appearing in ST but not Webcore…

Serious issues with Webcore. Commands disappearing into the ether

1) Give a description of the problem To be clear, I’m not sure if the problem is exclusive to Webcore, so I’m trying different things to nail down the problem. I have a larger piston that makes comments based on triggers. It fires successfully about 50% of the time. I took this smaller part out, and made a new, smaller piston. I can fire it twice, but on the third try, it doesn’t even run the first command (turn virtual switch off). These are commands used to change the voice of Alexa through E…

[Pantheon]

I am not the expert here, but I think that I have added your criteria and simplified your piston with the following. I have not been able to test this, so keep that in mind. You can divide these up into two pistons or leave them as one.

(Notice the negative approach towards the time since your original code spanned midnight)

IF Motion Sensor 1 motion changes to active
AND
All of Switch 3, Switch 4, Outlet 1 are not on
AND
Time is NOT between 7 am and 9 pm
THEN
  with Switch 5
  Turn On
END IF

IF Motion Sensor 1 stays inactive for 60 seconds
OR
Any of Switch 3, Switch 4, Outlet 1 changes to on

AND

Time is NOT between 7 am and 9 pm             
THEN
  Wait 90 seconds   (Set TCP to never here)
  With Switch 5
    Turn Off
END IF

[Pantheon]

Your could divide the second IF into two…

IF Motion Sensor 1 stays inactive for 60 seconds
AND
Time is NOT between 7 am and 9 pm             
  THEN
    With Switch 5
      Turn Off
END IF

IF Any of Switch 3, Switch 4, Outlet 1 changes to on
AND
Time is NOT between 7 am and 9 pm             
  THEN
    Wait 90 seconds   (Set TCP to never here)
    With Switch 5
      Turn Off
END IF