|

Smart Light Keeps Going Offline Home Assistant? Here’s How to Fix It

ByAlex Turner

If your smart light repeatedly shows “unavailable” or drops offline in Home Assistant, the problem is rarely the bulb itself. Most dropouts trace back to network congestion, coordinator interference, or a misconfigured integration. This guide walks you through the real causes and step‑by‑step fixes so you can get back to reliable control.

Why Your Smart Light Drops Offline (And It’s Usually Not the Bulb)

The counter‑intuitive angle: the most common reason a smart light disconnects in Home Assistant is a weak or overloaded coordinator, not a defective bulb. In Zigbee networks, every mains‑powered device can act as a repeater, but many cheap bulbs (like early IKEA TRÅDFRI or some Tuya‑based models) handle routing poorly and can choke the mesh. On Wi‑Fi bulbs, a single router channel conflict or IP‑lease collision can kick the light offline even when other devices stay online.

Concrete example: A user with a Yeelight Wi‑Fi bulb kept seeing it go offline every few hours. The bulb’s IP address conflicted with a static lease on the router. Once they assigned a reserved DHCP address, the dropouts stopped. Another user running ZHA with a Conbee II coordinator found that plugging the USB stick into a USB 3.0 port (which emits 2.4 GHz interference) caused three Zigbee bulbs to disconnect in sequence every 30 minutes. Moving the coordinator to a USB 2.0 port with a 2‑foot extension cable fixed all three lights.

First Checks That Solve Half the Cases

Run these two‑minute checks before touching any coordinator settings:

1. Power cycle the light – Turn it off at the wall switch for 10 seconds, then on. Many Wi‑Fi bulbs recover from a temporary IP‑lease loss this way.

2. Check the light’s native app – If the bulb works in the manufacturer’s app (e.g., Philips Hue, LIFX, Govee) but not in Home Assistant, the problem is in the integration. If it fails in the native app too, the bulb hardware or its connection to the internet/router is at fault.

3. Look for signal congestion – Are other Zigbee or Wi‑Fi devices near the light flickering or dropping? If yes, move the light or the coordinator.

Branch based on native‑app result:

  • If the bulb works fine in the native app → move to integration debugging (next section).
  • If the bulb fails in the native app → check the router’s DHCP logs for address conflicts, update the bulb firmware via the native app, or try pairing it fresh from scratch. If it still drops, the bulb’s radio is likely failing (see stop threshold below).

Zigbee and Z‑Wave: Coordinator or Mesh Issue?

Coordinator Location and USB Interference (ZHA / Zigbee2MQTT)

  • Rule of thumb: Keep the USB coordinator away from USB 3.0 ports, metal enclosures, and high‑current cables. Use a USB extension cable (1–3 feet) to isolate it.
  • Example: A user with a Sonoff ZBDongle‑P in a Raspberry Pi 4 had three Aqara bulbs dropping offline every 45 minutes. Moving the dongle to a powered USB hub on a 2‑foot extension eliminated all dropouts.
  • Verification after relocation: In Zigbee2MQTT’s map view, check the link quality of the previously problematic bulb. If it was below 50 (out of 255) and is now above 100, the interference fix worked.

Overloaded Coordinator (Too Many End Devices)

  • Most USB coordinators (Conbee II, Z‑Stick Gen5) handle 40–60 devices reliably. Beyond that, you’ll see random disconnects.
  • Sign it’s overloaded: Lights drop when you add a new device elsewhere on the network, or dropouts spike during mesh repairs.
  • Fix: Add a second coordinator with a separate network (via ZHA Multi‑PAN or a dedicated Zigbee2MQTT instance) and split your lights between them.

Poor Router/Repeater Placement

  • Bulbs that are Zigbee routers (most mains‑powered bulbs) can extend the mesh. But if a router bulb is too far from the coordinator, it may drop and take downstream devices with it.
  • Check with Zigbee2MQTT map or ZHA network visualization – look for routes with link quality below 50. Those links are prone to timeouts.
  • Fix: Move a mains‑powered smart plug (e.g., a Linkind Matter Smart Plug that also acts as a Zigbee router) halfway between the coordinator and the problematic bulb.

Failure‑mode trap: Assuming every bulb is a good router. Many Aqara and early Tuya bulbs are Zigbee end devices – they won’t repeat signals. If you place such a bulb far from the coordinator, it relies on other devices to relay, which can stretch the mesh thin. Check the device type in the integration (router vs. end device) before blaming range.

Wi‑Fi Lights: Router and Channel Conflicts

For Wi‑Fi bulbs (LIFX, Wyze, Nanoleaf, Govee), the culprit is almost always radio interference or IP assignment.

