The smart home interoperability glossary

Smart home vocabulary is unusually bad at explaining itself. The same physical thing gets four names depending on who is selling it, and words that sound interchangeable (hub, bridge, controller, border router) describe four different jobs. This glossary defines every term this site uses, and states the consequence, because a definition you cannot act on is not much use.

Terms are grouped by theme. Each one has its own anchor, so you can link straight to a single definition.

Standards and organizations#

Matter#

An application layer that defines how a controller and a device describe and command each other, published by the Connectivity Standards Alliance and first released in October 2022. It is not a radio: it runs over Wi-Fi, Ethernet and Thread, which is why "Matter vs Wi-Fi" is a category error. The practical consequence is that Matter decides what your device can say, and the radio underneath decides how reliably it says it. Start at what Matter is if this is your first stop.

Thread#

A low-power wireless mesh networking protocol that carries IPv6, built on the same 802.15.4 radio as Zigbee. Thread has no application layer of its own, so it needs something like Matter on top to define what a message means. In practice Thread is the reason a battery sensor can run for years and still respond in under a second, and the reason you need a border router in the house at all.

Zigbee#

A low-power mesh protocol with its own application layer, in consumer products since the mid 2000s and still the largest installed base of any smart home mesh. It runs on the same 802.15.4 radio as Thread but is not IPv6 based, so Zigbee devices always need a hub to translate. The consequence is that Zigbee gear is cheap, plentiful and hub-dependent, which is a good trade if you already run a hub. See Zigbee in 2026.

Z-Wave#

A sub-GHz mesh protocol standardized as ITU-T G.9959 and run by the independent Z-Wave Alliance. In the United States it operates at 908.42 MHz, well away from Wi-Fi, which is its single biggest practical advantage. Regional frequency variants are not interoperable, so a European Z-Wave device will not join a US network. See Z-Wave and Z-Wave Long Range.

Wi-Fi#

The high-bandwidth wireless network your phone and laptop use, and the transport for the majority of cheap smart plugs, cameras and appliances. The overwhelming majority of smart home devices are 2.4 GHz only, for range, wall penetration and chip cost, and that has not changed in 2026. The consequence is that every smart device you add competes for airtime with everything else on 2.4 GHz. See Wi-Fi smart devices.

Bluetooth LE#

The low-energy variant of Bluetooth, used almost everywhere in the smart home as a setup channel rather than a control channel. Matter commissioning, Zigbee Direct onboarding and most vendor app pairing flows all lean on it. The consequence is that pairing usually needs your phone physically near the device even when the device will later be controlled over Wi-Fi or Thread. See Bluetooth and BLE in the smart home.

Connectivity Standards Alliance#

The standards body formerly called the Zigbee Alliance, renamed in 2021. It now owns both Zigbee and Matter, runs their certification programs, and operates the Distributed Compliance Ledger. At its June 2026 event the alliance put membership at 940 companies, with about 300 actively working on the Matter specification.

Zigbee 3.0#

The unified Zigbee application profile that replaced the older, fragmented profiles such as Home Automation and Light Link. It remains the deployed baseline for consumer Zigbee products in 2026. If a box says Zigbee 3.0, it will join a modern coordinator without profile-matching games, which was not true of the generation before it.

Zigbee 4.0#

Announced on 18 November 2025 and fully backward compatible with Zigbee 3.0, which the alliance describes as protecting more than a billion already-deployed devices. It adds dynamic link keys, a device interview step, restricted mode, Zigbee Direct onboarding over Bluetooth LE, batch commissioning, sleepy-to-sleepy communication, and new sub-GHz radio layers. Nothing you own stops working, and as of September 2026 you should still expect to buy Zigbee 3.0 hardware.

Suzi#

The alliance's brand for standards-based long-range sub-GHz mesh built on the Zigbee network layer, using 900 MHz in North America and 800 MHz in Europe. Certification opened on 2 September 2026. It complements 2.4 GHz Zigbee rather than replacing it, and no shipping consumer products were confirmed at launch, so treat it as a technology to watch rather than a buying criterion.

Aliro#

