You moved your smart home from SmartThings to Home Assistant. Or from Google Home to Apple Home. Or you just refreshed your Echo Show to a newer generation. On the smart display, the widget cards that used to show your Ring camera view, the Ecobee thermostat status, and the calendar are now blank rectangles or spinning loaders that never resolve. This is the widget-cards-blank pattern that shows up after any ecosystem migration and its fix is not always obvious. This guide covers the two categories of cause and how to diagnose which is at play in your setup.
What the widget card actually needs to render
A card on a smart display is a small view that queries a specific device or account and renders a summary. To render, it needs three things simultaneously:
- An account or ecosystem link that the display recognizes as authoritative for that device.
- A permission grant giving the display’s app the right to view that device’s data.
- Cached device metadata (name, room, icon, current state) that matches what the underlying account says.
After an ecosystem migration, all three can get out of sync. The card’s app has a stale account link, the permission was implicitly revoked, and the cached metadata refers to the old device ID.
The two categories of failure
Category one is a broken account link. The display’s app is trying to talk to Ring, Ecobee, or Nest via the ecosystem that no longer owns those devices. Symptoms:
- The card shows a spinning loader indefinitely.
- Tapping the card opens a login screen or an error message referencing the old ecosystem.
- The device works in its own app but not in the display.
Category two is a stale metadata cache. The account link is fine, but the display is looking for a device that no longer exists (or that has a different internal ID after migration). Symptoms:
- The card shows the device name from before the migration, but is blank.
- Removing and re-adding the card causes it to disappear and not come back.
- The device is not listed in the display’s device chooser even though it appears in the main ecosystem app.
Recovery for category one, in order
- On the smart display, open Settings, Accounts (or Services), and find each linked service (Ring, Ecobee, Nest, etc.).
- Unlink each service that shows the old ecosystem as its source.
- Re-link the service through its updated integration flow: sign in with the account that now owns the devices, grant the requested permissions.
- Return to the home screen and add the widget card fresh. Do not restore a previous card layout, because it may still reference the old link.
Recovery for category two, in order
- Force-quit and re-launch the display’s home shell (on Echo Show: hold home button + swipe; on Nest Hub: swipe from top and tap Restart).
- If the device is still not visible in the card chooser, restart the smart display fully (unplug 30 seconds).
- In the ecosystem app, remove the device and re-add it. This regenerates its ID and forces the display to pick up fresh metadata.
- Rebuild the widget card from scratch.
Compatibility of common cards after migration paths
| Migration path | Camera cards | Thermostat cards | Calendar cards | Music cards |
|---|---|---|---|---|
| SmartThings to Home Assistant | Manual re-add | Manual re-add | Manual re-add | Not supported on HA displays |
| Google Home to Apple Home | Only via HomeKit-native cameras | HomeKit thermostats only | iCloud calendars only | Apple Music preferred |
| Alexa to Google Home | Manual re-add, camera brand must support Google | Manual re-add | Google Calendar preferred | YouTube Music, Spotify |
| Old Google Home app to new Home app (2026) | Cards migrate; some blank until manually refreshed | Same | Same | Same |
| Alexa app version upgrade (major release) | Cards persist; occasional cache flush needed | Same | Same | Same |
The specific case: Nest camera on Echo Show
Amazon and Google’s card interoperability changed twice in 2025 and 2026 with Google’s Camera-app deprecation. Nest cameras that showed on Echo Shows via the old “Works with Alexa” bridge lost that path when Google refactored their camera API. The current workflow is:
- Confirm the Nest camera is fully migrated to the Google Home app (not still on the legacy Nest app).
- In the Alexa app, disable and re-enable the Google Nest skill under Skills and Games.
- In the Alexa app, allow the discovery of new smart-home devices from the Nest account.
- On the Echo Show, remove any old Nest camera card and add a fresh one from the current device list.
Note that some Echo Show 5 and Show 8 units on the Alexa OS versions before 2026-03 do not receive the updated Nest interface at all. In that case the fix is to update the display’s firmware first: Settings, Device Options, Check for updates.
Frequently asked questions
Will my widget cards eventually restore themselves after a migration? No. They require manual re-add. The display does not automatically re-discover devices for existing cards.
Do I lose my custom card layout when I re-add cards? Yes. Save a screenshot of your layout before migrating so you can rebuild it.
Can I move cards between smart displays in the same ecosystem? Not directly. Each display has its own layout. You have to rebuild on each display separately.
Why does the calendar card work on my phone but not on the display? The phone and display have separate account links. Re-authenticate the calendar service on the display specifically.
Does a factory reset of the smart display fix widget-card issues faster? Usually yes, but it also wipes your entire display setup (Wi-Fi, account, layout, camera pairings). Save it as a last resort after account-relink and metadata-refresh have failed.
My camera card shows a still image instead of the live view. Is that a card problem? No, that is intended behavior for older display firmware or when bandwidth to the camera is limited. Live streaming to a display requires a persistent RTSP-like connection; when the display or network cannot maintain it, the display falls back to a periodic snapshot every 10-30 seconds.
Can I use widget cards from third-party services (Sonos, Roku, Plex)? Only for services with explicit integration into the display’s ecosystem. Sonos on Google Home is limited; Plex on Alexa is via a skill, not a native card. For unsupported services, the display shows nothing.
Do my widget cards drain the display’s power or bandwidth heavily? Idle cards refresh every few minutes and use trivial bandwidth. A live camera stream is the exception; it maintains a video-quality connection and uses roughly 1-4 Mbps continuously per stream.
