Matter and Thread explained: what Canadian smart home buyers actually need

Matter is the language, Thread is a road

The two names show up together on boxes so often that people treat them as one thing, and that causes a lot of confusion. Home Assistant's documentation describes Matter as an application-layer control protocol. It defines how a light switch, plug or sensor describes itself and accepts commands, and it runs over existing IP networks instead of bringing its own radio. The Connectivity Standards Alliance, which runs Matter, says the standard was built with its member companies, drawing on technology from Amazon, Apple and Google among others. It says the first release ran over Wi-Fi and Thread and used Bluetooth Low Energy for setup. Home Assistant dates version 1.0 to October 2022.

Thread is the network underneath. Home Assistant's Thread documentation calls it a low-power mesh standard built on the same IEEE 802.15.4 radio technology as Zigbee, but carrying IPv6 so every device has a real network address. On its own, Thread doesn't control anything. Matter, or Apple's HomeKit, does that on top of it. The Thread Group describes the protocol as open and IPv6-based, with security built into the network layer. That combination suits battery sensors and mains-powered plugs that only need to send small amounts of data.

The practical upshot is that a Matter device might use Wi-Fi, Ethernet or Thread. Home Assistant also warns that the reverse doesn't hold: a device with a Thread radio isn't automatically a Matter device. Look for the Matter logo, and Google's Matter help page suggests also checking for the Wi-Fi or Thread logo on the box or product page.

Controllers, hubs and border routers

Two pieces of hardware do the heavy lifting. A Matter controller is the app or hub that pairs and runs your devices. A Thread border router connects the Thread mesh to the rest of your home network. Home Assistant's documentation explains that a border router just forwards packets and doesn't control devices. It also notes that one Thread network can have several border routers, which extends coverage and removes a single point of failure.

Chances are you already own one. Apple's Canadian support page on Matter lists Apple TV 4K, HomePod (2nd generation) and HomePod mini as Thread border routers. It says an iPhone running iOS 18 or later can add and control Matter accessories without a home hub, though Apple still recommends one, and that hub-free control of Thread accessories needs an iPhone 15 Pro or later. Google's help page names the Google Home Speaker (2026), Nest Hub (2nd gen), Nest Hub Max, Nest Wifi Pro and Google TV Streamer as hubs with Thread border routers built in. It lists other Nest speakers and displays as Wi-Fi-only Matter hubs. Amazon's developer documentation lists Thread border routers across several Echo and eero models, including Echo Hub and Echo (4th Gen), and says Matter-compatible Echo devices support a subset of device types up to Matter 1.5.

Hubs from other brands do this too. The Aqara hub covered at Aqara Hub M3 review lists Zigbee 3.0 and Thread radios and documents Matter controller and bridge roles. The Home Assistant box at Home Assistant Green review is the opposite case. It has no built-in Thread radio, so Matter-over-Thread devices need a separate border router on the network.

Multi-admin: one device, several apps

One of Matter's most useful features is that a single device can belong to more than one ecosystem at once. Home Assistant calls each of these connections a fabric and says the standard expects devices to support at least five. That means a plug can answer to Apple Home for a family member on an iPhone and to Google Home for someone on Android, with nobody needing a separate brand app.

Apple's support page explains how to add an accessory that's already paired somewhere else: pick the 'More options' path in the Home app, or follow the other platform's instructions for adding a previously paired accessory. Home Assistant has an equivalent 'already in use' flow in its companion app, along with a screen for viewing and removing fabrics. Keep the Matter setup code for every device somewhere safe. You'll need it whenever you reset a device or move it to another ecosystem.

The catch: separate Thread networks

If you run more than one ecosystem, this is the part most likely to trip you up. Home Assistant's Thread documentation says each vendor usually forms its own Thread network, so one house can end up with separate Apple, Google and Home Assistant meshes. They use different credentials, so devices can't move between them. A Home Assistant community thread from September 2023 shows how this plays out: an owner with Home Assistant's own Thread radio and a Google Nest Hub on two different networks asked how to merge them. The replies offered suggestions such as matching channels, but no confirmed fix.

Thread 1.4 is meant to fix this. Bitdefender's September 2025 summary describes a credential-sharing feature that lets a border router grant temporary admin access, so new routers and phones join the existing network instead of starting their own. It reported that Apple was adding Thread 1.4 in tvOS 26 while Google, Amazon and Samsung were at various stages of rollout. It also said Thread 1.4 becomes the only border router certification after January 1, 2026. Until your own devices actually support it, it's simpler to pick one main ecosystem to commission Thread devices through.

Network settings that quietly break Matter

Google's help page warns that IPv6 has to be enabled on your home Wi-Fi. Without it, setup can appear to work and then control fails later. Home Assistant's documentation adds that Matter depends on IPv6 and mDNS, and that features like VLANs, multicast filtering and IGMP snooping can break device discovery. Its Thread page notes that some mesh Wi-Fi systems filter the multicast traffic border routers rely on. If you've tightened up your router settings or put smart devices on a separate network, check these first.

Matter can also do less than a brand's own integration. Home Assistant points out that its native Philips Hue integration offers more features than Hue over Matter. The notes at Philips Hue Bridge Pro review make a related point: sharing Hue lights to another platform through Matter doesn't turn the bridge into a universal controller.

Buying Matter devices in Canada

None of the Apple, Google, Amazon or Home Assistant documentation used here sets Canada-specific rules for Matter. The Canadian check is mostly about hardware. Buy the North American electrical version of plugs and switches. The Eve plug covered at Eve Energy (Matter, US/Canada) review is sold as a US and Canada model rated for 120 V and 15 A, and it needs both a Matter controller and a Thread border router. Also check whether your platform supports the device category, not just the Matter badge. Google's page says Matter 1.2 added categories such as appliances, robot vacuums, smoke and CO alarms, air purifiers and garage door openers, and it directs you to its developer list to confirm what's supported.

Winter adds one more reason to build a Thread mesh carefully. The CSA lists local connectivity among Matter's goals, and Home Assistant notes that an IPv6 internet connection isn't required. So, in principle, a home whose router, controller and border routers stay powered can keep local automations going when the internet goes down in a storm. How well that works depends on your platform and on whether those boxes are on backup power.

From a tech standpoint

Buy Matter for choice and Thread for low-power reliability, and remember they're separate decisions. Start with the border router you probably already own, commission Thread devices through one main ecosystem, and use multi-admin to share them out. Before you blame a device, check that IPv6 and multicast are working on your network.