Matter and Thread: what each one actually does

Matter and Thread get named in the same breath so often that they are taken for one thing. They sit at different layers. The Connectivity Standards Alliance describes Matter as "a unifying, IP-based connectivity protocol built on proven technologies": it is what a lamp and a controller say to each other, and what a lamp is allowed to be. Thread carries the sentence. The Thread Group describes Thread as an "Open IPv6 based protocol" that is "Based on the power-efficient IEEE 802.15.4 MAC/PHY". A Matter accessory can run over Wi-Fi and never touch Thread. A Thread accessory can carry traffic that is not Matter at all.

That split decides what hardware a house needs. The Alliance states that Matter "will run on Wi-Fi and Thread network layers and will use Bluetooth Low Energy for commissioning". Wi-Fi and Ethernet accessories reach the router that is already in the hallway. Thread accessories cannot, because 802.15.4 is a different radio, so something has to sit between the two networks. That something is a border router. As at 18 September 2026 the Alliance's specification download page lists Matter 1.4, 1.4.1, 1.4.2, 1.5, 1.5.1 and 1.6, each as a set of core, application cluster, device library and standard namespace documents. The reference implementation reached v1.5.0.0 on 17 November 2025 and v1.6.0.0 on 20 August 2026.

Where each protocol sits

Thread is the network. OpenThread's primer calls it "An IPv6-based networking protocol designed for low-power Internet of Things devices in an IEEE 802.15.4-2006 wireless mesh network", with "Self-healing mesh networking, with no single point of failure" and with all devices authenticated and all communications encrypted. It moves IPv6 packets between low-power nodes. It has no opinion about what a thermostat is.

Matter is the vocabulary above that. It defines device types and the clusters they expose, how a device is commissioned onto a fabric, and how controllers address it over IP. It has no radio of its own. This is why the two questions people ask at the shop counter have different answers. Whether an accessory will appear in a given app is a Matter question. Whether it will reach the house network at all is a Thread question.

What a border router does

OpenThread sets out the minimum a border router must provide:

• Bidirectional IP connectivity between Thread and Wi-Fi or Ethernet networks.
• Bidirectional DNS-based service discovery, using mDNS on the Wi-Fi or Ethernet link and SRP on the Thread network.
• Thread-over-infrastructure, which merges Thread partitions over IP-based links.
• External Thread commissioning, so that a phone can authenticate a device and join it to the network.

More than one is allowed. The Thread Group notes that adding border routers to the same network makes the mesh stronger and further reaching. Because the accessory holds an IPv6 address of its own, the border router's work stops at forwarding and discovery. It is not a translation gateway in the way an older bridge was.

Which accessories need one

So a Matter plug on Wi-Fi works with nothing new in the house. A Matter contact sensor on Thread does not, unless a border router is already present. Buyers regularly miss this because both carry the same certification mark.

The border routers people already own

Most households that have one bought it for another reason. Amazon publishes a list by Thread version. Echo (4th Gen) sits at Thread 1.1. Thread 1.3 covers Echo Hub, Echo Plus (2nd Gen), Echo Show 21, Echo Show 15 (2nd Gen), Echo Show 11, Echo Show 10 (3rd Gen), Echo Show 8 (3rd Gen), Echo Dot Max, Echo Studio, and the current eero range: eero 6, eero 6+, eero 7, eero Beacon, eero Outdoor 7, eero Max 7, eero Pro, eero Pro 6, eero Pro 6E, eero Pro 7 and the two eero PoE models.

Apple lists "Thread networking technology" in the specifications for HomePod mini and for Apple TV 4K, with one trap: on Apple TV 4K it appears only under the Wi-Fi plus Ethernet model, not the Wi-Fi only model. Both Apple pages add that the feature is "Compatible with HomeKit- or Matter-enabled Thread accessories only". Apple does not publish the Thread version on either specification page, so a household mixing an Apple and an Amazon border router cannot compare the two from the manufacturers' own material.

Google's own border routers are documented mainly through the developer side. Google Play services holds Thread network credentials for Google Thread Border Routers, and the Thread Network SDK lets an app call getPreferredCredentials or getCredentialsByBorderAgent rather than handling credentials itself. From version 16.0.0 that SDK supports Android 8.0 and above.

The mesh limits are published

Thread scales to hundreds of devices, but the ceilings are specific. OpenThread's documentation puts a maximum of 32 active routers on a network, with up to 511 children each. Current OpenThread wording calls a router a Mesh Extender, and a battery accessory that keeps its radio off most of the time a Sleepy End Device, which wakes to poll its parent.

Vendors narrow that further. Google's documentation states that the maximum sleep period for Thread Sleepy End Devices is three seconds, and that longer cycles may cause devices to appear offline in the Google ecosystem. A sensor designed for a longer poll interval will pass certification and still look dead in one app.

What works across ecosystems today

The honest test of interoperability is the device type list a controller publishes. Google Home's covers lights and switched plugs, thermostats, fans and air purifiers, door locks, smoke and carbon monoxide detectors, window coverings, dishwashers, laundry washers, robot vacuum cleaners, doorbells and chimes, pumps, electric meters, and a set of sensors covering temperature, humidity, occupancy, contact, illuminance, pressure, flow and air quality. The specification keeps adding to that pool. The Alliance's own account of Matter 1.5, published 20 November 2025, lists cameras, a unified closures type covering window shades, awnings, gates and garage doors, energy-tariff and grid-carbon-intensity reporting, and soil sensors. Matter 1.6, announced 17 June 2026, added full commissioning over NFC, so a device can be paired before it is powered on, and Joint Fabric, which lets more than one ecosystem co-administer a single Matter network.

What it still does not do

Controllers trail the specification, and say so. Amazon states that "Matter-compatible Echo devices support the Matter 1.5 Software Development Kit (SDK), enabling support for a subset of Matter 1.5 and lower device types", while the Alliance is already publishing 1.6. A device type in the specification is not a device type in the app.

Platform policy overrides the standard in places. In the Google ecosystem, a Matter door lock that does not mandate a PIN code cannot be opened remotely or by voice, whatever the lock supports. A Matter On/Off Light Switch cannot be bound to another device inside the Google Home app. Google does not expose the Matter Binding cluster to its controllers. A manufacturer that wants the switch to operate a lamp has to build its own Matter administrator, which Google's documentation calls a director, and create the binding outside Google Home entirely. Anything a maker offers beyond the standard device types stays in that maker's own app as well.

Thread versions also differ inside one home. An Echo (4th Gen) at Thread 1.1 and an eero at Thread 1.3 both act as border routers, and each will form or join a Thread network. Thread 1.4 addresses that directly with credential sharing, alongside Thread over infrastructure, network diagnostics, commissioning at scale and direct cloud connectivity, and the Thread Group states it is fully backward compatible with earlier versions. Whether a given box has taken it is a firmware question, answered by the manufacturer and not by the certification mark.

Before buying a Thread accessory, check the exact model of the hub or router in the house against that vendor's current border-router list, not against the brand. Apple TV 4K is the clearest warning: the same product name covers a model with Thread and a model without.