[OBSOLETE] Smart Alarm is here

[geko]

@jeff1

So basically as far as I can tell, SmartAlarm lost mode awareness at some point last night. Obviously the app was still working and doing exactly what it thought it was supposed to do.

Yes, it’s a known issue. I was able to trace it to TimeoutException during unschedule() API execution. See this thread for details:

Unschedule() API Execution Time Too Long?

This is a question for SmartThings software developers. During smart app development I’ve run into a problem when one of my functions occasionally triggered java.util.concurrent.TimeoutException which means that it’s exceeded 20 sec execution limit. With some debugging I was able to narrow it down to calling the unschedule() API. A simple test revealed that executing unschedule() API can take anywhere from 90 milliseconds to 3.7 seconds (!). And that’s on a good day. Occasionally, unschedule() gets stuck for longer than 20 seconds, resulting in java.util.concurrent.TimeoutException. Here’s a simple test that I ran: private def myUnschedule() { def t0 = now() unschedule() def t = now() - t0 log.trace "unschedule() is executed in ${t} ms" } And here’s what it prints: X…

For additional information, refer to Issue #20 on Github:

https://github.com/statusbits/smartalarm/issues/20

Also, for the reference:

Support request #86683: Smart App TimeoutException: Execution time exceeded 20 app execution seconds.