For months now, my smart lights have been a guessing game. I’d tap the light button in the manufacturer’s app or Home Assistant, and about half the time nothing would happen. Bulbs would randomly go offline even though they were getting power.

I did all the usual troubleshooting steps first. Reset the bulbs, re-paired them, moved them closer to the router, added Wi-Fi repeaters for better signal strength, even swapped one out with a brand new one. They’d behave for a day, then drop off again. Turns out, it wasn’t a bulb issue at all. The real culprit was my Wi-Fi all along.

Smart bulbs never had a choice about which band to use

2.4 GHz travels further, but it’s also the noisiest neighborhood

Almost all smart bulbs talk exclusively over 2.4 GHz Wi-Fi, not the faster 5 GHz your phone and laptop prefer. That’s true across the popular brands from Kasa and Tapo to Wiz, Sengled, Govee, and Cync, which all connect directly to a 2.4 GHz network with no hub in sight.

Manufacturers do this on purpose because 2.4 GHz travels further and pushes through walls better, and a light bulb doesn’t need much bandwidth to say turn on or go red. The tradeoff is that 2.4 GHz is a crowded, noisy neighborhood. It’s the same slice of spectrum your microwave, your Bluetooth devices, your neighbor’s router, and half your wireless gadgets all operate over. So anything that adds more noise to that band tends to hamper the cheap, low-power radios inside your bulbs first, long before it bothers your phone.

Three non-overlapping channels, and 40 MHz eats them all

Cisco calls anything but 20 MHz bad practice, for good reason

Channel width is how much of the airwaves your Wi-Fi uses at once. On 2.4 GHz you usually have two choices: 20 MHz, which is the standard, and 40 MHz, which bonds two channels together to squeeze out more speed.

A wider channel sounds better, and it is faster on paper. But 2.4 GHz simply doesn’t have the room for it. The entire band only has three channels that don’t overlap—1, 6, and 11, and a 40 MHz channel eats up so much space that it overlaps with the others and collides with nearby devices.

That’s exactly why you should avoid it. Cisco flat-out doesn’t support 40 MHz channel bonding on 2.4 GHz and calls using anything other than 20 MHz on that band bad practice. Enterprise guides also describe locking 2.4 GHz to 20 MHz as a non-negotiable in busy environments because it keeps those three channels from bleeding into each other.

That said, many routers still ship with a 20/40 MHz auto mode by default, which is probably what your router is doing out of the box. And that’s exactly what fixed my smart lights.

Auto mode was quietly widening the channel every time

My phone never noticed. My bulbs never stood a chance

Once I figured this out, the bulb dropping mystery made sense. My router was set to that auto 20/40 mode, so whenever it decided to widen the channel for a speed boost, it dragged my bulbs into a noisier, overlapping chunk of the wireless spectrum.

My phone and laptop, sitting comfortably on the 5 GHz spectrum, never noticed anything. But the little radios in my smart bulbs and ESP32s — already the weakest devices on the network — would lose their connection. That’s why they kept wandering off the network overnight when background traffic and channel switching happened without me watching.

Narrowing to a fixed 20 MHz gave those bulbs a stable, predictable lane. 20 MHz means less interference, less overlap, and more reliable communication for smart-home gear, and the bulbs gain nothing from a wider channel anyway. It’s the recommended IoT setting almost anywhere you look.

Two minutes in your router settings, no new hardware needed

Fixed to 20 MHz, locked to channel 1, 6, or 11

The setting is buried in your router settings and can be named and located differently based on your router’s make and model. The easiest way is to log into your router, either through its app or by typing its address into a browser, and find the wireless or Wi-Fi settings.

Look for the 2.4 GHz band specifically, then find the field labeled channel width, channel bandwidth, or just bandwidth. Change it from 20/40 MHz or Auto to just 20 MHz, save everything, and let the router reboot.

While you’re in there, it’s worth setting the 2.4 GHz channel manually to 1, 6, or 11 instead of Auto, since those are the only three that don’t overlap. If you want to be thorough, keeping your smart-home security on WPA2 rather than on a WPA3 exclusive mode also helps as a lot of older IoT chips get confused by WPA3.

No more re-pairing, no more half-lit rooms

The bulbs never needed that extra bandwidth anyway

After the reboot, I power cycled each bulb once at the wall so they’d reconnect to the calmer network, and that was genuinely all I needed to do. No more random disconnects, half-lit rooms, and re-pairing every couple of days. The lights have stayed rock solid since.

You won’t notice any real speed loss on your 2.4 GHz network from this either. Your bulbs never use that extra bandwidth anyway, and the devices that actually matter should already be connected to the faster 5 GHz network where the wide, fast channels actually make sense.

So if your smart lights keep dropping out, resist the urge to buy new hardware. Spend two minutes flipping your 2.4 GHz channel width down to 20 MHz first, and the change will almost certainly fix these random disconnects.