Did you mean “in the right field” or “in right field” LOL. But seriously, I came here not to resolve it, but to see if it was common behavior. If it breaks again, I will report it while it is broken.
But it is possible that it was my lazy code that broke it completely… I had an ignore state set when the fan turns off, that I reset X minutes later in a schedule handler. If that schedule handler doesn’t fire, my event handler is dead. Maybe this kind of logic puts too much faith in SmartThings being able to do what it is told.
I think for important tasks, we’re going to need some error handling. For instance, how can my app know the schedule handler won’t execute… that either the SmartThings’ servers didn’t receive it, or after being received, it somehow fell out of the queue? Is there some form of response that can be parsed to know it was received, or a function I can call periodically to confirm my scheduled events are still pending execution? and is there an event (other than poll) that works reliably (my experience so far has been that poll does not).
Now I have only been at this a couple of months, and these kinds of things may “be in there” someplace, but every App example I have looked at just expects things to work, with no error handling code of any kind. So if they don’t, we simply stand by while our equipment melts down or our basement floods; unless we are present and have the wherewithal to notice our automated devices are no longer automated.
Since this stuff is all running in the cloud, we need for the could to police itself. But more importantly… we need the cloud to communicate with the SmartThings app when an error is encountered, with an intelligible response in as timely a manner as possible (and not through the hub, but directly). Perhaps some kind of realtime audit process tracking events, and verifying their execution. I realize this would be redundant as I am sure the server side stuff has some level of error checking/handling, but at this point it doesn’t seem that it is enough.