Lenovo Smart Clocks Show Wrong Time After Canada Time Change

If your bedside smart clock suddenly cannot be trusted to tell the time, you are not alone. In the days after Canada’s November 1 time change, owners of Lenovo Smart Clock devices across several Canadian regions have reported that their displays are showing the wrong time — off by an hour — even though the voice assistant on the same device can still answer the time correctly. For a device whose main job is to be a clock, that is more than a cosmetic glitch: it affects alarms, timers, and the routines people build around them.

The reports surfaced on November 2, the day after the changeover, and they point to a specific and still-unexplained gap between Lenovo’s older Google Assistant clocks and the new permanent time rules in parts of Canada. Neither Lenovo nor Google has yet publicly confirmed a fix, according to Android Authority, which says it has contacted both companies and will share updates when they reply.

What owners are reporting

According to Android Authority’s November 2 report, several Lenovo Smart Clock units are showing the incorrect time in many parts of Canada. The problem has been reported on both the Lenovo Smart Clock and the smaller Lenovo Smart Clock Essential, based on user reports on Reddit.

What makes the reports striking is how consistent the pattern is. Owners say other Google Home devices in the same homes — including the TV Streamer and other smart displays — updated correctly to the new time. Only the Lenovo clocks are off. That contrast is why owners have been quick to treat this as a device-specific problem rather than a household Wi-Fi or account issue.

There is a second, stranger detail. When owners ask the clock for the time, Google Assistant answers correctly, even though the display itself shows the wrong time. The voice answer and the visible clock appear to disagree on the same device, which suggests the problem sits in how the clock face itself handles the new time rules, not in the device’s connection or its general knowledge of the time.

Which devices and regions are affected

The affected devices are the two Lenovo models that have long served as Google Assistant bedside clocks: the Lenovo Smart Clock, which has a small touchscreen display, and the Lenovo Smart Clock Essential, which uses a simpler LED display. Both models were reported as affected, with Essential owners prominent among the early reports.

The affected regions reported so far are in Canada, where several territories recently moved away from the twice-yearly clock change. Android Authority lists Alberta, parts of British Columbia, Manitoba, Northwestern Ontario, Saskatchewan, and Yukon among the areas that have permanently switched to daylight saving time. Reddit reports cited in the article specifically mention owners in Alberta, British Columbia, and Manitoba seeing the wrong time.

Google had warned last month that the final time change, due on November 1, could turn the clocks back by an hour on Android devices that are old or running outdated software. The Lenovo clock reports fit that warning in broad terms: devices that still apply the old seasonal rule end up an hour out of step once the rule no longer applies. But Google’s warning was about Android devices in general, and the Lenovo reports show the problem reaching into the smart home, where a clock is often the device people glance at first thing in the morning.

Why this matters more than a wrong display

A smart clock is easy to dismiss as a minor gadget until it gets the time wrong. Android Authority notes that the frustration is understandable precisely because owners rely on the Smart Clock’s core job — being a clock — for alarms, timers, and other time-sensitive routines. A display that is an hour off can mean waking up late, missing a reminder, or mistrusting every timer the device shows.

The split between the correct voice answer and the wrong display makes the problem harder to live with, not easier. A user who asks the clock for the time gets the right answer, but the number they see every time they glance at the nightstand is wrong. For a bedroom device, the glance is the whole point.

There is also a generational wrinkle. The Smart Clock Essential still runs Google Assistant and has not fully moved to Gemini, while the non-Essential model with a full display started migrating to Gemini last year, according to Android Authority. That difference has not been shown to cause the time bug — both models are reported as affected — but it is a reminder that these are older devices on different software paths, which can make a single clean fix harder to roll out.

The workarounds owners have tried

So far, the fixes owners have tried on their own have been limited, and none of them counts as an official solution.

• Factory reset does not help. Owners report that resetting the clock does not correct the display, which points away from a corrupted setting on an individual device and toward a broader software or time-zone data problem.
• A home-address workaround has worked for some. Some users say they fixed the displayed time by switching their home address to another region whose time matches their actual location. That is a user-discovered workaround, not guidance from Lenovo or Google, and it is worth treating with caution: changing a home address can affect other location-based features, so it is a stopgap at best, not a repair.
• Checking other devices helps confirm the scope. Owners have compared their Lenovo clocks with other Google Home devices, which updated correctly. If your other displays are right and only the Lenovo clock is wrong, the evidence points to the clock itself rather than your account or network.

Until Lenovo or Google issues a fix or guidance, the safest approach for anyone who depends on a Lenovo Smart Clock for waking up is to cross-check alarms against another device — a phone, or another smart display that updated correctly — rather than trusting the Lenovo display alone.

This has happened before

The Lenovo reports are not the first time a permanent time-rule change has tripped up smart displays. Android Authority notes a similar pattern in 2022, when Jordan permanently adopted summer time, and again in 2023, when Mexico discontinued daylight saving. In those cases, the resolution took months, though it is unclear how long a fix might take this time.

That history matters for expectations. Time-zone data lives in many layers — the operating system, the device software, and the services behind it — and a device that misses an update at any layer can keep applying a rule that no longer exists. The fact that the voice assistant answers correctly while the display does not hints at exactly that kind of layered mismatch, though neither company has confirmed the cause.

It also matters for who should act. This is not something owners can reliably fix by changing a setting, as the failed factory resets show. It needs a software or time-zone data update from Lenovo, Google, or both, pushed to the affected models.

What to watch next

Three things will determine how quickly this fades from a daily annoyance to a footnote. First, whether Lenovo or Google acknowledges the issue publicly and names the affected models. Second, whether a fix arrives as an automatic update or requires owners to take action. Third, whether the same problem appears on other older Google Assistant devices as more regions settle into their new permanent time rules.

For now, the practical advice is simple. If you own a Lenovo Smart Clock or Smart Clock Essential in an affected Canadian region, check the display against a known-good clock after November 1. If it is an hour off, do not assume a reset will fix it, and do not rely on it alone for alarms until an official update lands. And if you have found the display wrong, it is worth watching for statements from Lenovo and Google — this is the kind of bug that only the manufacturers can properly close.

Smart clocks are supposed to remove one small daily friction: glancing at the time and trusting it. The November 1 changeover has shown how much quiet infrastructure sits behind that glance, and how visible it becomes when one layer of it falls an hour behind.