Twice a year, on the second Sunday in March and the first Sunday in November in the United States, clocks change, and twice a year the same question shows up across smart-home support forums: why did the kitchen smart display update itself overnight, while the oven, the thermostat and one specific streaming box are still an hour off two days later? The answer is not that some devices are smarter than others. It comes down to where a given device gets the current time from: a network time server that already knows the rule, a manually-set internal clock that does not, or a schedule tied to sunrise and sunset rather than a wall-clock hour at all.
Once that distinction is clear, the twice-yearly confusion across TVs, thermostats, routers and connected appliances stops looking random.
Network-connected devices usually fix themselves; offline-clock devices don't
A device that is online and configured to sync time automatically (most phones, computers, smart TVs, streaming boxes and smart displays) checks a network time server that already accounts for the current daylight-saving rule for its configured region, so the clock shown on screen updates itself at 2 a.m. on the changeover date without anyone touching it. A device with an internal clock that is not synced to a network time source, such as a basic microwave, a standalone alarm clock, or some older range and oven control panels, has no way to know a rule changed, because it was never told the rule in the first place; someone has to move it by hand, exactly the way it always has been.
The distinction that trips people up is a device that IS connected to Wi-Fi but still doesn't move: usually because its time setting was manually overridden at some point (a specific time zone selected instead of “automatic”), or because it takes its time from a different source than the rest of the household, such as a cable or satellite TV box that sources time from the broadcast signal rather than the home network.
A schedule can be right and the visible clock can still look wrong
Several smart-home devices, including thermostats, some smart lighting routines and irrigation controllers, let a schedule run relative to sunrise or sunset rather than a fixed clock time, so the schedule keeps making sense as day length changes through the seasons; that kind of schedule does not need daylight-saving time to “fix” anything, because it was never tied to a clock hour. Confusion shows up instead with a schedule that WAS set as a fixed hour (“turn the heat down at 10 p.m.”) on a device whose underlying clock has not yet updated for the new time: the schedule fires at the old 10 p.m., which is now an hour off from what the household clock reads.
This is also why a smart thermostat, once its own clock updates, can appear to briefly skip or repeat an hour of its programmed schedule on changeover night. The schedule itself did not move; the reference clock underneath it did, and the two are momentarily out of step until the next scheduled event after the change.
Why a device set to the wrong region can be off by an hour year-round now
Not every region observes daylight saving time (most of Arizona and Hawaii in the U.S. do not, for example), and a device whose time zone was set to a nearby region that DOES observe it (or vice versa) will read correctly for half the year and be an hour off for the other half, which is a different and less obvious failure pattern than a device that simply hasn't updated yet. If a device is consistently an hour off starting on a changeover date and staying that way indefinitely, rather than for a day or two, checking that its selected time zone actually matches the region it's used in, not just the country, is worth doing before assuming the clock itself is broken.
At a glance
Where four common device types get their time from, and what that means on changeover night
| Device type | Time source | Updates itself? | If it doesn't move |
|---|---|---|---|
| Smart display / smart speaker | Network time server (via Wi-Fi) | Yes, automatically | Check it is set to “automatic” time zone, not a manual one |
| Smart TV / streaming box | Network time server, or broadcast signal for cable/satellite boxes | Usually, but broadcast-sourced boxes depend on the provider | Restart the box; check network vs. broadcast time source in settings |
| Smart thermostat | Network time server for the clock; sunrise/sunset for some schedules | Clock: yes. Sunrise/sunset schedules: not applicable, they don't use a fixed hour | Confirm Wi-Fi connection; check whether a schedule was set as a fixed hour |
| Basic microwave / standalone appliance clock | Internal clock, set manually | No: has no rule to apply | Move it forward or back by hand, as always |
| Any Wi-Fi device stuck an hour off long-term | Likely a manually-set or mismatched time zone | No | Check the selected region matches where daylight saving time is actually observed |
Evidence ledger
Sources behind this post
The U.S. National Institute of Standards and Technology's own reference for the current daylight-saving-time rule and its legal basis.
Google's own Nest Thermostat software/connectivity troubleshooting article, relevant when a thermostat's clock isn't syncing at all.
Exact questions
Common follow-ups
Why did my smart display update for daylight saving time automatically but my oven's clock didn't?+
The smart display checks a network time server that already knows the current rule; a basic oven clock is an internal clock with no network connection and no built-in calendar rule, so it has to be moved by hand the same way it always has been.
My thermostat is connected to Wi-Fi. Why is it still an hour off?+
Being connected to Wi-Fi doesn't guarantee automatic time sync if its time zone was ever manually set instead of left on automatic, or if it lost its network connection around the changeover date and hasn't reconnected and re-synced yet.
Do smart thermostat schedules based on sunrise and sunset need to be changed for daylight saving time?+
No. A sunrise- or sunset-based schedule tracks actual daylight, which is why it was designed that way, so daylight saving time doesn't affect it. Only schedules set to a fixed clock hour are affected by the underlying clock updating.
Why does my cable box show the wrong time even though my smart TV is correct?+
Many cable and satellite boxes get their time from the broadcast signal or the provider's own system rather than from home network time, so its update timing depends on the provider's own systems rather than your Wi-Fi.
Which U.S. states don't observe daylight saving time?+
Most of Arizona and all of Hawaii do not observe daylight saving time. A device whose time zone is set to a neighboring state that does observe it will be an hour off for roughly half the year.
My smart plug's schedule seems to have shifted after the time change. What happened?+
If the schedule was set to a fixed clock hour, the schedule itself did not move. The device's underlying clock updated, so an event scheduled relative to the old hour now looks shifted until the very next event fires on the corrected clock.
How do I set a device to update its clock automatically instead of manually?+
Most devices have a time-zone or date-and-time settings menu with an “automatic” or “set by network” option versus a manual time zone; selecting automatic is what lets it check a network time source going forward, though the exact menu wording varies by device and manufacturer.
Why does my smart display briefly show the wrong time right at 2 a.m. on the changeover date?+
The change is defined to take effect at 2 a.m. local time specifically because it is a low-traffic hour for most systems; a device syncing at that exact moment can show a brief transitional state before settling on the corrected time.
Does daylight saving time affect internet-connected security cameras' timestamps?+
A camera synced to network time updates its recorded timestamps the same way any other network-time device does; a camera with a manually-set clock, or one that lost connectivity around the changeover, can log footage with an incorrect timestamp until it's corrected.
Why did my smart speaker's morning routine trigger an hour early?+
If the routine is tied to a fixed clock time and the speaker's own clock had not yet completed its sync when the routine's trigger time arrived, it can fire against the not-yet-updated internal reference before the correction completes.
Is daylight saving time the same date every year?+
In the United States it is defined as the second Sunday in March (spring forward) and the first Sunday in November (fall back), which moves the specific calendar date slightly each year even though the rule itself is fixed.
Will my devices eventually stop needing this twice-yearly change?+
That depends on future legislation in the jurisdictions that currently observe daylight saving time, not on the devices themselves. A network-time device would simply follow whatever rule its region publishes next, the same way it follows the current one.
From the troubleshooting library
Records related to this post