Matter over Wi-Fi vs Thread

Same Matter on both networks

Matter is the same on both networks. The Connectivity Standards Alliance built Matter on Internet Protocol and specified Wi-Fi and Thread as its network layers, with Bluetooth Low Energy for commissioning. Pairing, device types and controllers are shared. The only difference is which network the device sits on once it is set up.[1]

Both kinds of device use Bluetooth during setup. Home Assistant describes the controller sending the network credentials to the new device over Bluetooth. After that the device runs on its normal network. Bluetooth does not control the device. It only pairs a new or factory-reset device.[2]

The network does not change who can control the device. Home Assistant states that Matter products run locally and always allow local control. One device can join several controllers at once, because each should support at least five fabrics simultaneously. So a Wi-Fi plug and a Thread sensor can both sit in HomeKit, Google Home and Home Assistant together.[2]

What Matter over Wi-Fi needs

A Wi-Fi Matter device joins Wi-Fi like a laptop or phone, so the only extra piece is a Matter controller. Google calls that a Matter-enabled hub. SmartThings says Matter devices must connect to a compatible hub, either stand-alone or built into recent Samsung TVs, Smart Monitors and Family Hub refrigerators. With Home Assistant, Home Assistant is the controller.[2][4][5]

More devices act as controllers for Wi-Fi devices than as border routers for Thread. Google lists speakers such as the Nest Audio and Nest Mini as hubs for Matter over Wi-Fi. Only some Google devices also include a Thread border router: the Nest Hub (2nd gen), Nest Hub Max, Nest Wifi Pro and Google TV Streamer (4K). On Google Home, IPv6 must be on before Matter devices are added. Without it, control can fail later even when setup appears to succeed.[4]

Google's own thermostat shows the split. Google lists Wi-Fi only for the Nest Learning Thermostat (4th gen), and it connects to Matter over Wi-Fi, so it needs no border router, even though Google sells several.[6]

What Matter over Thread needs

Thread is a low-power mesh network for IoT devices. The Thread Group describes it as an IPv6 mesh that is low-power and low-latency, can self-heal and has no single point of failure. Home Assistant notes that the low-power design suits battery devices and that the low bandwidth limits it to devices that send little data. Door and window sensors, motion sensors, buttons, switches and locks fit that description.[3][7]

A Thread device cannot reach a phone or controller on its own. A Thread border router connects the Thread network to Wi-Fi or Ethernet. Home Assistant's network map shows the difference: Wi-Fi devices connect through an access point, Thread devices through a border router.[2][8]

In return, Thread devices help each other. Google describes them relaying information through mesh extenders, and a home can have more than one extender, so the network keeps working if one goes offline. Thread can also use several border routers in one network to improve coverage.[3][9]

Every platform states the requirement. Apple says Thread accessories need a Thread-enabled home hub such as an Apple TV 4K or HomePod. From iOS 18, a Thread-enabled iPhone can pair them locally, and an iPhone 15 Pro or later can control them without a hub. Philips Hue says its Matter-enabled bulbs need a Thread border router, and names the HomePod mini and Google Nest Hub as examples.[10][11]

Separate Thread networks

Thread networks from different companies do not merge on their own. The Thread Group says border routers that share credentials form one mesh and those that do not form separate meshes, and that devices on separate meshes can still reach each other over IPv6. Home Assistant states that each vendor forms its own Thread network when a household starts using its products. To commission a Thread device into Home Assistant, the phone also needs the credentials of the Thread network the device will join.[2][3][12]

Wi-Fi devices do not have this split, because they all share the router's network. Thread adds a self-extending mesh for battery devices and one more piece of infrastructure, the border router. Border routers from one platform keep the devices on one network.[3][12]

Device counts

The index holds 3243 devices. Of those, 148 end devices list a Matter over Thread path and 453 list Matter over Wi-Fi. Hubs and border routers that run Thread themselves are left out of those counts and of the first table.[2][8]

Bridged Matter is a third route, shown in the second table for comparison. A vendor hub exposes the devices connected to it to Matter, so those devices need neither Wi-Fi nor Thread of their own. Philips Hue says its Bridge has been updated to support Matter so that Hue lights and accessories automatically support it too. Home Assistant notes that a bridge keeps the devices available through the vendor's own app.[2][11]

Where each network is used

• Battery sensors, buttons and remotes: Thread, when a product comes in both versions. The low-power mesh is designed for devices that sleep and send little data.[3]
• Plugs, fans, appliances and thermostats: Wi-Fi. These are mains-powered, need no border router, and work with any Matter controller. On Google Home, IPv6 must be enabled first.[2][4]
• Locks: Thread's low-power design suits a battery lock. With a second border router, a lock stays reachable if the first goes offline.[3]
• Homes without a border router: a HomePod mini, an Apple TV 4K or a Nest Hub (2nd gen) may already route Thread for its platform.[9][10]
• Wi-Fi and Thread devices can sit side by side under one controller, and multi-admin lets the same device appear in more than one platform.[2]