Continuing the discussion from ST Blows DST Again!:
@bravenel’s post above was in March 2015 (which, in turn, referred to past failure(s) of DST), and here were are a year later, March 2016, and basic DST / Sunset functional still fail?
Yes … that’s a question mark, because I really can’t believe DST isn’t being handled properly.
- I’m in San Francisco, CA. Timezone: PDT (UTC-07:00).
- I’m using the SmartThings developed and officially supported standard SmartApp “Smart Lighting”, because I am considering migrating to Hub V2 and want my lighting automations to run 100% locally to minimize latency and risk.
- I just edited and re-saved a super simple schedule that turns on 3 lights, -15 minutes (before) Sunset.
- Sunset will be at 19:18h; therefore the lights should turn on at 19:03h.
- My lights were just turned on at 17:34h; 1.5 hours early. If we were still on “standard time”, Sunset would have been at 18:18h, and the trigger should have been 18:03h. Where did 17:34h come from?
The parameters and current schedule of the SmartApp are pictured below:
I used the new “Update” button in the IDE on the Smart Lighting and child SmartApp … no change.
My Location Specs
Zip 94112 is in San Francisco, but not the closest Zip to my Location PIN which is correctly identified in the Lat/Long Coordinates.