Request a firmware review
Menu

Matter over Thread or Wi-Fi: choosing the transport for a new device

Reader question: Should our new smart home device use Matter over Thread or Matter over Wi-Fi, and what certification work and cost does each path add?

Micrograph-style illustration of the skeleton of a leaf showing its mesh of fine veins, with a few vein junctions tinted amber.

Choose Matter over Thread for battery-powered devices that send small, infrequent messages, and Matter over Wi-Fi for mains-powered devices, devices that move a lot of data, and buyers who may not own a Thread border router. Both paths need the same Connectivity Standards Alliance (CSA) Matter certification, and each adds its own transport certification: Thread Group certification (often inherited from your chip vendor’s certified component) or Wi-Fi Alliance certification (often a QuickTrack or derivative path built on a certified module). If you commission over Bluetooth LE, as the Matter SDK’s reference platforms do, add Bluetooth SIG qualification; the fees for all of these are published by each body and linked below, checked November 2026.

This article is for founders and firmware leads choosing the radio for a new smart home product. It compares the two transports on power, border-router dependency, commissioning, firmware size and updates, then walks through each certification program step by step. It names no prices: membership and test fees change, so each section links to the body’s own fee page.

How Thread and Wi-Fi differ once Matter sits on top

Matter is an application layer that runs over IP, so the same device types, clusters and security model work on either transport; what changes is the radio underneath, how the device sleeps, and what else the home needs. The Matter SDK README describes Matter as “built with market-proven technologies using Internet Protocol (IP)” and “compatible with Thread and Wi-Fi network transports”.

Thread, per the OpenThread primer, is “an IPv6-based networking protocol designed for low-power Internet of Things devices in an IEEE 802.15.4-2006 wireless mesh network”. IEEE describes 802.15.4 as a standard for low-rate wireless networks with “low-data-rate wireless connectivity” for devices with limited energy. Wi-Fi is the home’s existing 802.11 network, with far more bandwidth; what it costs a device in energy to stay connected is the question the power section below takes up.

Question Matter over Thread Matter over Wi-Fi
Radio IEEE 802.15.4, low data rate 802.11 (Wi-Fi 4, 5, 6 and later)
Topology Mesh; mains-powered devices can forward for others Star around the home’s access point
Reaching the internet or a phone app Through a Thread border router Directly through the home router
Sleeping devices Sleepy end devices poll a parent Station must stay associated; Wi-Fi 6 adds target wake time
Bulk data (video, large images) Poor fit Good fit
Commissioning Bluetooth LE, or on-network Bluetooth LE, or on-network
Extra certification Thread Group Wi-Fi Alliance

Most of the decision follows from three of those rows: whether the device runs on a battery, how much data it moves, and whether your buyers have a border router. The sections below take each one in turn, then turn to firmware and certification.

Moves video or large files? yes Wi-Fi no Runs on a battery? no Either works Thread adds mesh yes Thread border router in buyers' homes? no Ship a router or Wi-Fi, rare wakes yes Thread, sleepy end device
Figure 1. A first-pass transport decision for a new Matter device. Decision rules from this article, based on OpenThread, Wi-Fi Alliance and CSA documentation checked November 2026; measure your own hardware before committing.

What stays the same on both transports

A good deal of the work does not depend on the radio. The device types, the clusters that describe what a device can do, the commissioning flow, the security model and the update mechanism are all defined by Matter, not by Thread or Wi-Fi. The CSA describes Matter as supporting “30+ device types” and lists “Authenticated onboarding, encrypted communication, and standardized security mechanisms” as part of its design.

For a firmware team, that means the application layer (the code that turns a detected leak into a reported state, or a button press into an on or off command) can be written once and carried across transports. What does not carry across is everything below it: the radio, the network stack, the power management, the board and the certification evidence. Moving a product from Thread to Wi-Fi is therefore a new board and a new certification round, not a configuration change, which is why the decision belongs before the first engineering prototype boards are ordered.

Which transport a battery-powered device can afford

