Dynamic Basement Lighting is Erratic (Chicago Bears Lighting Theme & Normal Lighting Theme)


#1

1) Give a description of the problem
I have a piston created to dynamically control my Lightify basement lighting. I have an open/close sensor used as a potential trigger condition, along with a time range so that if the door is opening and closing during a movie or football game, the lights don’t trigger unless it’s been over two hours since the last door “event”. There is also a Lightify switch that can be used for manual control. My issue is with the door open/close sensor.

2) What is the expected behavior?
Behavior is erratic of the lights. Days where I haven’t opened the door all day, when I finally go downstairs, the Chicago Bears lighting (navy & dark orange/10%) virtual switch won’t trigger on when the door is opened.

3) What is happening/not happening?
It will flawlessly work for one or two sequences when I manually test via the switch, but when lighting is supposed to be invoked with the door open/close sensor, that’s where my issue is I think.

4) Post a Green Snapshot of the pistonimage

5) Attach any logs (From ST IDE and by turning logging level to Full)
I’ll post logs if that’d prove helpful, but I think it’s just a logic flaw in my piston.


#2

Have you tried changing line 84 to “Contact was closed for at least 2 hours”?

I think your current setup looks forward for the 2 hours window, rather than backward in time.


#3

That is a great suggestion. I will test that change out. I also changed line 82 to Contact Is Open instead of changed to open. I’m not sure how the engine interprets the difference, but all of my other conditions used the “is open” instead of “changes to” and work OK.