An alliance standard for phone and wearable based door lock credentials, using NFC together with Bluetooth LE and ultra-wideband for proximity. Samsung's Wallet Digital Home Key launched on Aliro in March 2026. The point of it is that your phone becomes a key that works across lock brands and wallet apps, instead of one proprietary app per lock.

Radios and networking#

802.15.4#

The IEEE standard defining the physical radio and media access layer that both Zigbee and Thread use: 250 kbit/s, 16 channels numbered 11 to 26 in the 2.4 GHz band. Because they share a radio, a Zigbee network and a Thread network in the same house interfere with each other exactly as they interfere with Wi-Fi. Put them on different channels from each other and from your Wi-Fi, using the channel planner.

6LoWPAN#

Short for IPv6 over Low-power Wireless Personal Area Networks: the adaptation layer that compresses IPv6 headers and fragments packets so they fit inside tiny 802.15.4 frames. Thread is built on it; Zigbee is not. That is the structural reason a Thread device has a real IP address your router can route to, while a Zigbee device only exists behind its hub.

IPv6#

The addressing scheme Thread and Matter are built on. On a single flat home network, link-local addressing is enough and the specification says no extra IPv6 infrastructure is required, so "IPv6 disabled on your router breaks Matter" is imprecise. What actually breaks things is IPv6 disabled on the controller host, blocked IPv6 multicast, VLAN boundaries with no mDNS reflector, or Thread, which does need routable prefixes across the border router.

mDNS#

Multicast DNS: the mechanism that lets devices resolve .local names on a local network with no DNS server, using multicast on UDP port 5353. Matter and Thread depend on it completely for finding devices after commissioning. It is also the single most common cause of Thread and Matter discovery failures, which is why Thread troubleshooting starts with mDNS and only then looks at radio.

DNS-SD#

DNS Service Discovery: the convention layered on top of mDNS that lets a device advertise what it is, not just its name. Matter uses _matterc._udp to advertise a device that is open for commissioning and _matter._tcp for a device already on a fabric. If you are packet-sniffing a failed pairing, those two service names tell you which stage you are stuck at.

SRP#

Service Registration Protocol: how a Thread device registers its name and services with the border router, which then republishes them on your main network over mDNS. A border router must run an SRP server and an advertising proxy for sleeping devices. That relay is exactly why mDNS problems on your home router show up as Thread devices "disappearing" rather than as a network error.

Multicast#

Sending one packet to a group of listeners rather than to a single address. Matter group commands use IPv6 multicast with a shared group ID and key, and mDNS uses multicast for discovery. Anything on your network that filters or drops multicast (aggressive IGMP snooping, client isolation, a VLAN boundary) will break device discovery and group control while unicast control keeps working, which makes the fault look random.

Mesh#

A topology where devices relay traffic for each other instead of every device talking straight to a central point. Zigbee, Thread and classic Z-Wave are all meshes; Wi-Fi and Z-Wave Long Range are not. The practical implication is that mains-powered devices are infrastructure: adding a few well-placed plugs or bulbs fixes range problems that no amount of restarting the hub will.

Band steering#

A router feature that advertises 2.4 GHz and 5 GHz under one SSID and pushes clients to whichever band it prefers. It is the most common cause of "my smart plug will not set up", because provisioning fails when your phone is on 5 GHz and the device can only see 2.4 GHz. The fix is a separate 2.4 GHz SSID for IoT devices, covered in Wi-Fi smart devices.

Client isolation#

An access point setting, often called AP isolation or guest mode, that stops devices on the same SSID from talking to each other. It is a reasonable guest network default and a disaster on an IoT network, because your phone, your hub and your devices all need direct local traffic. Turn it off on the IoT SSID or nothing will discover anything.

IGMP snooping#

A switch feature that learns which ports actually want multicast traffic and stops flooding it everywhere. Configured well it reduces noise; configured badly, or enabled without an IGMP querier on the network, it silently drops the multicast that mDNS and Matter group commands depend on. If discovery works on one switch and not another, this is a prime suspect.

VLAN#

