can you give this a try, i’ve just tried it at my house and it works like this pretty well but my sensor doesn’t report every 5 mins… see what happens with yours,
Garage lights left on (illuminance)? Let me know. HELP!
Baz2473
#22
Baz2473
#24
yup… ok my bad, thought it was repeating but it wasnt…
this one does however… not sure with your 9 min wait and the lux level being checked every 5 mins though. worth a try…
turn off execute on piston state though, i forgot to turn it off on the screen shot… sorry,
if this still doesnt work then i would suggest going down the road that @bangali mentioned earlier…
Baz2473
#26
@randem after all the fuss yesterday. I’ve finally got it sorted for you. This is what I would do if I were in your situation.
It seems that because your lux sensor checks every 5 minutes and is slightly different every time it’s causing the piston to re-evaluate and restart the countdown so this WILL fix it.
It may not be the neatest way but it DOES work.
Create a GlobalVariable called @garageOpen
Then import both these pistons.
The first one controls turning the global variable on/off
The second one controls the 9 min repeated message if the global variable is on or not.
Seeing as the troublesome lux Sensor is only in the first piston it doesn’t interfere with the countdown because that’s only in the second piston.
Piston 1
Piston 2
randem
#27
Thanks so much for the help! (Sorry for the long reply lag - hit my “new user” reply limit.)
I came to the same conclusion but used a virtual device simulated switch called Garage Lights that is set on or off by a piston that watches the illumination. (Your solution with the global is more elegant - may have to switch.) Works like a charm!