Hi Fred, I just did some quick testing and it seems to work ok so I'm wondering if it's having issues due to a full 24 hour cycle.
The last mode you shouldn't need, at 9:00pm I'm assuming the lights are off so you only need to start a schedule at 7:00am and it will start the morning fade using the 9:00pm levels.
(10-12-2021, 07:27 AM)Rob F Wrote: Hi Fred, I just did some quick testing and it seems to work ok so I'm wondering if it's having issues due to a full 24 hour cycle.
The last mode you shouldn't need, at 9:00pm I'm assuming the lights are off so you only need to start a schedule at 7:00am and it will start the morning fade using the 9:00pm levels.
10-15-2021, 10:29 AM (This post was last modified: 10-15-2021, 10:32 AM by Dom59.)
(10-14-2021, 07:39 PM)Rob F Wrote: Oh no, could you post pictures with the modes expanded so I can see the levels and test the same. Also what ports are you using?
(10-14-2021, 07:39 PM)Rob F Wrote: Oh no, could you post pictures with the modes expanded so I can see the levels and test the same. Also what ports are you using?
Issue would not be because it starts at 12pm to finish at 7pm?
It shouldn't be, the start/stop times are stored in seconds. 86400 seconds in 24 hours so 12:00pm would be saved as 43200. Today I'm going to dig into this, something must be wrong as a few has reported it.
When the controller starts or after a mode runs the system reads all the modes, converts the start/stop seconds to a unix timestamp, sorts them and knows the next schedule to start. Then it just waits for current timestamp to be greater than schedule timestamp.
Hi Fred, sorry it's still slowly getting there as I haven't had much time lately but it's too far from being done. I'm hoping this week I can complete it.