Loading...

IoT Chipsets Explained: Why One Chip Now Speaks Four Protocols

Smart Utilities

Published by IOT San Jose Research & Editorial Team

IoT Chipsets Explained: Why One Chip Now Speaks Four Protocols

Ask an engineer in 2020 what chipset to use for a new smart lock and the answer depended entirely on which smart home ecosystem the product needed to support, Zigbee for one retailer's platform, a proprietary protocol for another, Bluetooth for a third, often requiring separate radio hardware for each. Ask the same question in 2026 and the answer increasingly involves a single chip that speaks Bluetooth Low Energy, Thread, Zigbee, and Matter simultaneously, switching between them as needed rather than committing a product to one ecosystem at the hardware level. That shift, from single-protocol chips to multi-protocol wireless system-on-chips, is arguably the single biggest change in what an IoT chipset actually is over the past several years, and it is worth understanding on its own terms rather than as a footnote to the smart home interoperability story everyone already knows about.

What a Chipset Actually Bundles Together

The term chipset gets used loosely, but for IoT hardware it specifically refers to the combination of a processor core, wireless radio, and supporting peripherals integrated into a single piece of silicon, as opposed to a design that uses separate chips for compute and connectivity wired together on a board. This integration matters because it directly determines a device's cost, size, and power consumption, three variables that matter enormously for any IoT product built at meaningful volume. A wireless system-on-chip built around an Arm Cortex-M33 core, for example, combines general-purpose processing with a radio and often dedicated security hardware in one package, letting a manufacturer build a complete connected sensor or smart home device around a single core component rather than assembling separate compute and radio chips.

What has changed substantially in 2026 is how many distinct wireless protocols a single chipset can now support simultaneously. Modern multiprotocol wireless system-on-chips support Bluetooth Low Energy, Bluetooth mesh, Zigbee, Thread, and Matter all on the same silicon, with software determining which protocol a given device uses at any moment rather than the protocol being fixed at the hardware level the way it typically was in earlier chip generations.

A Concrete Comparison: Then and Now

The practical difference this makes is easiest to see by comparing two versions of the same hypothetical product built five years apart. A smart lock designed in 2020 targeting broad smart home compatibility might have needed a Zigbee radio chip for one retail partner's ecosystem, a separate Bluetooth chip for direct-to-phone setup, and possibly a third proprietary radio for a specific platform integration, each requiring its own antenna design, certification process, and firmware stack, and each adding cost and board space to the final product. A comparable smart lock designed in 2026 can achieve broader compatibility with a single multiprotocol chipset supporting Bluetooth for commissioning, Thread for the underlying mesh network, and Matter as the application layer that lets the lock work across Apple Home, Google Home, Amazon Alexa, and Samsung SmartThings without vendor-specific hub requirements. The bill of materials shrinks, the board design simplifies, and the certification burden, while not eliminated, concentrates around fewer physical radio designs even as the effective compatibility of the finished product expands.

Why Matter Made Multi-Protocol Chipsets Nearly Mandatory

The Matter standard, maintained by the Connectivity Standards Alliance and now at version 1.6 as of mid-2026, does not use a single wireless technology. It runs over Thread, Wi-Fi, or Ethernet for its core transport, while requiring Bluetooth Low Energy for device commissioning regardless of which transport the device ultimately uses day to day. That requirement alone means any chip built to support Matter certification needs at minimum both a Bluetooth radio and a Thread-capable radio, or a Wi-Fi radio for Matter over Wi-Fi devices, on the same piece of silicon, which is precisely the multi-protocol architecture chipmakers have converged on rather than each vendor building separate single-purpose radios.

This has downstream effects on how South Bay smart building and smart home hardware companies design new products. A team building a Matter-certified sensor for a commercial building automation platform no longer needs to choose between a Thread-based mesh architecture and a simpler Bluetooth-only design at the hardware level, since a single multi-protocol chipset can support both, with the final protocol decision made in firmware rather than locked in during board design. That flexibility reduces the risk of betting on the wrong protocol during a product's initial design phase, a real cost in earlier IoT hardware generations when choosing Zigbee over a competing mesh protocol could mean redesigning the entire radio subsystem if the market shifted.

Thread itself has continued evolving alongside this chipset consolidation. As of January 2026, new Thread border routers can only be certified against Thread 1.4, with the earlier Thread 1.3 specification no longer accepted for new certifications, extending the protocol toward larger commercial and industrial deployments rather than remaining confined to residential smart home use. That evolution matters for South Bay smart building projects specifically, since a multiprotocol chipset purchased today needs to support the current certification baseline, not an older protocol version that may already be approaching end of life for new product certifications.