A logical network segment that separates traffic on shared physical hardware, commonly used to put IoT devices on their own subnet. It is good security practice and it breaks smart home discovery by default, because mDNS is link-local and does not cross subnets. If you use VLANs you must run an mDNS reflector and allow the right traffic, or Matter, AirPlay and border router discovery all stop working.

mDNS reflector#

A router or firewall function (also called an mDNS repeater, proxy or Avahi reflector) that copies multicast discovery packets between subnets so devices on one VLAN can find services on another. Without it, VLAN segmentation and smart home discovery are mutually exclusive. Note that reflectors are imperfect: some implementations mangle records or loop, which produces devices that appear and vanish rather than a clean failure.

Matter concepts#

Fabric#

A security domain with a 64-bit fabric ID, scoped to a single root certificate authority. Each ecosystem you pair a device into creates its own fabric, and devices are only required to support five of them. That five-slot floor is the root cause of most multi-ecosystem pairing failures, explained in sharing a Matter device across ecosystems.

Node#

An addressable device on a fabric, identified by a 64-bit node ID. The same physical device joined to three fabrics has three node identities and one shared data model. That is why changing a setting from one app shows up in the others: there is one device underneath, wearing three badges.

Endpoint#

A numbered feature set inside a node. Endpoint 0 is always the root node and holds the descriptor, basic information, access control, operational credentials, network commissioning, group key management and diagnostics clusters, with application endpoints numbered from 1. A two-gang switch or a temperature-and-humidity sensor is one node with several application endpoints, which is why some controllers split it into several entries and others do not.

Cluster#

A named group of attributes, commands and events covering one capability, such as on/off, level control or door lock. Clusters are the unit of interoperability: if a controller implements a cluster, it can drive any device that exposes it. When people say Matter "strips features", they mean the vendor capability had no matching cluster. How Matter actually works walks through this with real symptoms.

Attribute#

A piece of state inside a cluster, such as current level, temperature or battery percentage. Controllers read attributes, write them, or subscribe to changes. If your app shows a stale value, the usual cause is a broken subscription rather than a broken sensor.

Command#

An action you invoke on a cluster, such as On, Toggle or MoveToLevel. Commands are the "do something" half of the data model, as opposed to attributes, which are the "what is true right now" half. Sensitive commands such as door lock operations use timed transactions with a maximum timeout, which defeats replay attacks.

Event#

A timestamped log entry a device emits, such as a lock being operated or a fault clearing. Events differ from attributes because they record that something happened at a moment, rather than what is true now. Matter 1.6 added security sensor event history, which is what lets a controller show you a list of past triggers rather than just the current state.

Device type#

A named, certifiable bundle of mandatory and optional clusters bound to an endpoint, such as "dimmable light" or "robot vacuum". The specification defined 92 of them as of Matter 1.6. A device type in the specification is permission for someone to build a product, not evidence that anyone did, and not a promise your controller implements it: see which device types Matter supports.

Commissioning#

The full process of adding a device to a fabric: discovery, an encrypted session from the setup code, attestation, credential installation, network credentials, then operational discovery. It is six distinct stages, and knowing which one failed is most of the diagnosis. Matter pairing explained takes it stage by stage.

Commissioner#

The role that performs commissioning: usually your phone app, acting on behalf of an ecosystem. The commissioner is the thing that verifies attestation and installs credentials, which is why pairing often fails on a phone problem (Bluetooth off, no local network permission) rather than a device problem.

Commissioning window#

The period during which a device accepts a new fabric. The maximum is 900 seconds and the minimum is 180 seconds, and a factory-new device with no fabrics may advertise for up to 48 hours. Enhanced commissioning generates a fresh, short-lived passcode that the device itself never learns, which is why the temporary code from your app is safer than the printed one.

QR setup code#

The square code on the device or its packaging, carrying an 88-bit payload: version, vendor ID, product ID, commissioning flow, discovery capabilities, a 12-bit discriminator and a 27-bit setup passcode. Photograph it before you install the device behind a fixture, because you will need it again after any factory reset.

Manual pairing code#

