Matter and Thread: what hardware you need

Matter promises one smart home standard, and Thread adds a second word you have to look up. Before you order another hub, check the drawer and the shelf: you may already own the missing box.

The short answer

Matter and Thread: what hardware do you need? Three roles, not three boxes. You need a Matter controller, which is the speaker, display, TV box or Home Assistant that sets devices up and controls them. You need a Thread border router only if you own devices that use Thread; Matter devices on Wi-Fi or Ethernet do not need one [9][10]. And you need a bridge only if older Zigbee or DECT devices should show up in Matter [9][18]. Many controllers already contain a border router, and the manufacturer lists below (retrieved 25 Oct 2026) name several speakers, displays, TV boxes and routers. Our assessment: write down the devices you own, mark which roles they already cover, and buy only for the gaps.

How it works

1. What Matter is. Matter is a standard from the Connectivity Standards Alliance (CSA). Its core specification describes an interoperable application layer for smart home devices over the Internet Protocol [2]. Home Assistant explains what that means: Matter has no radio of its own, and its devices talk IPv6 over your existing network (Wi-Fi or Ethernet) or over Thread [9]. Control stays local and needs no cloud, although some vendors ask for an account before they enable Matter on their own hubs [9]. The CSA download page lists Matter 1.6.1 as the newest specification on 25 Oct 2026 [1]. Treat the version number as a label, not a buying criterion: the CSA says that makers and ecosystems implement new features on their own timelines [4], so the packaging and the manufacturer page tell you which device types a product supports.
2. What Thread is. Thread is a low-power mesh network for smart home devices. It uses the same radio technology as Zigbee (IEEE 802.15.4) but gives every device an IPv6 address, so it behaves like part of your network [10]. Thread alone controls nothing: a higher protocol such as Matter or Apple HomeKit does that [10]. That is why a Thread logo on the box does not promise Matter. Home Assistant warns that some Thread devices speak HomeKit or a vendor protocol, and a few need a (beta) firmware update before Matter works; look for the Matter logo itself [9]. The "Built on Thread: requires border router" logo means that Thread is the only way the device connects, with no Wi-Fi fallback [10].
3. The roles. There are four: device, controller, Thread border router and bridge. The list "The four roles" below the numbered list describes each one.
4. Which devices contain a border router. The manufacturers publish their own lists. These are examples that we copied from their pages on 25 Oct 2026, not a ranking, and we have not tested any of these devices. The table "Border routers named by the makers" below the numbered list shows the examples, with three cautions.
5. One Thread network, not five. The Thread Group describes the problem that Thread 1.4 addresses. Adding a new border router without the stored credentials would form an entirely new network, and splitting devices over several networks can weaken the mesh [5]. Thread 1.4 adds credentials sharing, so a new border router or device can join the existing network instead [5][7]. Thread 1.3 had already standardised border router basics such as bidirectional IP connectivity and service discovery [6]. For routers, Matter 1.4 introduced certifiable Home Routers and Access Points that combine a Wi-Fi access point with a Thread border router and keep a directory of Thread credentials [3]. Whether your own router or speaker supports any of this is a question for its documentation. Home Assistant adds that Google and Apple set up their border routers through their own ecosystems and that Home Assistant itself can configure only OpenThread border routers that offer the REST API [10]. The Thread page in Home Assistant lists the Thread networks it finds in your home [10].
6. FRITZ!Box: bridge, not border router. FRITZ! describes its Matter integration as a bridge: the FRITZ!Box 5690 Pro or the FRITZ!Smart Gateway carries FRITZ! Smart Home devices into an existing Matter network, and the controller stays Alexa, Apple Home or Google Home [18]. The retailer tink, which also sells Matter devices under its own brand, wrote on 22 Oct 2026 that by its own research no FRITZ! device works as a Thread border router and that Thread devices therefore need a border router elsewhere [19]. That is third-party information with a date. We read nothing on the FRITZ! page that contradicts it, and we make no statement about future firmware.
7. Home Assistant and your network. The official Matter Server app on Home Assistant OS is the only supported installation; a container image exists but comes without official support [9]. The Matter Server documentation adds a network rule that surprises people with segmented networks: Matter uses link-local multicast, which does not cross LANs or VLANs, so server, devices, border routers and the phone used for commissioning should share one (v)LAN. The host needs IPv6, multicast optimisations should be off, and mDNS forwarders should not be enabled; IGMP/MLD snooping can help or hurt [12]. If you separated your smart home devices into their own VLAN, plan this before you buy. The Home Assistant documentation (25 Oct 2026) also notes that Matter updates for Thread devices currently fail behind Apple border routers, because they do not forward the mDNS packets that Home Assistant needs [9].
8. Zigbee devices you already own. Home Assistant is a Matter controller, not a bridge, and it cannot turn existing devices into Matter devices [9]. Your Zigbee sensors keep working through the Zigbee integration of Home Assistant. A bridge is worth it when another app or ecosystem should see them; for Philips Hue, Home Assistant even says that the native integration offers more features than Matter does [9]. The Connect ZBT-2 runs either Zigbee or Thread, and you have to choose one for each adapter [11]. The maker's recommended price on 25 Oct 2026 is 49 USD or 45 EUR; retailers set their own prices [11].

