This morning I upgraded my hub to ver 2.1.6.118 and last night the time changed from PDT to PST. This evening my apps ran one hour before they should have. The sunset time today was 16:50. The rule should have triggered at sunset - 10 min which was 16:40 at which time the fireplace light should have turned on. However as shown in the attached log the light turned on at 15:40 which is one hour earlier than it should have.
I had something similar happen to me. I don't have a lot of strictly time-based automations, but from what I do have it, seemed to only affect sunset-based times. I have Mode Manager configured to turn Evening Mode on 30 minutes before sunrise (happy to share a screenshot but it's been configured correctly and the schedule suggests it will be fine tomorrow so it's too late to capture that). However, what happened is that it turned it on 30 minutes plus one hour before sunset. See the correct sunset time getting logged here but the incorrect time for the Evening mode change from my System Events:
However, the sunrise-based events (Morning mode on at sunrise, Day mode on 30 minutes after sunrise) were fine. I don't think I have any "x minutes before sunrise" automations to look back on, so from what I can see it was at least a problem with "before sunset" offsets, but I can't rule out "before sunrise" offsets either.
What happened with the before-sunset automation is that it appears to have run at the originally scheduled UTC time, not the desired scheduled time based on local time. Why, I don't know, but I'm guessing this has to do with when the app calculates sunrise and sunset (perhaps my sunrise automations were OK because they happened at or after that event) and when it schedules these events (the day before when there's a time change is too soon, but sunset itself would be too late for a "before sunset" offset--recalculation at sunrise is my guess for why those were OK for me). I don't know how other platforms deal with these problems, but I certainly understand the difficulty here (though I guess scheduling everything for local time instead of UTC would take care of most but leave the problem of what to do with something scheduled during the one hour a year that doesn't exist in local time--or happens twice).
1 Like
I fixed mine by going in to Mode Manager and clicking Done. Then the schedule showed the correct time.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
