Over the weekend a power pole met its demise in our back alley. We were out of power for about 12 hours and my apps that run once a day of course failed. Is there another app that is persistent or something that checks if an event did fire and what was the result. I’m kind of sleepy so I’m not sure if this is making sense haha. I will revisit my post later
I think what you’re asking is if communication is lost of the hub, what happens with schedule apps?
Do they queue up, and then all fire once communication to the hub resumes? Or are they just “killed” and disappear into the great cloud of nothingness.
I believe the answer is the later… that they just disappear. This is certainly my preferred method as well. I don’t want functions like lights turning on or doors unlocking, etc. to happen at unscheduled times.
Just as an example, I have a night light sort of thing in my daughter room that turns on at 8:30pm and turns off 3 hours later. If my hub doesn’t have power at 8:30 pm, I don’t want this function queued up and running when power is restored. It might turn on at 1:00 in the afternoon when no one is home and just waste power.
chrisb, I figured that they disappear but I would like to have maybe an option somewhere in the app to verify that it did happen. Or maybe even a separate app just because some people might use it for door locks and stuff that you mentioned.
My app that I would like this feature on is my porch light (currently using Once a Day). The ON time was during the time power was out so that never happened, if there was a ‘check timer’ then it would turn it on when power resumed.
Yeah, I think ideally there should be an option when installing an app:
In the event of loss of communication to the Hub…
O …this app should not run.
O …this app should queue up and run as soon as communication is restored.
In theory this would be a nice option. Practically speaking it would be REALLY hard to implement. It would require that the SmartThings Cloud be constantly checking the status of your Hub.
Then I guess I’d try to setup two different cron lists… The one would check Hub status before running a job. If the Hub was down, it simply wouldn’t run the job. If it was up it would run the job.
The other cron list would check the status of the hub and if it was down it would have to put the job in a queue somewhere. Then the queue would obviously have to be run when communication was restored. This would be a nightmare to code I think.