Do you need a smart home hub at all? Wi-Fi-only vs hub-based setups
Updated · Reviewed against the current HomeHubAtlas dataset
Short answer: for a handful of Wi-Fi plugs and bulbs controlled from a phone — no, you don't need a hub. The hubless setup hits three walls as it grows: battery-powered sensors (which can't afford Wi-Fi), automations that should survive an internet outage, and a router groaning under dozens of chatty Wi-Fi clients. Each wall has a cheap, specific fix — and one of them you may already own.
What "no hub" actually gets you
A Wi-Fi smart device talks to your router and, almost always, to its maker's cloud; the phone app and the Alexa/Google voice layer sit on top. This covers plugs, bulbs, cameras, and appliances well: no extra box, no protocols to learn, gift-friendly. Two structural limits come with it. First, control usually routes through the vendor's servers — see what happens when the internet drops. Second, there is a device class Wi-Fi physically can't serve.
Wall 1: battery devices
A Wi-Fi radio drains a coin cell in days, which is why door/window sensors, motion sensors, buttons, and most lock keypads run on Zigbee, Z-Wave, or Thread — and all three need a radio on the hub side. The moment you want "hallway light when motion at night," you need either a coordinator/hub or a Thread border router. That's the single most common reason a hubless home stops being one; the 1,555 sensors in our dataset are almost entirely non-Wi-Fi.
Wall 2: automations that must not depend on the cloud
Phone-app scheduling is fine until the ISP hiccups at 11 pm. Locks, presence lighting, and heating logic belong on something that executes locally — a Hubitat, Home Assistant, Homey Pro, or an Apple Home setup anchored by an Apple TV or HomePod mini.
Wall 3: router load
Every Wi-Fi device is a full network client. Past a few dozen, consumer routers shed clients and 2.4 GHz airtime gets contested. Zigbee, Z-Wave, and Thread devices don't count against that budget — one hub represents the whole mesh to your network. This wall arrives latest but is the most annoying to fix retroactively.
The middle path you may already own
Matter blurred the old hub/no-hub line: an Apple TV, HomePod, recent Echo speaker, or Nest Hub is already a Matter controller, and several include a Thread border router — check the built-in list. That turns "buying a hub" into "using the speaker on your shelf," and it covers battery Thread sensors without a dedicated box. What it doesn't cover: the enormous Zigbee and Z-Wave catalogs, which still need their own radio.
A decision rule that holds up
- ≤10 devices, all plugs/bulbs/cameras, cloud acceptable: stay hubless.
- You want sensors or buttons anywhere: you need a radio — a Matter controller with Thread you already own, or a Zigbee coordinator from the hub guide.
- Locks, heating, or security in the mix: go local-first — see the local-control guide — and check each candidate hub's device coverage on its works-with page before committing.