Wait a certain amount of time after condition met

#1

Hi,

I’m trying to design a simple piston that waits for a condition to be met, but won’t fire the piston unless a certain amount of time has gone by. For example, if light “A” is ‘on’ and it has been 60 minutes, then turn of light “B.” I’d like it set up so that if the second condition, the amount of time passed, hasn’t been met alone with the first condition, the piston won’t fire…

Thanks

#2

well, the piston needs to fire for the condition if light “A” is ‘on’ and it has been 60 minutes to be checked. what you may be looking for is turn of light “B” not to be executed till that condition is true. this will do it:

if light 1 switch stays on for 60 minutes
   with light 2 switch
      turn off
   end with
end if
#3

Yes, I think the way you said it is correct. Light A - physical device, is in an on status…and if remains on for 60 minutes, then turn off Light B - physical device. I’m trying to figure out how to pull up the options you typed out from within WebCoRE.

#4

Founds it…once I picked Stays…it populated what I needed…thanks :slight_smile:

#5

you are welcome.

#6

So this is a little weird, I tested a similar scenario with two different zwave on/off switches… If this happens, then turn this lamp on and this lamp off…and I wasn’t getting dependability on the execution of the pistons. As soon as I made two separate pistons for the same IF but different lamps, it worked MOST of the time, but not each time and I tested this with other lamps as well that I never have the issue. Strange.

#7

do you have a snapshot of the piston that was not behaving dependably?

#8

Yes, but I just tried to replicate the issue using CoRE and CoRE is functioning properly…Programming identical way…anyone else having issues in general?

#9

44 PM
Screen Shot 2017-09-10 at 6.29.44 PM.png784×361 17.7 KB

#10

i have not used core much, but certainly seen posted multiple times on the forum that in some things core and webcore behave differently. :slight_smile:

which part of this piston was not working reliably?

#11

the whole thing…but other things aren’t working correctly, such as presence based events, etc…they’ve been really late or sometimes don’t happen, even though ST is reporting the correct presence…

#12

maybe ST wss having some issues? i saw my hub go offline a few times today and get resolved after a few minutes. sometimes the result can be unpredictable when that happens.

#13

Interesting…i have another light that goes on when a sensor opens and I had it programmed to go off in a couple minutes after…yesterday, working perfectly…today…not…not sure if something is going on…buy manually, I can control all “things” without a problem…hopefully things settle down tomorrow…i really enjoy using WebCoRE and have moved ALL my scenarios over…so I depend on it