Smart Appliance Not Responding to Alexa or Google

Smart or mechanical?#

Ask one question: does the appliance still respond to its own brand app (SmartThings/ThinQ/SmartHQ)? If yes, the problem sits between the voice assistant and the brand cloud — stay here. If no, the appliance itself is offline from the brand cloud; fix that Wi-Fi connection first.

The five-hop chain#

A voice command travels five hops: your voice to the assistant; the assistant's cloud processes it; the assistant calls the brand's cloud API through the linked skill; the brand cloud sends the command to your home network; and your router delivers it to the appliance. A break at any hop reads as "device not responding," and hop three — the skill link — is the most fragile, because it expires every 90-180 days and needs re-authentication.

Fix 1: re-link the brand skill#

For Alexa: More > Skills & Games > Your Skills > the brand skill > Disable, then Enable > Link Account > re-enter credentials, and say "Alexa, discover devices." For Google Home: Settings > Works with Google > the brand > Unlink > Re-link > re-enter credentials, then "Hey Google, sync my devices." For Siri, most brands need a bridge (Homebridge or Home Assistant); check the bridge's link to the brand cloud.

Fix 2: check for a cloud outage#

Brand clouds go down for maintenance. Check the brand's status page (Samsung and Amazon publish one; GE does not, so an unresponsive SmartHQ app usually means the cloud is down). During an outage the appliance still runs from its physical controls — only remote and voice control are affected.

Fix 3: names and discovery#

Voice assistants match appliances by the names you set. If you renamed an appliance in the brand app but not in the assistant, commands fail. Make the names match, keep them simple and distinct ("kitchen [dishwasher](/blog/repair-or-replace-dishwasher)" beats "Samsung DW80R9950US"), and re-run discovery after renaming.

Brand-specific quirks#

Samsung runs two Alexa skills — the newer "SmartThings" and a legacy "Samsung Smart Home"; use SmartThings and unlink the legacy one to avoid duplicates. LG's Google integration supports fewer commands than the ThinQ app, so a command that works in the app may not exist through Google. GE's skill appears as "GE SmartHQ" or "Geneva" depending on region — try both. Whirlpool's Google integration is known to let status queries work while action commands intermittently fail; re-linking usually fixes it.

Why re-linking fixes so much#

The reason "just re-link the skill" resolves the majority of these is that the skill link is a rolling authorization, not a permanent connection. Every 90-180 days — and immediately whenever you change your brand-account password — the token that lets the voice assistant speak to the brand cloud on your behalf expires, and the assistant has no way to renew it silently. From your side nothing changed, which is exactly why it feels like a random failure, but under the hood the handshake simply timed out. Disabling and re-enabling the skill forces a fresh handshake and a new token, and the appliance reappears. Do this before any other step, because it costs a minute and clears the single most common cause.

When it is a technician's job#

Voice issues are almost never hardware. If the appliance works from its physical controls and from the brand app, the fault is in the cloud integration, not the machine. Only if the appliance also will not respond to the brand app, after you have exhausted Wi-Fi troubleshooting, does the Wi-Fi module become a suspect for replacement. Before assuming that, confirm the appliance shows connected in its brand app, your Wi-Fi is up, and the skill is linked — and note that router band steering, which can shove the appliance from 2.4 GHz onto a 5 GHz band it cannot use, is a common hidden cause of intermittent voice failures.

---

Smart appliance ignoring voice commands? Book a free diagnostic — our technicians handle both the connected side and the traditional repair.