|

How to Fix Smart Light Shows Offline in Home Assistant: Troubleshooting Guide

ByAlex Turner

If a smart light shows as offline in Home Assistant, the most common cause is a temporary network or power glitch. Try restarting the light (flip its physical switch off for 10 seconds, then on) and run a quick Configuration → Server Controls → Check Core Config to see if the entity reconnects. If it doesn’t, the issue is usually one of these: weak signal, a dead battery (for battery-powered lights), a faulty Zigbee/Z-Wave coordinator, or a Wi‑Fi channel conflict.

The right fix depends on the light’s protocol. For battery-powered Zigbee lights, start with battery level and link quality. For Wi‑Fi lights, check channel congestion first. This simple protocol-based decision can save you from unnecessary resets.

First Check – Is the Light Actually Responding?

Before diving into configuration files, verify the light’s basic connectivity:

  • Power cycle the light. Use the wall switch or pull the bulb for 10 seconds. Wait 30 seconds for it to rejoin the network.
  • Check the light’s own app. If the manufacturer’s app (e.g., Philips Hue, LIFX, IKEA TRÅDFRI) shows the light online, the issue is isolated to Home Assistant’s integration layer.
  • Look at the coordinator/hub. In Home Assistant’s sidebar, go to Settings → Devices & Services → Integrations. Click your Zigbee coordinator (ZHA, Zigbee2MQTT, or deCONZ) or your Wi‑Fi light’s integration. The “Log” tab may show recent disconnection errors.

If the light responds in its own app but not in Home Assistant, skip to the integration-level fixes below. If the light is genuinely offline everywhere, start with the hardware and network checks.

Verification step after any fix: Go to Developer Tools → States in Home Assistant, search for the light’s entity ID, and confirm its state is “on”, “off”, or “unavailable” is gone. Then toggle the light from the dashboard to ensure it responds.

Most Likely Causes (With Real Examples)

Zigbee/Z-Wave Signal Drop or Coordinator Issue

A battery-powered Aqara LED Strip T1 loses connection because the coordinator (e.g., Sonoff Z‑Bridge or Conbee II) is too far or has a full routing table. In the Zigbee2MQTT frontend (or ZHA’s device page), look at the device’s “Link quality” (LQI). Values below 50 often cause intermittent offline status. Move the light closer to a mains-powered Zigbee router (like a smart plug) or add a new router near the light. Restart the coordinator from its integration page.

Wi‑Fi Channel Congestion (for Wi‑Fi Lights)

A LIFX A19 bulb (2.4 GHz only) shows offline after a neighbor’s router switched to the same channel. Home Assistant may still see the bulb’s MQTT topic, but the bulb stops responding. Use a Wi‑Fi analyzer app to see channel utilization. Change your router’s 2.4 GHz channel to 1, 6, or 11 (choose the least crowded one). For dual‑band routers, disable 5 GHz on the SSID the bulb uses – many smart lights won’t connect to 5 GHz.

Dead Battery in Battery-Powered Lights

A Philips Hue Go (battery‑powered) shows as offline in Home Assistant when its battery falls below 10%. The Hue Bridge still reports it online, but Home Assistant loses the entity. In the integration’s device page, look for a “battery_level” attribute. If it’s missing or below 15%, that’s the cause. Charge or replace the battery. If the entity doesn’t come back, remove and re‑add the device in Home Assistant.

Incorrect Device Key or Pairing Data

After restoring a Home Assistant backup, some Zigbee devices keep an old network key and refuse to reconnect. The light appears offline even though the coordinator sees it. In Zigbee2MQTT, check the device’s “Definition” – if it says “inActive” or “0x0000”, the key is mismatched. Remove the device from Home Assistant, factory reset the light (usually by cycling power quickly 3–5 times), and re‑pair it.

Step-by-Step Quick Fixes (Ordered)

1. Restart the light’s coordinator/hub.

  • For ZHA: Go to Settings → Integrations → ZHA → Configure → Hardware → Restart Coordinator.
  • For Zigbee2MQTT: In the frontend, click Settings → Restart Coordinator.
  • For a Wi‑Fi hub (e.g., Hue Bridge): Unplug it for 30 seconds.
  • After restart, check if any other devices on the same coordinator came back. If yes, the coordinator is fine.

2. Force Home Assistant to reload the integration.

Go to Settings → Devices & Services → Integrations, click the three‑dot menu on the light’s integration, and select Reload. This re‑reads entity states from the coordinator/bridge. Immediately check the entity state in Developer Tools → States.

3. Ping the device via a service call.

In Developer Tools → Services, call `light.toggle` or `homeassistant.update_entity` with the entity ID. If the state changes to “unavailable” in the log, the device is unreachable.

4. Check for IP address conflicts (Wi‑Fi lights only).

In your router’s DHCP client list, verify the light has a unique IP. If two devices share the same IP, the light will appear offline randomly.

5. Update Home Assistant and all integrations.

A known bug in the 2024.12 ZHA component caused certain lights to go offline after a core update. Always upgrade to the latest version. After updating, reload the integration.

Decision Checklist – Is It Time to Factory Reset?

Use this quick pass/fail list before resorting to full factory reset:

Check Pass Fail
Light responds in its own app? Skip to integration fixes Proceed to hardware/network checks
LQI > 60 (Zigbee) or RSSI > -75 dBm (Wi‑Fi)? Network is fine Move device closer or add a repeater
Battery level > 20% (if applicable)? Not battery issue Charge or replace battery
Restarting coordinator brought other devices back? Coordinator is okay Try coordinator replacement or USB port change
Entity ID appears in Home Assistant developer tools? Entity exists Remove and re‑add the device
Last core update was more than 7 days ago? Stable version Roll back if recent update broke connectivity

If you fail four or more checks, a factory reset of the light and a fresh pairing is the most reliable path.

When to Stop Troubleshooting

If you’ve tried all the steps above and the light still shows offline, the hardware itself is likely defective. Signs it’s time to stop:

  • The light fails to pair even after a factory reset.
  • Multiple lights on the same coordinator/hub are all offline – the coordinator or its USB cable may be damaged.
  • The coordinator’s LED never flashes or turns solid green after a restart.

At this point, contact the manufacturer for warranty service or replacement.

FAQ

Why does my light show offline only in Home Assistant but works in its own app?

This usually points to an integration issue. Reload the integration, check for outdated custom components, or try removing and re-adding the device within Home Assistant.

Can a Home Assistant update cause lights to go offline?

Yes. Some Home Assistant releases (e.g., 2024.12) introduced bugs that disconnect certain Zigbee devices. Check the release notes and roll back if necessary, or wait for a patch.

Should I use a Zigbee repeater for a distant light?

If the link quality (LQI) is below 50, a mains-powered Zigbee router (like a smart plug) placed halfway between the coordinator and the light will significantly improve reliability. Do not use battery-powered devices as repeaters.

Explore This Topic

Related guides in this cluster:

Similar Posts