The four roles

• Device. The lamp, plug, sensor or lock. It joins over Wi-Fi, Ethernet or Thread.
• Controller. The place where you add devices and automate them. Home Assistant names Google Nest products, Apple HomePod speakers, the Samsung SmartThings Station and newer Amazon Echo devices as examples, besides Home Assistant itself [9]. FRITZ! describes controllers the same way: hubs for all smart home devices in the network, often built into a smart speaker, and the choice decides which platform and app you use [18]. Each controller has its own Matter network, called a fabric. Multi-admin lets one device join several controllers, and Home Assistant states that the standard expects a device to support at least five fabrics [9]. Matter 1.4 added Enhanced Multi-Admin and Matter 1.6 added Joint Fabric, two ways to share devices between ecosystems [3][4].
• Thread border router. It joins the Thread mesh to your Wi-Fi or Ethernet network. The OpenThread documentation lists its minimum functions: bidirectional IP connectivity, service discovery through mDNS and SRP, merging Thread partitions over IP links and external commissioning, for example from a phone [8]. According to Home Assistant, it only forwards packets without looking at their content and does not control devices [10]. The data between your controller and a Matter device stays encrypted, and the border router only passes it on [9]. One Thread network can have several border routers, which widens coverage and removes a single point of failure [10].
• Bridge. It makes devices visible in Matter whose radio standard does not carry IP, for example DECT ULE, HAN FUN or Zigbee [18]. Home Assistant gives SwitchBot Hub 2, Aqara Hub M2, IKEA Dirigera and the Philips Hue Bridge as examples of Matter bridges [9].

Border routers named by the makers (examples, 25 Oct 2026)

Read the lists with three cautions. First, not every smart speaker is a border router: Google's help page puts Nest Audio, Nest Mini and Google Home Mini in the group that supports Matter over Wi-Fi only [15]. Second, lists change with every product and update, so open the maker's page again on the day you buy. Third, if an Apple TV is connected by Ethernet and pairing fails, Apple's troubleshooting page suggests connecting it to the same Wi-Fi network as your phone [14].

Decision order

1. Pick one controller platform for your automations: Apple Home, Google Home, Alexa, Home Assistant or another.
2. List your devices and sort them: Matter over Wi-Fi or Ethernet, Matter over Thread, Zigbee or DECT.
3. No Thread devices on the list: you need no border router.
4. Thread devices on the list: check the maker lists above against what you own. Buy a border router only if none of your devices is on a list.
5. Zigbee or DECT devices: keep them native, or add a bridge only if you want them in another ecosystem.
6. Network: put controller, border routers, devices and phone in the same (v)LAN while you set up, and keep multicast filters and mDNS forwarders off.
7. Add one device first and look at the Thread page or the network map in Home Assistant before you buy more.

A scenario, not our data

Imagine a Home Assistant on a mini PC, a handful of Zigbee sensors and two new Thread door sensors that carry the Matter logo. Home Assistant is the controller. The door sensors need a border router. If an Apple TV 4K (3rd generation, Wi-Fi + Ethernet) already hangs on the TV, Apple's own list covers that role [14], and you buy nothing. If nothing on the lists is in the house, a Connect ZBT-2 could become the Thread border router [10][11], but then that adapter no longer serves the Zigbee sensors, so a second adapter or an existing border router has to take one of the two jobs. Decision: use what the house contains, and buy last. We have not built this setup for this article; the logic follows the documentation.

Checklist

• Write down every smart home device and mark Wi-Fi, Ethernet, Thread, Zigbee or DECT.
• Look for the Matter logo itself on every Thread device, not only the Thread logo.
• Check the maker lists for border routers you already own before you buy one [13][15][17].
• Choose one controller and add one device first.
• Keep controller, border router, devices and phone in one (v)LAN during setup [12].
• Switch off multicast optimisation and mDNS forwarding in your network gear [12].
• Dedicate a ZBT-2 to either Zigbee or Thread, not both [11].
• Re-read the maker's page on the day you buy, because lists and firmware change.

Related pages: Home Assistant hardware, VLANs at home, Zero trust. Our assessment: a separate network for IoT devices improves isolation and costs convenience. Plan the segment boundary before you buy Matter hardware, because Matter needs controller and devices to see each other by multicast.