I may have posted this before, but I don’t remember.
Is there a way to change the followed by time from 1 minute to something else?
I just can’t find the option to change that.
Thanks in advance
Gopack2
Change followed by time?
bthrock
#3
Lol. All this time and I never even knew the “followed by” was even there. I’m quite sure I’ve done some interesting programmatic gymnastics to accomplish nearly the same thing in at least one or two of my pistons.
That’s why I love browsing the Design Help topics. Sheesh. 
geeky
#4
Does this piston work for you? I have been trying ‘followed by’ unsuccessfully to test for two triggers in a row as you have done in your piston (even posted the logs in another thread), but did not get a satisfactory explanation as to why it does not work. I also could not find any documentation explaining the proper use of ‘followed by’. Thanks.
geeky
#6
Here is my use case: When I enter the garage and close the door, ‘followed by’ opening my garage (detached) door lock, I want my back door lock to my house to unlock. The code and the log follows. While the first trigger shows evaluating to true in the log, the second trigger evaluates to false even though the lock status shows as ‘unlocked’. This is very puzzling! Please help.
Gopack2
#7
Not exactly sure. But, try changing the garag door lock changes, to garage door is unlocked. It might be that your device handler is not reporting properly or fast enough. The other way to check is by sending info to the logs. For example write a quick piston, that will check what it is reporting.
If garage door changes to unlocked
Then log to console garage door lock
Something like that.
It looks like it should work as is.
One last thought would to turn off task cancelling for the restrictions
Sorry I don’t have locks. ( yet)
geeky
#8
Thanks for a prompt reply. I already tried the first option without success but will try the log option. Thanks again.