Your lights come on an hour early, or the heating starts in the middle of the afternoon, or everything was fine until the clocks changed. Schedule problems in smart home systems come from a small number of causes, and the clock changes expose most of them twice a year.
The short answer
Check the time zone set on the hub, on the individual devices and in the app account, because all three can differ and the one that wins is not always obvious. Then check whether the schedule uses a fixed time or a sunset offset, since sunset moves by hours across the year and a routine set in summer fires in the middle of the afternoon in December.
Where the time comes from
A smart home system may take its time from several places: the hub’s own clock, each device’s clock, the cloud service, or your phone. When they disagree, schedules fire at the wrong moment and nothing tells you why.
The common mismatches:
- The account time zone is wrong, often set during a trip or left at a default.
- The hub has a different time zone from the app.
- Individual devices hold their own time zone and were configured separately.
- A device has lost its clock after a power cut and has not resynchronised.
- The daylight saving setting is manual rather than automatic on one component.
Check the time zone in three places
The app account settings, the hub settings, and any individual device that offers its own. They should all match, and one that does not is very likely your answer.
Set daylight saving to automatic everywhere
Any component set to adjust manually will be an hour out for half the year. This is why so many schedule problems appear within a week of the clocks changing.
Check whether the schedule uses sunset or a fixed time
A sunset trigger moves by several hours across the year. If a routine that made sense in June now fires in the afternoon, that is why, and it is working as configured.
Use an offset rather than sunset alone
Most systems let you set sunset plus or minus a number of minutes. That keeps the routine sensible year round rather than tracking the extremes.
Check your location is set correctly
Sunset and sunrise depend on where the system thinks you are. A location set to a default city, or to somewhere you visited, shifts every solar trigger.
Look at the activity log for the actual fire time
The log shows exactly when each routine ran. Comparing that against when you expected it turns a vague complaint into a precise offset, which usually identifies the cause immediately.
Check for duplicate or conflicting schedules
Two routines controlling the same device at different times look like one routine firing unpredictably. Search your automation list for every rule mentioning that device.
Re-save the schedule after fixing the time zone
Some systems store the calculated fire time rather than recalculating it, so an existing schedule keeps the old offset until you edit and save it again.
The size of the error tells you the cause. Exactly one hour out means daylight saving or a neighbouring time zone. Several hours out means a sunset or sunrise trigger that has drifted with the season. A random offset means conflicting routines or a device whose clock has lost synchronisation.
The clock change problem
Twice a year, a set of smart home schedules that worked perfectly begin firing an hour out. The cause is almost always one component in the chain not handling the change, and the reason it is hard to diagnose is that most of the system is correct.
The reliable approach is to check every schedule in the week after each clock change rather than waiting to notice. It takes ten minutes and it catches the problem before it has annoyed you for a month.
Be particularly careful with heating schedules after a clock change. An hour’s offset in a heating routine is more than an inconvenience: it means a cold house in the morning or heating running while nobody is home. Check those first.
Fixed times versus solar triggers
- Use a fixed time for anything tied to your routine: waking, leaving the house, going to bed, heating.
- Use sunset or sunrise for anything tied to light: outdoor lights, curtains, security lighting.
- Use an offset to stop solar triggers reaching extremes, such as sunset minus thirty minutes rather than sunset.
- Use a combination where your system supports it, such as at sunset but no earlier than four and no later than eight. That is the arrangement that survives the whole year.
Why are my smart home schedules an hour out?
Almost always daylight saving, with one component set to adjust manually or holding a different time zone from the rest. Check the app, the hub and individual devices.
Why does my sunset routine fire in the afternoon?
Sunset moves by several hours across the year. A routine set in summer fires very early in winter. Use an offset, or a combination rule with an earliest and latest time.
Where does my smart home system get the time from?
Potentially the hub, the cloud service, individual devices or your phone. When they disagree you get schedule errors, which is why checking all of them matters.
How do I know what time a routine actually ran?
The activity log. It records the real fire time, and comparing that against the expected time gives you a precise offset that usually names the cause.
Should I check schedules after the clocks change?
Yes, within the first week. It takes ten minutes and it catches the one component that did not adjust before it has irritated you for a month.
The bottom line
Check the time zone in the app, the hub and on individual devices, because a mismatch between them is the usual cause and it is invisible until you look. Set daylight saving to automatic everywhere. Read the activity log for the real fire time, since the size of the error points straight at the cause: an hour means the clock, several hours means a sunset trigger doing exactly what you told it to.