2.4 GHz vs 5 GHz – The Obvious Trap

  • Many Wi‑Fi bulbs only support 2.4 GHz. If your router’s smart band steering pushes the bulb to 5 GHz (even momentarily), it disconnects.
  • Fix: Create a dedicated 2.4 GHz SSID for IoT devices. Give the bulb a static DHCP reservation so it doesn’t change IP after a power cycle.

Channel Congestion from Other IoT Devices

  • Neighbors’ Wi‑Fi, baby monitors, or nearby Zigbee routers on the same channel (e.g., Zigbee channel 11 overlaps with Wi‑Fi channel 1) can cause dropouts.
  • Fix: In your router, set the 2.4 GHz channel to 1, 6, or 11 – the only non‑overlapping channels. On Zigbee, change the coordinator’s channel to 15, 20, or 25 (avoiding Wi‑Fi overlap).
  • Real case: A user with 12 Kasa Wi‑Fi plugs could not keep one specific Kasa bulb online. Changing the router’s 2.4 GHz channel from “Auto” to fixed channel 11 stopped the dropouts overnight.

Step‑by‑Step Fixes (Operator Flow)

Follow this sequence in order. Stop and verify after step 4 if the light stays online for 24 hours.

1. Restart Home Assistant (Settings → System → Restart) – clears integration caches.

2. Force‑reconnect the bulb – In the integration page, click the bulb’s entry and select “Reconfigure” or “Remove and re‑add” (keep the bulb powered).

3. Rebuild the mesh

  • In Zigbee2MQTT: Settings → Advanced → “Reconfigure all devices”.
  • In ZHA: remove and re‑pair the light.

Note: This can take 10–15 minutes for larger networks.

4. Move the coordinator – Use a USB extension cable or change its location by at least 2 feet away from metal or USB 3.0 ports.

5. Change Wi‑Fi or Zigbee channel

  • For Wi‑Fi bulbs: set a fixed 2.4 GHz channel on your router.
  • For Zigbee bulbs: change the coordinator’s channel (requires re‑pairing all devices – only if nothing else works).

6. Replace the bulb – If the light fails steps 2–3 and drops again within an hour despite good signal, the bulb’s radio may be faulty. Example: a generic Tuya Zigbee bulb that worked for six months then started disconnecting every 15 minutes – replacing it with a Philips Hue White solved it.

Success Check (Verification Step)

After each fix, open Home Assistant → Logbook and filter by the bulb’s entity. Watch for “state changed” events (from “unavailable” to “on/off”). If you see no “unavailable” entries for at least 15 minutes of normal use (turning the light on and off a few times), the fix is holding. For a full confidence test, let it run overnight.

Stop / Escalate Threshold

If after step 4 the bulb still drops offline within one hour and the signal quality in your coordinator’s map is above 150 (good), the bulb’s radio is likely failing. Cease DIY troubleshooting and contact the manufacturer’s support for warranty replacement. If the bulb is out of warranty and the problem started after a firmware update, check the manufacturer’s forum for known bugs – some first‑gen LIFX bulbs had connectivity issues that were never fully patched.

Checklist: When to Swap the Light vs Swap the Coordinator

Use this decision aid before buying new hardware:

Check item Pass/Fail? Action if fail
Bulb stays online in manufacturer’s app for 2 hours Pass → skip to next row Fail → bad bulb or router conflict (check router logs, try a different outlet)
Coordinator is on USB 2.0 port, away from metal enclosures Pass → skip Fail → relocate coordinator with USB extension
Zigbee network has fewer than 40 devices (for single USB coordinator) Pass → skip Fail → add second coordinator or split network
Wi‑Fi bulb has a static DHCP reservation Pass → skip Fail → set static IP in router DHCP reservation
Light stays online for 24 hours after re‑pair Pass → done Fail → consider replacing the bulb or upgrade the coordinator (e.g., to a PoE‑powered coordinator for heavier loads)

Quick Reference Table: Common Causes by Platform

Platform Typical cause Quick fix
ZHA (Conbee II) USB 3.0 interference Move to USB 2.0 port + extension
Zigbee2MQTT (Sonoff) Coordinator overload Reduce device count or add second coordinator
Wi‑Fi bulb (LIFX, Wyze) 5 GHz roaming Create dedicated 2.4 GHz SSID
Matter over Thread Stale Thread border router Reboot border router (Apple TV, HomePod, or Amazon Echo Hub)

If your smart light still goes offline after these steps, check the manufacturer’s firmware update page – some older bulbs (like first‑gen LIFX) had known connectivity bugs patched years ago. In rare cases, a failing power supply in the light’s driver can cause intermittent dropouts; replacing the bulb is the simplest test.

With a methodical approach you can isolate the cause in under 15 minutes and avoid buying unnecessary hardware.

Explore This Topic

Related guides in this cluster:

Similar Posts