Daylight saving time ends 2026 — check your smart home

Confirmed status as of August 25, 2026

Daylight saving time is still scheduled to end at 2:00 a.m. local time on Sunday, November 1, 2026. If you searched for what happens to smart home devices if daylight saving time ends 2026, the practical answer is: plan for the fall-back unless the law changes after this verification date. USA Today reported the November 1 end date for 2026, and no Senate action has changed the outcome as of this article’s August 25 check. [1]

The legislative noise is real, but it has not removed the clock change. H.R.139, the Sunshine Protection Act, is the bill in play; the House passed it 308–117 on July 14, 2026, but a Senate vote and the president’s signature would still be required before the schedule changes. [2][3][4]

The smart-home problem is usually not a dramatic failure

A clean clock change should be boring: the hub keeps network time, the phone reports the correct local time, and scheduled routines continue at the intended local hour. The failures worth checking are the quieter ones. A porch light comes on at yesterday’s version of sunset. A thermostat schedule shifts by an hour because the device’s own clock did not move correctly. An older controller still follows daylight saving rules that no longer match the calendar.

The useful sorting question is simple: where does this device get its time? Network-synced hubs and phone-driven apps are usually the least suspicious. Devices with onboard clocks deserve inspection. Devices with old, hardcoded daylight saving rules deserve special attention, because they may appear healthy while using the wrong local time.

Pre-flight check before Saturday night

Run this before the house is depending on the automation. Saturday night is a bad time to discover that the app has no useful error message and the device log only says the routine “ran.” The goal is not to test every smart device in the house. It is to inspect the three places where an exact one-hour drift is plausible.

1. Sunrise and sunset automations

Sunrise and sunset routines look simple from the outside, but they are calculated values. The controller needs the home location, the date, the time zone, and the current offset from UTC. If one part updates and another part does not, the routine may still fire, just one hour away from the moment you expected.

That pattern has shown up in user-facing reports before. In a Hubitat community thread from 2018, staff discussed a transition-day issue where sunrise and sunset times were wrong until recalculation logic caught up. Treat that as corroborating context, not proof that your hub will fail in 2026. The useful lesson is narrower: sunrise and sunset automations can be wrong while the hub otherwise looks alive. [5]

• Open the automation before the fall-back and check the next scheduled event time, not just whether the routine is enabled.
• Confirm the home location used by the platform. A wrong or missing location can make sunrise/sunset logic unreliable even when fixed-time routines are fine.
• If the app shows both a condition and a trigger, check both. A light that turns on “at sunset” but only “between 5 p.m. and 11 p.m.” can be affected by either calculation.
• For important exterior lighting, add a one-night backup fixed-time rule or reminder, then remove it after verification.

This is also the place to be suspicious of clever offsets. “Sunset minus 20 minutes” is still a sunset calculation. If sunset recalculates incorrectly, the offset can faithfully preserve the wrong answer.

2. Fixed-time schedules on devices with onboard clocks

A fixed-time schedule is only as good as the clock reading it. If a thermostat, plug, irrigation controller, appliance, or older bridge stores its own schedule locally, the app may not be the only clock in the chain. The app can say “7:00 a.m.” while the device’s internal idea of 7:00 a.m. is now an hour out of step.

Home Assistant users have reported this kind of symptom around a DST transition as well. In a March 2023 community thread, a Times of Day sensor was described as running an hour late after the change until a restart. Again, this is a user report, not a universal finding. It is useful because it matches the failure shape: no total outage, just local time logic drifting by exactly one hour. [6]

• Check thermostats first if they control comfort overnight or early Sunday morning.
• Check any device that can run without the hub after setup: plugs with built-in timers, wall switches with local schedules, irrigation controllers, robot vacuums, pet feeders, and appliance timers.
• Compare three things: the device display, the app display, and the next scheduled run time.
• If a schedule is built inside a controller rather than inside the end device, check the controller’s timezone and schedule preview instead of hunting through every bulb or plug.

If your controller setup has become hard to audit, use the schedule inventory approach in the Home Automation Controller Setup Guide before rebuilding anything. The fastest fix is often finding the one local schedule you forgot existed.

3. Devices with hardcoded DST rules

Older devices are the least forgiving because they may not ask the network what time it is. Some were designed around daylight saving rules stored in firmware. If those rules do not match the current calendar, the device can adjust on the wrong weekend, fail to adjust, or require a manual DST setting.

Honeywell’s support guidance for some pre-2007 VisionPRO thermostats is a useful example of the mechanism. Honeywell says those thermostats did not receive updated daylight saving dates and recommends disabling automatic DST and changing the time manually. That does not mean every thermostat has this problem; it means older onboard-clock devices should not be waved through without inspection. [7]

• Look for settings named DST, Daylight Saving, Auto DST, Summer Time, or Time Zone.
• If the device offers automatic DST but is old enough to predate current rule updates, check the vendor’s support page before trusting it.
• If the device has a manual DST toggle, note its current position before changing it. A wrong toggle can create the same one-hour drift you are trying to prevent.
• For a thermostat or controller with an obviously wrong clock, correct the clock first, then inspect the schedule. Do not edit comfort periods while the base time is wrong.

Morning-after verification

On Sunday morning, do not stop at “everything is online.” Online only means the device can communicate. It does not prove the local schedule fired at the intended local time. The pass below is quick because it checks outcomes instead of explanations.

For lighting, the cleanest test is the next scheduled event. For thermostats, check both the displayed time and the active program period. A thermostat that says it is in the right mode can still be running the wrong time block if the onboard clock is wrong.

If something is exactly one hour off

An exact one-hour error is a clue. Treat it as a time-source problem before rewriting automations. Random failures, offline devices, and broken integrations can happen on the same weekend, but they do not usually land exactly one hour early or late.

1. Identify where the schedule lives: hub, cloud app, phone, bridge, or device.
2. Check the clock at that layer before changing the routine.
3. Look for a next-run preview or last-run history. If the log says the automation ran, compare the logged time with the real-world event.
4. Restart only the layer that appears stale. Restarting everything can erase the trail you need.
5. After correction, create one near-term test event and watch it fire.

If the symptom spreads across multiple Matter devices or a shared controller layer, move to broader platform diagnosis instead of editing each endpoint. The Matter 2026 Troubleshooting Guide is the better path when the clock issue is mixed with pairing, fabric, hub, or bridge symptoms.

What not to chase before 2:00 a.m.

Do not spend Saturday night rebuilding routines for a law that has not taken effect. Do not assume “cloud-connected” means “verified.” Do not trust a green status dot as a time check. The practical work is smaller and more useful: confirm the fall-back is still scheduled, inspect sunrise/sunset logic, inspect onboard-clock schedules, and give older DST-rule devices a manual look.

If the Senate acts after this August 25, 2026 status check, the first thing to update is the calendar instruction. Until then, the November 1 fall-back remains the event your smart home has to survive.

References

1. Nov. 1 is when daylight saving is over but Trump has other plans, USA Today, July 31, 2026
2. H.R.139 - Sunshine Protection Act, Congress.gov
3. What Impact Would a Switch to Permanent Daylight Saving Time Have?, WTTW Chicago, July 27, 2026
4. Latest Updates: Daylight Saving Time Legislation Change, Sleep Foundation
5. Sunrise/Sunset Time Wrong, Hubitat Community, November 2018
6. Times of Day sensor wrong after Daylight Savings Time, Home Assistant Community
7. Why is my thermostat not adjusting for Daylight Saving Time?, Honeywell Home