The 11 or 21 digit numeric equivalent of the QR code, including a check digit, for when a camera cannot see the label. The 11-digit form carries less information than the QR payload, so pairing can take longer while the commissioner works out what it is talking to. It is a fallback, not a preference.

Discriminator#

A 12-bit value in the setup payload that tells a commissioner which advertising device is the one you mean. It exists because a room full of unpaired identical bulbs all advertise at once. If pairing repeatedly grabs the wrong device, power down the others and retry.

Passcode#

The 27-bit setup number, valid from 1 to 99999998, that seeds the first encrypted session. Trivial values such as 11111111 and 12345678 are explicitly banned by the specification. The factory passcode printed on a device cannot be revoked, which is the security argument for using an app-generated temporary code when sharing to a second ecosystem.

PASE#

Passcode Authenticated Session Establishment: the first encrypted session in commissioning, derived from the setup passcode. It proves you have physical access to the code without ever sending the code over the air. If pairing dies here, the cause is almost always a wrong or expired code, or a device that is not actually in pairing mode.

CASE#

Certificate Authenticated Session Establishment: the ongoing encrypted session between a controller and a device on a fabric, using the operational certificates issued during commissioning. Every normal command you send runs inside a CASE session. It is what makes local control cryptographically safe without any cloud involvement.

SPAKE2+#

The password-authenticated key exchange used to build the PASE session from the setup passcode. It is designed so that an eavesdropper who records the exchange learns nothing useful, and the device stores a verifier rather than the passcode itself. You never interact with it directly; it is the reason a short numeric code is not a security hole.

Attestation#

The step where a commissioner sends a 32-byte challenge and the device proves it is genuinely the product it claims to be, by returning a signed certificate chain plus an alliance-signed certification declaration. This is what stops a counterfeit device impersonating a certified one. It is also why a device with a manufacturing certificate problem fails to pair with an error nobody can act on.

DAC#

Device Attestation Certificate: the per-device certificate presented during attestation, carrying the vendor ID and product ID. It is provisioned in the factory and cannot be reissued in the field. A missing or malformed DAC is unrecoverable for the owner, and is one reason cheap uncertified hardware sometimes cannot be commissioned at all.

PAI#

Product Attestation Intermediate: the intermediate certificate that signs a manufacturer's device certificates and chains up to a root. It exists so a vendor can issue millions of device certificates without exposing its root key. During commissioning, the device sends the DAC and the PAI, and the commissioner supplies the root from its own trust store.

PAA#

Product Attestation Authority: the root certificate at the top of the attestation chain, published in the alliance's Distributed Compliance Ledger. A commissioner that cannot find the relevant PAA cannot verify the device. This is why a controller occasionally needs an update before it will accept a brand new manufacturer's products.

Certification declaration#

An alliance-signed document, carried by the device, stating which device types and specification version the product was certified against. The commissioner checks it during attestation. It is the closest thing to a machine-readable compliance claim, and it is also why "certified" and "behaves correctly" are different statements: see what Matter still cannot do.

Distributed Compliance Ledger#

The alliance's shared record of certified products, attestation roots and firmware update locations, usually abbreviated DCL. Controllers consult it to verify attestation and, where supported, to find over-the-air updates. Vendors who publish firmware to the ledger (Eve, Nanoleaf and IKEA among them) can be updated by any controller that implements it, which is a genuine lock-in-avoidance feature.

ICD#

Intermittently Connected Device: Matter's model for battery devices that are not reachable all the time. An ICD tells the controller how often it will check in, so the controller knows the difference between "asleep" and "gone". Without it, a sleeping sensor and a dead sensor look identical to your app.

LIT and SIT#

The two ICD operating modes. A short idle time device polls at most every 15 seconds, which suits a device that must respond quickly; a long idle time device, added in Matter 1.3, polls far less often, with idle durations running up to 18 hours. The trade is blunt: LIT buys you years of battery life and costs you responsiveness, so it belongs on contact and leak sensors, not on anything you expect to command.

Multi-admin#

