Condition change on other watched device cancels initial trigger

#1

1) Give a description of the problem
Simple piston watching multiple devices, if two are triggered, the action on the first is cancelled and only the second triggers,

2) What is the expected behavior?
Would prefer the actions to be treated discretely

3) What is happening/not happening?
Only the latter event is acting properly

4) Post a Green Snapshot of the piston

e08ff-1
e08ff-1.png1178×532 61.4 KB

5) Attach any logs (From ST IDE and by turning logging level to Full)
(PASTE YOUR LOGS HERE BETWEEN THE MARKS THEN HIGHLIGHT ALL OF THE LOGS SND CLICK ON THE </> ICON TO FORMAT THEM)

The piston is set to 10 seconds for testing purposes. The desired delay is 10 minutes which is why the console logging doesn’t match.

#2

select the with statement in edit mode and change TSP to allow multiple.

#3

Hello and thanks for the tip. I made that change and the behavior is different now but still not right. Originally, the second light to turn on was the only one that shut off. With the edit suggested, the FIRST light shuts off properly but the SECOND remains on.This text will be hidden

UPDATED: I got it. You headed me in the right direction. I changed the TCP value to Never Cancel Tasks and left your TSP suggestion in place and that combo solved it! Thanks a lot.

#4

now try by turning on all the switches within 10 seconds :wink:

#5

Yep, exactly what I did. I tested with two lights across the hall from each other. Turned number one on, 5 seconds later number two on. Number one went off at 10 secs followed by number two 5 seconds later. With a desired 10 minute window and an active house this will get some good runtime today.

Thanks again

#6

have you tried turning on … pause 2 sec … then off … pause 2 sec … then on for the same switch and checking what happens?

#7

I have not but it’s added to the list. These are Zigbee A19’s on standard switches.

#8

thats how most of us got started with ST.

be aware that ST will drop the zigbee connection to the bulb if they have been turned off at the switch for a while.

edit: even though you didnt ask … heres what i used to solve that problem: :slight_smile:

and broke off the tab on only one side of the guard. so the switches are in always on state and the light is controlled with motion. folks cant turn on and off the switch by reflex. but when ST has one of its outages and it will … you can still turn on the lights manually by going sideways around the guard as shown in the picture.

edit2: no that is not an affiliate link … i just like the product even though i think its a little expensive than it should be.

#9

Thanks for the tip. I pimped my last house with a Vera and all the fun Lua scripting it allows. I had finally swapped out all of the key decora switches for Jasco’s, about 12 or 13, but I didn’t swap them out before the guy that bought the house saw them on a showing, and of course, he noticed they were not standard and said he wanted them to stay because he was into HA, too. Oh, he paid for them, but now in my new house I just cannot part with the $ to swap them all out. So Zigbee bulbs and ST it is for now. I’ll watch for the long-off periods and ST connectivity issues.

Side note, coming from Vera and it’s Lua/Luup code I was super disappointed with ST until I found webcore. Well done.

#10

welcome to webcore. :slight_smile:

all credit for wC goes to @ady624