Hi All,
I have been using the attached piston for a good 6 + months and it usually works great. I’ve noticed in the last couple days that it isn’t executing anymore. I have a sensor that detects illuminance and it looks like it is working fine.
Not sure what the issue is:
Looking at some of the logs, it looks like it is seeing the illumiance value that should trigger it (3) but then saying it’s false?
Have you tried changing it to “less than or equal to”?
Drops below will become false after 10 seconds.
Not sure why it’s stopped working though.
I changed it to that now, hopefully that fixes it.
Ya, I have no idea why it stopped working, but it did 
Thanks 
It worked :). Thanks a lot.
I’ve realized how spoiled I’ve become not having to do these monotonous tasks each day.
It didn’t work for this evening…not sure why. I did have to take down the hub for a while, but it was put back online prior to the time restrictions I had set up…I paused and restarted them, so hopefully that will get the pistons going again…
I ran into this in one of my pistons that calculates distance ‘ranges’ (or bands) from home for adjusting thermostat set points. Once I changed the piston to “less than” and “greater than” distance comparisons, the piston started working consistently. At the time, I wondered if I had added ‘never cancel’ to my "drops below/rises above’ sections, it’d work. It just seemed like it would work more efficiently with the “drops below/Rises above” logic, but since it worked after adding the “less than” and “greater than” comparisons, I didn’t think about it too much.
