scotte
commented
7 years ago I've seen some cases where my piston conditions don't fire as expected, but I'm not sure it's the same thing as your report (and I'm new to all of this, so I assume I'm doing something wrong). I don't really want to pile onto your issue here with an unrelated thing, but just in case it is related - I'll describe my issue, with apologies in advance, though I'm pretty sure I've seen the same thing when using "changes to" states, similar to your logic.
It might help to include a screenshot of your piston from the CoRE dashboard, just to be pedantic about what your exact logic is. In my case, I'm using an Else-If piston and if I use "is inactive" event, my ELSE action occurs, but if I use "was inactive for at least X minutes", my ELSE action does not fire. In the CoRE piston editor, the conditions show that they are being evaluated correctly (show as true or false correctly for the condition).
Here's what the pistons look like.
Working ("is inactive"):
Not working ("was inactive for at least X minutes"):
Again, I sincerely apologize for muddying up your issue if mine is in fact different (in which case I'll delete this comment). And, in case anyone wonders, with the light I'm using, setting level to 0 then turning on causes it to do a slow fade to 100%.
Also, I should note that using a latching piston with logic like https://community.smartthings.com/t/core-get-peer-assistance-here-with-setting-up-pistons/50187/427 works just fine.
From what I understand the "Then If" works this way:
When something happens, wait for another thing to happend to execute an action. The action can only be executed if a trigger happens and is followed by an other trigger.
In my piston I have:
IF Movement changes to inactive in 1 sensor THEN IF Movement changes to active in one of 5 sensors THEN Turn off light
This scenario does not work for me. Could you explain if I am doing something wrong?
Thank you, Arno.