Joining one device to several ecosystems at once, so the same lock appears in Apple Home and Alexa. It works by the first controller opening a commissioning window, producing a fresh short-lived code that the second ecosystem uses to commission the device onto its own separate fabric. Access is then governed per fabric by the access control cluster, and each fabric consumes one of the device's limited slots.

Joint Fabric#

The Matter 1.6 feature that lets several controllers co-administer one shared fabric through a central datastore, instead of each holding a separate fabric. An anchor administrator owns the root certificate authority and issues intermediates to the others, and the whole arrangement uses one fabric slot per device no matter how many controllers you have. As of September 2026, no ecosystem has shipped it to users.

Fabric Sync#

The Matter 1.4 predecessor to Joint Fabric, intended to let one ecosystem's devices appear in another automatically. No ecosystem shipped it in more than 19 months. It is worth knowing purely as the precedent that should temper your expectations for Joint Fabric.

Bridge#

A device that presents non-Matter devices (typically Zigbee, Z-Wave or a proprietary radio) to a Matter fabric as if they were Matter devices. It is the main path for getting existing gear into a modern ecosystem. It is also lossy in specific, predictable ways, listed in Matter bridges and what you lose through one.

Aggregator#

The endpoint on a bridge whose parts list enumerates all the bridged devices. It is the structural difference between a bridge and an ordinary multi-endpoint device. Practically, it is why a controller shows a single "bridge" accessory that then expands into dozens of sub-devices, and why hitting a controller's per-bridge limit makes all of them vanish at once.

Bridged node#

One device behind a bridge, exposed as an endpoint carrying bridged device basic information plus its application clusters. Two limits matter: firmware updates for bridged sub-devices are never available over Matter, and endpoint numbers are not reused, so a re-paired Zigbee device usually reappears as a brand new accessory with its automations lost.

Group#

A set of endpoints sharing a group ID and key, addressed with a single multicast command. Groups exist so that "all kitchen lights off" is one packet rather than eight. Whether your controller uses them is the difference between a room snapping off together and the popcorn effect.

Scene#

A stored set of attribute values you can recall as one action, such as a brightness and color per light. Matter scenes are a cluster-level feature, and they are not the same thing as your vendor's scenes. The Actions cluster is the only standard way for a bridge to expose vendor scenes, and no consumer controller implements it, which is the structural reason Hue and Aqara scenes do not cross a bridge.

OTA#

Over-the-air firmware updating. In Matter this is optional, not guaranteed, and availability depends on both the vendor publishing images and your controller implementing delivery. Controllers that can deliver updates include Apple Home, SmartThings, Home Assistant, Google and Homey. Bridged sub-devices are never covered, so keep the vendor app installed for anything behind a bridge.

Thread concepts#

Border router#

The device that connects a Thread mesh to your normal IP network: bidirectional IPv6 routing, on-mesh prefix advertisement, SRP and advertising proxy services so controllers can discover Thread devices, and commissioning relay. It is not a Matter controller and it does not add devices to your fabric. Which box you have matters more than most buyers realize: see Thread border routers.

Leader#

The single router in a Thread partition that assigns router IDs and holds the authoritative copy of network data. The role is elected automatically and moves if the current leader disappears, with no user action. You never configure it, but seeing which device is leader is a useful diagnostic when a mesh has split.

Router#

A mains-powered Thread or Zigbee device that stays awake and forwards traffic for others. Every mains-powered device you add is potential mesh infrastructure, and every battery device is not. Thread caps active routers at 32 per network, and targets 16 to 23, promoting standby devices when the count falls below 16.

Mesh extender#

Thread 1.4's new name for the router role, used in current Thread Group and OpenThread documentation. Nothing about the behavior changed, only the word. If one vendor's app says "router" and another says "mesh extender", they are describing the same thing.

REED#

Router-Eligible End Device, now also called an Extender-Capable Device: a device that could route but is currently acting as an end device, and can be promoted when the network needs more routers. This is how Thread avoids wasting router slots on a dense mesh. It also means the topology you see today is not the topology you will see next week.

End device#

A Thread or Zigbee node that does not route traffic and communicates only through one parent. End devices keep the mesh simple but add nothing to its coverage. If your network has range problems and every device is an end device, more of them will not help.

