Voice control

Voice assistant says the device is not responding

Alexa or Google Assistant reports that the device is not responding even though the vendor app controls it fine.

Applies to
  • Alexa and Google Home integrations
  • Skills and linked services
  • Devices renamed or moved to another room
Last verified2026-10-14
Quick answerTroubleshooting · last verified 2026-10-14

Alexa or Google Assistant reports that the device is not responding even though the vendor app controls it fine. Most common cause to check first: Device renamed in the vendor app after discovery

Applies toAlexa and Google Home integrations, Skills and linked services, Devices renamed or moved to another room
CategoryVoice control
Escalate whenIf a renamed device breaks voice control but the app works, the fix is discovery and naming, not re-pairing the device.
Last verified2026-10-14
How to cite this pageIoT Atlas. "Voice assistant says the device is not responding". https://hi-spark.net/troubleshooting/voice-assistant-device-unresponsive.html Last verified 2026-10-14.

Likely causes

  • Device renamed in the vendor app after discovery
  • Account link expired or password changed
  • Skill or integration removed and re-added
  • Duplicate device names in the same home
  • Region or language mismatch in the assistant account

Quick checks

  • Test the device in the vendor app first
  • Say the exact device name as it appears in the assistant app
  • Check the linked account status in the assistant app
  • Look for duplicate entries with the same name

Step-by-step fix

1

Confirm the device works in the vendor app

2

Re-run device discovery in the assistant app

3

Rename devices so each name is unique in the home

4

Re-link the account if the status shows an error

5

Disable and re-enable the skill or integration if discovery fails

Frequently asked questions

Why does this happen: Voice assistant says the device is not responding?

Alexa or Google Assistant reports that the device is not responding even though the vendor app controls it fine.

What is the most likely cause?

Device renamed in the vendor app after discovery; Account link expired or password changed; Skill or integration removed and re-added.

What should I check first?

Test the device in the vendor app first; Say the exact device name as it appears in the assistant app; Check the linked account status in the assistant app; Look for duplicate entries with the same name.

How is it fixed?

Confirm the device works in the vendor app; Re-run device discovery in the assistant app; Rename devices so each name is unique in the home; Re-link the account if the status shows an error; Disable and re-enable the skill or integration if discovery fails

When should the case be escalated?

If a renamed device breaks voice control but the app works, the fix is discovery and naming, not re-pairing the device.