For a battery-powered sensor, Thread is usually the better fit, because a Thread sleepy end device can turn its radio off and wake only to poll its parent. Wi-Fi can work on a battery only if the device sleeps for long periods and reconnects rarely, or if both the device and the home’s access point support Wi-Fi 6 target wake time.

How a Thread device sleeps

The OpenThread node roles page splits Thread nodes into Mesh Extenders, which forward packets, keep “transceiver enabled at all times” and provide commissioning services, and End Devices, which talk to a single parent and “can disable its transceiver to reduce power”. Among end devices, a Sleepy End Device (SED) is “normally disabled, wakes on occasion to poll for messages from its parent”. A Full Thread Device always has its radio on, so mains-powered products such as plugs and light bulbs are the ones that extend the mesh.

Matter adds its own layer on top. The Matter SDK documents Intermittently Connected Devices (ICDs), configured through the ICD Management cluster, with a Short Idle Time (SIT) mode and a Long Idle Time (LIT) mode. LIT devices add a Check-In Protocol, so registered controllers hear from the device when it wakes, and a User Active Mode Trigger, so a user can be told how to wake it on demand; the SDK’s Texas Instruments ICD guide shows the build flags and the idle, active and polling parameters a firmware team tunes.

How a Wi-Fi device saves power

A Wi-Fi station that wants to stay reachable must stay associated with the access point and wake regularly to hear it. The Wi-Fi Alliance lists target wake time (TWT) among the Wi-Fi 6 features and says it “significantly improves network efficiency and device battery life”. TWT only helps when the home’s access point supports it too, and you do not choose your buyers’ routers.

Decision rules for power

  • Battery-powered, small events, must stay reachable (leak sensor, contact sensor, button): Thread, as a sleepy end device configured as a Matter ICD.
  • Battery-powered, wakes rarely, may be offline between reports: Wi-Fi is possible if reconnecting costs less energy than staying associated; measure it on your hardware before deciding.
  • Mains-powered: either transport works. A mains-powered Thread device also strengthens the mesh for every sleepy device near it.

Measure both before you decide

When the rules above leave the answer open, measure. The comparison that matters is average current over a realistic day, and the two transports spend energy in different places, so measure the right events on each.

  1. Build two test firmwares on the chip vendor’s development kits: one as a Thread sleepy end device with your intended poll interval, one as a Wi-Fi station with your intended reporting pattern.
  2. On Thread, capture the sleep current between polls, the charge used by one poll of the parent, and the charge used by one report to a controller.
  3. On Wi-Fi, capture the sleep current while associated, the charge used to stay associated over an hour with your router, and the charge used by a full reconnect if the device drops off the network between reports.
  4. Run each for at least a day in a real home network, not on a bench next to the access point, because retries and weak links dominate the totals.
  5. Combine the measured charges with your event rate to get an average current for each design, and compare against your battery-life target.

The method for capturing sleep and event currents without fooling yourself is in measuring sleep current. Then estimate battery life from those measured currents, not from datasheet figures. The battery life calculator does the arithmetic, and why battery life comes in shorter than the estimate covers the effects a simple estimate misses, such as cold cells and pulse loads.

The border router question

A Thread device cannot reach a phone, a cloud service or a Wi-Fi controller without a Thread border router in the home. That dependency is a strong commercial argument for Wi-Fi, and you have to decide up front whether you will rely on your buyers’ border routers, ship one, or avoid the question with Wi-Fi.

The OpenThread border router guide states it plainly: “A Thread network requires a Border Router to connect to other networks.” A border router minimally provides bidirectional IP connectivity between Thread and Wi-Fi or Ethernet, service discovery across the two (mDNS on Wi-Fi or Ethernet, SRP on Thread), merging of Thread partitions over IP links, and external commissioning, for example from a phone. A Thread network can have more than one border router.