Sleepy end device#

A battery device that keeps its radio off between scheduled polls, which is how a coin cell lasts years. All of its traffic goes through its parent, and it is unreachable between polls by design. That is why a sleepy sensor reports quickly but a sleepy device you try to command can feel slow, and why they are wrong for anything you actuate.

PAN ID#

A 16-bit identifier for a personal area network, used by both Zigbee and Thread to distinguish neighboring networks on the same channel. Two networks that share a channel and a PAN ID will interfere with each other in ways that look like random device dropouts. Coordinators and border routers normally pick one for you.

Extended PAN ID#

The 64-bit network identifier carried in a Thread operational dataset, used to tell networks apart with far less chance of collision than the 16-bit PAN ID. It is the value to compare when you suspect you have two Thread networks: same extended PAN ID means one network, different values mean fragmentation. See why you have three Thread networks.

Network key#

The symmetric key in a Thread operational dataset, alongside the channel, PAN ID and extended PAN ID. Possessing it is what makes a device part of that Thread network. This is precisely why joining two ecosystems' Thread networks is a credential problem, not a radio problem.

TREL#

Thread Radio Encapsulation Link, added in Thread 1.4: 802.15.4 frames wrapped in UDP over IPv6 so mesh traffic can travel across Wi-Fi or Ethernet between border routers. It exists to stop a mesh partitioning when two halves of the house cannot hear each other over radio. It only helps if your border routers support Thread 1.4, which many deployed units still do not.

Thread Direct#

Announced on 17 June 2026, a capability that would let a phone commission a Thread device with no border router present. It is expected in Thread 2.0 with no announced timeline. Until it ships, a Thread device without a compatible border router in the house is unusable, which is the most common Thread buying mistake.

Credential sharing#

The Thread 1.4 mechanism for handing one border router's network credentials to another: the border router shows a nine-digit one-time passcode or a QR code, both sides derive an ephemeral key, and the requester pulls the operational datasets over an encrypted session. It is mandatory for Thread 1.4 certified border routers, and it is user triggered, single use and time limited. It is not automatic merging, and it will not retroactively unify networks you already have.

Zigbee and Z-Wave concepts#

Coordinator#

The single Zigbee device that forms the network, picks the channel and PAN ID and acts as the Trust Center. There is exactly one per Zigbee network and it is normally your hub or USB dongle. Its real limit is how many devices can attach to it directly, not the theoretical network size, so the fix for a crowded network is adding mains-powered routers rather than a bigger coordinator.

Binding#

A direct device-to-device link, classically a Zigbee wall switch bound to a bulb, so the switch commands the bulb without the hub in the path. Bound pairs have lower latency and keep working when the coordinator is down. Matter has an equivalent binding concept, and Joint Fabric's shared datastore holds bindings alongside groups and access rules.

Green Power#

A Zigbee profile for energy-harvesting devices such as kinetic wall switches with no battery at all. They need a proxy device (a mains-powered Hue bulb, for example) to relay their messages, they do not support binding, and they do not appear in network scans. Expect them to be invisible in your network map even when they work perfectly.

DSK#

Device Specific Key: the value printed on a Z-Wave device and encoded in its QR label, used to authenticate secure pairing. You typically type the first five digits to confirm you are including the device in front of you rather than a neighbor's. Photograph the label before installation, because in-wall devices bury it.

S2 security#

Z-Wave's Security 2 framework, required for certification since 2016, which uses an authenticated key exchange tied to the DSK. It closed the weaknesses of the older S0 scheme, which also drained batteries with its chatty key handling. If a controller offers you S0 for a modern device, something has gone wrong in inclusion.

SmartStart#

Z-Wave provisioning where you scan a device's DSK QR code into the controller before installation, and the device joins automatically the first time it powers on. No button pressing at the device, which matters for in-wall switches and ceiling fixtures. It requires controller support, so check before you rely on it.

Z-Wave Long Range#

