Matter and Thread Explained: The Smart Home Standards and How They Use Your Network
Matter and Thread are two separate standards that usually get mentioned in the same breath, and mixing them up is the source of most smart home confusion. Matter is an application language: it defines what a light, lock or thermostat is and how an app tells it what to do. Thread is a low-power wireless mesh network that carries some of that traffic. A Matter device can run over Thread, over WiFi or over Ethernet. A Thread device can, in principle, run something other than Matter.
Why care? Because Matter is now the default way new smart home gear talks to Apple Home, Google Home, Amazon Alexa, Samsung SmartThings and Home Assistant, and the way it uses your network (IPv6, multicast discovery, border routers) is different from the cloud-connected gadgets most home networks were set up for. This page covers both standards as of October 2026.
What Matter is and who runs it
Matter started in December 2019 as Project Connected Home over IP, a joint effort by Amazon, Apple, Google and the Zigbee Alliance. The Zigbee Alliance renamed itself the Connectivity Standards Alliance (CSA) in 2021 and now maintains Matter, publishes the spec and runs certification. The reference SDK is open source under the Apache license and royalty-free; companies pay for CSA membership and certification.
The core ideas are simple. Devices talk to each other and to controllers over IP on your local network, so a Matter light switch can work with the internet down. Every device type is described by a shared data model (largely inherited from the Zigbee Cluster Library), so an on/off light from one brand looks the same as one from another. Security is built on device certificates: each certified product carries an attestation certificate that a controller checks during setup, which is how your phone knows the bulb is a real, certified product.
Matter versions
The CSA has settled into roughly two releases a year, each adding device types or fixing setup and network pain points.
| Version | Released | What it added |
|---|---|---|
| 1.0 | October 2022 | Lights, plugs, switches, locks, thermostats and HVAC, blinds, contact and motion sensors, TVs and media players, bridges |
| 1.1 | May 2023 | Fixes and SDK improvements; better support for battery-powered devices |
| 1.2 | October 2023 | Nine device types including fridges, dishwashers, washers, robot vacuums, room air conditioners, air purifiers, air quality sensors, fans, smoke and CO alarms |
| 1.3 | May 2024 | Energy and water reporting, EV chargers, ovens, cooktops, hoods, dryers, microwave ovens, scenes, casting improvements |
| 1.4 | November 2024 | Enhanced multi-admin, home routers and access points as device types, solar inverters, batteries, heat pumps, water heaters, long idle time for battery devices |
| 1.4.1 | May 2025 | Setup improvements, including NFC tags for onboarding and adding several devices at once |
| 1.4.2 | August 2025 | WiFi-only setup without Bluetooth, access restriction lists, vendor ID checks for multi-admin, Thread 1.4 required for border routers in Matter routers |
| 1.5 | November 2025 | Cameras and video doorbells, closures with modular motion (garage doors, gates, windows), soil moisture sensors, more energy management |
| 1.5.1 | March 2026 | Camera refinements: multiple simultaneous streams, more media formats, doorbell chimes and intercoms |
| 1.6 | June 2026 | NFC commissioning (setup before the device is powered), Joint Fabric for shared multi-ecosystem control, thermostat suggestions, more device status reporting |
Matter 1.6 also came with an update to the CSA’s product security requirements, aligned with the EU Cyber Resilience Act, that requires manufacturers to report actively exploited vulnerabilities within 24 hours from 11 September 2026.
A device’s Matter version matters less than you’d think. Controllers and devices negotiate features, so an old 1.0 plug works fine with a 1.6 hub; you just won’t get newer device types or setup methods until both sides support them.
Thread: the mesh underneath
Thread is a low-power mesh network maintained by the Thread Group, an industry body founded in 2014. It uses the same IEEE 802.15.4 radio as Zigbee, in the 2.4 GHz band, at 250 kbit/s. On top of that radio it carries real IPv6 packets, squeezed down with a compression layer called 6LoWPAN. That’s the key difference from Zigbee: every Thread device has an IPv6 address and can be reached like any other host once traffic gets onto the mesh.
Devices take on roles:
- Border router: connects the Thread mesh to your WiFi/Ethernet LAN. It routes IPv6 between the two and announces Thread devices on the LAN using mDNS (multicast DNS). Without one, a Thread network is an island.
- Router: a mains-powered device (a plug, a bulb, a wall switch) that relays traffic for others. A Thread network can have up to 32 active routers.
- Router-eligible end device: a powered device that can be promoted to router if the mesh needs more coverage.
- End device and sleepy end device: battery gear such as sensors and buttons. Sleepy devices wake briefly to check in with a parent router, which is how a door sensor lasts years on a coin cell.
The mesh repairs itself. If a router goes offline, devices pick another parent, and if one border router dies, another can take over, as long as they share the same network.
Thread versions
Thread 1.1 (2017) was the first widely certified release. Thread 1.2 (2019) added Bluetooth LE commissioning and backbone border routers. Thread 1.3 (2022) shipped alongside Matter 1.0 and added service discovery over the mesh. Thread 1.4 (September 2024) is the one that fixes the biggest home problem: credential sharing, which lets border routers from different brands join one shared Thread network instead of each ecosystem creating its own. It also added certificate-based commissioning, default internet connectivity for Thread devices (via NAT64 and DNS64) and better diagnostics.
Since 1 January 2026, new Thread border routers can only be certified against Thread 1.4. Matter 1.4.2 also made Thread 1.4 mandatory for border routers built into Matter-certified routers, along with support for at least 150 Thread devices.
WiFi vs Thread vs Ethernet devices
Matter gives a device three ways onto your network, and manufacturers pick based on power and bandwidth.
| Thread | WiFi | Ethernet | |
|---|---|---|---|
| Typical devices | Sensors, locks, buttons, bulbs, plugs, blinds | Cameras, doorbells, appliances, robot vacuums, some plugs | Hubs, bridges, TVs, controllers |
| Power | Battery for years, or mains | Mains (or rechargeable) | Mains or PoE |
| Bandwidth | Low (hundreds of kbit/s on the air) | High | High |
| Needs | A border router | Your WiFi, usually 2.4 GHz | A cable |
| Adds load to your WiFi | No | Yes, one client each | No |
The practical rule: anything on a battery or anything you want lots of goes on Thread. Anything moving video goes on WiFi. Every Thread device you add makes the mesh stronger if it’s mains-powered, while every WiFi device adds another client for your router to handle. A house with 60 smart devices on WiFi is a real load on a consumer router; the same 60 on Thread barely touch it.
Most WiFi smart home devices are still 2.4 GHz only, for range and cheap chips. That has knock-on effects for band steering and network naming, covered in why 5 GHz WiFi is faster but shorter-range than 2.4 GHz.
Multi-admin and fabrics
Multi-admin is Matter’s answer to the old lock-in problem. When you set up a device, the controller adds it to its fabric, a security domain defined by that ecosystem’s certificate authority. A device can belong to several fabrics at once, each with its own credentials, so the same lock can be controlled from Apple Home and Google Home with no cloud link between them. To add a second ecosystem, you open a pairing window from the first app and enter the code in the second.
Matter 1.4 simplified this so one consent can cover several ecosystems, and Matter 1.6 added Joint Fabric, where several controllers co-administer one shared fabric rather than each keeping its own copy of the home. Expect support to arrive in the big platforms over time; a spec release doesn’t mean your hub supports it yet.
Thread has a parallel issue. Before credential sharing, an Apple HomePod mini and a Google Nest Hub would each start their own Thread network, splitting your devices into separate meshes that couldn’t help each other. Thread 1.4 border routers can share one network. If your border routers predate 1.4, check for firmware updates before buying more Thread gear.
How Matter relates to Zigbee
Matter and Zigbee come from the same organization and share a lot of DNA. Matter’s device model grew out of Zigbee’s cluster library, and Thread uses the same 802.15.4 radio, so the same chip families often run either protocol.
They don’t interoperate directly, though. Zigbee is not IP-based and needs a hub. The bridge is the standard answer: a Zigbee hub such as the Philips Hue Bridge exposes its Zigbee lights as Matter devices, so they show up in any Matter controller. Z-Wave and Bluetooth mesh devices can be bridged the same way.
Zigbee itself isn’t going away. The CSA announced Zigbee 4.0 in November 2025, alongside Suzi, a sub-GHz version aimed at longer range in large buildings, utility metering and outdoor use, and opened Suzi product certification in September 2026. For whole-property range outside the 2.4 GHz band there is also WiFi’s own sub-GHz option, covered in HaLow (802.11ah) explained, though Matter has no HaLow transport.
Network planning tips
Matter is local and IP-based, so your network config matters more than it did with cloud-only gadgets.
Allow IPv6 on the LAN. You don’t need IPv6 from your ISP, but your router must not block local IPv6, link-local addresses or router advertisements. Border routers use router advertisements to tell your phone and hubs how to reach the Thread mesh. Some routers and firewalls filter these by default, which breaks Thread control in ways that look random.
Let multicast through. Matter discovery uses mDNS. Mesh WiFi systems with aggressive multicast filtering, or “client isolation” on the SSID, stop controllers from finding devices.
Be careful with IoT VLANs. Putting smart devices on a separate network is good practice, as why smart home devices should be on a separate WiFi network explains, but Matter controllers (your phone, HomePod, Nest Hub, Echo) need to reach devices by IPv6 and mDNS. Either keep controllers and border routers on the IoT segment, or run an mDNS reflector and allow the needed IPv6 traffic between segments. Test before you move everything.
Have two or more border routers. If your only border router is a speaker that gets unplugged, every Thread device goes dark. Two or three spread around the house, on Thread 1.4 firmware and ideally from the same ecosystem until credential sharing is common, gives the mesh redundancy.
Mind the 2.4 GHz overlap. Thread, Zigbee, Bluetooth and 2.4 GHz WiFi share the same band. Thread channels sit between WiFi channels in places, and the upper channels (25 and 26) fall above WiFi channel 11 in most regions. If you run a busy 2.4 GHz WiFi network on channel 11, a Thread mesh on a low channel will usually see less interference than one parked right under it. The same logic as planning WiFi channels in a dense building applies.
Spread mains-powered Thread devices. Plugs and bulbs are the routers of the mesh. A few in the right hallway do more for range than a better border router.
What to watch
Matter’s pace is now set by the platforms rather than the spec. Cameras arrived in the spec in late 2025, but what counts is when Apple, Google, Amazon and Samsung support them in their apps. The same goes for Joint Fabric and NFC setup from Matter 1.6. Thread 1.4 credential sharing is the other milestone: once every major ecosystem ships it in its border routers, the “one home, three Thread networks” problem goes away.
Headphones, trackers and many accessories still use Bluetooth, and Bluetooth LE is the radio most Matter devices use for setup; Bluetooth versions compared covers what each version added. For where WiFi itself is heading, including the Wi-Fi 8 draft, see the WiFi standards timeline.