You had a power outage. After power restored, your smart display shows the wrong time. It might be off by hours (showing UTC instead of local), or off by a few minutes. The display’s clock is wrong, and that affects everything: alarms, reminders, scheduled routines, time-based widgets.
Why the time is wrong
Smart displays do not have battery-backed clocks. When power is lost, their internal clock resets. After power restoration, they need to:
- Boot up and connect to Wi-Fi
- Query an NTP server for current time
- Determine their location for time zone
- Apply daylight saving rules
If any step fails or is slow, the display shows an incorrect time.
Verify network connectivity
The display needs internet to sync time. If it is showing the wrong time, check that it is online. Ask Alexa or Google for the weather; if it responds with current weather, the display has internet and the time issue is elsewhere.
If the device is offline, fix that first.
Check the configured location
The display uses the location set in its account or settings to determine time zone.
For Echo Show: Alexa app, More, Settings, Device Settings, your Echo Show, Device Location. Verify the location is correct.
For Nest Hub: Google Home app, your device, Settings, Device Information, scroll to Address. Verify the address.
If the location is wrong, the time zone calculation is wrong even if NTP is working.
Restart the display
If the time is wrong but location and network look fine, a restart often resyncs the clock cleanly. Unplug for 30 seconds, plug back in. After boot, the display should show correct time within a minute.
The auto-detect time zone setting
Some displays auto-detect time zone based on IP geolocation. If you use a VPN or your ISP routes traffic through a distant data center, the detected location may be wrong.
Override with manual time zone selection if available. This is more reliable than auto-detect for VPN users.
Daylight saving issues
If the time is off by exactly one hour, DST is the likely culprit. The display may be using stale DST rules or may have failed to apply the recent DST transition.
Force a sync by restarting the device. The fresh time pull will use current DST rules.
The NTP server unreachable
Some networks block NTP traffic. If your firewall blocks outbound UDP port 123, the display cannot reach NTP servers.
Check your firewall rules. Allow outbound NTP for the display’s IP.
The device’s stored time zone
Even with location set correctly, the device may have a separate time zone setting. Verify it matches the location.
This is sometimes split: location is for weather and sunrise, time zone is for clock. Both should match.
The 12 versus 24 hour format
If your display shows the right time but in a confusing format (24-hour when you expect 12-hour), check the format setting in the device’s display preferences.
The home address issue
Both ecosystems use home address for various functions. If you moved and did not update the address, the display thinks you are in the old location.
Update home address in the account settings.
The default time zone fallback
If the device cannot determine its time zone, it falls back to a default (often UTC or the account’s primary time zone). Symptoms: time is exactly UTC, or matches a time zone other than your physical location.
Manually set the time zone to override the fallback.
The Wi-Fi router clock
Some routers act as NTP servers for their network. If the router’s own clock is wrong, devices using it as NTP source get the wrong time.
Check your router’s time. Set the router to use external NTP servers (pool.ntp.org, time.google.com).
The slow boot during outage recovery
If multiple devices are coming online simultaneously after an outage (because the whole house lost power), there is contention for network resources. The display’s NTP query may time out and use a default value.
Stagger device power-on after outages if possible. Or accept that initial time may be wrong, and rely on the next sync (typically within an hour) to correct.
The Echo Show specific quirk
Some Echo Show models have shown time drift over weeks of uptime. The clock slowly diverges from real time even when the device is online. The fix is a periodic reboot.
Adding a weekly restart helps with this drift, in addition to its memory benefits.
The displayed clock versus the actual time
The clock shown on the display may not exactly match the device’s actual internal time. If you ask Alexa what time it is and she responds with a different time than the display shows, the display widget is using a slightly stale time. This is rare but happens.
Restart fixes this.
Realistic expectations
Smart displays should sync time within a minute of coming online. If your display consistently takes longer or shows wrong time persistently, the underlying network or location config is at fault and needs addressing.
The UPS that saves more than data
A small UPS on your router and smart display prevents the time-reset cascade after brief power outages. The router stays up, your devices never lose Wi-Fi, the displays never have to re-sync time from NTP. The cost is modest and the operational benefit is daily.
For households where power blips happen even occasionally (during storms, neighbor construction), a UPS is worth more than it costs. The broader topic of outage resilience is in our ISP outage guide.
The NTP source verification
If your network blocks outbound NTP traffic (some corporate or enterprise networks do), smart displays cannot sync time and stay on whatever time they had at boot. Verify your router allows outbound UDP 123 traffic. If you must restrict NTP, allow specific known servers like pool.ntp.org. The wider context of network gotchas is in our camera app crash guide.
The chained-device timing problem
If multiple devices reset their time after an outage, fix the one that other devices depend on first. A smart thermostat that runs schedules from local time will misbehave if it boots before NTP sync completes. The wider pattern of post-outage device sequencing is covered in our thermostat recovery guide.
