The Kasa smart plug "Local Only" error occurs when your device loses its authentication token with TP-Link's cloud servers. While the plug remains connected to your Wi-Fi network and works locally, it cannot communicate with remote services needed for out-of-home control and voice assistant integration.
Quick answer
- Toggle Remote Control off and on in Device Settings → Remote Control to refresh the cloud token
- Sync the device time in Device Settings → Device Info → Time/Location if the toggle is missing
- Factory reset the plug (hold button for 10 seconds) and re-add it if other methods fail
- Check for Pi-hole blocking of tplinkra.com domains that prevent cloud authentication
Symptoms
- App displays "Local Only" tag next to the device name
- Voice assistant failures with "Device is unresponsive" messages from Alexa
- Controls work on home Wi-Fi but are greyed out when switching to cellular data
- Remote access fails when away from home network
Quick checks
- Verify the plug responds to commands when your phone is on the same Wi-Fi network
- Check if other Kasa devices have the same "Local Only" status
- Test voice commands to confirm they're failing consistently
- Look for the Remote Control toggle in Device Settings → Settings (gear icon)
Step-by-step fix
- Open the Kasa app and tap your affected device
- Navigate to Settings → tap the gear icon in the top right
- Find Remote Control toggle in the device settings menu
- Turn Remote Control OFF, wait 5 seconds, then turn it back ON
- Wait 30 seconds for the cloud connection to re-establish
- Test remote access by switching your phone to cellular data and controlling the plug
If the Remote Control toggle is missing:
- Go to Device Settings → Device Info → Time/Location
- Tap "Sync Time" to update the device clock
- Wait 60 seconds for SSL certificates to refresh
- Check if Remote Control toggle has reappeared in settings
If time sync doesn't restore the toggle:
- Press and hold the plug's button for 10 seconds until it flashes amber and blue rapidly
- Open Kasa app → tap "+" → Add Device
- Follow setup wizard to reconnect the plug to your network
- Test remote functionality once setup is complete
If it still isn't working
Check network configuration: Ensure your router isn't blocking tplinkra.com domains if using Pi-hole or similar ad blockers. Whitelist TP-Link cloud domains in your firewall settings.
Verify WPA security: Older Kasa plugs (HS103 V1-V2) may fail on WPA3 networks. Switch to WPA2/WPA3 mixed mode or WPA2-only in router settings.
Disable AP isolation: Router "AP Isolation" or "Client Isolation" prevents devices from communicating during initial cloud setup. Disable this feature temporarily.
Check account region: Ensure your Kasa account region matches your plug's region. US accounts may not work with EU hardware due to server restrictions.
Refresh voice assistant: Disable and re-enable the "TP-Link Kasa" skill in your Alexa app to refresh OAuth authentication.
FAQ
Why does my plug work locally but not remotely? The plug maintains its Wi-Fi connection for local control but needs a separate authentication token for cloud services. This token can expire or become corrupted.
Can I prevent "Local Only" errors from happening? Keep your Kasa app updated and avoid frequently switching between different network configurations. Stable 2.4GHz connections reduce authentication failures.
Is it safe to use Kasa plugs for high-power devices? HS103/EP25 plugs are rated for 15A but should not exceed 12A (1440W) for continuous loads. Never use smart plugs for critical medical equipment or sump pumps.
Will factory reset delete my schedules and scenes? Yes, factory reset removes all local settings. Cloud-based schedules tied to your account will need to be reconfigured after re-adding the device.