Next Developer Call will be on 02/25/15

[garyd9 (Gary D)]

I’d be interested in a discussion on using “sunrise” and “sunset” for event times. The ST status page perpetually contains:

SmartThings is currently experiencing delays in the processing of scheduled actions during a few peak times (including sunrise and sunset) across all continental US timezones. The engineering team is working on a solution to this issue.

Why is “sunrise” and “sunset” a peak time? My “sunrise” time is different from 99% of the other ST users.

I created a thread for the topic here, but perhaps it would be interesting to hear something on the dev call:

Platform slowdowns in regards to sunrise/sunset

I’ve seen quite a few comments about using sunrise and sunset offsets to help mitigate issues with slowdowns on the ST platform around those times of the day. However, I don’t understand how using an offset would help at all. Sunrise/sunset times are based on zipcode. So, it’s reasonable to assume that the sunrise/sunset time is local to a specific location. As an example, sunset time today (Feb 23rd) is 6:04pm in Pittsburgh, PA, and 5:40pm in New York City, NY. (Both are in the same timezone, but Pittsburgh is several hundred miles west of NYC.) So if I (being in Pittsburgh) was to offset my sunset time by -24 minutes, my sunset scheduled events would be clashing with folks in NYC. The point here is that, being in the Eastern Timezone, unless I were to offset by more than 1 negativ…