The first thing to check
Is the wall switch on? Smart bulbs need constant mains power to stay on the network. If someone has flipped the physical switch, the bulb is not offline — it is unpowered, and no amount of app troubleshooting will reach it. This accounts for far more “broken” smart lights than any actual fault, which is why smart switches or switch guards are the standard fix in households where people forget.
Three different systems, three different failure modes
Before troubleshooting, know which kind of smart light you have, because the diagnosis differs completely.
Wi-Fi bulbs connect directly to your router. Each bulb is its own network client. They fail when the Wi-Fi changes, when the 2.4GHz band is unavailable, or when the router runs out of DHCP addresses.
Zigbee or Z-Wave bulbs — Philips Hue, most Aqara, many Ikea — connect to a hub, which connects to your router. They fail when the hub loses power or network, or when the mesh between bulbs is broken by removing a bulb that was acting as a relay.
Bluetooth bulbs connect directly to a phone. They fail when you are out of range, or when another phone has grabbed the connection.
Matter and Thread devices behave broadly like the hub category, with a border router in place of a traditional hub.
Work through it in order
Confirm the bulb has power
Turn the wall switch off and on again. If the bulb lights up at all — even at the wrong colour or brightness — it has power and the fault is elsewhere. If it stays dark, try the bulb in a lamp you know works. A smart bulb can fail like any other bulb, and the LEDs do eventually die.
While you are there, check the fitting. Smart bulbs are heavier and longer than standard ones, and a poor contact in an old fitting causes intermittent behaviour that looks exactly like a network problem.
Check the hub, if you have one
For Hue and similar systems, look at the hub’s status lights. You want to see power, network and internet indicators all steady. A hub that has lost its ethernet connection will show every bulb as unreachable in the app, which reads as a catastrophic failure and is usually a loose cable or a router that reassigned the hub’s IP address.
Power-cycle the hub by unplugging it for thirty seconds. Give it two full minutes to rejoin and rediscover devices before judging the result — hubs rebuild their mesh slowly.
Verify the 2.4GHz band for Wi-Fi bulbs
Almost all smart bulbs are 2.4GHz only. They cannot see a 5GHz network and they cannot see 6GHz. If your router broadcasts both bands under one name with band steering, setup and reconnection often fail because the phone is on 5GHz while the bulb needs 2.4.
The reliable fix is to give the 2.4GHz band its own network name, at least temporarily, so you can connect the phone to it during setup. Some routers also have a “smart connect” or band steering toggle that can be disabled. And check your router has not run out of DHCP addresses — a house with forty smart devices on a router with a small default pool hits this ceiling and it presents as random devices dropping off.
Restart the bulb's own radio
Most smart bulbs respond to a power-cycle pattern. Turning the wall switch off and on again a few times in succession will, on many brands, either reset the bulb’s network connection or put it into pairing mode. Check your specific brand’s sequence before doing this, because on some systems five rapid cycles performs a factory reset and you will have to set the bulb up from scratch.
A single off-on is always safe and resolves a good number of stuck radios.
Check the app and the account
Open the manufacturer’s own app rather than Alexa, Google Home or HomeKit. If the bulb responds in the native app but not through a voice assistant, the bulb is fine and the integration has broken — relink the account in the assistant app.
If the native app shows the bulb as offline, check whether the service itself is down. Cloud-dependent brands have outages, and there is nothing to fix at your end when that happens.
Look at mesh coverage for Zigbee and Z-Wave
These systems relay through mains-powered devices. If you removed a bulb or a smart plug that sat between the hub and a distant light, you may have broken the path. The symptom is specific: one or two devices at the edge of the house go unreachable while everything near the hub is fine.
Adding a mains-powered device between the hub and the problem area restores the route. Most hubs also have a “rebuild network” or “heal” function worth running after any change to the device layout.
If a bulb works from the app but not from a schedule or automation, the bulb is healthy. Check the automation’s conditions — a sunset trigger with the wrong location set, or a routine that requires someone to be home, will silently do nothing while looking correctly configured.
Patterns worth recognising
All lights offline at once
Something shared has failed: the hub, the router, or the manufacturer’s cloud service. Check the hub’s lights and whether other internet devices work before touching individual bulbs.
One light offline, rest fine
Local to that bulb. Power, fitting, distance from the hub, or a failed bulb. Swap it with a working bulb from another fitting — if the fault follows the bulb it is the bulb, and if it stays with the fitting it is wiring or range.
Lights work but respond slowly
Usually network congestion or a cloud round-trip. Local control — Zigbee, Thread, or a brand with local API support — is far faster than a command that travels to a server and back. If slowness started recently, check whether your Wi-Fi is congested or whether the router firmware changed.
Lights turn on by themselves
Check automations and routines first, including ones created by a voice assistant that you may have forgotten about. Then check whether anyone else has app access. Genuine spontaneous activation from a fault is rare; a forgotten schedule is common.
Do not put smart bulbs behind a dimmer switch unless the bulb explicitly supports it. Traditional dimmers chop the mains waveform, which starves the bulb’s electronics and causes flickering, buzzing, unreliable network behaviour and shortened life. Smart bulbs expect full mains power and dim themselves electronically.
Making a smart lighting setup that stays reliable
Three decisions make the difference between a system that works for years and one that needs constant attention.
Prefer hub-based systems for anything beyond a few bulbs. Zigbee and Thread meshes handle dozens of devices without loading your Wi-Fi, and they recover from problems better than a router juggling forty individual clients.
Solve the wall switch problem physically. Either replace the wall switch with a smart switch that keeps the bulb powered, or fit a switch guard, or put a battery-powered smart button over the old switch. Relying on everyone in the house remembering not to touch a light switch does not work.
Give the router a static DHCP reservation for the hub. This prevents the single most annoying recurring failure, where the router reassigns the hub’s address after a reboot and everything appears to break at once.
Why do my smart bulbs come back on at full brightness after a power cut?
Because that is the default behaviour for most bulbs — after losing mains power they return to a known state, which is usually full brightness and warm white. Many brands now offer a “power-on behaviour” setting that lets you choose to restore the previous state or stay off instead. Look in the bulb’s advanced settings in its native app.
Can I use smart bulbs with an existing dimmer switch?
Generally no. A conventional dimmer interferes with the bulb’s power supply and causes flickering, buzzing and network dropouts. The correct approach is to replace the dimmer with a standard on/off switch, or better, a smart switch designed to work alongside smart bulbs, and do the dimming in the app.
Why does the bulb work in the app but not with Alexa or Google?
The integration between the bulb’s cloud service and the assistant has broken, which happens after password changes, service outages, or account migrations. Remove the skill or linked service in the assistant app and add it again. The bulbs themselves need no attention.
How many smart bulbs can one hub handle?
It varies by system. A Philips Hue bridge officially supports 50 lights; other Zigbee hubs range from 30 to over 100. The practical limit is usually mesh quality rather than the stated number — devices spread thinly over a large house will struggle before you reach the maximum, while a dense cluster will not.
Is it worth switching to Matter?
Matter’s real benefit is cross-platform compatibility, so a device works with Apple, Google, Amazon and Samsung ecosystems without separate integrations. If you are starting fresh or use more than one ecosystem, it is genuinely useful. If you have a working single-brand setup, there is no urgency to replace anything.
The bottom line
Check power at the wall first, then the hub, then the network band, then the individual bulb. The pattern of what is offline tells you almost everything: everything at once points at a shared component, one device points at that device. And if the household keeps flipping the wall switch, fix that physically rather than trying to solve it in software.