Matter ecosystems are broad: the CSA’s Matter page lists Apple Home, Google Home, Amazon Alexa, Samsung SmartThings and Home Assistant as places Matter is deployed, as of November 2026. Whether a given buyer’s home has a working Thread border router depends on which hubs, speakers or routers they own. Your product page, packaging and setup flow must say what is required, and your support team must be ready for “it will not pair” calls from homes without one.

The three practical answers:

  1. Require a border router. State it on the box and in the app, and test commissioning with each major ecosystem’s border routers before launch.
  2. Ship a border router. You take on a Linux or co-processor product of your own, with its own updates, certification and support. OpenThread’s border router uses a radio co-processor (RCP) design, where the host runs OpenThread and the 802.15.4 chip handles only the lower radio layers.
  3. Use Wi-Fi. Every home with a router can connect the device, at the cost of power and of depending on the buyer’s Wi-Fi quality.

What your firmware should do when the border router goes away

Border routers get unplugged, rebooted for updates and replaced. Your Thread device has to behave sensibly when that happens, and this is firmware work that is easy to skip until field units start draining their batteries.

  • Keep local operation working. The Thread mesh itself does not need the border router to carry traffic between its own nodes. Design the device so that a missing border router costs remote access and reporting, not its local function, such as a leak sensor’s buzzer or a plug’s physical button.
  • Back off instead of hammering. A sleepy device that retries a failed report every few seconds keeps its radio busy far more often than its battery budget assumed. Use increasing retry intervals with a cap, and queue reports instead of resending them.
  • Recover without user action. When a border router returns, the device should resume reporting without a reset or re-pairing. Test this explicitly by power-cycling the border router during a soak test.
  • Record what happened. Count border-router losses and failed reports in a diagnostics counter, so a support call or a crash report can tell a network problem from a device fault.

These behaviors belong in the test plan for Thread products alongside commissioning and update tests, and they are worth running in the same automated rig.

Commissioning, device identity and the factory

Both transports commission the same way: a controller, usually a phone app, finds the device, checks that it is a certified Matter product, and gives it network credentials and an operational identity. In the Matter SDK’s reference platforms that first contact runs over Bluetooth LE for Thread and Wi-Fi devices alike, which is why Bluetooth qualification appears on both certification paths.

The SDK’s nRF Connect platform overview is a typical example: the Bluetooth LE interface “is used to perform pairing and Thread or Wi-Fi network provisioning operations between the Matter device and the Matter controller”, after which the device talks over Thread or Wi-Fi. Devices already on the IP network can also be commissioned on-network, and the CSA’s Matter page mentions NFC tap-to-pair and multi-device setup as newer onboarding options.

Device attestation

Matter checks that a device is certified during commissioning. Silicon Labs’ certification guide puts it bluntly: “non-certified Matter devices are prevented from commissioning into Matter networks”. Its device attestation page describes the chain each production device carries:

  • a Device Attestation Certificate (DAC), unique to each device, with its private key, installed in the factory;
  • a Product Attestation Intermediate (PAI) certificate that signed the DAC;
  • a Certification Declaration (CD), issued by the CSA after certification, listing your Vendor ID and Product IDs.

The PAI chains to a Product Attestation Authority (PAA) whose root certificate sits on the CSA’s Distributed Compliance Ledger, a signed, distributed database that is open for reading and requires authorized accounts for writing. The CSA lists Product Attestation Authorities, including some that offer their public key infrastructure as a service to other members, so a startup does not have to run its own certificate authority.

This identity work is the same on Thread and Wi-Fi, and it has to be planned with your contract manufacturer. Unique keys and certificates per unit are the subject of factory provisioning of device identity; budget for it before the first production run, not after certification.

Firmware size and over-the-air updates on each transport

A Matter device carries the Matter stack, a network stack (OpenThread or a Wi-Fi driver and supplicant), a Bluetooth LE stack for commissioning, a cryptography library and a bootloader with room for a second image. A Thread device can fit all of this on one wireless SoC with an 802.15.4 and Bluetooth LE radio; a Wi-Fi device either uses a Wi-Fi SoC or pairs a microcontroller with a Wi-Fi companion chip.

