Custom Timer not working

[fleetz]

I have set up a custom timer to allow a light turn off time to be adjusted after it turns on after dark. The problem is it turns on but won't turn off. Here is what I have done

Created a custom time of day called "OS LTS on to" selected timer from the drop down menu and then set 10:30pm. I the created a new rule

WHENEVER IT IS DARK OUTSIDE
THEN Turn Outside LTS [19(B3] ON FADE RATE=0 FOR OS LTS on to (Cust Set 3)

Maybe I am missing something it is quiet a simple rule and there are no other rule that conflict with the Outside LTS . The lights come on but at 10:30pm don't switch off??

Anyone see any problem with what I have done? I have used TOD timers on my system and never had any issue it is a simple rule that just won't work.

Regards,

Fleetz

 

[Del91574]

Based on your rule, you have a start event for the lights to come on but nothing I see is telling them to turn off, so you'll need a second rule, forgive me not providing the exact phrases as in RP.

WHENEVER Time is XX:XX (or similar, depends on the variables involved) THEN turn B3 OFF. You're also able to do similar relative to sunset, as I have an account where the outside lights do exactly as you want, but turn on :30 after sunset and turn off at 10PM.

 

[fleetz]

Based on your rule, you have a start event for the lights to come on but nothing I see is telling them to turn off, so you'll need a second rule, forgive me not providing the exact phrases as in RP.

WHENEVER Time is XX:XX (or similar, depends on the variables involved) THEN turn B3 OFF. You're also able to do similar relative to sunset, as I have an account where the outside lights do exactly as you want, but turn on :30 after sunset and turn off at 10PM.

Yes I agree with your logic. The only thing I was trying to achieve was give the user the flexibility of setting the off time via ELKRM. I thought the "THEN Turn Outside LTS [19(B3] ON FADE RATE=0 FOR OS LTS on to (Cust Set 3" provide the off command via the custom time of day embedded in the THEN command???

I would have thought that the custom time of day was the off command?

I am comfortable with doing it the way you suggest the user was excited about the flexibility of setting the off time himself.

Regards,

Fleetz

 

[Del91574]

I believe that a custom time commmand in this case would conflict with the operand "whenever dark outside" as that can be a time on either end of a 24 hr period which would be technically 2 rules, otherwise the time will conflict.

From what I see, the custom setting would have to contain a time or a duration in order for the rule to fire correctly, but it might be worthwhile to run it by Elk, because there are multiple ways of doing the same things at times.