Hi Jay,

I changed the conditions as you suggested but unfortunately, as I thought might happen, the motion detector is now causing the landscape lights to go off after 10 mins even before 10:02 pm.. I was hoping to have the landscape lights stay on from dusk to 10 PM all the time and then go off after 10 mins once they are triggered after 10:02 pm .. any other suggestions? Thanks

Geoff

My last post was directed at ckeyes888 (negative number comparisons) - there is no workaround for the "time is between" bug that you're experiencing (you can't switch the values around because of the way time is calculated). As I stated above it will be fixed in the next release.

well that explains it.. I thought you post was directed to me... no problem

Just out of curiosity, did you try the script I posted earlier?

jay wrote:My last post was directed at ckeyes888 (negative number comparisons) - there is no workaround for the "time is between" bug that you're experiencing (you can't switch the values around because of the way time is calculated). As I stated above it will be fixed in the next release.

Wouldn't a pair of "or" conditions (AFTER 10 pm OR BEFORE 6 am) work?

jay wrote:My last post was directed at ckeyes888 (negative number comparisons) - there is no workaround for the "time is between" bug that you're experiencing (you can't switch the values around because of the way time is calculated). As I stated above it will be fixed in the next release.

Hi Jay,

Was just wondering if the problem that I brought up in this posting that you thought would be fixed in the next build, was fixed in the most recent release since, even after downloading the newest release, I am having the same problem... no pressure, just thought I would ask.....Thanks

geoff

The original bug that you reported in the first post on this thread (which was that time between calculations didn't work) was fixed in 5.1.0. Make sure that's the version you have installed.