Short answer: these three radios usually aren't rivals during setup. Bluetooth LE is often the short-range "hello" between phone and device, while Wi-Fi or Thread is where the device lives once it is set up. This guide explains each role, what infrastructure each one needs, and how to choose. Everything below reflects official documentation as of Oct 16, 2026.
Bluetooth LE vs Thread vs Wi-Fi: decision table
A simplified comparison, based on the official pages cited in this guide.
| Bluetooth LE | Wi-Fi | Thread | |
|---|---|---|---|
| Typical role in onboarding | Short-range link used during setup (Matter™ uses it for commissioning) | The home network the device joins and stays on | The low-power IPv6 network the device joins and stays on |
| Needs a hub or border router | No, it talks to a nearby device directly | No, it joins the existing home router | Yes, a Thread Border Router (Google's developer docs cover setting one up) |
| Basics, per the cited pages | 2.4 GHz ISM band, 40 channels | Interoperability backed by the Wi-Fi CERTIFIED program | IPv6-based, built on IEEE 802.15.4 |
| Power | Designed for very low power operation | Not characterized on the cited pages | Low energy footprint, per the Thread Group |
Table based on: Bluetooth SIG technology overview, Wi-Fi Alliance, Thread Group, Connectivity Standards Alliance, Google Home Developers, all as of Oct 16, 2026.
Q: Why do Wi-Fi devices use Bluetooth LE for setup?
A brand new Wi-Fi device does not yet know which home network to join or its password, so a setup flow can use a short-range Bluetooth LE link with the phone to pass those details across first; the Matter standard formalizes this, using Bluetooth Low Energy for commissioning while devices then run on Wi-Fi or Thread.
The Connectivity Standards Alliance says the first Matter release runs on Wi-Fi and Thread network layers and uses Bluetooth Low Energy for commissioning (Connectivity Standards Alliance, as of Oct 16, 2026). Bluetooth LE itself supports point-to-point, broadcast and mesh topologies, and the Bluetooth SIG describes the LE radio as designed for very low power operation (Bluetooth SIG, as of Oct 16, 2026).
Q: Thread vs Wi-Fi: which is better for battery devices?
For battery-powered devices, Thread is worth a close look: the Thread Group describes it as based on the power-efficient IEEE 802.15.4 radio and designed to extend the internet into low power end devices, while the Wi-Fi Alliance page cited here focuses on interoperability, security and reliability rather than power.
The trade-off is infrastructure: Thread setups involve a Thread Border Router, and Google's developer documentation describes how Android apps set up border routers and share Thread network credentials through Google Play services (Google Home Developers, as of Oct 16, 2026). The official pages cited here publish no battery life figures, so this guide does not quote any; your own measurements on your own hardware are the number that counts.
Onboarding flows step by step
These are generic flows, not any one vendor's implementation.
Wi-Fi device with Bluetooth LE setup
- The device powers on and advertises over Bluetooth LE.
- The companion app on the phone finds it and opens a short-range connection.
- The app passes the home network name and credentials to the device.
- The device joins Wi-Fi and checks in with its cloud or local controller.
- Bluetooth LE goes quiet, or stays available for recovery and re-setup.
Thread device
- The home needs a Thread Border Router on the network first.
- The device is brought into the Thread network, via a Bluetooth LE commissioning step when it is a Matter device.
- The device receives the Thread network credentials and joins the Thread network.
The Thread Group lists commissioning among the areas its certification program tests (Thread Group, as of Oct 16, 2026).
Bluetooth LE only device
- The device advertises over Bluetooth LE.
- The phone app connects directly.
- The device works while the phone is in range, with no home network involved.
Q: Do Thread devices need a hub?
Thread devices rely on a Thread Border Router rather than a classic proprietary hub: Google's developer documentation covers setting up Thread Border Routers and sharing Thread network credentials, and the Thread Group describes Thread as an open IPv6-based protocol for device-to-device and device-to-cloud connections.
That's based on Google Home Developers and the Thread Group, both as of Oct 16, 2026.
Q: Does Matter replace Bluetooth LE, Wi-Fi or Thread?
No, Matter sits on top of these technologies rather than replacing them: the Connectivity Standards Alliance describes the first Matter release as running on Wi-Fi and Thread network layers and using Bluetooth Low Energy for commissioning, so a Matter product built that way still relies on those radios underneath.
Google's developer docs also describe a Matter API that lets Android apps commission and share Matter devices using Google Play services (Google Home Developers, as of Oct 16, 2026).
Decision checklist
- Is the device battery powered? Thread was designed with low power end devices in mind. Devices on mains power have no battery to protect, so power draw weighs less in the choice.
- Does every target home have a Thread Border Router? If you can't count on one, a Thread-only product will need a plan for homes without it.
- Does the device need to work with nothing but a phone nearby? Bluetooth LE alone may be enough.
- Are you building for Matter? Then plan for Bluetooth LE in the setup flow and pick Wi-Fi or Thread for operation.
- What happens when setup fails? Decide how a user re-enters setup mode, and whether Bluetooth LE stays available for recovery.
- Who owns the credentials? On Android, Thread network credentials can be shared through Google Play services, so check how your app fits that flow.
What this means for your post-purchase app
Onboarding is the first experience a customer has with your product after the box is open. Which radio carries setup decides how many steps the app has to explain and how many things can go wrong. A Bluetooth LE handshake followed by a Wi-Fi or Thread join is two steps, and each one needs its own clear error message. Copilot.cx's Setup Engine is the part of our platform built around this stage of the customer journey.
FAQ
Why do Wi-Fi devices use Bluetooth LE for setup?
A brand new Wi-Fi device does not yet know which home network to join or its password, so a setup flow can use a short-range Bluetooth LE link with the phone to pass those details across first; the Matter standard formalizes this, using Bluetooth Low Energy for commissioning while devices then run on Wi-Fi or Thread.
Thread vs Wi-Fi: which is better for battery devices?
For battery-powered devices, Thread is worth a close look: the Thread Group describes it as based on the power-efficient IEEE 802.15.4 radio and designed to extend the internet into low power end devices, while the Wi-Fi Alliance page cited here focuses on interoperability, security and reliability rather than power.
Do Thread devices need a hub?
Thread devices rely on a Thread Border Router rather than a classic proprietary hub: Google's developer documentation covers setting up Thread Border Routers and sharing Thread network credentials, and the Thread Group describes Thread as an open IPv6-based protocol for device-to-device and device-to-cloud connections.
Does Matter replace Bluetooth LE, Wi-Fi or Thread?
No, Matter sits on top of these technologies rather than replacing them: the Connectivity Standards Alliance describes the first Matter release as running on Wi-Fi and Thread network layers and using Bluetooth Low Energy for commissioning, so a Matter product built that way still relies on those radios underneath.