The SDK’s nRF Connect overview shows both shapes. For Thread, OpenThread runs with an IEEE 802.15.4 radio driver, and a multiprotocol service layer “allows running Bluetooth LE concurrently with other stacks on the same radio chip”. For Wi-Fi, the application processor runs a Wi-Fi driver and supplicant and talks to an nRF7002 companion chip, “compliant with IEEE 802.11ax (Wi-Fi 6)”, over SPI or QSPI. The second shape adds a part, a bus and a second firmware image to track.

Updating Matter devices in the field

Matter defines its own update mechanism. The SDK’s nRF Connect update guide describes two node roles: an OTA Provider, which answers queries about available updates and serves images, and an OTA Requestor, the device being updated. The OTA Provider example notes that “All Matter software images must contain a header as defined in section 11.21.1 of the specification” and that the image transfer runs over BDX, the transfer protocol whose poll interval the provider lets you set. The same guide lists Bluetooth LE updates over the Simple Management Protocol as an alternative, noting that “this protocol is not part of the Matter specification”.

Under either transport, the device still needs what any field-updatable product needs: a bootloader that verifies signatures, two image slots or an equivalent recovery path, and a tested rollback. The transport changes how long a download takes and how much it costs in energy:

  • Thread. Images cross a low-data-rate radio, and a sleepy end device only receives data when it polls its parent. Plan to switch the device into an active mode with faster polling for the duration of the transfer, and accept longer download times.
  • Wi-Fi. Downloads are fast, but a battery device spends energy staying connected while the image arrives.

Size the flash for the whole set: Matter, network and Bluetooth stacks, two image slots and storage. The flash budget calculator checks whether the layout fits with growth room, and A/B versus single-slot updates covers the trade-offs if two full slots do not fit. Updates delivered to a phone over Bluetooth have their own speed limits, covered in faster Bluetooth LE firmware updates.

Choosing a Matter SDK release and planning its updates

The open-source Matter SDK moves quickly, and your firmware will carry one release of it for a long time. As of November 2026, the releases page lists v1.4.0.0 (December 11, 2024), v1.5.0.0 (November 17, 2025), v1.6.0.0 (August 20, 2026) and v1.6.1.0 (September 25, 2026) among its tagged releases. Those are SDK versions; the specification has its own numbering, published by the CSA through its specification download page.

In practice you will not take the SDK straight from GitHub. Chip vendors integrate a Matter SDK release into their own SDKs, with their radio drivers, certified Thread or Bluetooth libraries and production samples, and that combination is what carries their inheritance evidence. The SDK’s own examples say as much: the nRF Connect LIT ICD example notes that it “is intended only to perform smoke tests” and that “It is not recommended to use this example as a basis for creating a market ready product.”

Three planning points follow:

  • Pin the vendor SDK release you certify with, and record it in the release notes and the SBOM for every build.
  • Plan a schedule for SDK updates after launch. Fixes you need after launch will usually be in a newer release than the one you shipped, and moving to it means retesting, and possibly recertifying, against the same programs.
  • Keep the update path proven. A Matter device that cannot take a firmware update in the field cannot take a security fix either, so test the full OTA cycle, including rollback, on every release candidate.

A sustaining releases arrangement is one way to keep that SDK and security schedule running after the first product ships.

The certification path for each transport

Every Matter product needs CSA Matter certification, and the CSA expects proof that the device’s network transports are certified before it accepts the Matter application. So a Thread device goes through the CSA and the Thread Group, a Wi-Fi device through the CSA and the Wi-Fi Alliance, and either one through the Bluetooth SIG if it uses Bluetooth LE.

CSA Matter certification

