Google fixes daylight saving time bug affecting Nest and Lenovo smart home devices

TL;DR Google says it has resolved the daylight saving time issue that caused incorrect timers and alarms on some smart home devices. The confirmation comes through Google’s Nest Community account on Reddit, following reports involving Nest and Lenovo devices. Google is asking users still experiencing problems to report them. Smart homes in parts of Canada have spent the week struggling with something their owners…

Affiliate links on Android Authority may earn us a commission. Learn more.

Nov 6, 2026 — 3:40 AM ET

- Google says it has resolved the daylight saving time issue that caused incorrect timers and alarms on some smart home devices.

- The confirmation comes through Google’s Nest Community account on Reddit, following reports involving Nest and Lenovo devices.

- Google is asking users still experiencing problems to report them.

Smart homes in parts of Canada have spent the week struggling with something their owners rarely have to think about: telling the correct time. After several days of misplaced hours, unreliable alarms, and disrupted routines, Google says it has finally straightened things out.

In replies to Reddit discussions, the official Google Nest Community account confirmed that the daylight saving time issue affecting timers and alarms has been resolved. The account also posted the same confirmation involving Lenovo Smart Clock devices, suggesting the fix extends beyond Google’s own hardware.

Hey all, the issue with Daylight Savings Time causing some timers and alarms to be incorrect has been resolved.

The trouble began following the November 1 clock change, when devices in Canadian regions observing permanent daylight saving time incorrectly adjusted their clocks. Some Lenovo Smart Clock and Clock Essential owners found their displays running an hour behind, even when Google Assistant knew the correct time.

The problem also affected Google’s Nest devices, with users reporting alarms firing an hour late, disrupted automations, and thermostat schedules behaving unexpectedly. Google subsequently acknowledged the issue, telling Android Authority that it affected a small subset of devices in certain Canadian provinces and that a fix was underway.

Encouraging signs are already coming from Lenovo owners reporting that their clocks have returned to normal, so it should be a matter of time before every affected device gets the fix. Google hasn’t detailed how it’s delivering the fix, but devices correcting themselves without user intervention suggest it may be a server-side fix.

If you’re still seeing incorrect times or alarms, Google wants to hear about it. It’s also worth checking existing alarms and schedules to make sure everything is running on time again.