You have a routine that runs when you tap a specific button on your smart display’s home screen. The button worked for months. Today it does not. The button is visually still there but tapping does nothing. The routine itself still runs from voice or app trigger; just the display button is dead.
What is happening
Routine buttons on the home screen are special: they require both the touch input to work and the routine link to be valid. If either is broken, the button fails.
Most cases: the routine reference was broken by a recent change. The button is still on screen but pointing at an invalid routine.
Check the routine in the app
Open your smart home app. Find the routine that the button is supposed to trigger. Is it enabled? Does it still exist with the same name?
If the routine was renamed or deleted, the button reference may be broken. Re-create the button or update its link.
Restart the display
If the routine is fine but the button still does not work, the display’s local state may be stuck. Restart the display.
The touch screen check
If multiple buttons or interactive elements on the display do not respond, the touch screen itself may be faulty.
Test touch on other parts of the display. If touch works elsewhere but specifically the button area is dead, the routine link is the issue. If touch is dead everywhere, hardware fault.
The home screen layout reset
Some updates reset the home screen layout. Buttons you had configured may have disappeared and been replaced with default tiles.
Re-add the routine button to your home screen.
The widget configuration
Routine buttons are often part of a widget configuration. If you modified widgets recently, the button may have been removed.
Open widget settings on the display. Look for routine button options. Add or restore.
The voice trigger versus button
Voice triggers a routine using the routine’s voice phrase. Button triggers use a direct routine ID. If the routine ID changed (some routines have IDs that change with edits), the button reference becomes stale.
Delete the button and re-add it to fix the ID reference.
The Alexa-specific behavior
On Echo Show, the home screen tiles are limited. Some tiles are routine-based and some are not. If you cannot find your routine button, it may have moved to a sub-menu.
Browse Settings, Home Content to find available widgets.
The Google Home tile
On Nest Hub, certain home automation actions appear as tiles. If your tile is gone, the underlying integration may have lost the action’s exposure.
Refresh the integration in Google Home app.
The household account access
If you are not the home owner, you may have limited access to routine buttons. Verify your account has permission to use the affected routine.
The screen lock mode
If the display is in a locked or kiosk mode for guest use, button interactions may be restricted. Verify the display is in its normal mode.
The notification overlay
If a notification or dialog is partially over the button, taps may be intercepted by the notification rather than the button. Dismiss any visible notifications and retry.
The visual versus actual
Sometimes the visual element appears but the underlying touch handler is not bound. The button looks tappable but is actually not interactive.
Force-quit and restart the display app (Alexa Home, Google Home equivalent on display) if available. Otherwise restart the device.
The action versus shortcut distinction
Routines and Quick Phrases are different. If you set up something called “routine button” but it is actually a Quick Phrase, the behavior differs.
Verify what type of widget you actually have.
The screen calibration
Touch screens can become miscalibrated. A tap registered at a different position than where you actually touched. This is rare on modern displays but happens.
Calibrate or factory reset the display.
The third-party skill
If the button was created by a third-party skill, the skill may have stopped publishing the button. Verify the skill is still installed and enabled.
The temporary glitch
Sometimes the issue is transient. Wait a few minutes and retry. Some display glitches resolve themselves.
The hardware diagnostic
If the issue persists across restarts and the screen seems otherwise responsive, the routine button feature may be specifically broken on this device. Factory reset and re-setup may resolve.
The shortcut that lost its target
When a routine button stops working and you cannot find why, the underlying shortcut definition may have been deleted from the cloud. The button is a local reference to a cloud-stored shortcut. If the cloud-side shortcut was deleted (sometimes through unrelated app cleanup), the local button still appears but has nothing to invoke.
Verify the shortcut still exists in your account’s shortcut list. If it does not, recreate it with the same name and bind a new button to it. The old button can be deleted; the new one inherits the role.
The button that needs a confirming tap
Some smart displays have a confirm-on-tap setting for routine buttons to prevent accidental triggers. If accidentally enabled, the button needs a second tap to actually fire, which feels like the first tap did nothing. Check display settings for confirmation requirements on routine actions.
For routines that are tied to safety actions (unlock door, disable alarm), confirmation is intentional. For convenience actions (turn on lights, play music), disable confirmation to make the buttons feel responsive.
The screenshot-before-reset principle
Before factory resetting any smart display, take screenshots of every customization that lives only on the device: home screen widgets, routine buttons, alarms, do-not-disturb schedules. After reset you will need these as a checklist for re-setup.
This adds ten minutes to the reset process and saves an hour of rebuilding from memory afterward. The wider topic of smart display recovery is in our display replacement guide.
The shortcut that survives reboots
For routines you trigger most often via display buttons, set up an equivalent voice command as a backup. When the button stops working, the voice command is your fallback while you troubleshoot. The redundancy is cheap and the resilience is real. The wider context of display-side reliability is in our display widget guide.
