Its getting lighter outside earlier so I went in to change some trigger activated schedules to trigger from 6:30 PM instead of 5 PM.
When you change the start time, it changes the end time to 30 minutes after start time resulting in you having to go back and change all the end times again (double the work). Its a pain if you have a lot of rules like me. Why cant they make it so you can change start times and the end times are left alone?
Better yet, why cant they have a selection for sunrise and sunset like the other timers so you never have to worry about this.
Another solution (but not as good) would be to be able to check multiple rules and then change the times accordingly and it would change it for ALL of the checked.
But on the low side, it should not change the end times and I feel this is a bug
This is not a bug. Since you can select any start time that means you could select a start time after the end time in a given 24 hour period. The end time is automatically adjusted, then can be re-adjusted from there.
See the quote below from a prior thread:
Yes. We can confirm that behavior when setting a period of time when an event triggered rule is active. Your suggestion is being forwarded to Alarm.com
The original statement was taken to mean scheduled automation, specifically, setting a light to come on at a specific time or turn off at a specific time. “Scheduled automation” time selection is not affected.
The way the “During This Time Frame” functions likely influenced the decision to automatically adjust the time.
The selection drop down cycles through a 24 hour period. Each time you select a different start time, a completely new set of end time options is generated, meaning your previously selected end time could be no longer a choice on the list, so it is defaulted every time. This is due to hours “before” your selected start time being designated specifically as “Next Day”
Better yet, why cant they have a selection for sunrise and sunset like the other timers so you never have to worry about this.
Sunrise/Sunset rules employ a comparatively huge amount of data and processing in a complex algorithm. Currently using them as a scheduled “on-off” time for the lights directly is the most common source of schedule errors. Adding them as a variable that can be freely turned on/off is likely not feasible yet on most panel hardware.
Another solution (but not as good) would be to be able to check multiple rules and then change the times accordingly and it would change it for ALL of the checked
This I would like to see myself. As the automation side of things grows, I think you will see a more robust and streamlined creation UI.