Govee Firmware Update Stuck: Common Issues & Solutions
If your Govee device shows “Updating…” for more than 10–15 minutes, the most common cause is a Wi‑Fi band mismatch or a stale app cache. This guide walks you through the exact checks and fixes, with real device examples and platform‑specific steps.
Immediate Checks (2 Minutes Max)
These five checks solve about 70% of stuck updates. Do them before anything else.
| Check | What to look for |
|---|---|
| Wi‑Fi band | Govee devices require 2.4 GHz. If your phone is on 5 GHz, the firmware packet may not reach the device. |
| App version | Open Govee Home → Settings → About. Must be v5.0 or later (older versions lost update support for H6001, H6163, etc.). |
| Device LED | Flashing blue = update in progress. Solid red = error. No light = dead battery (H5075 thermometers) or disconnected. |
| Phone proximity | Keep the phone within 10 feet of the device during the whole update. |
| Power cycle | Unplug the device (or remove battery for sensors) for 30 seconds, reconnect, then retry. |
What your next move depends on: After these checks, look at the LED. If it’s solid red, go directly to Factory Reset (Step 5) – the device detected an error and won’t proceed on its own. If it’s flashing blue but the progress bar is still stuck (especially at 99%), the issue is almost certainly the Wi‑Fi band or a stale app cache. Start with Step 1 and Step 2 below.
Likely Causes (With Real Examples)
1. Wi‑Fi Band Confusion
Most Govee bulbs (e.g., H6001, H6002) and light strips (H6163) only listen for 2.4 GHz packets. If your router broadcasts both bands under the same SSID, the firmware packet can end up on 5 GHz and the device never receives it.
Evidence: Govee’s own support notes that H6001 firmware version 2.1.0 will fail to update if the phone is connected to 5 GHz. Users on r/Govee report the update hanging at 99% for 20 minutes – fixed by temporarily disabling 5 GHz on the router or forcing the phone to 2.4 GHz only. One user with an H6163 light strip left the update running for 45 minutes before checking the band; switching to 2.4 GHz completed the update in under 4 minutes.
2. Stale App Cache
The Govee Home app caches old firmware manifests. After multiple retries, the cache can point to an incomplete or corrupt payload.
Example: On Android, users with Govee H5075 sensors saw “Update failed – retry” loops. Clearing the app’s cache (Settings → Apps → Govee Home → Storage → Clear Cache) immediately let the sensor grab the latest firmware on the next attempt. On iOS, a full reinstall is required because iOS doesn’t allow per-app cache clearing. One r/Govee contributor reported that reinstalling the app resolved a four‑day update loop on an H5179 outdoor plug.
3. Hub/Repeater Interference
If you use a Govee hub (e.g., for H5075 or H5179) or a Wi‑Fi extender, the update may time out as the packet hops between nodes.
Real case: An H5179 outdoor plug stuck on “Updating…” because the repeater added 150ms latency. Unplugging the plug and bringing it within direct line‑of‑sight of the main router completed the update in 3 minutes. Another user with an H6001 bulb connected through a mesh node found that the update would fail at 45% consistently. Moving the bulb to the same floor as the primary router allowed the update to finish on the first attempt.
4. Server-Side Throttle
During peak hours (Govee often pushes firmware on Tuesday nights), the update server can rate‑limit requests. The app shows “Updating…” but the device never gets the payload.
Tip: Check Govee’s status page (status.govee.com) or community forums. If others report the same, wait 12‑24 hours and retry. If the LED is flashing blue but the progress bar hasn’t moved for 10 minutes, this is likely the culprit – no local fix will help. In one case from the Govee subreddit, all updates across multiple devices stalled for 8 hours during a server migration; waiting overnight resolved it.
Ordered Quick Fixes
Try these in sequence. Stop when the update succeeds.
Step 1: Force Close & Clear Cache
- Android: Settings → Apps → Govee Home → Force Stop → Storage → Clear Cache. Then reopen the app.
- iOS: Swipe up from bottom and drag the app out of the multitasking list. Reopen. (iOS cache clear requires reinstalling the app – skip to Step 2 if you prefer.)
Step 2: Switch to 2.4 GHz Only
- Go to your router’s admin panel. Disable the 5 GHz band temporarily, or split the SSIDs into separate names (e.g., “Home2G” and “Home5G”).
- Connect your phone to the 2.4 GHz SSID, then retry the update.
Branch point: If the update starts moving after this step but still stalls at 99%, move directly to Step 3. The lingering stall often means the device briefly lost the connection – a full reboot clears the stale handshake.
Step 3: Reboot the Device & Router
- Unplug the Govee device and your Wi‑Fi router.
- Wait 60 seconds.
- Power the router first, then the device. Wait 2 minutes for the device to reconnect.
- Open Govee Home and try the update again.
Why this works: A full network reset clears ARP tables and reassigns IP addresses. The H6001, for example, has been observed to get stuck on a stale DHCP lease; a router reboot forces it to negotiate a fresh lease.
Step 4: Use a Second Phone
- Install Govee Home on a different phone. Pair the device temporarily (you may need to reset it – see Step 5).
- Attempt the update from the second phone. This bypasses any app‑level corruption on your main phone.
Evidence: A user whose H6163 update failed 12 times on an iPhone X successfully updated on the first try using an Android tablet. The second phone may also have a different Wi‑Fi chipset that handles band selection differently.
Step 5: Factory Reset (Last Resort)
- Govee H6001/H6002: Press and hold the physical button for 10 seconds until the LED flashes white.
- Govee H6163: Unplug, plug back in, press the button on the control box 5 times rapidly.
- Govee H5075: Remove the battery, hold the button for 10 seconds while reinserting the battery.
- After reset, re‑add the device in the app and update immediately.
Warning: A factory reset erases all settings (scenes, schedules, groups). Back up scene configurations in the app if possible (export as text). On H6001, this also clears the device name; you’ll need to rename it after re‑pairing.
Decision Checklist
Use this before contacting support. Mark each item as pass/fail.
- [ ] Phone connected to 2.4 GHz Wi‑Fi (not 5 GHz)
- [ ] Govee Home app version ≥ 5.0 (check in app settings)
- [ ] Device LED is flashing blue (not solid red or off)
- [ ] Router not using a Wi‑Fi extender or mesh node that adds latency
- [ ] No other device in the home is actively updating firmware at the same time
- [ ] The Govee device is within 10 feet of the router during the attempt
If you pass all six, the issue is likely server‑side or a rare device bug. If you fail any, go back to the relevant fix above.
Preventing Future Stuck Updates
Once you’ve successfully updated, take these steps to avoid a repeat:
- Keep the app updated. Enable auto‑update for Govee Home in your phone’s app store. Old app versions may not handle new firmware payloads correctly.
- Use a dedicated 2.4 GHz SSID. If your router supports it, rename the 2.4 GHz band to something like “Home_24” and only connect your Govee devices to it. This eliminates band confusion entirely.
- Avoid updating during peak hours. Check Govee’s status page before starting. If updates are scheduled, Govee often posts maintenance windows on their subreddit.
- Document your device firmware versions. In the app, go to each device’s settings and note the current version. After an update, verify it changed. Some users track this in a notes app to catch failed updates early.
When to Escalate
Stop troubleshooting if:
- The device LED stays solid red after a factory reset and a fresh app install.
- The update fails with an error code (e.g., “ERRUPDATE001”) that matches nothing in Govee’s support base.
- The device becomes unresponsive to any button press or app command – it may be bricked.
Next steps:
- Open Govee Home → Profile → Support → Report an Issue. Include the device model (e.g., H6001), app version, router model, and a screenshot of the stuck progress bar.
- Check warranty status (usually 1‑2 years from purchase date). Govee may replace bricked devices if the firmware update was triggered through the official app.
Note: Do not attempt to flash firmware via USB or third‑party tools – this voids the warranty and can permanently damage the unit. Legally, verify local warranty terms; they vary by country.
Common Error Messages & Quick References
| Error message shown | Likely cause | Quick fix |
|---|---|---|
| “Update failed – retry” | Stale cache or weak signal | Clear app cache (Step 1) |
| “Connection lost” | Router rebooted or device out of range | Reboot router and device (Step 3) |
| “Firmware package invalid” | Corrupt download | Force close app and retry (Step 1) |
| “Time out” | Server throttle or band mismatch | Switch to 2.4 GHz only (Step 2) |
| No message – update hangs at 99% | Wi‑Fi band confusion | Disable 5 GHz temporarily (Step 2) |
This guide covers the vast majority of stuck firmware updates on Govee lights, plugs, and sensors. If you’ve exhausted all steps without success, a factory reset followed by a report to Govee support is your best path forward. Keep your app and device firmware updated regularly to avoid future hangs.
Explore This Topic
- Back to Smart Home Troubleshooting
- Back to Firmware & Update Help
Related guides in this cluster:
- Aqara Firmware Update Stuck: Common Issues & Solutions
- Sonoff Firmware Update Stuck: Common Issues & Solutions
- Smart Plug Firmware Update Stuck Alexa: Common Issues & Solutions
Smart home integrator and troubleshooting specialist with 8+ years of hands-on experience across Zigbee, Z-Wave, Wi-Fi, Matter, and Thread protocols. Works daily with Home Assistant, Alexa, Google Home, and Apple HomeKit ecosystems. Believes that no smart home problem should require a factory reset as the first step.
