When your TP-Link Kasa smart devices show "Local Only" status, they've lost connection to TP-Link's cloud servers while remaining connected to your local Wi-Fi network. This typically happens due to DNS resolution issues or expired authentication tokens preventing the device from reaching TP-Link's cloud infrastructure.
Quick answer
• Re-login to your TP-Link account in the Kasa app to refresh expired security tokens • Change your router's DNS server to Google (8.8.8.8) or Cloudflare (1.1.1.1) to resolve cloud connectivity issues • Toggle the Remote Control setting on older Kasa devices if available • Applies to: Kasa Smart Plugs (HS103, HS105, EP25), Kasa Light Switches, and Kasa Cameras
Symptoms
• App displays "Local Only" under the device name • Device works while connected to home Wi-Fi but not on cellular data • Alexa or Google Assistant reports "Device is unresponsive" • Existing schedules continue running but cannot be edited remotely • Device responds to local app commands but not voice commands
Quick checks
Verify local connectivity — Open the Kasa app while connected to your home Wi-Fi and test if you can control the device. If this works, the issue is cloud connectivity, not local network problems.
Test remote access — Switch your phone to cellular data and try controlling the device. If it fails, confirm this is a cloud connection issue.
Check affected components — The device needs TCP port 50443 access to TP-Link servers, NTP time sync, and DNS resolution of devs.tplinkcloud.com.
Step-by-step fix
-
Try the Remote Control toggle (older devices only) • Open the Kasa app and tap your device • Tap Settings (gear icon) • Look for Remote Control toggle • Turn it OFF, wait 5 seconds, then turn it ON • If this option doesn't exist, continue to step 2
-
Log out and back into your TP-Link account • In the Kasa app, tap Me → View Account • Tap Log Out • Log back in with your credentials • This refreshes security tokens for all your devices
-
Change your router's DNS settings • Access your router's admin panel (usually 192.168.1.1 or 192.168.0.1) • Navigate to Network → DNS Settings (location varies by router) • Change from "Automatic/ISP" to Manual • Set Primary DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) • Set Secondary DNS to 8.8.4.4 or 1.0.0.1 • Save settings and reboot your router
-
Power cycle the Kasa device • Unplug the smart plug or turn off power to switches/cameras • Wait 10 seconds • Plug back in or restore power • Wait 2-3 minutes for full reconnection
If it still isn't working
Check firewall settings — If you use custom firewall hardware (pfSense, Firewalla), ensure you're not blocking outbound internet traffic for your Kasa devices. They need unrestricted access to "phone home" to TP-Link servers.
Test DNS reliability — ISP DNS servers often fail intermittently with IoT devices. Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1) show high reliability, while typical ISP DNS from Comcast or AT&T frequently causes random "Local Only" issues.
Consider device age — Very old HS100 models (Gen 1) may have trouble with modern TLS cloud endpoints. If firmware updates fail and the device remains stuck, replacement may be necessary.
FAQ
Why does "Local Only" happen randomly? ISP DNS servers often fail to resolve IoT cloud domains consistently. Switching to Google or Cloudflare DNS provides more reliable cloud connectivity.
Can I use the device in Local Only mode? Yes, basic on/off control works locally, and existing schedules continue running. However, you lose remote access, voice control, and the ability to modify settings when away from home.
Will changing DNS affect my internet speed? No, and it may actually improve performance. Google and Cloudflare DNS often respond faster than ISP DNS servers.
Do I need to reconnect all my Kasa devices? No, logging out and back into your account refreshes tokens for all devices simultaneously. The DNS change affects your entire network.