Skip to content
intenv

Topic

Connectivity and Standards

Every connected device depends on two agreements: a way to move bits, and a shared meaning for them. This topic covers both. It explains home Wi-Fi, low-power meshes such as Zigbee, Z-Wave and Thread, Bluetooth Low Energy, long-range networks such as LoRaWAN, wired building protocols such as KNX and BACnet, and Matter, the shared application layer that runs over several of them. It is also plain about why mixing them is still hard.

A smart plug’s box lists a string of names: Wi-Fi, Bluetooth, Zigbee, Thread, Matter. They look like rivals, but most do different jobs at different levels. Sorting them by job is the quickest way into home automation standards and connected building systems.

A radio is not a language

Two questions sit under every connection. How do the bits travel: on which band, how far, at what cost in battery? That is the radio, or the wire. And what do the bits mean: how does a switch tell an unfamiliar light to turn off? That is the language, or application layer.

Wi-Fi, Bluetooth, Zigbee, Z-Wave and Thread mainly answer the first, though Zigbee and Z-Wave bring languages of their own. Matter answers only the second: it has no radio and runs over Wi-Fi, Thread or Ethernet.

The families, by job

FamilyTypical jobWhat it trades away
Home Wi-FiCameras, speakers and other data-heavy, mains-powered kitBattery life, and router capacity as the device count grows
Low-power mesh: Zigbee, Z-Wave, ThreadBattery sensors, locks, switches and bulbsBandwidth; usually needs a hub or border router
Bluetooth Low EnergyWearables, locks, short-range sensors, and setting up new devicesRange, and remote access without a bridge
Long-range low-power: LoRaWAN, cellular IoT such as NB-IoT and LTE-MMeters, city sensors, farm and site monitoring over kilometresData rate and message frequency; cellular adds a subscription
Wired building protocols: KNX, BACnetLighting, blinds and plant in larger or newer buildingsFlexibility: cabling and professional set-up
Matter, the shared application layerOne device language over Wi-Fi, Thread and EthernetSome maker-specific features; it does not change range or battery life

In a mesh such as Zigbee or Z-Wave, mains-powered devices relay for their neighbours, so coverage grows as you add kit. Z-Wave’s sub-gigahertz band passes through walls more easily than the crowded 2.4 GHz band the others share. LoRaWAN belongs mostly outdoors, where a sensor sends a few bytes now and then on a battery meant to last years. KNX is cabled in during construction, and BACnet is how commercial heating and cooling plant is usually described and controlled.

Why interoperability is hard

Sharing a radio does not guarantee cooperation. Two Zigbee devices from different makers usually connect, yet one’s features may not appear in the other’s hub. Two building controllers can both support BACnet and still label the same reading differently. Many devices also depend on their maker’s cloud service, which sits above every standard and can be switched off.

Each gap is bridged by a gateway or hub that translates, and every translator is one more part that can fail. Certification helps: Z-Wave has long required certified devices to work with certified controllers, and Matter exists to give makers a shared vocabulary.

How to read a product box

Look past the logos for five things:

  1. The radio. It decides battery life, range and what else you need.
  2. What it needs from you. “Requires a hub” or “requires a Thread border router” means it will not work alone.
  3. The transport under the Matter logo. The logo alone does not say whether it uses Thread or Wi-Fi.
  4. Bluetooth next to Matter. That is usually just the setup radio.
  5. Local control. Does it keep working when the internet drops?

Where to start

Begin with home-automation protocols compared, which sets the main radios side by side and ends with a way to choose. Then read Matter and Thread for how the language and the mesh fit together, and Matter over Thread vs Matter over Wi-Fi for what the choice of road changes. For the layers beneath, including messaging such as MQTT, how IoT works follows one reading from start to finish. The building side is under smart buildings.

Questions people ask

What are the main smart home wireless standards?

Wi-Fi, Bluetooth Low Energy, Zigbee, Z-Wave and Thread. Wi-Fi suits mains-powered devices that send a lot of data. Bluetooth handles short-range links and setting up new devices. Zigbee, Z-Wave and Thread are low-power meshes for battery sensors, switches and locks. Matter is not a radio but a shared language that runs over Wi-Fi and Thread.

What is the best home automation protocol?

There is no single best one. Match the radio to the device: Wi-Fi for cameras and other mains-powered kit, a low-power mesh for battery sensors and locks. Z-Wave’s sub-gigahertz band can help in thick-walled homes. For new devices, Matter over Thread gives the best current chance of mixing brands, as long as you have a border router.

What standards do connected building systems use?

Commercial buildings mostly use BACnet for heating, ventilation and air conditioning, KNX for lighting, blinds and room control (especially in Europe), and Modbus for meters and drives. Wireless sensors added during a retrofit often use Zigbee, Thread or LoRaWAN, and reach the building management system through a gateway that translates between protocols.

What standards cannot fix

Standards settle what devices say to one another, not physics, business models or time. A thick wall still blocks a 2.4 GHz signal, a maker can still withdraw a cloud service, and a new protocol version never reaches a device whose firmware is not updated. Low latency and reliable control still come from good placement, local processing and a sensible mix of radios.

In this topic

Guides