|

Smart Bulb Shows Offline in Home Assistant? Here’s How to Fix It

ByAlex Turner

If your smart bulb shows offline in Home Assistant, don’t restart the bulb first. Power‑cycle the coordinator — the hub, bridge, or Zigbee dongle — instead. That single step resolves over half of “offline” cases. The bulb itself is usually fine; the connection between Home Assistant and the coordinator timed out, or the coordinator’s firmware glitched. Most users instinctively press the bulb’s power switch or use the native app to toggle it, but that rarely fixes the underlying connection drop because the bulb is still responding to its own hub – it’s the bridge between Home Assistant and the hub that failed.

Below is a step‑by‑step playbook. Use the diagnostic flow first, then follow the ordered steps with checkpoints.

Diagnose: Coordinator or Bulb Problem?

Start with a simple test. Check whether other devices on the same protocol are also offline. The table below tells you where the fault likely lives.

If… Likely cause
Multiple Zigbee bulbs show offline + your coordinator light is solid but no responses Coordinator hung – power cycle required
Only one Wi‑Fi bulb is offline, but other Wi‑Fi devices work Bulb lost Wi‑Fi credentials or router changed band
All Wi‑Fi devices are offline Router / access point issue – not a bulb problem
The bulb is offline in Home Assistant but its native app still controls it Home Assistant integration glitch (entity registry or MQTT topic mismatch)

Counter‑intuitive case: Sometimes the bulb was never offline. Home Assistant’s entity registry can silently corrupt. Reloading the integration or restarting Home Assistant Core brings the bulb back without touching hardware. For example, a user on the Home Assistant forum reported that after a power outage, a Zigbee bulb showed “unavailable” for two days despite the coordinator working fine. Reloading the ZHA integration restored it instantly.

Fix Steps in Order

Follow these steps in order. Stop after each checkpoint to avoid unnecessary work.

Step 1 – Restart the Coordinator (not the bulb)

  • Zigbee (ZHA/Zigbee2MQTT) – Unplug the coordinator (Conbee II, Sonoff ZBDongle‑E, Hubitat C‑8 stick, etc.), wait 10 seconds, plug back in. If your coordinator is a USB stick, also check the USB cable; a loose connection can cause intermittent disconnects.
  • Wi‑Fi bulb hub – Power‑cycle the hub (Philips Hue Bridge, Sengled Hub, Lutron Caséta bridge, etc.). Leave it off for 30 seconds to allow capacitors to drain.
  • Matter/Thread – Restart the Thread Border Router (Apple TV 4K, HomePod mini, or Nest Hub Max) or the hub if using Matter over Wi‑Fi. For Matter over Thread, a simple power cycle of the Border Router often resolves routing table issues.

Checkpoint: After the coordinator comes back online, wait 1–2 minutes. Refresh the Home Assistant dashboard. If the bulb reappears (shows “on” or “off” instead of “unavailable”), you’re done.

Branch here: If the bulb is still offline but other bulbs on the same coordinator are back, the issue is likely with that specific bulb’s path. Skip straight to Step 3 (logs) instead of reloading the integration. However, if no bulbs came back, move to Step 2 — the integration may be stuck.

Step 2 – Reload the Integration

If the bulb still shows offline, don’t delete it. Go to Settings → Devices & Services → Integrations. Click the integration used by the bulb (e.g., “Zigbee Home Automation,” “Zigbee2MQTT,” “Tuya,” “Kasa”), then click “Reload”.

Checkpoint: Check the bulb’s state again. If it’s now “on” or “off” (not “unavailable”), the fix is complete. This works because reloading forces Home Assistant to re‑fetch the device state from the hub and clear any stale cache entries.

Step 3 – Check Logs for Channel or Firmware Errors

Open Settings → System → Logs. Filter for the bulb’s integration.

  • Zigbee: Look for `Zigbee: device 0x… not reachable` or `timeout`. In ZHA, you might see `Timeout waiting for response from 0x…` — this often means interference on the same Zigbee channel as a neighbor’s network. Use a channel scanner like Zigbee Network Map (built into Zigbee2MQTT) to find the least congested channel. Changing your coordinator’s channel requires re‑pairing all devices, but it’s the only lasting fix for chronic interference.
  • Wi‑Fi bulbs: Look for `connection refused` or `unsupported protocol`. Also check if the bulb’s IP address changed. If your router uses DHCP, the bulb may be assigned a new IP after a power loss. Assign a static IP via router DHCP reservation or the bulb’s native app. Additionally, verify the bulb is on a 2.4 GHz network – most smart bulbs (LIFX, TP‑Link Kasa, Meross) don’t support 5 GHz.