The Edge AI Layer Increasingly Bundled Into the Same Chip

The newest generation of multiprotocol wireless chipsets is adding a further layer beyond connectivity: on-chip AI acceleration. Some current-generation wireless system-on-chips now integrate a dedicated neural processing unit alongside the radio and application processor, enabling hardware-accelerated edge AI inference, simple gesture or presence detection, anomaly detection in sensor data, directly on the same chip handling Bluetooth, Thread, Zigbee, and Matter connectivity. This convergence, connectivity and inference on one piece of silicon, reflects the same underlying industry trend covered in more depth elsewhere on this site regarding edge AI hardware, but applied specifically to the connectivity chipset layer rather than a separate dedicated AI accelerator.

Implementation Advice for Choosing an IoT Chipset in 2026

  1. Default to multi-protocol unless there is a specific reason not to. The cost premium for a multi-protocol chipset over a single-protocol equivalent has narrowed considerably, while the flexibility it provides against future protocol requirements is difficult to replicate after a product has already shipped.
  2. Evaluate Matter certification requirements early, since the Bluetooth-for-commissioning requirement applies regardless of a device's primary transport, meaning even a Wi-Fi-based product needs Bluetooth radio capability to achieve Matter certification.
  3. Treat on-chip AI acceleration as increasingly standard for new designs, evaluating whether a chipset's integrated NPU capability, even a modest one, can eliminate the need for a separate AI accelerator chip in simpler edge inference use cases.
  4. Confirm software and SDK maturity, not just hardware specifications, since a chipset's practical usability depends heavily on the quality of its software development kit and how well-documented its multi-protocol switching actually is in production firmware.

Common Challenges in Multi-Protocol Chipset Selection

ChallengeDescription
Firmware complexitySupporting multiple protocols on one chip shifts complexity from hardware design into firmware, requiring more sophisticated software development
Radio coexistence and interferenceRunning multiple wireless protocols on shared radio hardware requires careful management to avoid performance degradation
Certification overhead across protocolsA product supporting Bluetooth, Thread, and Matter may need separate certification processes for each, even on unified silicon
Component and lead time constraintsMulti-protocol chipsets are still subject to the same mature-node and analog supply constraints affecting the broader IoT chip market

That last point connects directly to the mature-node semiconductor capacity constraints covered elsewhere, since the analog and RF components inside these multi-protocol chipsets are manufactured using the same constrained mature-node processes affecting IoT components broadly, meaning a more capable chipset does not necessarily mean an easier sourcing experience.

What's Next for IoT Chipset Design

As Matter continues expanding its device category coverage, its June 2026 version 1.6 release adding features like NFC-based commissioning and joint fabric support, expect chipset vendors to keep folding additional protocol support and on-chip intelligence into single-die designs rather than adding separate chips for each new capability. For hardware teams evaluating chipsets today, the practical lesson is that the old model of picking a protocol first and a chip second has largely inverted: the chip increasingly comes first, supporting whichever protocol combination the product needs, with the specific protocol decision deferred as late in the design process as the firmware, rather than the printed circuit board, will allow.

Frequently asked questions

For IoT hardware, a chipset refers to the combination of a processor core, wireless radio, and supporting peripherals integrated into a single piece of silicon, as opposed to separate chips for compute and connectivity wired together on a circuit board.

The Matter standard requires Bluetooth Low Energy for device commissioning regardless of whether a device's primary transport is Thread, Wi-Fi, or Ethernet, meaning any chip built for Matter certification needs at least two radio types on the same silicon, which pushed the industry toward multi-protocol chipset architecture.

Current multiprotocol wireless system-on-chips can support Bluetooth Low Energy, Bluetooth mesh, Zigbee, Thread, and Matter all on the same silicon, with software determining which protocol a device uses rather than the protocol being fixed at the hardware level.

Yes. Some current-generation wireless system-on-chips integrate a dedicated neural processing unit alongside the radio and application processor, enabling hardware-accelerated edge AI inference for tasks like gesture or presence detection directly on the same connectivity chip.

No. Multi-protocol chipsets are still manufactured using the same mature-node semiconductor processes facing capacity constraints across the broader IoT chip market, so a more capable chipset does not necessarily mean an easier sourcing experience.

Firmware complexity increases significantly, since supporting multiple wireless protocols on shared radio hardware shifts much of the design complexity from hardware selection into software development and requires careful management of radio coexistence and interference.

Related articles

Top