Skip to main content
NestGrid logoNestGrid

Smart Thermostat Schedule Off After DST? Fix It by Brand

Thermostat schedule runs exactly 1 hour off after DST; thermostat clock may show wrong time

Last updated

If your smart thermostat schedule is exactly one hour early or one hour late after the daylight saving time change, do not start by deleting the schedule. A corrupted schedule usually looks messier than that. An exact one-hour offset points first to the thermostat’s local clock, registered location, time zone, DST setting, or app/account layer.

For 2026, the U.S. spring-forward happened on March 8 and the fall-back is November 1, both at 2:00 a.m. local time under the current rule. Arizona outside the Navajo Nation, Hawaii, and U.S. territories do not observe DST, so a thermostat registered in one of those places should not be “fixed” by forcing a DST shift; check for a wrong address or time zone instead. [1]

Smart thermostat showing 6:00 AM while its schedule bar starts at 5:00 AM

The shortest useful answer is this: fix the clock before touching the schedule. Scheduled heat, cooling, comfort periods, and setbacks all depend on the thermostat’s idea of local time. If that clock is wrong by one hour, every scheduled setpoint will look wrong by the same clean amount.

The fix order that saves the schedule

Use this order before rebuilding weekday/weekend periods on the thermostat screen:

  1. Look at the thermostat itself, not only the app. Confirm whether the displayed time is wrong by exactly one hour.
  2. Check the home address, ZIP/postal code, registered location, time zone, and DST setting for that brand.
  3. Force a sync by saving the location/time-zone setting again, then rebooting the thermostat or cycling its connection as the vendor allows.
  4. Only re-enter the schedule if the device clock is now correct and the schedule still fires one hour off.
Four-step sequence showing clock check, location and time-zone sync, restart, and schedule review
What you seeWhat it usually meansWhat to do next
Thermostat display is one hour wrongDevice clock or time-zone/DST sync failedFix location, time zone, DST setting, then reboot
Thermostat display is correct, app time or schedule behavior is wrongAccount, app, home address, or hold layer is staleRefresh the home/location layer and check active holds
Home is in Arizona outside the Navajo Nation, Hawaii, or a U.S. territory and the thermostat shiftedThe thermostat may be registered to a DST-observing locationCorrect the address/time zone; do not force a DST correction
Only one comfort period is wrongThat block may have been edited, held, or copied incorrectlyInspect that period after the clock is verified

For a broader smart-home diagnosis, use Fix Smart Home Schedules After Daylight Saving Time or Why Smart Home Schedules Run an Hour Off After DST. This guide stays on the thermostat-side fix.

Google Nest: refresh the home address and location first

Status on Aug. 25, 2026: Investigating for hands-on reproduction; vendor-documented procedure available. Google says connected Nest thermostats set date and time from location information and automatically adjust for daylight saving time from the time zone. For a wrong clock, Google’s documented path is to update the ZIP or postal code in the Nest app under Settings > Home info > Address, and to make sure the thermostat’s Location menu is correct. [2]

Start there even if the address looks right. Open the home address screen, correct anything wrong, save it, then check the thermostat display. If the thermostat has a Location menu, confirm the region shown there. The point is not to rewrite the schedule; it is to make Nest recalculate local time from the right place.

  1. On the thermostat, check whether the displayed time is one hour off.
  2. In the Nest app, go to Settings > Home info > Address.
  3. Verify the street address and ZIP/postal code, then save.
  4. Check the thermostat’s Location menu if your model exposes it.
  5. Restart the thermostat after the saved location is correct.
  6. Only then test the next scheduled period.

There is also a Google Nest Community workaround report for a one-hour offset: remove the saved address, save it again, restart the app, and restart the device. Treat that as Workaround status, not as the same thing as Google’s documented support path. It is useful when the address is visually correct but appears stale in the account layer. [3]

If the Nest display time is correct but scheduled heat or cooling still happens one hour off, look for an active hold, copied schedule block, or account/app mismatch before rebuilding the whole week. For model context, see the Google Nest thermostat profile.

