Smart bulbs that drop at dusk, plugs that need resetting, a thermostat that works until the microwave runs: this is the 2.4GHz tax. It is not evidence that you need a new ISP. It is evidence that the house network was designed for laptops.
Pair this with why WiFi is slow with fast broadband and WiFi troubleshooting.
The devices are not on the network you tested
You ran a speed test on a phone, on 5GHz, in the kitchen. The bulb is on 2.4GHz, in a ceiling, next to a transformer. The plug is behind a fridge. The camera is a whole other article: CCTV on WiFi.
2.4GHz travels further and through more brick. It is also where every neighbour, baby monitor and cheap gadget lives. Terraced Slough and Maidenhead streets are noisy. Rural houses are quieter but have more distance.
Smart devices also sleep, reconnect badly, and stick to a mesh node they met once. “Dropping” is often “never roamed back”.
A laptop test is a 5GHz conversation with a talkative client. A bulb is a sleepy 2.4GHz radio with a tiny antenna, often inside a metal fitting, often on a circuit that gets switched at the wall. If the laptop is fine and the plug is not, you have proved the laptop is on a different band, in a different place, with a better radio.
We see this weekly in Windsor terraces, Maidenhead kitchens, and Uxbridge flats sharing a party wall. The broadband line is rarely the villain. The 2.4GHz neighbourhood is.
Causes we see on call-outs, in order
- Router in a cupboard, devices at the far end of the house
- Mesh node in the dead zone, backhaul already dying
- 2.4GHz channel set to auto in a dense street, fighting 15 other networks
- A separate IoT SSID with no coverage, or the opposite: one SSID with sticky clients
- Powerline “backhaul” that collapses when the kettle boils
- Too many devices on a consumer router that falls over at 40 clients
Faster broadband does not add 2.4GHz airtime. Whole home WiFi does, if the APs are in the right rooms.
Cupboard routers are the opening move. The ISP left the kit under the stairs. The bulbs are in a rear kitchen and an upstairs landing. 2.4GHz will try. It will not always hold a session through a closed door, a chimney, and a fridge.
Mesh makes this better when the node is in a strong-signal room near the gadgets. It makes it worse when the node is in the dead bedroom, whispering back to the cupboard, and every plug in the house decides that whisper is “the network”. Sticky clients are real. Cheap radios latch onto the first AP they saw and never let go, even when a better one is two metres away.
Auto channel on 2.4GHz in a Slough terrace is a weekly fight. There are only three clean channels. Everyone’s kit hops between them. A fixed, surveyed channel is boring and kinder.
Powerline is not backhaul. Ring mains in UK houses are noisy. When the kettle or the hob comes on, the “Ethernet over power” path you trusted for a mesh node becomes a brown-out. The plugs drop. You blame the bulb brand.
Fixes that stick
- Put a real AP (or a mesh node with a strong backhaul) near the cluster of gadgets: landing, kitchen ceiling, not the office 5GHz shrine
- Use Ethernet to that AP if you can. Cat6
- Cap how clever the roaming is on cheap bulbs. Sometimes a dedicated 2.4GHz SSID with a simple name is kinder
- Stop extending with another supermarket node
- Move hubs off WiFi if they have Ethernet. Hubs are not bulbs.
UniFi and similar platforms let you see a plug flapping on a particular AP. Consumer apps say “offline” and shrug.
The landing ceiling is a better home for an access point than the study desk. Gadgets cluster in halls, kitchens, and bedrooms. The study is where the laptop lives. Design for the sleepy radios, and the laptop will be fine. Design only for the laptop, and the bulbs will keep vanishing.
A dedicated IoT SSID is a management tool. It is not coverage. If that SSID only exists on the cupboard router, you have built a second network that still cannot see the kitchen. Put the SSID on the access point that actually sits near the devices. Keep the name simple. Some cheap kits hate spaces, punctuation, and band steering that yanks them onto 5GHz they cannot use.
If a hub has an Ethernet port, use it. The hub is the brain. The bulbs can stay wireless if the radio around them is honest. A hub in a metal TV cabinet on congested 2.4GHz will take the whole lighting circuit down with it.
When the smart home is a symptom
If laptops fail too, fix the house network, not the bulb brand. If only gadgets fail, it is still a coverage and band problem, but the laptop test fooled you.
Period walls make it worse: Victorian WiFi. Upstairs sensors: poor WiFi upstairs.
A house where Zoom dies in the loft and the thermostat drops in the hall does not have a smart-home problem. It has a coverage problem that the gadgets noticed first, because they are the weakest radios. Treat it as a whole-home job: access point positions, cable where the hops fail, then tidy the SSIDs.
A house where every laptop is happy and only the garden sensors drop might be distance, a metal shed, or a 2.4GHz channel fight with a neighbour. That can still be an AP placement job. It is not an ISP job, and it is not a reason to replace every bulb.
Kitchens, ceilings and the 2.4GHz neighbourhood
Kitchens are where this complaint is born. Microwaves sit on 2.4GHz. Fridges hide plugs. Foil-backed plasterboard in a rear extension eats what little signal survived the chimney. A node on the kitchen worktop looks helpful and then lives next to the noisiest appliance in the house.
Ceiling or high-wall placement above that mess is kinder. The radio sees the landing and the hall, not the microwave door. In a Maidenhead or Windsor kitchen extension we would rather drop Cat6 from the loft into a small AP than perch a mesh unit next to the toaster.
Loft sensors and water alarms have the opposite problem: distance, insulation, and a hatch that was never a good AP site. If those devices matter, give the loft a real access point or accept that a sleepy battery sensor at the far eaves will always be the first to vanish.
Neighbours are the bit you cannot unplug. Terraced Slough, parts of Hounslow, and busy Maidenhead streets share a small set of 2.4GHz channels. We pick a channel on survey instead of leaving the router on auto overnight. That does not silence the street. It stops your kit joining the street’s argument every ten minutes.
Hubs, threads, and why the bulb is still your problem
Some of the newer smart homes speak Thread or a hub protocol and only use WiFi for the hub. That can be more stable, but only if the hub has a decent location and, ideally, Ethernet. A hub in a metal TV cabinet on a congested 2.4GHz SSID will still look like “the lights are broken”.
If you are mixing five apps, five 2.4GHz clouds, and a consumer mesh, no installer can make that elegant. We can make the radio part less awful: coverage at the ceiling, a calmer 2.4GHz, APs that do not reboot when 60 devices join at dusk.
CCTV should not live in that soup. Cameras that “are just another smart device” are how driveways go blind. Wire them. Why CCTV cameras drop off WiFi.
We are not here to pick your lighting app. We are here so the radio those apps depend on actually exists in the ceiling where the bulbs sit. If the hub can take Ethernet, that is the first cable we offer. One wired brain and a decent 2.4GHz cell in the kitchen will out-perform a cupboard router plus four cloud accounts.
A practical order of operations we use on site
- Count the gadgets and where they sit, not where the nice laptop sits
- Look at the 2.4GHz neighbourhood
- Fix AP placement or add a cabled AP near the cluster
- Only then rename SSIDs or invent an IoT network
- Move any hub that has a spare Ethernet port onto a cable
People want step 4 first because it feels like configuration. Step 3 is the work. Adding Ethernet is often a short loft drop, not a renovation.
If the rest of the house is also failing, stop calling it a smart-home issue. It is poor WiFi upstairs or WiFi in a large house wearing a bulb-shaped hat.
On a typical Maidenhead terrace visit we photograph the router cupboard, the kitchen ceiling, and the landing. We walk with a phone on 2.4GHz, not only 5GHz. We note the microwave, the neighbour count, and whether a mesh node is already dying in a bedroom. Then we place or cable an AP, then we talk names.
Bring a list of what drops and when. “Lights, dusk, rear kitchen” is a brief. “The smart home is broken” is not. If a particular plug is behind a fridge, say so. We can move a radio. We cannot make 2.4GHz enjoy a compressor.