Matter, Thread, Wi-Fi, and Zigbee are not four versions of the same thing. They solve different layers of the smart-home problem, and confusing them is one of the easiest ways to buy hardware that needs an unexpected hub, loses features in your preferred app, or becomes awkward to expand later.
This guide explains the practical difference, what you actually need in the house, and the checks to make before buying.
The short version
| Technology | What it does | What you may need | Best fit |
|---|---|---|---|
| Matter | A common smart-home application standard for compatible devices and ecosystems | A Matter controller; some devices also need Wi-Fi or a Thread border router | Cross-platform compatibility |
| Thread | A low-power IPv6 mesh network | A Thread border router to connect the Thread mesh to the home IP network | Low-power sensors, locks, lights and similar devices |
| Wi-Fi | Your normal IP wireless network | A Wi-Fi router | Devices that need more bandwidth or already have mains power |
| Zigbee | A mature low-power mesh technology with its own device ecosystem | Usually a compatible hub/coordinator or bridge | Large existing ecosystems and mature low-power device ranges |
Matter is the compatibility layer, not the radio
Matter is designed so compatible smart-home products can expose standardized functions to certified ecosystems. A Matter device can communicate over technologies such as Wi-Fi, Ethernet, or Thread. The Connectivity Standards Alliance describes Matter as an interoperability standard that runs over underlying transports rather than replacing them.
That distinction matters when shopping. A box can say Matter while the device itself connects over Wi-Fi. Another Matter product may be Matter over Thread, which changes what infrastructure you need at home.
The current specification is Matter 1.6, released by the Connectivity Standards Alliance in June 2026. It focuses on better commissioning, stronger multi-ecosystem management, and richer standardized device-state behavior. As always, a specification release does not mean every ecosystem or product immediately supports every new feature; manufacturers and platforms adopt new capabilities on their own timelines.
Thread is a network, not an app ecosystem
Thread is an IPv6-based, low-power mesh network. Thread devices can communicate across the mesh, and mains-powered Thread devices can help extend it. A Thread border router connects that low-power Thread network to the rest of your IP home network.
The border-router role can be built into equipment you may already own. Depending on model and software support, examples include HomePod or Apple TV models, Google Nest/Google Home devices, and selected Echo or eero hardware. The exact model matters, so never assume every speaker, streamer, or router in a product family includes Thread.
A useful mental model is:
- Matter controller: manages Matter devices for an ecosystem.
- Thread border router: connects Thread devices to the wider IP network.
Those roles are different, even though one physical device may perform both.
What “Matter over Thread” means
If a product says Matter over Thread, it uses the Matter application standard and Thread for networking. To set it up reliably in a typical smart-home ecosystem, you need the ecosystem’s Matter support plus a compatible Thread border router.
For example, Apple states that Thread-based Matter accessories require a Thread-enabled home hub or compatible third-party Thread border router. Google likewise states that Matter devices using Thread require a Thread border router for setup in Google Home. Amazon maintains its own list of Echo and eero models with built-in Thread border-router capability.
Where Wi-Fi fits
Matter over Wi-Fi uses the home Wi-Fi network instead of Thread. That can be convenient because most homes already have Wi-Fi coverage, and devices do not need a Thread border router. It is common for mains-powered products and devices that benefit from higher bandwidth.
But “uses Wi-Fi” does not automatically mean “works with every smart-home app.” Before Matter, many Wi-Fi products depended heavily on a manufacturer cloud and proprietary integration. Even with Matter, check the exact feature set available in the ecosystem you plan to use.
Where Zigbee still fits
Zigbee is not obsolete just because Matter exists. It remains widely used for low-power lighting, sensors, switches, and mature hub-based ecosystems. In many installations, Zigbee devices connect to a dedicated hub or coordinator, and that hub can expose selected devices to other platforms.
A Matter bridge can make supported non-Matter devices behind the bridge visible to Matter ecosystems. That is useful for preserving an existing installation. It does not necessarily turn every bridged device into a native Matter device with identical capabilities in every platform.
Can Apple Home, Google Home, and Alexa control the same Matter device?
Matter was built for multi-ecosystem use. Its Multi-Admin model allows a compatible device to be shared with more than one certified ecosystem. Google documents using Matter devices across applications such as Google Home, Apple Home, and Amazon Alexa, and Matter 1.6 expands standardized options for multi-ecosystem administration.
That does not guarantee that every feature looks identical everywhere. A device may expose its core standardized functions broadly while advanced manufacturer-specific settings remain in the brand’s own app.
The buying checklist that prevents most compatibility mistakes
- Choose your primary ecosystem first. Decide whether Apple Home, Google Home, Alexa, Home Assistant, SmartThings, or another system will be your main control layer.
- Check the exact device, not just the brand. Confirm the product and model supports the ecosystem and functions you need.
- Identify the transport. Is it Matter over Thread, Matter over Wi-Fi, Zigbee, or a proprietary/cloud integration?
- If it uses Thread, verify your border router. Check the specific model number of the HomePod, Apple TV, Nest, Google Home, Echo, eero, or other device you expect to perform that role.
- Check whether a hub is mandatory. Zigbee and proprietary ecosystems often depend on one. Some hubs add useful local automation even when they are not strictly required.
- Check local versus cloud behavior. Ask what still works if the internet is down.
- Check subscription requirements. Cameras, security systems, cloud storage, AI features, and history often have recurring costs.
- Check firmware support. A device that stops receiving security or compatibility updates can become the weakest part of the system.
- Preserve the setup code. Keep Matter QR/setup codes in a secure place for future resets or ecosystem changes.
A sensible default for a new smart home
For a new installation, favor products with clear standards support and a strong update policy rather than buying solely by price. Use Thread where its low-power mesh design makes sense, Wi-Fi where bandwidth or device design calls for it, and keep good existing Zigbee gear when a reliable hub already gives you the automation you need.
The goal is not to make every device use the same radio. The goal is to make the system predictable: one primary control layer, known network requirements, documented fallback behavior, and as few unnecessary clouds and bridges as practical.
Primary sources and further reading
- Connectivity Standards Alliance — Matter 1.6
- Connectivity Standards Alliance — Matter FAQ
- Thread Group — Thread networks and border routers
- Google Home — Matter setup and requirements
- Apple Support — home hubs and Matter
- Amazon Alexa — Matter and Thread support
Editorial note: this article explains standards and platform requirements from primary documentation. It does not claim hands-on testing of every device or ecosystem combination.