Conditional Timer not as expected
I had a client we just started servicing ask for a simpler solution to 'vacation mode'
The request was to have certain lights turn on at dusk, different lights turn on at 9pm, and then all lights turn off at 11pm.
They had a button engraved as "away" that originally toggled between vacation mode record and playback.
I wrote 3 new timeclocks with conditionals.
One at sunset that "if variable AWAY = away then run preset 1. End if" (preset 1 turns on lights on the 1st floor)
A 2nd at 9pm that "if variable AWAY = away then run preset 1. End if" (preset 1 turns on lights on the 2nd floor)
A 3rd at 11pm that "if variable AWAY = away then run preset 1. End if" (preset 1 turns off lights on 1st and 2nd floor)
I deleted the vacation mode programming on the away buttons and now that button uses an advanced toggle to change the variable AWAY between away and home. the led ON state is away.
I expect that when the client presses the button so that the away LED is lit, then the timers will run. When the client presses the button so that the away LED is unlit, then the timers will NOT run.
I've gotten a call stating that the timers work but the client cannot get the timer to stop running.
Does anybody see an obvious flaw in the above logic? Did I overcomplicate the process by choosing advanced toggle?
thanks for any help with this!