A Z-Wave variant using a star topology, where every device talks straight to the hub with no repeaters and no hops, supporting up to 4,000 nodes with range up to about 1.5 miles line of sight and up to 30 dBm transmit power. It coexists with classic mesh on the same network and hub, and supports S2 and SmartStart. By CES 2026 there were 125 certified Long Range devices, and around 80% of the certification pipeline targeted it, so it is where the protocol is heading.

Platform and hub words#

Hub#

A box in your house that speaks one or more radios and runs some or all of your automation logic. The word is used for four different jobs (radio gateway, automation engine, cloud relay and Matter controller) and a given product may do one or all of them. Hubs, bridges, controllers and border routers separates them properly, and do you need a hub answers the buying question.

Controller#

In Matter terms, the software that holds a fabric's credentials and issues commands: the Apple Home, Google Home, Alexa, SmartThings, Home Assistant, Hubitat or Homey side of the relationship. Controller support, not specification version, decides what you can actually do. Ecosystems typically take 6 to 12 months to implement a new Matter release, and reporting from the alliance's June 2026 event described Apple, Google and Amazon as barely at 1.3.

HomeKit#

Apple's smart home framework and accessory protocol, introduced in 2014 and predating Matter by eight years. Apple's legacy HomeKit architecture was retired on 10 February 2026, and households that never migrated lost Home app control, automations and shared access. HomeKit still matters because some older accessories, including Belkin Wemo devices paired before its shutdown, keep working locally through it and nowhere else.

HomeKit Secure Video#

Apple's camera feature that analyzes and stores footage encrypted in iCloud, requiring an iCloud+ plan and a home hub. It is entirely separate from Matter: Apple raised it to 4K at WWDC 2026 and made no Matter camera announcement, and Apple Home still supports no Matter cameras. If you want camera footage in Apple Home, this is the only path, and it is a subscription.

Edge driver#

SmartThings' device driver format, written in Lua and executed on the hub rather than in the cloud, which replaced the older cloud-hosted device handlers. It is the reason a SmartThings hub can drive many Zigbee and Z-Wave devices locally. When a device is "not supported", what is usually missing is an Edge driver, and community-published drivers often fill the gap.

Works with Matter#

Not an alliance program. There is no "Works with Matter" badge: only certified devices carry the Matter logo. The "works with" badges you see on boxes are ecosystem programs (Works with Apple Home, Google Home, Alexa, SmartThings) that test the platform experience rather than Matter conformance, which is why a badged product can still behave differently in each app. See "Works with Matter" vs Matter certified.

Practical terms#

Local control#

Commands that are processed inside your house, with no round trip to a vendor server. Matter does not guarantee it: the alliance's own FAQ notes that Matter-only devices need an internet-connected controller for control away from home, Google Home's local Matter control covers lights, plugs and switches only, and Alexa maps Matter clusters onto cloud-side interfaces. The Local Control Index scores every platform on what actually survives an outage.

Cloud dependency#

The degree to which a device or platform stops working when the vendor's servers do. It has three separate failure modes: the internet goes down, the vendor has an outage, and the vendor shuts the service off permanently. All three have real 2026 examples, and when a smart home company shuts down covers how to buy against the third.

Popcorn effect#

When a group of lights turns on one at a time instead of together, because the controller is sending individual commands in sequence rather than one group command. It is a controller implementation problem, not a device fault. The standard fix is group multicast or wildcard paths that address many endpoints in one action, so the cure is a controller update, not new bulbs.

Ghost device#

An entry that survives in a controller after the physical device is gone, usually because the device was factory reset or unplugged before being removed properly. Ghosts break automations, clutter voice assistants, and on Zigbee and Z-Wave they can keep routing decisions pointed at a node that no longer answers. Always remove in the controller first, then reset the device.

Fabric exhaustion#

Running out of a Matter device's fabric slots, of which only five are guaranteed. Apple Home consumes two on its own because it synchronizes accessories through iCloud Keychain, and removing a device in a controller's interface does not reliably send the remove-fabric command, so orphaned slots accumulate. The failure is badly signaled: pairing appears to progress and then reports "pairing failed" with no cause. A factory reset clears the table, and Home Assistant's "manage fabrics" interface is the practical repair tool.