The CSA’s certification page sets the frame: certification “is available to Connectivity Standards Alliance members”; “All new product certifications require product testing at a Connectivity Standards Alliance Authorized Test Provider, followed by an application”; and issued certifications “remain valid for the lifetime of the product”. Silicon Labs’ guide breaks the flow into steps that match what a startup will actually do:

  1. Join the CSA. The CSA’s membership page describes Adopter members as able to “certify products through Alliance certification programs”; Silicon Labs names Adopter as the minimum level for certifying your own product.
  2. Get a Vendor ID from the CSA and choose a 16-bit Product ID for each product.
  3. Finish the product and its transport, and pre-test with the Matter Test Harness.
  4. Obtain transport certification: Thread Group, Wi-Fi Alliance and Bluetooth SIG as applicable. The CSA accepts certification by inheritance where it applies.
  5. Test at an Authorized Test Provider (the CSA keeps a list of testing providers), unless your product qualifies for a no-test path.
  6. Apply through the CSA’s certification tool, with the PICS (Protocol Implementation Conformance Statement), a declaration of conformity, a network transport attestation and a security attestation.
  7. Receive the certificate, the Certification Declaration, logo rights and a record on the Distributed Compliance Ledger.

Silicon Labs also lists paths that avoid repeat testing: product family certification for variants of a tested parent, certification by similarity for a very similar certified product (the CSA decides whether it applies), and the Certification Transfer Program for products relabeled from another member.

Thread Group certification

The Thread Group’s certification page offers two routes. “For many types of Thread end products using Thread Certified Components, it is possible to skip testing and directly inherit the component certification”, with special requirements set by your silicon vendor; for inheritance, the member “submits evidence to Thread Group of inclusion of the claimed certified component device and Thread stack library in the end product”. Otherwise the product is tested at a Thread Authorized Test Lab. Either way you join the Thread Group, apply, are reviewed and are certified.

The evidence is specific. Silicon Labs asks for linker output proving that the build uses its certified OpenThread libraries, and notes that a product using a host and radio co-processor (RCP) architecture “will need to go through OpenThread Certification on its own”. Ask your chip vendor for its inheritance rules before you change the Thread stack or its build options.

Wi-Fi Alliance certification

The Wi-Fi Alliance offers three paths. FlexTrack is full testing at an Authorized Test Laboratory for highly customized products. QuickTrack certifies products “based on Qualified Solutions”, meaning modules and chipsets already tested, and allows targeted changes, with testing on site or at a lab. The derivative path certifies products using identical Wi-Fi designs with “No additional testing”. A company “must be a Wi-Fi Alliance member” to certify and use the Wi-Fi CERTIFIED marks.

Bluetooth SIG qualification

The Bluetooth SIG’s qualification page says “ALL Bluetooth Products must be qualified” and that “Your supplier or other member companies cannot qualify your products on your behalf.” A product qualification fee applies to the first product that includes a specific design, and later products with the same design are not charged. Using a module or a vendor’s qualified design reduces testing, per Silicon Labs, when “the design and functionality is unaltered”.

ProgramThread deviceWi-Fi deviceWays to avoid full testingMembership needed
CSA Matter certificationRequiredRequiredProduct family, certification by similarity, transfer programYes, Adopter or above for your own product
Thread Group certificationRequiredNot applicableInherit from a Thread Certified Component, with vendor evidenceYes
Wi-Fi Alliance certificationNot applicableRequiredQuickTrack on a qualified solution; derivative for identical designsYes
Bluetooth SIG qualificationIf BLE is used, as for commissioningIf BLE is used, as for commissioningReuse an unaltered qualified design; no fee for later products with the same designYes, under your own account
Radio regulatory approvalRequired per marketRequired per marketPre-certified modules can reduce the work; see the RF test firmware articleNot applicable
Figure 2. Certification programs each transport adds. Sources: CSA certification and membership pages, Thread Group certification page, Wi-Fi Alliance how-to-certify page, Bluetooth SIG qualification page and Silicon Labs Matter 2.9.2 certification guide, all checked November 2026.

What certification costs, and where the fees are published

Certification cost is a mix of membership and application fees, lab time and your own engineering time, and the biggest lever is whether each program is tested or inherited, not which transport you pick. We do not quote fees here because each body revises them; read them at the source on the day you budget.

