Skip to content

Google works on fix for Nest clock errors in Canada

The company says a small subset of devices is affected in some provinces after clock-rule changes. Users have reported late alarms and disrupted schedules, and the fix did not appear to be in place as of 4 November.

A woman in a dark coat reaches for a black bag on a rumpled bed beside a small blank-screen device. A living room is visible beyond. SI illustration
In this article

Google has acknowledged incorrect clock changes affecting some Nest devices in Canada and says it is working on a fix. Owners have reported consequences beyond the wrong time on a screen, including late alarms, altered schedules and home automations that run late or fail.

The problems followed changes in Canadian regions that ended twice-yearly clock changes. Google said on 23 October that British Columbia, Alberta, Manitoba, parts of Northwestern Ontario and the Northwest Territories would not turn clocks back on 1 November, instead remaining on daylight saving time year-round.

Alarms and schedules affected

Nest Hub and Nest Thermostat users on Reddit described incorrect device times after the clock change, 9to5Google said. Automations are actions set to run on a schedule, so a clock error can affect more than the display.

Google told Android Authority that the issue affects a small subset of devices in some Canadian provinces that no longer observe seasonal clock changes. It has not identified a complete list of affected models or provinces.

Fix has no announced release date

Before the clock change, Google warned that regional updates might not reach every user in time because of short notice and the long chain of updates needed. Some Google products could therefore still switch automatically to standard time. Its earlier guidance covered products including Android phones; 9to5Google said changing time zones on Nest devices was less straightforward.

Google has told affected users that a fix is coming, but it has not given a release date. As of 4 November, the fix did not appear to be in place.

All Technology stories