My bad. Missed that part. I did edit my post above.
I have my doubts though. I know for a fact, my schedule turn off registered, and it still tried to automate temp changes for what were essentially random long term setpoints (I wanted my unit off as AC was no longer required, so I set it to heat with target at 60°F - 61°F just for cold nights). My normal temps were as it got colder, either 65°F (until everyone started complaining), then 68°F. But on more than one occasion, we woke up to the tstat at 60°F - 61°F, or 65°F.
I suspect it is the “learning” aspect of the tstat/ADC algorithm- whether you manually adjust your temps, or use a programmed schedule to do it for you, the tstat sees it the same, and will modify set point targets based upon that perceived usage.
This would be easy to verify. All you need do is for those with active schedules that have been in effect for say a week or two, simply turn off schedules, raise/lower temp remotely via app or website to say a random set point, and see if it holds. The only thing that I think would stop would be the “smart away” settings.
The only way I stopped it short of a tstat reset, was to set the target set point at the tstat itself. I am not sure, but I think I had to set the target at tstat at least a few times to get it to hold even then. Perhaps it had to “learn” to hold it at that set point.