You set up a TP-Link Kasa, Wyze, or similar Wi-Fi smart plug. It paired to Alexa in five minutes. You then try to add it to Google Home, expecting the same experience. Google Home cannot find it. You go back to the plug’s own app, the plug is online and working. The plug is fine. Alexa sees it fine. Google Home is the only one that does not. This is a common pattern and the root cause is usually predictable.
How smart plugs reach Alexa and Google Home
Wi-Fi smart plugs do not talk directly to Alexa or Google Home. The plug talks to its manufacturer’s cloud. Alexa and Google Home each talk to the manufacturer’s cloud through a skill, action, or integration. So getting a plug to appear in Alexa or Google Home is really a matter of authorizing the manufacturer’s cloud account from inside the Alexa or Google Home app.
The plug being paired in Alexa but not Google Home almost always means: you authorized the manufacturer skill in Alexa, but you did not authorize the corresponding integration in Google Home, or you authorized a different account, or the integration is broken on Google Home’s side.
Verify the manufacturer integration is linked in Google Home
Open the Google Home app, tap your home name, then Settings, scroll to Linked Services. Look for the plug manufacturer. If it is not listed, the integration is not linked. Tap Add Service, find the manufacturer, and complete the OAuth flow with the same account you used in the manufacturer app.
If the integration is listed but the plug is still missing, the integration is linked to a different account than the one the plug is associated with. Unlink and re-link, taking care to use the right account.
The two-account trap
A common pattern: you signed up for the plug manufacturer’s account using your phone number, but you used a different email when you linked the integration to Google Home. The manufacturer cloud treats them as two separate accounts. The plug lives in one account; Google Home is looking at the other.
The fix is to ensure both your manufacturer app and the Google Home integration are using the same account. Log out of the manufacturer app, log back in with the same credentials you used in Google Home, and verify the plug is still visible.
Sync the integration after authorization
After linking, Google Home should automatically pull the device list from the manufacturer cloud. Sometimes it does not. If your plug is paired in the manufacturer app and the integration is linked but the plug is missing in Google Home, manually sync by saying “Hey Google, sync my devices” or by going into the integration’s settings in the Google Home app and tapping a refresh option.
Why Alexa might be easier
Alexa’s device discovery model is more aggressive. It scans for new devices in your account periodically and can also pull them in via SSDP or mDNS announcements if the device supports it. Google Home is more cautious and waits for explicit integration sync events. This is why plugs often appear in Alexa without you doing anything explicit, while requiring more action in Google Home.
Wi-Fi network considerations
If your plug is on a different Wi-Fi network than your Google Home speaker (a guest network, an IoT VLAN), local discovery will fail. The integration cloud-based path still works, but some Google Home features (like the Google Home app’s local response) will not. If you want full functionality, both devices should share a network segment.
The manufacturer cloud is down
Manufacturer clouds for budget smart plugs sometimes have outages that affect specific ecosystem integrations. The plug responds to the manufacturer app (which uses one cloud endpoint) but Google Home gets errors (because the Google Home integration uses a different endpoint).
Check the manufacturer’s status page if they publish one. If multiple users report Google Home integration issues at the same time, you are not the only one. The fix is to wait.
If the manufacturer app shows the device offline
If your plug is offline in the manufacturer app, neither Alexa nor Google Home can reach it. Fix the plug’s connection first: reboot the plug, verify it joined the right Wi-Fi network, check for firmware updates in the manufacturer app. Only then will it appear in the ecosystem apps.
Matter as the alternative
If your smart plug supports Matter, prefer Matter over the cloud integration. Matter devices appear in any Matter-enabled controller without an account or skill linkage. You commission the plug once into Google Home directly using its setup code, and the plug never depends on the manufacturer cloud for control.
Several recent TP-Link, Eve, and Onvis plugs support Matter natively. If your plug does, factory reset it and commission via the Google Home Matter flow. You will have one less integration to worry about.
Local control as a workaround
If the manufacturer integration to Google Home is permanently broken or unreliable, you can sometimes set up local control through an intermediary. For TP-Link Kasa plugs, the TP-Link bridge in Home Assistant gives you local control that you can then re-expose to Google Home through Home Assistant’s Google integration. It is a multi-step setup but completely sidesteps the broken integration.
When to return the plug
If the plug works in the manufacturer app but no third-party ecosystem can see it (Alexa, Google Home, Apple Home, SmartThings all fail), the issue may be that the device is region-locked or running firmware that does not support the integration. Check the model number against the manufacturer’s regional product matrix. Buying the wrong regional variant of a smart plug is more common than people realize.
The Matter detour to consider
If your plug supports Matter and you keep struggling with the manufacturer’s Google Home integration, the cleanest answer is often to factory reset the plug and re-commission it directly into Google Home through the Matter flow. This bypasses the manufacturer skill entirely. The plug now appears in Google Home as a generic Matter accessory rather than a branded one.
You lose some brand-specific features (energy reporting graphs, schedules in the manufacturer app), but you gain reliability. The deeper trade-off between brand-specific and protocol-native control is covered in our cross-ecosystem control guide.
