|

Smart Plug Firmware Update Stuck Google Home: Common Issues & Solutions

ByAlex Turner

If your smart plug shows a firmware update that never finishes in Google Home, the most likely cause is a Wi‑Fi band mismatch or a stale app cache. In many cases the update is actually optional — you can often ignore the notification if the plug works normally. This guide walks you through the fastest checks, the fixes that actually work, and when you should stop troubleshooting.

Counter‑intuitive fact: Forcing a factory reset to clear a stuck update can introduce more problems (lost schedules, re‑pairing headaches) than it solves. Only factory‑reset if the plug is actually failing to respond to voice commands or schedules.

Quick Checks: 5 Things to Verify First

Use this table before diving into deeper troubleshooting. Each check takes 30 seconds.

Check Pass / Fail Why it matters
1. Wi‑Fi band – Is your phone connected to 2.4 GHz? Pass = yes Most smart plugs only support 2.4 GHz. If your phone is on 5 GHz, the update command may not reach the plug.
2. Google Home app version – Updated in the last 30 days? Pass = yes Older app versions have known firmware‑stuck bugs. Update via your app store.
3. Plug power cycle – Unplugged for 10 seconds?

| Pass = done | A brief power cycle clears temporary glitches without wiping settings. |

| 4. Network congestion – Router less than 30 ft away, no heavy streaming? | Pass = yes | Updates time out if the network is overloaded or signal is weak. |

| 5. Plug’s own app – Does it report firmware as up‑to‑date? | Pass = yes | If the plug’s native app (Kasa, Wemo, etc.) says firmware is current, the Google Home notification is likely a miscommunication. |

Branch after check 3: After the power cycle, open Google Home and check the plug’s status. If the “updating” message has vanished, you’re done. If it still shows, move to the next step. This one quick test saves you from running through unnecessary fixes.

Ordered Fixes: What to Try First (and When to Stop)

Attempt these actions in order. After each fix, verify the result before moving on.

1. Force‑stop and clear cache in Google Home

  • Android: Settings → Apps → Google Home → Force stop, then Storage → Clear cache.
  • iOS: Double‑tap Home button and swipe up on Google Home (iOS doesn’t expose cache clearing; reinstall the app instead).

Verification: Re‑open Google Home and tap the plug. If the “updating” label is gone and the plug shows a normal status (online / ready), the fix worked. If the notification returns within 5 minutes, proceed.

2. Remove the plug from Google Home and re‑add

  • Open Google Home → tap the plug → Settings (gear icon) → Remove device.
  • Re‑add the plug by scanning its QR code or using the “Works with Google” option.

Branch here: If the update notification reappears immediately after re‑adding, the issue is likely server-side or the plug’s firmware is genuinely stuck. Skip to step 4. If the update does not reappear, test voice commands (e.g., “Hey Google, turn on the plug”). Voice response confirms full recovery.

Verification: Wait 2 minutes after re‑adding. If Google Home shows “Online” without any update banner, you’re good. Run a schedule test (e.g., “Turn off in 1 minute” via Google Home). If it executes, stop.

3. Update firmware through the plug’s own app first

  • Open the manufacturer’s app (e.g., Kasa, Wemo, TP‑Link, or the app that originally set up the plug).
  • Go to Device Settings → Firmware Update → Check for updates. If an update is available, install it from there.
  • Once complete, return to Google Home. The stuck notification usually clears within a few minutes.

Friction point: Some manufacturer apps (especially older Kasa models, like the HS103) only push updates when the plug is idle. If the plug is actively being used (e.g., powering a lamp that’s on), the update may fail silently. Turn off the load before starting.

Verification: After the manufacturer app reports “Update complete,” open Google Home. If the update banner persists, your Google Home app needs a full refresh. Force‑close and reopen it.

4. Factory reset the plug (only if all else fails)

  • Resetting wipes all schedules, rooms, and automations.
  • Reset method varies by model: hold the physical button for 10–15 seconds until the LED blinks rapidly, then release.
  • Re‑pair from scratch using your phone on the same 2.4 GHz network.

Branch after reset: If the update still gets stuck at this point, the issue is server‑side (Google Home backend) or the plug hardware is unable to process the update. Do not factory reset again – it won’t help.

Verification: After re‑pairing, the plug should appear in Google Home without any update message. If it appears, test a voice command immediately. If the command works and the update notice is absent, success.

5. Wait 24–48 hours (server‑side delays)

Google Home often queues firmware updates in batches. A “stuck” update may resolve itself once the backend processes the request. During this time, the plug remains usable (voice and schedules still work).

Verification: After 24 hours, open Google Home. If the update banner is gone, done. If it remains, you have a deeper issue (see below).

Likely Causes of a Stuck Update (with real examples)

  • Wi‑Fi drop during download – The plug loses connection mid‑update and never recovers. This is common with older Wi‑Fi plugs like the Wemo Mini (first generation), which has limited flash memory and fails silently if the connection drops for even 2 seconds. Solution: Move the plug closer to the router, or use a 2.4 GHz only SSID.
  • Unresponsive plug hardware – Some plugs (e.g., TP‑Link Kasa KP105) enter a state where the Wi‑Fi radio goes to sleep during an attempted update and does not wake until a full power cycle. Solution: Power cycle (unplug for 10 seconds) – not a factory reset.
  • Google Home server timeout – The app sends the update request but the backend doesn’t get a confirmation. More common during peak hours (evenings, weekends). No user fix – just wait 24 hours. The plug remains fully operational during this period.

Evidence: On the Kasa subreddit, many users report that a Google Home app reinstall eliminates the stuck notification even when the plug firmware hasn’t changed. The notification is often just a stale cache entry.

When to Stop Troubleshooting

  • The plug is physically unresponsive (LED off, no power output) even after factory reset.
  • Google Home still shows “updating” after 3 days, and the plug’s own app cannot initiate the update.
  • The plug is over 3 years old – many manufacturers (e.g., Belkin for Wemo) have discontinued firmware updates for older models.

In these cases, a plug that uses the Matter protocol can reduce firmware-related headaches. Matter plugs update through the smart home platform without a dedicated app, which means fewer points of failure and fewer stuck-update notifications.

FAQ

Can I still use the smart plug while the firmware update is stuck?

Yes, in nearly all cases the plug continues to work normally. The stuck notification is cosmetic unless the plug becomes unresponsive.

Will a factory reset force the firmware update to complete?

It may, but only if the plug was in an incomplete update state. Resetting erases all settings, so try it only after other steps fail.

Does this happen with all smart plugs on Google Home?

It is most common with Wi‑Fi plugs that use 2.4 GHz radios and have no dedicated hub. Matter and Thread plugs rarely experience this.

Explore This Topic

Related guides in this cluster:

Similar Posts