You say “turn off the kitchen lights” and Alexa, Google, or Siri responds “I cannot find any kitchen lights”. The lights are on. They are visible in the smart home app. They work when you tap them. The voice assistant just does not see them right now. The cause is usually a stale discovery cache, which you can refresh in a couple of minutes.
Why discovery drifts
Voice assistants cache device lists. The cache is built from the integration’s cloud (Hue cloud, manufacturer cloud) periodically. Between refreshes, if a device changes its identifier or its name or its room, the voice assistant’s cache can become inconsistent with reality.
Common triggers:
- You renamed a device in the source app
- You moved a device between rooms
- A hub firmware update changed how devices are registered
- The integration’s OAuth token was refreshed and identifiers shifted
- You added new devices that displaced cached entries
Force discovery in each ecosystem
The fix is to trigger a rediscovery, which rebuilds the cache from current source data.
Alexa: say “Alexa, discover my devices” or open the Alexa app, More, Add Device, scan for devices. Both trigger the same flow.
Google Home: say “Hey Google, sync my devices” or open the Google Home app, navigate to the integration, refresh.
HomeKit: discovery is automatic. If devices are missing, the issue is usually the hub or the iCloud sync rather than discovery itself. Restart your home hub.
If discovery does not find the missing device
If you ran discovery and the missing device is still missing:
- Check the device in the source app (Hue, manufacturer app). Is it actually there?
- If yes, the integration is broken between the source and the voice assistant. Go to the linked services list, unlink the integration, relink it.
- If no, the device was actually removed from the source. Re-add it in the source app first.
The rename problem
If you renamed a device in your Hue app from “Kitchen Light 1” to “Kitchen Pendant”, Alexa’s cache still has “Kitchen Light 1”. Voice commands using either name may fail until Alexa refreshes.
After renames, always run discovery. Wait 5 minutes for the refresh to propagate. Then test voice commands with the new name.
The duplicate device issue
Sometimes discovery creates a duplicate of a device that was already there. You end up with “Kitchen Light” and “Kitchen Light 2” in your voice assistant’s device list, both pointing to the same physical bulb.
Delete the duplicate in the voice assistant’s app. The one that was added by the integration sync is usually the canonical one; the older orphan is the duplicate.
The wholesale resync
If discovery seems to be making things worse (more missing devices, more duplicates), the integration itself is unhealthy. The fix is to unlink and relink the integration entirely. This is more invasive than a discovery refresh but rebuilds the integration’s data from scratch.
Steps:
- Note the integration’s settings (any routines that reference its devices, any group memberships).
- Disable or unlink the integration in the voice assistant’s app.
- Re-enable or re-link the integration.
- Re-authorize with the same account credentials.
- Run discovery.
The disadvantage: routines that referenced the integration’s devices by ID may break. You may need to edit each routine to re-select the devices.
The voice assistant device reboot
Voice assistant speakers cache device lists locally as well as in the cloud. After discovery completes in the cloud, the speakers can take time to pick up the changes. Rebooting the speaker (unplug 30 seconds, plug in) forces it to refresh from the cloud.
This is especially useful if discovery shows the device in the app but voice commands still fail at the speaker.
The OAuth token refresh
If you recently changed your password on the manufacturer service, every integration that uses OAuth needs to be re-authorized. Voice commands fail until the integration is relinked because the token is invalid.
This is common after password changes triggered by security events. Plan for some re-linking work whenever you change a major service password.
The device is technically removed
Some integrations remove devices that have been offline for a long time. If a device went offline (battery dead, unplugged, network issue) and stayed offline for weeks, the integration may have removed it from its device list. Voice discovery then has nothing to find.
Fix the underlying offline status first (recharge battery, reconnect to network), then re-add the device in the manufacturer app, then run discovery.
The localization issue
If you changed your voice assistant’s language, device names that were in the old language may not match voice commands in the new language. Either rename devices to the new language, or change the language back.
When discovery makes things worse
If running discovery actually decreases the number of devices visible (some that were there are now missing), the integration’s account binding is the issue, not just the cache. The integration is now logging into a different account or a degraded account. Unlink and relink with explicit attention to which account is being used.
Schedule periodic discovery
If your home has many smart devices and frequent changes, schedule a weekly “Alexa, discover my devices” via a routine. The routine fires the discovery automatically, preventing cache drift from accumulating. Set it for an off-peak time like 4 AM Sunday.
The weekly forced sync that prevents drift
Add a weekly scheduled routine that asks the voice assistant to discover devices. The forced discovery prevents the cache from drifting over time. The routine costs nothing to run and you may never notice it actively helping; the absence of “device not found” errors is the proof it is working.
Schedule it for early Sunday morning when no one is using the devices. The broader category of cache-vs-reality drift issues is in our device status drift guide.
The morning sync routine
Automate a discovery sync to run every morning at 4 AM via a scheduled routine. This catches any overnight cache drift before household members start using devices. The cost is negligible and the prevention is real. The wider context of how discovery interacts with platform updates is in our custom skills guide.
