| What works | First place to look |
|---|---|
| Kasa works locally; remote control does not | Internet/cloud reachability, app/account state and router restrictions. |
| Plug cannot join Wi-Fi during setup | Setup mode, supported Wi-Fi band/security and phone permissions. |
| Kasa works; Alexa does not | Kasa skill/account linking and device discovery. |
| Manual button and app both fail | Power/outlet/device state before any network work. |
← Full guide: Kasa Smart Plug Not Responding: Power, Wi-Fi, Cloud, Alexa
Pick the state that matches
What works. First place to look. Kasa works locally; remote control does not. Internet/cloud reachability, app/account state and router restrictions.
Start here
What works. First place to look. Kasa works locally; remote control does not. Internet/cloud reachability, app/account state and router restrictions. Plug cannot join Wi-Fi during setup. Setup mode, supported Wi-Fi band/security and phone permissions. Kasa works; Alexa does not. Kasa skill/account linking and device discovery. Manual button and app both fail. Power/outlet/device state before any network work.
What applies to this exact problem
Check these first
- What works: First place to look.
- Kasa works locally; remote control does not: Internet/cloud reachability, app/account state and router restrictions.
- Plug cannot join Wi-Fi during setup: Setup mode, supported Wi-Fi band/security and phone permissions.
Fix it in this order
- What works: First place to look.
- Kasa works locally; remote control does not: Internet/cloud reachability, app/account state and router restrictions.
- Plug cannot join Wi-Fi during setup: Setup mode, supported Wi-Fi band/security and phone permissions.
- Kasa works; Alexa does not: Kasa skill/account linking and device discovery.
- Manual button and app both fail: Power/outlet/device state before any network work.
Evidence to keep
- Device model/firmware — keep it with the evidence for “Pick the state that matches”.
- LED/error state — keep it with the evidence for “Pick the state that matches”.
- Router/network details without passwords — keep it with the evidence for “Pick the state that matches”.
- App/account error screenshots — keep it with the evidence for “Pick the state that matches”.
Do not make it harder
- Factory-resetting before checking simpler causes For “Pick the state that matches”, that can hide whether the underlying issue is actually resolved.
- Posting Wi-Fi passwords or tokens in support screenshots For “Pick the state that matches”, that can hide whether the underlying issue is actually resolved.
- Changing multiple router settings at once For “Pick the state that matches”, that can hide whether the underlying issue is actually resolved.
How you know it is fixed
- The official record and your real-world result agree for “Pick the state that matches”.
- You have enough written evidence to prove the issue is finished if it returns later for “Pick the state that matches”.
If this still isn't resolved
- Vendor status/support State the unresolved issue explicitly: “Pick the state that matches”.
- Router/ISP support if the network itself is failing State the unresolved issue explicitly: “Pick the state that matches”.
- Warranty/replacement when hardware diagnostics point to a device fault State the unresolved issue explicitly: “Pick the state that matches”.
Parent-guide references
These references support the parent guide and escalation context. Verify provider-, model-, policy-, or jurisdiction-specific details before an irreversible step.
Need the complete context?
This page solves one branch. The parent guide covers the full decision, edge cases, alternatives, and related checks.