Honeywell Home: newer Wi-Fi models and older VisionPRO units are different jobs

Status on Aug. 25, 2026: Investigating for hands-on reproduction; vendor-documented procedures available. On newer Honeywell Home Wi-Fi thermostats, including Lyric T5, VisionPRO, and certain Prestige models, Honeywell says time updates automatically based on the registered location. That makes the registered location the first thing to verify when the clock is one hour wrong. [4]

Do not apply the same answer blindly to every Honeywell-branded thermostat. Honeywell’s own support material says pre-2007 VisionPRO thermostats do not have the updated DST dates. For those units, the documented recommendation is to disable the automatic DST feature and adjust the time manually in spring and fall. [4][5]

Honeywell Home situationLikely fix path
Newer Wi-Fi thermostat with registered locationVerify the registered home/location first, then let the thermostat sync time automatically
Pre-2007 VisionPRO with outdated DST datesDisable automatic DST and adjust the clock manually at spring and fall changes
Clock is correct but one schedule block is wrongCheck holds and schedule periods before deleting the full program

The older VisionPRO case is one of the few places where a manual seasonal clock adjustment is not a defeat; it is the documented behavior for hardware that no longer knows the current DST rule.

Sensi: fix the registration time zone, and use the general zone

Status on Aug. 25, 2026: Investigating for hands-on reproduction; vendor-documented procedure available. Sensi says that when Wi-Fi is connected, the thermostat time updates automatically from the time zone selected during registration, including daylight saving time events. Manual time setting is available only when Wi-Fi is off. [6][7]

The useful detail is Sensi’s time-zone recommendation. If the thermostat is wrong, choose a general time zone such as America/New_York instead of a region-specific one such as America/Detroit. That is a small menu choice with a large consequence: it decides which clock rule the thermostat uses. [6]

  1. Confirm the thermostat display time.
  2. Open the Sensi app registration or thermostat settings where the time zone is stored.
  3. Select the correct general time zone for the home.
  4. Let the thermostat reconnect and sync.
  5. If needed, reboot after the corrected time zone is saved.

If Wi-Fi is intentionally off, the job changes: set the time manually and accept that the thermostat is not receiving network time. For model selection and platform notes, see the Sensi thermostat lineup and the Sensi, Nest, and ecobee comparison.

Trane Home: check online status, refresh the home time zone, then reboot

Status on Aug. 25, 2026: Investigating for hands-on reproduction; vendor-documented procedure available. Trane Home says DST changes are automatic, but the displayed time may lag past 2:00 a.m. A reboot forces the update. Trane also says there is no manual time change while the thermostat is registered. [8]

That makes the Trane order fairly clean: first make sure the thermostat is online, then correct the home time zone. If the time zone already looks correct, Trane’s documented refresh technique is to switch to a different zone, save, then switch back to the correct one. After that, reboot the thermostat. [8]

  1. Verify the thermostat is online in Trane Home.
  2. Check the home time-zone setting.
  3. If it is already correct, temporarily switch it, save, then switch it back.
  4. Reboot the thermostat to force the time update.
  5. Recheck the displayed time before editing any schedule period.

ecobee: internet-derived time, limited user-side clock repair

Status on Aug. 25, 2026: Investigating; sourcing is narrower than for the brands above. The available support guide says ecobee date and time are set automatically over the internet from the selected country and region, and that users do not normally set the date and time manually on the thermostat or portal for DST errors. [9]

Diagram comparing thermostat device clock layer with home account and app location layer

Because there is no directly verified ecobee support menu path here for DST clock repair, do not invent a hidden one. Check the selected country/region and network connection, reboot if appropriate, and then contact ecobee support if the device clock remains one hour wrong. That is slower than a clean local setting, but it is better than damaging a working schedule.

Advanced Home Assistant users have a documented ecobee.set_dst_mode action. That belongs in the advanced bucket, not the normal homeowner fix path, because it assumes a separate automation platform and does not replace ecobee support when the thermostat’s own time source is wrong. [10]

