You logged into Google Home and noticed some devices are missing. Some routines are broken. Voice commands that worked yesterday now respond with “I cannot find that device”. Nothing in your smart home setup actually changed. The cause is almost always a Google account event that Google did not surface clearly: a re-authentication, an OAuth token expiry, a household profile update.
How Google Home knows about your devices
Google Home maintains a device list that is populated through manufacturer integrations. Each integration is bound to your Google account. The integration uses an OAuth token to talk to the manufacturer’s cloud. When the OAuth token is valid, devices sync. When the token expires or is revoked, devices stop appearing.
OAuth tokens have lifetimes. Some refresh automatically; others require periodic re-authentication. When you change your Google password, every OAuth token tied to your account is invalidated immediately and must be re-established.
Check Linked Services first
Open the Google Home app, tap your home, Settings, Linked Services. Look at each manufacturer integration. Healthy integrations show no warning. Broken integrations show “Re-link” or “Sign in again” or “Authentication expired”.
For each broken integration, tap it, complete the re-authentication. The devices in that integration should reappear within a minute.
The Google home owner trap
If your home was created by another household member, their account is the owner. If they lose access (account deleted, moved out, password change), the home can lose its primary control account and devices can become unmanageable.
To check who owns your home: in the Home app, tap your home, scroll to People. The owner is marked. If the owner is not you and you cannot reach them, you need to either get them to transfer ownership, or rebuild the home under your own account.
The Matter migration issue
If devices were originally added via Matter, the Matter fabric is tied to a specific Google account. Switching accounts breaks Matter device control until they are re-commissioned.
Matter devices can be commissioned to multiple controllers, so the cleanest fix is to keep your original account active and add a new controller from your new account, sharing the device across both fabrics.
Re-discover after re-linking
After re-linking an integration, ask Google to sync: “Hey Google, sync my devices”. Or in the Home app, navigate to the integration and tap the refresh button if available.
If devices still do not appear after re-link and explicit sync, the manufacturer cloud may be slow to update Google’s device list. Wait 5 to 10 minutes and try again.
The hub speaker reboot
Your Google Home or Nest Hub speakers cache the device list locally. After a major sync change, rebooting the speakers forces them to pull a fresh list. Unplug each speaker for 30 seconds and plug back in.
Routines that reference vanished devices
If a routine references a device that was sync-lost, the routine breaks. Open the routine, look for actions marked with a warning or strikethrough. These actions failed to resolve. Either fix the underlying sync issue (which restores the device), or edit the routine to remove the broken action.
If you edit before the sync is restored, the routine will not magically re-include the device when sync returns. You will have to manually re-add the action to the routine after the device reappears.
Multiple accounts in the same household
Google Home supports multiple users per home through the household profile feature. Each user has their own voice profile and routines, but device control is shared. If a user is removed from the household, their personal routines disappear but shared devices remain.
If you find that you cannot control devices that other household members can, you may have lost household membership. The home owner can re-invite you.
The two-factor authentication side effect
Enabling or disabling two-factor authentication on your Google account triggers a session invalidation. Every Google Home integration may need to be re-authorized. Plan for this when you change 2FA settings; expect to spend 30 minutes restoring integrations afterward.
When a single device disappears but others remain
If one specific device is missing but the integration as a whole is healthy, the issue is on the device or manufacturer side, not Google. Open the manufacturer app. Is the device still there? If yes, force a sync from inside the manufacturer app, then re-sync Google.
If the device is missing from the manufacturer app too, the device has been removed somehow. Re-pair it in the manufacturer app first, then sync Google.
The Google account language change issue
Changing your Google account language can break device naming. Devices that were named in English get re-translated, sometimes badly, when language changes. Routines that use the old names break.
Re-name devices to the names you actually want, in the language Google Home is now using. Fix routines that reference the old names.
Local control as a backup
Some Google Home device categories support local control, where commands are sent directly from your Google Home speaker to the device without going through the cloud. When local control is available, voice commands work even during sync issues.
Local control is automatic for Matter and Cast-based devices. For other devices, it depends on the manufacturer’s implementation. Verify by issuing a voice command while your internet is briefly off; if it works, local control is active.
The recovery moment when an integration just will not relink
Sometimes the integration sits in a broken state where unlinking and re-linking both fail. The cause is usually that the manufacturer cloud thinks your Google account is still linked and Google thinks the link is broken. The fix is to log into the manufacturer’s website directly and revoke Google’s authorization there, then re-initiate the link from Google Home.
This breaks the deadlock by forcing the manufacturer side to acknowledge the unlink. If the manufacturer does not have a web interface that surfaces authorization revocation, contact their support; most can do it server-side. For the wider account-side recovery patterns, see our app config loss guide.
The factor often missed during account audits
Google Family Sharing membership affects which household members can see and control devices. If a member was recently removed from the family group, their access to shared devices is also revoked, which can look like a sync failure. Verify family membership when investigating account-related discovery problems. The wider topic of multi-user voice setup is in our household profiles guide.
Related reading: microphone aging guide.
