|

Smart Plug Keeps Going Offline Home Assistant: Causes & Fixes

ByAlex Turner

If your smart plug repeatedly shows “Unavailable” in Home Assistant, the short answer is that the plug is losing its network connection — either because of weak Wi‑Fi, Zigbee interference, or a power‑save timeout that kills the radio. Most drops can be fixed in under 15 minutes without buying new hardware. Here’s how to diagnose and fix each cause, in the order that gives the fastest wins.

Three Quick Checks Before You Start

Run through these five checks right now. Each takes less than a minute, and together they catch roughly 80% of offline‑plug problems.

  • [ ] Is the plug physically powered? Check that the outlet switch is on and the plug’s LED is lit. A switched outlet with a light switch is the #1 false alarm.
  • [ ] Is the plug within 30 feet of your router or Zigbee coordinator? Walls and metal appliances cut signal fast. Move the plug within 10 feet temporarily to test.
  • [ ] Does your router mix 2.4 GHz and 5 GHz on the same SSID? Many smart plugs only speak 2.4 GHz. A combined SSID can make the plug try 5 GHz and fail repeatedly.
  • [ ] Did you update the plug’s firmware recently? Open the manufacturer’s app (Kasa, Smart Life, Tuya, etc.) and check for pending updates. Outdated firmware is a leading cause of disconnect loops.
  • [ ] Check Home Assistant logs for the plug. Go to Settings → System → Logs and filter for the plug’s entity ID. Repeated “did not respond” or “timeout” messages point to a network issue, not a software glitch.

The One Failure Mode Most Home Assistant Users Miss

The most common but least obvious reason a smart plug goes offline is power‑save idle timeout. Many Wi‑Fi smart plugs — especially budget models from Tuya or earlier TP‑Link lines — enter a deep sleep after a few minutes of no activity to save a tiny amount of energy. When Home Assistant sends a command or tries to poll the plug, the radio takes several seconds to wake up, so the request times out. The plug then gets marked “Unavailable” even though it’s physically on.

How to detect it early: In Home Assistant, open Developer Tools → States and look at the `last_seen` attribute for the plug’s entity. If it jumps by 5–15 minutes during idle periods but updates normally after you physically toggle the plug, that’s the power‑save timer. Also check the manufacturer app — many brands hide a “Keep Online” or “Idle Timeout” toggle under device settings. For example, the Linkind Matter Smart Plug has a “Disable Power Saving” option in its native app. If your plug doesn’t offer that setting, it may simply be a poor fit for always‑on automation.

Step‑by‑Step Fixes (with Real‑World Branching)

Follow these steps in order. After each step, wait 24 hours and check the plug’s state history. The branch at step 2 decides your next move.

1. Separate the 2.4 GHz Band

Log into your router and either disable the 5 GHz band temporarily or create a dedicated 2.4 GHz SSID. Reconnect the plug to that network. This alone fixes about 60% of Wi‑Fi dropouts.

Branch: If the plug stays online for 24 hours, the problem was band‑steering confusion. Keep the dedicated 2.4 GHz SSID. If it still drops, move to step 2.

2. Move the Plug to a Test Location

Place the plug within 10 feet of your router (or Zigbee coordinator) for one day. If it stays online, signal strength was the issue. You’ll need to add a Wi‑Fi range extender or a Zigbee router (a mains‑powered Zigbee bulb or another plug) near the original location.

Branch: If the plug stays offline even at close range, the problem isn’t signal — it’s either the power‑save timer (step 3), Zigbee interference (step 4), or a failed radio.

3. Disable Power‑Save Mode in the Manufacturer App

Open the plug’s native app (not Home Assistant) and look for any setting called “Idle Timeout,” “Power Saving,” “Keep Online,” or “Sleep Mode.” Disable it. If no such setting exists, create a recurring automation in the manufacturer app that sends a ping every 10 minutes (e.g., toggle the plug off and on for 1 second). This keeps the radio awake.

4. Change the Zigbee Channel (for Hub‑Based Plugs)

If you use a Zigbee plug via ZHA or Zigbee2MQTT, check your Wi‑Fi channel first. Many routers default to channel 11 (2462 MHz). Zigbee channels 15–25 overlap heavily. A safe move is to set Zigbee to channel 25 (2475 MHz). In Zigbee2MQTT, go to the coordinator settings, change the channel, and re‑pair all devices. In Home Assistant ZHA, you need to reflash the coordinator with a new pan_id and channel.

What to look for: In your Home Assistant logs, you’ll see “Device did not respond to poll” messages clustered around the same time your Wi‑Fi channel is busy.

5. Re‑pair the Plug Fresh

If none of the above work, remove the plug from Home Assistant and from the manufacturer app. Factory reset it (usually hold the button 5–10 seconds until the LED blinks fast). Add it again from scratch, selecting the correct protocol. After re‑pair, monitor `last_seen` for 24 hours.

6. Swap the Integration (Last Software Triage)

If you’re using ZHA, try switching to Zigbee2MQTT (or vice versa) if the coordinator supports it. For Matter plugs, ensure your Thread border router (e.g., an Echo Show 11 or Echo Show 5) is within 20 feet and not blocked by metal or electronics.

When to Call It Quit and Replace the Plug

If you’ve done all six steps and the plug still drops offline daily, the hardware is failing. Red flags that mean replace now:

  • The plug feels warm to the touch when idle (defective power supply).
  • The LED flickers even when the plug is working.
  • The plug ignores a physical reset (button does nothing).
  • Multiple plugs of the same brand show the same symptom — it’s a design flaw, not a config issue.

At that point, buy a plug with a documented “keep alive” mode and strong Wi‑Fi radio, preferably one that supports Thread or a dedicated Zigbee coordinator. A cheap replacement is cheaper than hours of re‑flashing and re‑pairing.

Frequently Asked Questions

Why does my smart plug show “Unavailable” in Home Assistant but still works in the manufacturer app?

This means the plug’s cloud connection is alive, but the local API that Home Assistant uses is blocked or times out. Check that your router allows mDNS (for Matter) or that the plug’s local port isn’t firewalled. Often this happens after a router firmware update.

Can a weak Zigbee coordinator cause multiple plugs to go offline at once?

Yes. If the coordinator (e.g., an old CC2531 stick) handles more than 25 devices or has a failing oscillator, all Zigbee plugs will stagger offline. In Zigbee2MQTT, check the coordinator’s uptime and device count. Consider upgrading to a Sonoff ZBDongle-E or Conbee III.

Does the Echo Show affect smart plug connectivity as a Matter controller?

The Echo Show 5 and Echo Show 11 both contain Thread border routers. Place them within 20 feet of the plug and avoid putting them behind a TV or inside a cabinet. Poor border‑router positioning is a common cause of intermittent Matter dropout.

Explore This Topic

Related guides in this cluster:

Similar Posts