Body What you pay for Where the current numbers are
Connectivity Standards Alliance Annual membership; per-product certification fee by membership level; lab testing quoted by the test provider CSA membership levels and fees; the CSA says testing quotes come from the test provider
Thread Group Membership; product certification fees Thread Group membership benefits table, fees at the bottom
Wi-Fi Alliance Membership; certification by path Wi-Fi Alliance membership overview
Bluetooth SIG Membership; product qualification fee for each new design Bluetooth SIG fee schedule
Test labs Matter, Thread, Wi-Fi and Bluetooth testing, plus retests Quotes from each lab

All links checked November 2026. The CSA states that “The primary costs associated with product certification are the testing fee and the application fee”, and that you should “contact an Authorized Test Provider for testing fee quotes”.

Four cost drivers matter more than the transport:

  • Inheritance. A Thread product that inherits a certified component, or a Wi-Fi product on QuickTrack or the derivative path, skips most transport testing.
  • Retests. Silicon Labs warns that if a lab needs new firmware to fix an issue, “they may need to rerun more than just the failed test”. Pre-testing with the Matter Test Harness is the cheapest insurance.
  • Product count. Fees are per product, so variants should go through family or similarity paths where the CSA accepts them.
  • Changes to certified stacks. Changing the Thread stack, the Bluetooth design or the Wi-Fi solution can break an inheritance claim. Check with the vendor before you change build options in those layers.

To turn this into a budget line, work product by product:

  1. List the programs each product needs, using Figure 2.
  2. Read the membership and per-product fees from each body’s page on the day you budget, and write the date next to each number.
  3. Ask two or three test labs for quotes that cover Matter testing, Thread or Wi-Fi testing where you cannot inherit, Bluetooth testing if needed, and their retest rates.
  4. Add your own engineering time for pre-testing with the Matter Test Harness and for fixing what it finds.
  5. Decide early which variants will go through product family or similarity paths, and confirm with the CSA that they qualify before you plan around them.

How to test a Matter device before it goes to the lab

Lab testing is quoted by the test provider and retests add to it, so arrive with a device that has already passed the same tests on your bench. Both transports need a commissioning controller, a test harness and interoperability checks; Thread adds a border router to the bench.

The bench setup for each transport

The Matter SDK’s own procedures show the minimum bench. Its nRF Connect update guide starts from an OpenThread Border Router “set up either in Docker or on a Raspberry Pi”, uses the SDK’s chip-tool to commission devices (pairing ble-thread for a Thread device, pairing onnetwork for one already on the IP network), and runs an OTA Provider application on Linux to serve test images. A Wi-Fi device needs the same controller and provider, plus an access point you control.

A workable bench for a startup is small:

Item Thread device Wi-Fi device
Commissioning controller chip-tool on a Linux machine chip-tool on a Linux machine
Network OpenThread Border Router on a single-board computer, with an 802.15.4 radio An access point you can configure, including Wi-Fi 6 settings if you rely on target wake time
Update server OTA Provider application OTA Provider application
Power measurement A source-measure unit or power analyzer on the device’s supply The same
Ecosystem controllers The phones and hubs your buyers use The same

Pre-testing and interoperability

Silicon Labs recommends pre-testing with the Matter Test Harness before sending a product to an authorized lab, because “Testing is expensive” and a firmware change during lab testing can force reruns of tests that had already passed. Run the harness against each release candidate, not only before the first submission.

Certification does not prove that your device behaves well in each ecosystem’s app. The CSA runs an Interoperability Testing Facility where members can submit products for testing “against all ecosystem participants”, and hosts plug fests. Whether or not you use it, test commissioning, control, update and recovery with every ecosystem you name on the box.

Automate the repeatable parts: commissioning, a control loop, an OTA update and rollback, and a border-router power cycle can all run unattended in a hardware-in-the-loop rig. Firmware testing with CI and hardware in the loop covers when such a rig pays for itself.

Regulatory approvals that sit beside Matter

