Turn on at sunrise or sunset not working

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

@brianlees

Starting 5 minutes prior where accounts are randomly set to on a daily basis within that window?

I definitely agree that this “known issue” has been unresolved for too long, particularly since it affects a very common and expected use case (i.e., turning on/off lights at sunset/sunrise!).

I fear that the issue is that even 5 minutes may not resolve the problem (and I think – just guessing) that this is tied into the long execution times of “unschedule()”:

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…

The behavior of runIn() and all (?) related scheduling is defined with rules that seem too tight for the abilities of the execution environment. Jobs are not allowed to execute if their scheduled time has past. Maybe this is resolved with a queuing mechanism that takes a “tolerance” argument (i.e., a sunset job can live in the queue as long as 30 minutes, rather than being dropped altogether).