Wyze: treat DST fixes as workaround-level unless your app and firmware prove otherwise

Status on Aug. 25, 2026: Workaround/Investigating only. The available Wyze evidence is user-reported forum behavior, not a vendor-documented DST repair procedure. In one March 2021 report, a Wyze Thermostat did not adjust for DST and users reported no DST toggle in the app at that time; the workaround was to shift each schedule block by an hour. [11]

A separate user report described a Wyze Thermostat schedule stuck in the wrong time zone after travel, resolved only after factory reset plus app reinstall. That is a single-case workaround, not proof that every Wyze one-hour offset needs a factory reset. [12]

Use the least destructive Wyze path first: confirm the thermostat display time, check the home and account location in the app, reboot, and look for app updates. Shift schedule blocks only if you need heat or cooling to land correctly while the clock behavior remains unresolved. Save factory reset and app reinstall for the case where the schedule appears stuck to the wrong time zone and ordinary sync steps fail.

When the clock is right but the schedule is still one hour off

This is the point where schedule editing becomes fair game, but still not as the first move. If the thermostat face shows the correct local time and the next scheduled period still starts one hour early or late, check for these before wiping the program:

  • An active temporary hold, permanent hold, vacation mode, away mode, eco mode, or comfort override.
  • A schedule edited in the app while the app/account location was stale.
  • A copied weekday/weekend block that was manually shifted during a previous workaround.
  • A thermostat assigned to the wrong home, structure, or location in the app.
  • A brand-specific bug or unsupported DST behavior that support needs to see.

If you intentionally decide to rebuild, do it after the clock is stable. For a clean reconstruction path, use Smart Thermostat Schedules for 2026-2027 Winter Forecast. If you want a schedule that follows sunrise or sunset instead of civil clock time, see Switch Smart Home Schedules to Sun Time for Permanent DST. Legislative arguments about permanent DST belong in Why Permanent DST Won't Save Your Smart Home Energy, not in the middle of getting the house warm at 6 a.m.

Last-resort order: resync, reboot, support, then rebuild

A schedule that is exactly one hour off after DST is too precise to treat as random thermostat confusion. If the displayed clock is wrong, repair the time source: registered address, ZIP/postal code, country/region, time zone, DST setting, or online sync. Reboot after the corrected setting is saved.

If the displayed clock is right but the schedule still fires wrong, inspect account/app layers and active holds. If your brand only has user-reported workarounds, label your own fix accordingly: useful, maybe necessary for comfort, but not the same thing as a documented repair.

Re-enter the schedule only when the thermostat knows the correct local time and still refuses to run the correct periods. At that point you are fixing the schedule. Before that, you are just teaching a wrong clock a new set of wrong instructions.

References

  1. When Is Daylight Saving Time? — The Old Farmer’s Almanac
  2. Change Nest thermostat time and date — Google Nest Help
  3. Google Nest Community thread 444849806 — Google Nest Community
  4. All New VisionPRO Thermostats — Honeywell Home
  5. How do I change the clock settings on the thermostat? — Honeywell Home
  6. Change and set time of thermostat — Sensi
  7. Daylight Savings Time HVAC Tips — Sensi
  8. Wrong Time on Thermostat — Trane Home
  9. How to Set the Date and Time on an ecobee Thermostat — Support.com
  10. ecobee.set_dst_mode — Home Assistant
  11. No Daylight Savings Time Adjustment - Thermostat — Wyze Forum
  12. Wyze Thermostat Schedule Uses Wrong Time — Wyze Forum

Corroborating context

For protocol background on why this failure happens, see Compatibility & Protocols.

Not currently linked to a known regression. Background on the underlying protocol lives in Compatibility & Protocols.

Other fixes for this device

Report / Feedback

If this fix didn't hold on your exact hardware/firmware combination, file a scoped report -- it feeds the re-verification queue instead of an open comment thread.

Blogarama - Blog Directory