@Robertokc - without seeing Rachio’s code, I’m shooting in the dark here. It could be difficult given - 1) they may have to synchronize/handle the pause over four different environments (mobile app (two flavors), web app, device (two versions) and the back end system), 2) there will be many situations that need to be accounted for - multiple schedules stacked at the same or near time and ready to run, a schedule that is not yet active but becomes active during the pause, cycle and soak - how to handle the pause time, a forgotten pause (i.e. a pause without a restart), a rain or temperature sensor cycling during the pause, what to do about the weather intelligence at the end of the pause, what to do about checking the weather for an upcoming schedule when in pause, pause just the currently running zone and move to the next zone (like cycle and soak) or pause the entire running schedule. Those are the items that just came to my head while composing this post.
While some may think I’m over engineering it or over thinking it and all that is needed is a simple single digit minute countdown time, others will chime in to say they need at least two digits for pause, or three digits or unlimited time, etc. - better to have all the bases covered at the beginning.
I’ll leave it to @franz to correct any of my misconceptions or over/under complexity (inversely simplicity).