If a Kasa smart plug is connected but device unreachable, power-cycle the plug, reopen the Kasa app, confirm 2.4GHz main Wi-Fi, check router access control, then update firmware when the plug comes back online.
A solid or connected-looking plug does not always mean cloud control is working. The plug needs Wi-Fi, local network access and TP-Link/Kasa cloud access.
Connected to Wi-Fi is not the same as reachable
A Kasa smart plug can look connected and still be impossible to control from the app, Alexa or Google Home. The light may suggest it joined Wi-Fi, but the app says device unreachable, automation fails, or voice assistants cannot toggle it. That split usually means the plug has local Wi-Fi but lost cloud access, app sync, account link, DNS, router permission or a stable 2.4GHz path. Smart plugs are small devices, so little router changes can make them look broken.
Start with one plug, one app and one Wi-Fi network. If every Kasa device is unreachable, check router and cloud status. If only one plug fails, focus on that plug’s power, placement and saved network profile.
Quick diagnosis table
Try these fixes in order
Smart plug fixes should be small and ordered. Avoid deleting the home setup until you know what failed.
- 01
Power-cycle the plug
Unplug it from the outlet for 30 seconds, plug it back in and wait for the app to refresh.
- 02
Restart the Kasa app
Force close and reopen the app. Device status can lag after a router or plug restart.
- 03
Use main 2.4GHz Wi-Fi
Many smart plugs depend on 2.4GHz. Avoid guest Wi-Fi, isolated IoT networks and VPN during setup.
- 04
Restart the router once
A normal restart can refresh DNS, DHCP and device sessions without deleting settings.
- 05
Check router blocks
Look for access control, paused devices, security filters or MAC blocking in the router app.
- 06
Check voice assistant links
If Kasa works but Alexa or Google does not, relink the assistant skill or service instead of resetting the plug.
- 07
Update firmware later
Update firmware after the plug is stable. Do not start updates while it is dropping offline.
Detailed checks
Cloud access is the hidden layer
Kasa app control often depends on cloud communication. The plug can join Wi-Fi but still fail to respond if it cannot reach the cloud.
- That is why other devices may browse normally while one smart plug looks unreachable.
- Check DNS, router security and account status if several Kasa devices fail.
IoT networks can isolate too much
Separate IoT networks can be useful, but some are isolated from phones or cloud services in ways that break setup and control.
- If setup fails on an IoT SSID, test the main 2.4GHz network.
- Once the plug works, you can decide whether your router’s IoT settings are worth tuning.
Voice assistants add another link
If the Kasa app controls the plug but Alexa or Google cannot, the plug is not unreachable in the basic sense.
- The broken link is the assistant integration.
- Relink the skill or service after confirming Kasa itself works.
Router changes affect smart plugs quickly
New routers can change band steering, security mode, DNS and device protection settings. A plug may reconnect to Wi-Fi but lose cloud control.
- Check the router client list and allow the active plug.
- Then reconnect setup only if the app still cannot control it.
Separate Kasa app trouble from smart speaker trouble
Many people notice the problem through Alexa, Google Home or Siri first, but those services are one layer away from the plug. Open the Kasa app and check whether the plug responds there before unlinking every smart-home account.
- If Kasa control works but Alexa says unreachable, refresh the skill or reconnect the integration.
- If the Kasa app also fails, return to Wi-Fi band, router isolation, cloud status and firmware instead of blaming the speaker.
Why moving the plug can change everything
Smart plugs sit low on walls, sometimes behind furniture or near appliances that weaken signal. A plug can connect during setup near the router, then become unreliable when moved to its real outlet.
- Test it for ten minutes in the same room as the router.
- If it becomes reliable there, the permanent outlet may need a better router position, closer access point or a less crowded 2.4GHz channel.
- Do this test before deleting the plug from the app. If the signal is the real issue, removing and re-adding the device only gives you the same failure in a more annoying package later.
Mistakes to avoid
Do not use guest Wi-Fi for setup.
Do not confuse Alexa failure with Kasa failure.
Do not update firmware on an unstable plug.
FAQ
Why is my Kasa smart plug connected but device unreachable?
The plug may be connected to Wi-Fi but unable to reach Kasa cloud services or the app. Router rules, DNS, 2.4GHz setup, firmware or account sync can cause it.
Power-cycle the plug and check the Kasa app before deleting the device.
Does Kasa need 2.4GHz Wi-Fi?
Many Kasa plugs use 2.4GHz, especially older models. 2.4GHz also reaches better through walls.
Use the main 2.4GHz network during setup, not guest Wi-Fi or a heavily isolated IoT network.
Why does Kasa work in the app but not Alexa?
That means the plug is probably reachable, but the Alexa integration is broken.
Relink the Kasa skill or refresh device discovery in Alexa instead of resetting the plug.
Can router security block Kasa?
Yes. Access control, paused devices, client isolation and security filters can block the plug from reaching the cloud.
Check the router app for the active plug entry and allow it.
Should I factory reset the Kasa plug?
Reset after power, app, router and Wi-Fi checks fail. Resetting first can repeat the same setup problem.
If all Kasa devices fail, the router or cloud path is more likely than one plug.
Why did Kasa stop after a new router?
The plug may still have old Wi-Fi details, or the new router may use different security and band steering.
Reconnect it to the main 2.4GHz network and check device blocking.
Outside references
- TP-Link Kasa Support
Official TP-Link smart home support.
- Kasa Smart support
Official Kasa product help.