Silicon Labs and Matter in 2026: What the Chip Maker Changes for Your House

This post may contain affiliate links. As an Amazon Associate we earn from qualifying purchases. Disclosure.

Most smart home news is about the thing on the shelf. This story is about the part inside it. Silicon Labs doesn't sell you a lock, a bulb or a hub, yet its radios sit under a surprising share of the Zigbee and Thread gear a Home Assistant owner touches, including the Connect sticks and Yellow board covered in our Yellow vs Green vs DIY comparison. So when the company had a busy summer, it was worth reading what it actually said.

I'll be plain about my vantage point. I haven't flashed any of this SDK or run a 200-node mesh, and my own house uses a Connect ZBT-1 stick on Zigbee firmware. What follows comes from reading the press releases and the three Matter release notes line by line, then asking one question of each item: does it change what I'd buy or how I'd set things up?

What Did Silicon Labs Announce for Matter in 2026?

Four things matter, and they're easy to blur together.

• June 16: a 200-node Matter-over-Thread validation network, presented at the CSA's first Unify event.
• June 23: a collaboration with Signify to put Zigbee and Matter-over-Thread on the same Philips Hue bulbs.
• June 25 and August 3: Matter SDK releases 2.9.0-1.6 and 2.9.1-1.6, aligned with Matter 1.6.
• Background noise: Texas Instruments' agreement to buy the company for about $7.5 billion, still pending.

The first three are engineering news. The fourth is corporate news that colours how you read the other three.

Does a 200-Node Thread Test Mean Anything at Home?

Silicon Labs says it ran 200 Matter-over-Thread devices across its Boston Connectivity Lab and office, in the middle of ordinary Wi-Fi, Bluetooth and Thread traffic, on an OpenThread Border Router. It reports on-network commissioning that succeeded every time, mean multicast latency as low as 87 ms, and packet loss under 1 percent for most payload sizes. It also says no special topology engineering was needed.

Those are good numbers, and I'd still hold them loosely for three reasons.

First, the company designed, built and graded the test. Second, the release doesn't say which chips the 200 nodes used; it names MG26 and Series 3 parts only as platforms that support concurrent multiprotocol operation. Third, the audience is commercial buildings, where 200 nodes is a floor plan, not a hobby.

Does that make it irrelevant to a house? Not quite. Reading the release, my takeaway is narrower and more useful: commissioning didn't fall over at scale. In forums and issue trackers, pairing is where Thread hurts most, and our Thread troubleshooting guide spends most of its length there. A vendor showing clean pairing in a noisy building is the right direction. It isn't proof that your flat, three border routers and a mesh Wi-Fi system will behave.

What Is in the Matter 1.6 SDK Releases?

This is the least glamorous item and the one I'd read first if I built devices. Silicon Labs' Matter software has tracked the spec closely this year:

The CSA published Matter 1.6 on June 17, so the SDK followed within eight days. Version 2.9.0 added EVSE and Wake on Matter examples, reworked the Energy Management clusters, and dropped Matter Wi-Fi support for the MG24 plus WF200 combination. Version 2.9.1 added LLVM compiler support and moved more application types to a new architecture.

The wording matters, though. The 2.9.0 notes say the CSA certification for Matter 1.6 isn't finalized, so the release may not pass every test case. The 2.9.1 notes describe it as "aligned with" Matter 1.6 and don't claim certification. In other words, 1.6 products built on this code aren't on shelves yet, and the usual gap between a spec and a product you can buy still applies.

Here's my one firm opinion on this section: ignore chip-vendor SDK dates when you shop. A new SDK tells you what a manufacturer could build, not what it will ship, and the real signal is a device on a store page with a Matter logo and a firmware changelog.

Why Do the Hue Bulbs Matter More Than the Test?

Because they're a product, not a lab. On June 23 Signify and Silicon Labs said select Philips Hue bulbs built on the MG26 and SiMG301 chips are available now or being introduced across the range, and that they're designed to run Zigbee and Matter-over-Thread concurrently.

Read the fine print before you get excited. At launch you still pick one protocol during commissioning, and the update that allows both at once is promised for later this year. Nobody has shipped the simultaneous mode yet, so I can't tell you how it behaves, and neither can anyone writing from a press release.

If it works as described, it eases one specific headache: the "Zigbee or Matter?" decision per bulb. A bulb could stay on a Hue bridge for its scenes and also appear in a Matter ecosystem. Is that a feature for you? Only if you run both. A house built entirely on Home Assistant with a Zigbee coordinator has no need for a second radio protocol inside every lamp.

For a bigger picture of when each protocol earns its place, see our Thread vs Zigbee vs Matter guide.

Does This Change What Sits Inside a Home Assistant Stick?

No, and it's worth saying out loud because the word "concurrent" invites the wrong conclusion. Concurrent multiprotocol is a chip and firmware capability. Home Assistant's own Thread documentation takes a conservative line on multiprotocol sticks: enabling Thread on a Connect adapter is a manual step, the adapters run Zigbee by default, and the guidance is one radio per protocol. The silicon being able to do two things at once doesn't mean the host software wants you to.

That matches what I'd do. My ZBT-1 stays on Zigbee, and when Thread arrives it gets its own radio. A second USB stick costs about as much as one night of frustration. For the hardware side, our Zigbee coordinator guide covers which chips sit in which sticks.

What About the Texas Instruments Deal?

In February 2026 Texas Instruments agreed to buy Silicon Labs for about $7.5 billion in cash. The company's quarterly report for the period ended June 30, 2026 still expected the deal to close in the first half of 2027, subject to regulatory approvals and customary conditions. I didn't find a completed closing or a termination.

For an owner, nothing breaks. Sticks, bulbs and locks with Silicon Labs chips keep working, and firmware for shipping products doesn't depend on who owns the chip maker next spring. The longer-term question is roadmap: whether MG-series parts and the open Matter SDK carry on at the same pace under new ownership. That's a risk for device makers first and for you a year or two later. I wouldn't change a purchase over it today.

So What Should You Do With This?

Short list, because the honest answer is "not much, yet."

1. Don't buy because of a chip name. A Silicon Labs logo on a spec sheet says nothing about firmware quality or update policy.
2. Wait on dual-protocol Hue bulbs until the concurrent-mode update ships and someone has run it for a few weeks.
3. Keep your stick on one protocol, as Home Assistant's documentation advises.
4. Watch for certified Matter 1.6 products, not SDK versions. The release notes themselves say certification wasn't final at 2.9.0.

The pattern across all of it is consistent, and it changes less than the headlines suggest. The announcements are real, the numbers are specific, and the benefit reaches a normal house later than the headlines imply. That isn't a criticism of the engineering. It's how the standard moves.