[RELEASE] 5-2 Day Programmable Thermostat Scheduler (Weekday, Weekend) with Remote Temperature Sensor for each Schedule

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Most definitely if one timer is missed/times out (which I’ve seen happen some time ago and I thought ST had fixed it) then the entire chain stops, so when you change settings it bootstraps it. So adding another timer to bootstrap won’t help, the root of the issue needs to be found as to why a timer would not fire.
And no it doesn’t matter if the thermostat doesn’t respond or is even offline the app runs independent of the device.
Maybe start a separate thread on why timers won’t fire and some users can throw in their thoughts. here’s one thread where I had reported that timers don’t fire.

Sequence of RunIn()'s stop running after several minutes

Tim, that’s great and all, but some devices that humans interact with really do change more often than 1 minute. Even my 1 minute actions are getting ?canceled? after just one or 2 cycles. I have a Enerwave RSM2 zwave device that is a really cost-effective option for controlling two lighting circuits. It has toggle inputs for both circuits too, so you can hook it to existing light switches for manual control as well. It sends a BasicReport when circuit 1 is toggled manually, but doesn’t do the same for circuit 2. Sure, the device has a weakness, but can’t ST work around that? Sure, I’ll use runIn() to trigger a manual refresh on the device states (which I know how to do, and works reliably)… oh wait, runIn doesn’t actually work that well. One of devices is on my garage overhead ligh…