Your Echo Show or Nest Hub displays weather from this morning at 8 PM. The calendar widget shows yesterday’s events. News headlines are from days ago. The display is online (voice commands work, you can stream music), but the displayed information is stale. The widgets cache aggressively and do not refresh.
How widget data updates
Each widget on a smart display pulls data on its own schedule:
- Weather: usually hourly
- Calendar: every 15-60 minutes
- News: every few hours
- Photos: rotates within a session, refreshes from source on a schedule
The schedules are set to balance freshness against API calls and network use. They are usually appropriate, but can leave a widget showing stale data for a while.
Force a refresh
Most widgets refresh when the display is touched or when you interact with the home screen. Tap the widget, swipe, or just touch the screen.
If touch does not refresh, ask the voice assistant: “Hey Google, what is the weather?” or “Alexa, what is on my calendar today?” The voice query pulls fresh data and updates the widget.
Restart the display
If widgets are persistently stale across multiple types, the display’s data sync is hung. Restart the display by unplugging for 30 seconds.
After restart, all widgets pull fresh data during boot.
The home screen update interval
The home screen as a whole refreshes on an interval. Echo Show: usually every 15 minutes. Nest Hub: similar.
The interval is not user-adjustable. If you need real-time information, do not rely on the home screen for it.
The cloud sync delay
If your calendar widget shows yesterday’s events, the underlying calendar may have synced new events but the widget is still on yesterday’s cache.
Verify in your calendar app that the new events are visible. Force a sync between the calendar service and the widget by editing the calendar integration in the smart home app.
The locale mismatch
If your smart display is set to a different locale than your data source (Spanish display showing English weather), the display may not understand the data and show a default.
Verify locale settings match across display and data source.
The display has a different location
If your weather widget shows a different city than where you actually are, the display’s location is wrong.
Echo Show: Alexa app, Settings, your Echo, Location.
Nest Hub: Google Home app, your device, Settings, Address.
Update to your current address.
The widget specifically
If only one widget is stale (weather is current but calendar is not), focus on that widget’s integration:
- Calendar integration is linked correctly?
- Calendar OAuth token is valid?
- Calendar permission is granted?
Re-link the affected integration in the smart home app.
The news source change
If your news widget is stale, the configured news source may be inactive. Some news sources stop updating; others get retired.
In Alexa app: Settings, Flash Briefing, verify sources are active.
In Google Home app: choose newer news sources if your configured ones are outdated.
The notification disable
If you disabled notifications, some widgets do not refresh because they rely on notification-triggered updates.
Enable notifications for the relevant categories.
The home screen mode
If the display is in a quiet mode, ambient mode, or do not disturb, widget updates may be suppressed. Take the display out of the quiet mode temporarily.
The data source rate limit
If many users of a free data source hit it at the same time, the source may rate-limit the smart home cloud. The cloud serves stale cached data instead of fresh.
This is rare but happens with free weather APIs. The fix is to wait for the rate limit to clear.
The factory reset of widget
Some widgets can be removed and re-added through display settings. Removing and re-adding clears local cache.
The display software update
If widget refresh logic was buggy in older firmware, an update may fix it. Verify display is on current firmware.
The third-party integration
If your widget is from a third-party (a custom skill that displays data), the third-party may have stopped functioning. The widget shows stale data because no fresh data is arriving.
Check the third-party service’s status. Remove the widget if the service is dead.
The internet quality
If your internet is slow or has high latency, widget refresh may time out. The widget keeps showing old data because the fresh fetch failed silently.
Test internet performance. Improve if needed.
The interaction with display power saving
If the display goes to sleep or low-power mode, refresh may pause. When the display wakes, the widgets have not been updated during the sleep.
This is by design. The first interaction after sleep should trigger updates.
Realistic expectations
Smart displays are not real-time information dashboards. They are convenience tools. If you need second-by-second accuracy, look elsewhere. For “good enough” weather, calendar, and news, the displays serve adequately when properly configured.
The widget that reports stale data on purpose
Some widgets are designed to lag intentionally. Weather widgets, for example, often show the daily forecast rather than the current hour because forecasts are pulled from a less expensive data source. The widget is doing what its designer intended, even when it looks stale to you. Check the widget’s documentation or settings; you may be able to switch it from forecast mode to current mode.
The same applies to news widgets that show headlines from the morning rather than updating throughout the day. The publishing cadence of the news source matters more than the widget’s refresh rate. If your news source updates once per day, the widget will only ever show that day’s content regardless of how often it refreshes. Either switch to a news source that updates more frequently, or accept the daily cadence.
The widget priority order
Smart displays refresh widgets at different rates based on how the device prioritizes them. Weather usually refreshes hourly, calendar every fifteen to thirty minutes, news only a few times per day. If the calendar widget feels stale, you can sometimes force it to refresh more often by setting it as the primary widget.
This is undocumented but works on most Echo Show and Nest Hub models. The wider topic of how widgets behave on smart displays is in our smart display freeze guide.
