LUX piston stopped working

#1

1) Give a description of the problem
Piston has worked for a long time, but just stopped working in the last couple of days.

2) What is the expected behaviour?
Once my LUX sensor hits 11 or below, it should set off a sequence of turning lights on.
3) What is happening/not happening?
The piston detects the LUX, but doesn’t continue with the rest of the sequence (turning on the lights). It’s set up to only run once a day, that way if I turn those lights off after they turn on, the piston doesn’t try to turn them back on again.
4) Post a Green Snapshot of the pistonimage

Lux
Lux.png1178×1229 132 KB

#2

As you stated, your piston is only scheduled to run once a day.
Also note that, “EVERY” blocks always stay inside that specific block.
(and ignores all other code when processing)

This means that lines 21-61 will never execute, unless you press Test.
(you can turn line 22 into a trigger to execute the earlier code)

IE: IF Sensor's illuminance DROPS BELOW 12 lux

#3

It’s interesting, because I had "drops to or below " previously and it has worked since last year, but then stopped working in the last couple days. Because of that, I fiddled around with line 22 in the last couple days hoping the re-programmed trigger would resolve it. I’ll change it to “drops below 12” and see how it works.

What do you mean by “EVERY” blocks always stay inside that specific block? Do I need to change anything other than line 22 to fix this? Other than line 22, nothing has changed and it worked perfectly before. Thanks.

#4

Basically, the EVERY block only looks at that one block.
(at midnight, it will not run (or look at) lines 21-61)

Once you change line 22 into a trigger (with a lightning bolt), then the lux changes will trigger those lines.

#5

Thank you, I’ll give it a go and see how it does…

#6

It worked - thanks again.

#7

Glad to be able to help…
Perhaps you can solution a post as the solution to help others?

#8

Done.