← Full guide: TP-Link Kasa Smart Plug Not Responding: Fix Guide

Fix It: Step-by-Step Troubleshooting

Fix It: Step-by-Step Troubleshooting. Check the cause, evidence to keep, recovery steps, and escalation.

Start here

If the LED is solid but the app still shows "offline" or "not responding": Power-cycle the plug. Unplug it from the wall for 30 seconds, then plug it back in and wait 1-2 minutes.

What applies to this exact problem

  • If the LED is solid but the app still shows "offline" or "not responding": Power-cycle the plug
    • Unplug it from the wall for 30 seconds, then plug it back in and wait 1-2 minutes
    • Force-close and reopen the Kasa app to refresh the device status
  • If power-cycling doesn't fix it: Check your router's band settings
    • Kasa plugs connect only to 2.4GHz networks — if your router recently switched to a combined/5GHz-priority SSID, the plug can silently drop off
    • Temporarily split your network into separate 2.4GHz and 5GHz SSIDs if your router supports it, then reconnect the plug to the 2.4GHz one
  • If the plug still won't connect after confirming the 2.4GHz network is available: Move the plug closer to the router temporarily
    • Smart plugs have small antennas; a weak signal at the outlet location can cause intermittent drops even when it initially paired fine
  • If none of the above resolves it: Factory reset the plug and re-add it in the app
    • Hold the plug's reset button (usually recessed, near the power button) for 5-10 seconds until the LED blinks rapidly
    • In the Kasa app, remove the old device entry first, then add it as new
Warning: If you reset the plug without first removing it from the Kasa app, you may end up with a duplicate "ghost" device entry that continues to show offline. Always delete the device from the app before or immediately after a factory reset.

Check these first

  • State the exact expected result and the exact result you have now.
  • Find the official record that owns the result and compare it with your evidence.
  • Change one thing at a time, then verify the final state before moving on.

Fix it in this order

  1. State the exact expected result and the exact result you have now.
  2. Find the official record that owns the result and compare it with your evidence.
  3. Check device power and local status before blaming Wi-Fi or the cloud.
  4. Confirm phone, device, router band, account, and app are using the expected network and region/account.
  5. Restart only one layer at a time: device, app, router, then cloud/account reconnect.
  6. Re-pair only after saving automations/settings you may lose and checking the official reset sequence.
  7. After recovery, test remote control, automation, notifications, firmware, and reconnection after a power cycle.

Build the proof pack

  • Device model/firmware
  • LED/error state
  • Router/network details without passwords
  • App/account error screenshots

Avoid making the case harder

  • Factory-resetting before checking simpler causes
  • Posting Wi-Fi passwords or tokens in support screenshots
  • Changing multiple router settings at once

How you know it is really fixed

  • The official record and your real-world result agree.
  • You have enough written evidence to prove the issue is finished if it returns later.

If it is still not fixed

  1. Vendor status/support
  2. Router/ISP support if the network itself is failing
  3. Warranty/replacement when hardware diagnostics point to a device fault

Official sources from the full guide

Need the complete context?

This page solves one branch. The parent guide covers the full decision, edge cases, alternatives, and related checks.

Open the full guide