An independent publisher — unconnected to any manufacturer, retailer or brand named here. Guides and nothing further: no line to ring, nothing mended. No credential or payment requested. Published by DIGITALDOTS TECHNOLOGIES of Ontario, Canada.
Wi-Fi and wireless protocols, explained
Why so much smart home equipment insists on 2.4 GHz, what Zigbee, Z-Wave and Thread each do, and what Matter is really standardising.
Two radios, five protocols and one standard that is not a radio at all. Most confusion here comes from those being discussed as though they were the same kind of thing.
On this page
Start here
Two bands, and why it matters
If you read one section here, make it this one. An enormous share of setup problems trace back to this single distinction, and it takes about two minutes to understand.
A home router broadcasts on two frequency bands. They behave differently in ways that decide whether a device holds a connection two rooms away.
| 2.4 GHz | 5 GHz | |
|---|---|---|
| Range | Longer. Passes through walls and floors far more effectively. | Shorter. Degrades noticeably through anything solid. |
| Speed | Lower. | Higher. |
| Congestion | Crowded. Shared with older equipment, some cordless phones, microwaves and the neighbours. | Generally cleaner, with more channels available. |
| Power draw | Lower, which matters enormously for anything running on cells. | Higher. |
Why smart devices choose the slower band
It reads as a limitation. It is a deliberate design choice, and a sensible one. A smart plug reporting whether it is on or off sends a trivial amount of data. What it needs instead is a connection that holds from wherever it happens to be plugged in, which is frequently a socket behind furniture two rooms from the router.
Supporting one band also makes the radio cheaper and simpler, which matters when a manufacturer is building something to sell at a low price. So a great many devices carry a 2.4 GHz radio and nothing else, and no setting anywhere changes that.
A common obstacle
When your router combines both bands
Most modern routers broadcast both bands under a single network name and decide for themselves which one each device receives. It goes by several names, band steering among them, and in ordinary use it is convenient.
During setup it causes a specific and confusing problem. Many devices need your handset to be on the same 2.4 GHz network they are joining. If the router has quietly placed the handset on 5 GHz, the device is never found, and nothing on screen explains why.
Ways through it
- Separate the bands for a while. A router's own configuration usually allows band steering to be switched off, or the 2.4 GHz band to be given its own name. Whoever supplied the router documents where that sits.
- Leave them separate permanently. Some households keep the bands separately named and put everything connected on the slower one. Tidier for a large setup, at the cost of remembering which is which.
- Switch 5 GHz off briefly. Blunt, and effective for the ten minutes a pairing takes.
- Use a second handset as a hotspot. Occasionally useful for a stubborn device: pair it to a 2.4 GHz hotspot, then move it across afterwards.
Other router settings that interfere
- Guest network isolation. Useful for security, and it prevents devices seeing one another, which several need to do.
- WPA3-only security. Some older equipment supports WPA2 only. A mixed mode usually resolves it.
- Hidden network names. Many devices cannot join a network that is not broadcasting its name.
- MAC address filtering. Where it is on, each new device has to be added explicitly.
- Captive portals. Networks with a sign-in page, common in shared accommodation, generally cannot be used by connected devices at all.
Beyond Wi-Fi
What else devices speak
Wi-Fi is not the only way connected equipment communicates, and for some purposes it is a poor choice.
| Protocol | How it works | Typical use |
|---|---|---|
| Wi-Fi | Straight to your router. Nothing extra needed. | Cameras, mains-powered plugs and switches. Anything with power to spare and data to move. |
| Zigbee | Low-power mesh. Devices relay for one another, and a hub bridges to your network. | Bulbs, sensors, buttons. Very common where there are a lot of devices. |
| Z-Wave | Low-power mesh on a different, less crowded frequency. Also needs a hub. | Sensors, locks, switches. Frequencies differ by region, so hardware is region-specific. |
| Thread | Low-power mesh where each device has its own network address, so it reaches your network more directly. Needs a border router. | Newer sensors, locks and bulbs, often alongside Matter. |
| Bluetooth | Short range, handset to device. No hub, and no reaching it from elsewhere. | Initial setup on many devices; primary control on some locks and trackers. |
Why mesh matters
On a mesh, mains-powered devices do not merely receive. They relay. A message travelling from a hub to a distant door sensor can hop through a smart plug and a bulb on the way, which is why adding mains-powered devices tends to improve coverage for everything rather than crowding it.
Battery devices generally do not relay, because listening constantly would drain them. A mesh built entirely of battery sensors therefore gains none of that benefit, which is worth knowing before buying a dozen of them.
The regional frequency point
Z-Wave in particular uses different radio frequencies in different regions, because the unlicensed spectrum available differs by country. Equipment bought abroad may simply not work at home, and that is a hardware matter rather than a setting.
Frequently misunderstood
What Matter actually is
Matter is the most misunderstood term in this whole subject, and clearing it up removes a good deal of confusion.
Matter is not a radio protocol. It does not compete with Wi-Fi, Thread or Zigbee the way those compete with one another. It is a layer sitting on top of them, describing how a device presents itself so that equipment from different makers can be controlled from one place.
The problem it addresses is real. Historically a device built for one ecosystem often did not appear in another at all, so a choice of voice assistant quietly narrowed what could be bought afterwards.
What it genuinely delivers
- Devices that work across several platforms at once, without picking a side.
- Local control. Many Matter interactions happen on your own network rather than by way of a manufacturer's servers, which is quicker and keeps working during an outage.
- A more consistent setup, usually scanning a code rather than installing yet another application.
What it does not
- Feature parity is not promised. Makers commonly expose the basics through Matter while keeping the interesting parts in their own application. A lock might unlock but not report battery.
- Thread devices still need a border router. Matter does not remove that, which is why several speakers and displays now include one.
- Existing devices are not upgraded retroactively. Support depends on a firmware update the maker chooses to ship, and many older products never receive one.
- The logo is a floor, not a ceiling. It says a device passed a compatibility bar. It says nothing about whether it is well made or well supported.
Terminology
Hubs, bridges and border routers
These words are used loosely, and product pages rarely explain them. All three describe something that translates between a low-power radio network and your ordinary one.
- A hub usually both bridges radio protocols and runs the logic, deciding what happens when a sensor triggers.
- A bridge typically just translates, leaving the logic to an application or a service. Many bulb systems ship one.
- A border router is the Thread-specific term for whatever connects a Thread mesh to your main network.
Do you need one?
If everything you own speaks Wi-Fi, no. If you want Zigbee, Z-Wave or Thread devices, yes, though you may already have one without realising it, since several speakers and displays now include the function.
The case for a hub anyway
- Local processing. Automations running on a hub keep working when the internet is down, and respond faster because nothing travels to a distant server and back.
- It keeps the Wi-Fi uncluttered. Thirty bulbs on a mesh protocol put no load on the router at all.
- Better battery life for sensors, which is why almost every long-lived battery sensor uses a mesh protocol rather than Wi-Fi.
And against
- Another box, another socket, another thing that can fail.
- Additional cost, sometimes not obvious until checkout. Worth establishing whether a bridge is included or sold separately.
- A single point of failure. If the hub goes, everything attached to it goes with it.
Growing pains
Why things break as you add devices
A common trajectory: five devices work beautifully, and somewhere around twenty-five things begin dropping out unpredictably. This is rarely coincidence.
Router device limits
Consumer routers have a practical ceiling on simultaneous connections, and it is frequently lower than the marketing suggests. Connected devices are individually undemanding and collectively numerous, which is exactly the load that ceiling was not designed for.
2.4 GHz congestion
The band is crowded, and in a flat or a terrace you are sharing it with the neighbours. It also has far fewer non-overlapping channels than 5 GHz. Microwaves and some cordless phones sit in the same space.
What actually helps
- Move the bulk off Wi-Fi. Bulbs and sensors on Zigbee, Z-Wave or Thread free the router entirely. This is the single most effective change for a large setup.
- Add mains-powered mesh devices in weak spots, since they extend the mesh rather than competing for airtime.
- Check the 2.4 GHz channel. Routers choose automatically and not always well; moving away from a crowded neighbour can help noticeably.
- Consider a mesh Wi-Fi system for a large or awkwardly shaped house, noting that it improves coverage rather than the device-count ceiling.
- Put the router somewhere central and open. Unglamorous, and still the highest-value thing many households can do.
Before you spend
Choosing what to buy
Protocol arguments get heated. In practice a few plain guidelines cover most decisions.
- A handful of devices? Wi-Fi is fine. Do not buy a hub for four smart plugs.
- Planning something larger? Favour a mesh protocol from the start. Converting later means replacing hardware.
- Battery sensors? Prefer Zigbee, Z-Wave or Thread. Wi-Fi sensors exist and generally want charging far more often.
- Cameras? Wi-Fi or wired. Video needs bandwidth the low-power protocols do not have.
- Using more than one ecosystem? Matter support is genuinely worth preferring.
- Want automations that survive an outage? Look for local control and hub-based processing rather than anything cloud-dependent.
- Buying from abroad? Check the regional frequency variant, especially for Z-Wave.
Frequently encountered
Common situations, and what usually causes them
- A device cannot see your network during setup. The band, almost always. Confirm it is being offered 2.4 GHz and that the handset is on that band too.
- Setup finishes, then the device drops off immediately. Often band steering moving it, or a signal too weak where it finally sits. Worth testing in the intended position rather than beside the router.
- Everything worked until the router changed. Devices store network details. Most applications carry a reconnect option, and keeping the same network name across a router change avoids the whole business.
- Devices respond slowly or intermittently. Congestion rather than failure. Worth counting how many things sit on 2.4 GHz.
- A distant sensor keeps dropping. On a mesh, a mains-powered device between it and the hub will relay. On Wi-Fi, the answer is usually better coverage.
- A Matter device appears in one application and not another. Check it was shared to the second platform. Matter supports more than one administrator, and it is usually a deliberate step rather than an automatic one.
Where a situation persists beyond these, the manufacturer is the right place to go next. They hold model-specific information and the warranty, neither of which general guidance can substitute for.
Keep reading
Most setup failures trace back to one thing
If a device cannot see your network, the band is nearly always the reason. The speaker guide covers what that looks like in practice.
Read the speaker guideHow we checked this
Where this comes from
- The literature each manufacturer issues for its own equipment, which is where intended behaviour is set down
- What Apple and Google publish for people building software, since that is where handset permissions and radio handling are described
- The wireless specifications themselves, which govern how each band and every low-power protocol actually conducts itself
- Opening the applications and observing them in whatever state they are in today, with every check dated
Nothing stated here rests on a forum thread or an article with no name attached to it. Where a point simply cannot be pinned down, the page admits as much instead of papering over it.
Written reference material about connected household equipment, published independently by DIGITALDOTS TECHNOLOGIES of Ontario, Canada.
Free to read. Nothing to download, and no account to open.
- No sales copy
- No affiliate links
- Sources named
- Reviewed twice a year
Around the house
Doors, safety & sensing
Climate, energy & network
Not affiliated with, sponsored by or endorsed by any equipment maker, voice platform or network vendor whose products are described here. Product names appear so a reader knows which equipment is meant, and for no other reason.
No telephone line has ever been issued here. Nobody advises readers individually, nothing is reached into from a distance, nothing is diagnosed or repaired, and no hardware is sold. The tools on these pages respond to taps and nothing more. On some guide pages a finder supplied by Tidio Ltd asks a short set of questions before linking to the relevant section. Neither is staffed by any person, and neither has access to readers’ devices or accounts. For a specific product, the maker's own documentation is the place to look.
The site carries no advertising, no affiliate links and no sponsored content, and nothing on it is for sale. It receives no payment, product or other consideration from any manufacturer whose equipment is described here. Writing, hosting and publication are paid for by DIGITALDOTS TECHNOLOGIES, which operates the site. No commercial relationship shapes what is written.
Nowhere on this website is there a sign-in, an account of any kind, or a screen that takes money. A password, card number, verification code, or other credential is never requested, and no technical-support request is accepted.