Matter, Thread, Wi-Fi and Bluetooth certifications show conformance to a specification and interoperability. They are not legal approvals to sell a radio product. Each market’s radio rules apply on top, on both transports, and test firmware for the radio lab is part of the work; what test firmware the RF lab needs covers that side.

In the EU, certain categories of radio equipment have had cybersecurity requirements since the RED delegated regulation (EU) 2022/30 “entered into application in August 2025”, per the Commission’s Radio Equipment Directive page. The same page says its repeal “will be effective as of 11 December 2027”, when the Cyber Resilience Act takes over. Matter’s security model helps, but it does not by itself show conformity; the details are in RED cybersecurity and EN 18031. This is a summary as of November 2026, not legal advice.

A worked example: one startup, three products

Transport choice is per product, not per company. The fictional example below shows how the rules above sort a small product line.

Example (fictional). Fennel Home, a two-year-old Denver startup, plans three Matter products: a battery water-leak sensor, a plug-in smart outlet and a video doorbell. Its firmware lead applies the rules in this article.

Product Power Data Transport chosen Certification route
Leak sensor Two AA cells A few bytes per event Thread, as a sleepy end device and Matter ICD CSA testing; Thread by inheritance from the SoC vendor; Bluetooth qualified under Fennel’s own account, reusing the vendor’s qualified design
Smart outlet Mains Small Thread, so it also extends the mesh for the leak sensors Same SoC and stack as the sensor, so the Thread and Bluetooth evidence is reused
Video doorbell Mains Video Wi-Fi CSA testing; Wi-Fi QuickTrack on a certified module; Bluetooth qualified under Fennel’s own account for commissioning

The leak sensor’s box states that a Thread border router is required, and the app checks for one before setup starts. The team budgets two firmware update paths: Matter OTA over Thread for the sensor and outlet, with the sensor switched to faster polling during a download, and Matter OTA over Wi-Fi for the doorbell. Because the outlet uses the same SoC and Thread stack as the sensor, its build options are frozen with the sensor’s, so the inheritance evidence stays valid for both.

A checklist before you commit to a transport

Make the transport decision with the certification plan and the update plan in hand, because changing radios after EVT costs a board spin and a new round of certification. Work through these questions with your hardware lead and your chip vendor.

  1. Power. Is the device battery-powered? If yes, can it reach your battery-life target as a Thread sleepy end device, and have you measured it?
  2. Data. Does it move video, audio or large files? If yes, plan for Wi-Fi.
  3. Border router. For Thread, will you require one, ship one, or accept that some homes cannot use the product?
  4. Silicon. Does your chip vendor offer a Thread Certified Component or a Wi-Fi qualified solution, and what evidence does inheritance need?
  5. Bluetooth. Will you commission over Bluetooth LE, and can you reuse a qualified design unaltered?
  6. Identity. Who will issue your device attestation certificates, and how will your contract manufacturer install them?
  7. Updates. Does the flash layout hold two images plus the Matter, network and Bluetooth stacks with growth room, and how long will an update take on this transport?
  8. Memberships and fees. Which memberships do you need (CSA, plus the Thread Group or Wi-Fi Alliance, plus the Bluetooth SIG), and what are the current fees on each body’s page?
  9. Regulation. Which radio approvals and cybersecurity rules apply in each market you will sell in?
  10. Schedule. Have you left time for pre-testing, lab testing, retests and the CSA application review?

Fumbar is a Denver company that writes embedded firmware and over-the-air update systems for hardware startups, including Thread, Matter, Wi-Fi and Bluetooth LE firmware. Our connectivity services and the connected consumer products page describe how we work on this kind of device, and over-the-air update work covers the bootloader and release side. If you want the transport, flash layout and certification plan checked before you commit, request a firmware review.

Facing this decision on a real device?

If this article describes a choice in front of you, a firmware review puts it in writing for your board, your code and your update plan.

Request a firmware review

Or email sales@fumbar.com, or call (720) 675-4202.