Twice a year, daylight saving transitions shift clocks by an hour. Your time-based automations either fire at the right wall-clock time (correct) or shift by an hour (incorrect). When automations shift, the cause is usually a time zone misconfiguration somewhere in the chain: on your hub, on the cloud, or on the trigger source.
Verify the hub time zone first
The hub needs to know your time zone. Each hub has a setting:
- SmartThings: Settings, your hub, Location, Time Zone.
- Hubitat: Settings, Location, Time Zone.
- Home Assistant: Settings, System, General, Time Zone.
- HomeKit: home hub uses iCloud account location automatically.
- Hue Bridge: Settings, Location, automatic based on internet IP.
Verify each is set to your actual time zone, not a default like UTC. If you moved, update the time zone.
The automatic versus manual time zone
Some hubs detect the time zone from IP geolocation. If you use a VPN, your hub’s detected time zone may differ from your actual location. The hub then runs automations on the wrong schedule.
If you use a VPN, set the time zone manually rather than letting it auto-detect.
The cloud time zone
Cloud-based automation engines (Alexa, Google Home) use the account’s location to determine time zone. If your account location is wrong:
- Alexa: Settings, Your Locations.
- Google Home: account settings, home address.
- Apple Home: device location services.
Verify each is correct. Discrepancies between your hub’s time zone and your cloud account’s location can cause split-personality behavior where some automations fire on hub time and others on cloud time.
The sunrise and sunset shift
Automations triggered by sunrise or sunset use the home’s geographic coordinates. If your coordinates are slightly off, your sunrise and sunset times shift accordingly.
Verify your home address in each ecosystem’s settings. A few miles of address inaccuracy can shift sunset by 5-10 minutes, which is usually not noticeable but can accumulate to confusing behavior.
The DST handling on individual devices
Some smart thermostats and irrigation controllers maintain their own internal clocks. If their clocks do not handle DST correctly, scheduled actions on those devices shift by an hour while hub-scheduled actions do not.
Check each device that has its own scheduling: thermostats, sprinkler timers, smart pool controllers. Verify their time and DST handling.
The two days after DST
Most modern voice assistants handle DST automatically, but the transition window (the actual day of the change) often shows weird behavior. Automations may fire at the old time on the day of the change, the new time the next day. This is usually self-correcting within 24 hours.
If your automations are wrong for 2-3 days after DST, the time zone is probably mis-set somewhere.
The 23-hour day problem
On the spring-forward day, the day is 23 hours long. Automations scheduled for the missing hour (typically 2-3 AM) do not fire at all. Automations that rely on a specific duration after a previous trigger may also be affected.
If you have a critical automation scheduled for the early morning, schedule it before 2 AM or after 4 AM to avoid the DST transition window.
The 25-hour day problem
On the fall-back day, the day is 25 hours long. Automations scheduled for the repeated hour (typically 1-2 AM) may fire twice. Verify your automation engine’s behavior; some handle this correctly, others do not.
The cross-ecosystem time mismatch
If your automation involves multiple ecosystems (Alexa triggers a routine that calls Home Assistant which calls SmartThings), each ecosystem has its own time zone. A mismatch causes the automation to fire at the right time in one and the wrong time in another, with unpredictable composite behavior.
Verify time zone in every ecosystem in the chain. They should all match.
The clock drift problem
Some hubs do not synchronize with NTP and their internal clocks drift. Over months, the drift can accumulate to several minutes. Scheduled automations fire at the drifted time, not the wall-clock time.
Reboot the hub to force a clock resync. If the drift returns, the hub has a clock issue that may need firmware update or hardware replacement.
Calendar-based triggers
If your automation triggers from a calendar event, the calendar’s time zone matters too. A Google Calendar event scheduled in one time zone may appear at a different time in your automation if the time zones do not match.
Verify calendar events are in your home’s time zone, not your travel time zone.
The first weekend after DST
Many users notice DST issues on the first Saturday or Sunday after the change because that is when weekend automations would fire. Weekday automations may have fired correctly on the Monday because most ecosystems had already synced by then.
If your automations are off only on weekends, you may have a weekend-specific schedule with a stale time zone reference.
The Google Calendar trap
Google Calendar has a setting for the time zone of an event. If your event is in a different time zone than your device, the event displays at the local time but the trigger fires at the event’s time zone. This trips up users who travel and create events on the road.
The DST audit takes ten minutes twice a year
Every March and November, spend ten minutes verifying each of your time-based automations fires at the right time after the DST change. Most platforms handle this correctly but a handful of edge cases (calendar-based triggers, sunset offsets configured manually) drift by an hour and stay drifted.
Set a calendar reminder for the Sunday after each DST transition. By the third year of doing this, you will know exactly which of your automations need attention and which always work. The broader context of seasonal automation drift is in our sunset drift guide.
The hardware-clock drift on older hubs
Hubs that have not been rebooted in months sometimes show slight time drift that becomes visible around DST changes. A scheduled monthly hub reboot prevents accumulated drift. Pair it with the post-DST audit and you catch both clock drift and missed DST transitions. The wider topic of time-related automation issues is in our sunset drift guide.
