Hi,
I have scenes that wait for several hours before performing another action, and I noticed that waiting scenes did not finish when a Gladys update happened during that time.
Would it be possible to postpone the update as long as a '“Wait” action is in progress, or to resume the '“Wait” action after the restart?
In the meantime, I found a workaround using the trigger “On Gladys startup” to perform the actions in case the scenes hadn’t finished.
Thanks in advance!
Hi @Mastho,
Indeed, overly long « Wait » blocks will be interrupted by a Gladys outage or an update.
In general, I don’t think it’s good practice to have « Wait » blocks lasting several hours, because aside from updates, you can have restarts (power outage? issue with the host mini-PC?)
I think there are other ways to do it, for example a scene run every hour that checks a condition. It’s more robust 
We use Watchtower which is a program independent from Gladys, so it’s complicated. And actually I don’t think it’s good practice.
I’m following up on this topic.
I’ve already had aquariums that didn’t turn on or off, or that had no heating at all, because Gladys restarted (or there was a power outage) right when a scene was being executed.
Could a flag be added to allow Gladys to know, on startup, whether one scene or another was in progress or should have been executed?
The flag to indicate that a scene was running, why not!
However, detecting a scene that should have run is much more complex, and in my opinion it’s likely to create more problems than it solves 