Smart home glossary

Short, direct answers to the terms that come up when matching devices to a hub.

Bridged vs native pairing: Many devices can join your ecosystem two ways: natively (paired directly to your hub’s radio or via Matter) or bridged (paired to the maker’s hub, which represents it onward — a Hue bulb via the Hue Bridge, an Aqara sensor via an Aqara hub). Native pairing removes a box and a hop; bridging keeps the maker’s full feature set, firmware updates, and a dedicated radio network.
Commissioning / pairing code: Commissioning is Matter’s standardized setup process: scan the QR code (or type the 11-digit numeric code) printed on the device, and the controller securely verifies the device, joins it to your Wi-Fi or Thread network, and installs its fabric credentials. Every Matter device ships with such a code, and it is worth keeping.
Local vs cloud control: Local control means your hub talks to devices directly on your home network, so automations run with no internet — Matter, Zigbee, Z-Wave, and Thread are all local protocols. Cloud control means commands route through a vendor’s servers, adding latency and a dependency: if the service is down or discontinued, so is your smart home.
Matter: Matter is the smart home interoperability standard run by the Connectivity Standards Alliance (CSA) and backed by Apple, Google, Amazon, and Samsung. A Matter-certified device works with any Matter controller — Apple Home, Google Home, Alexa, SmartThings — over Wi-Fi, Ethernet, or Thread, with local control and no vendor-specific app required for basic functions.
Matter bridge: A Matter bridge is a hub that represents its non-Matter devices — typically Zigbee — as Matter devices, so ecosystems like Apple Home can control them. The Philips Hue Bridge, Aqara hubs, IKEA DIRIGERA, and Bosch Smart Home Controller II all do this: pair a bulb to the bridge, and it appears in your Matter ecosystem as if it were a native Matter light.
Matter controller: A Matter controller is the software brain that commissions Matter devices onto its fabric and controls them: Apple Home (via a home hub), Google Home, Amazon Alexa, SmartThings, Home Assistant, Hubitat, or Homey. Every Matter setup needs at least one, and the controller — not the device — decides which device types and features you can actually use.
Matter fabric & multi-admin: A Matter fabric is one ecosystem’s trust domain: the set of devices and controllers sharing security credentials, such as your Apple Home. Multi-admin is the Matter feature that lets a single device join several fabrics at once — the same plug can live in Apple Home and Google Home simultaneously, each with local control, no re-pairing.
OTA firmware updates: OTA (over-the-air) updates let a smart home device’s firmware be upgraded by radio — fixing bugs, patching security, and sometimes adding features such as Matter support. Whether you can actually apply them depends on the platform: vendor hubs update their own brand automatically, while Matter, Zigbee2MQTT, ZHA, and Z-Wave JS each have their own OTA mechanisms with varying coverage.
S2 security & SmartStart: S2 is Z-Wave’s modern security framework: devices join with authenticated, encrypted inclusion, verified by entering a 5-digit PIN from the device’s DSK (Device Specific Key) or scanning its QR code. SmartStart builds on it — scan the QR code before installing, and the device joins the network automatically when powered up, with no inclusion-mode dance.
Thread: Thread is a low-power wireless mesh protocol built on IEEE 802.15.4 radio (2.4 GHz, the same silicon as Zigbee) that speaks native IPv6. It is the network most battery-powered Matter devices use: sensors, buttons, and locks join a self-healing mesh and reach your home network through a Thread border router.
Thread border router: A Thread border router is the device that connects a Thread mesh to your regular Wi-Fi/Ethernet network, forwarding IPv6 traffic between the two. Without one, Matter-over-Thread devices cannot be commissioned or controlled. It is a built-in function of many hubs and speakers — Apple TV 4K, HomePod, Nest Hub, Echo (4th gen), SmartThings Station — not a separate box you buy.
Works-with certification programs: “Works with” badges — Works with Alexa, Works with Google Home, Works with Apple Home, Works With SmartThings, Friends of Hue — are per-ecosystem certification programs, run by each vendor, that test a device’s integration with that one platform. They predate Matter and still cover many cloud-linked and proprietary integrations that Matter does not.
Z-Wave: Z-Wave is a sub-GHz mesh protocol (908.4 MHz in North America, 868.4 MHz in Europe) governed by the Z-Wave Alliance, known for strict certification, strong cross-brand interoperability, and zero Wi-Fi interference. Devices pair to a Z-Wave controller (SmartThings, Hubitat, Home Assistant with a USB stick, Homey), and it is the incumbent standard for locks, security sensors, and professionally installed systems.
Z-Wave Long Range (ZWLR): Z-Wave Long Range is a mode of Z-Wave (700/800-series hardware) that swaps mesh for a direct star topology: every device talks straight to the controller at up to a mile or more line of sight, with up to about 4,000 nodes per network and 10-year battery claims. Both the controller and the device must explicitly support it.
Z-Wave Plus & 800 series: Z-Wave Plus is the certification badge for devices built on the 500-series chip or later; the current 800-series silicon brings longer range, multi-year battery life, mandatory S2 security and SmartStart, and support for Z-Wave Long Range. Newer series matter for range and battery, but every generation remains backward compatible on the same network.
ZHA (Zigbee Home Automation integration): ZHA is Home Assistant’s built-in Zigbee integration: plug a supported coordinator dongle into the machine running Home Assistant and it runs a Zigbee network natively — no separate software, no MQTT broker, no vendor hub. It is the simpler of the two big DIY Zigbee routes, with Zigbee2MQTT being the more configurable one.
Zigbee: Zigbee is a low-power 2.4 GHz mesh protocol (IEEE 802.15.4) that has been the workhorse of affordable smart home devices for over a decade — Hue bulbs, IKEA and Aqara sensors, and thousands of others. Devices pair to a Zigbee coordinator (a hub or USB stick), not to Wi-Fi, and mains-powered devices extend the mesh as routers.
Zigbee binding: Zigbee binding links two devices directly — a remote to a bulb, a switch to a plug — so commands flow device-to-device without passing through the coordinator. Bound devices keep working even if the hub is down, with none of the latency of a hub round-trip.
Zigbee coordinator, router & end device: Every Zigbee network has exactly one coordinator — the radio in your hub or USB dongle that forms the network and stores its keys. Mains-powered devices (plugs, bulbs) join as routers that relay traffic and extend range; battery devices join as end devices that sleep between transmissions and route nothing.
Zigbee2MQTT: Zigbee2MQTT is an open-source (MIT-licensed) bridge that runs a Zigbee network from a USB coordinator dongle and publishes every device over MQTT, making any supported Zigbee device usable in Home Assistant and other platforms without a vendor hub. Its device database — the zigbee-herdsman-converters project — is the most comprehensive public record of Zigbee devices, and the source of the 5,405 Zigbee devices in our dataset.