Success signal: After changing channel or moving the bulb closer to the router, the logs stop showing the error and the bulb comes back online.

Step 4 – Re‑pair as Last Resort

If the bulb is still stuck offline after steps 1–3, it needs re‑pairing.

  • Zigbee: Put the coordinator in pairing mode, then factory‑reset the bulb (usually 5 on/off cycles within 2 seconds). Re‑add it via ZHA or Zigbee2MQTT.
  • Wi‑Fi: Factory‑reset the bulb (hold the button or power‑cycle 3 times quickly), then add it fresh in the bulb’s native app. Use the same Home Assistant integration binding (e.g., Tuya, Kasa, LIFX). For bulbs that use MQTT (like earlier LIFX Z strips), ensure the MQTT broker is running and the topic matches.

Common mistake: Trying to re‑pair without removing the old device from Home Assistant first. Delete the dead entity from Settings → Devices & Services → Entities before adding it again. Otherwise, Home Assistant may create a duplicate entity with the same name, causing confusion.

Five Quick Checks Before You Start

Confirm these five things with a visual check:

  • [ ] Coordinator power light – Is the Zigbee dongle/hub showing a steady LED? If blinking or off, power‑cycle it.
  • [ ] Wi‑Fi bulb app – Can you still control the bulb with its native app (Philips Hue, LIFX, TPLink Kasa)? If yes → the integration is broken, not the bulb.
  • [ ] Home Assistant logs – Are there `unavailable` entries for other devices on the same protocol? If yes → coordinator or network issue.
  • [ ] 2.4 GHz band – Is your router’s 5 GHz band disabled or running with the same SSID? Many bulbs won’t connect to 5 GHz; they need a separate 2.4 GHz network.
  • [ ] Bulb firmware – Is the bulb’s firmware up to date? Check in the native app. Outdated firmware can cause random disconnects. For example, Philips Hue bulbs with firmware 1.58.2 had a known issue where they would drop off the network every few hours until updated to 1.59.1.

If you check all five and the problem persists, move to the re‑pair step.

FAQ

Why does my smart bulb show offline in Home Assistant but still works with Alexa?

The native app talks directly to the bulb’s cloud or local hub. Home Assistant uses a separate integration; that integration may have lost its binding, or the bulb’s local API changed. Reload the integration first.

Can a full Home Assistant restart fix the offline bulb?

Yes, if the cause is a stuck entity or database cache. Restart Core (Settings → System → Restart Core), but avoid a full host reboot unless you suspect the OS or hardware. A per‑integration reload is faster and less disruptive.

My Zigbee bulb reconnects after a coordinator restart but goes offline again within an hour. What’s wrong?

Likely Zigbee channel conflict or a weak signal. Change the coordinator’s Zigbee channel to 15, 20, or 25 (check which is least congested with a tool like Zigbee Network Map). Also move the coordinator at least 3 feet away from Wi‑Fi routers – USB 3.0 ports on computers can also cause interference.

Do I need to delete and re‑add the bulb every time I change my Wi‑Fi password?

Yes – most smart bulbs store Wi‑Fi credentials at pairing time and require a factory reset to accept new credentials. Use a guest network that never changes for bulbs if possible.

My bulb shows offline only during certain hours. Any idea why?

Could be a scheduled router reboot or Zigbee channel congestion during peak Wi‑Fi usage (e.g., when neighbors’ routers switch channels). Enable Home Assistant’s “state timer” for the bulb – if it flips between online/offline at predictable times, check your router’s logs for channel changes.

If the bulb remains offline after all steps, verify your Home Assistant version and the integration’s compatibility list. Some older bulbs (e.g., early LIFX Z strips) dropped support after a firmware update – you may need to flash an older firmware using the vendor’s support tool. Keep logs, and search the Home Assistant community forum for your specific bulb model and protocol.

Explore This Topic

Related guides in this cluster:

Similar Posts