Hello readers!

This week, we’re looking at the promising new updates to the Matter standard, the biggest IoT mistakes that even smart teams keep making, and more!

The Connectivity Standards Alliance released Matter 1.6 last week at its inaugural Unify conference in Austin, and for the first time in the standard's four-year history, the spec itself isn't the problem. The headline feature is Joint Fabric — a shared network architecture that lets Apple Home, Amazon Alexa, and Google Home all manage the same devices from a single unified state, rather than running parallel ecosystems that barely acknowledge each other. Set a device up once, and every authorized platform sees it. That's not a minor improvement. It's the thing Matter was supposed to be when it launched in 2022.

The original promise was straightforward: buy a device, bring it home, and it works — regardless of whether you're an Apple household, an Amazon household, or some messy combination of both. What actually shipped was more modest. Matter 1.0 gave devices a common language but kept the ecosystems in separate rooms. You could add the same smart lock to both Apple Home and Amazon Alexa, but each platform maintained its own view of it. When they issued competing commands, things got weird. Automations built in one ecosystem couldn't see state changes made in another. The interoperability was real, but shallow. Fragmentation didn't go away — it just moved one layer deeper.

Joint Fabric attacks that directly. Instead of each platform running a separate fabric and syncing awkwardly, the new architecture introduces a shared Datastore that multiple controllers access simultaneously. A routine built in Google Home can now respond to a door unlocked through Apple Home. Device states stay consistent across platforms because there's one source of truth, not three. Matter 1.6 also ships NFC-based commissioning that completes the full setup handshake without Bluetooth — a light fixture can be provisioned before it's even wired in, using the inductive field from a phone to power the NFC tag. These aren't incremental refinements. They're the gaps that made the multi-app frustration feel permanent, addressed at the spec level.

The catch is that the spec and the product are two different things. Matter 1.6 is available to developers now. What that actually means for the thermostat on your wall depends entirely on when Apple, Google, and Amazon ship app updates implementing it — and historically, that gap runs anywhere from several months to well over a year. As of this week, Google Home is still catching up to earlier Matter versions. A journalist covering the Unify conference went to Austin specifically to ask Apple, Google, and Amazon when they plan to implement Joint Fabric, and came away without a timeline from any of them. The CSA can write the specification. It cannot make platform teams prioritize it.

That's the thing to watch. The standard is no longer holding the smart home back — the platforms are. Every major version of Matter has faced this same lag: a spec that moves faster than the ecosystems that have to implement it, for reasons that aren't purely technical. The platforms have real competitive reasons to delay features that reduce switching costs and make their ecosystems more interchangeable. Joint Fabric, done right, makes it genuinely easy to run Alexa and Apple Home side by side on equal footing — which is not obviously in Amazon's or Apple's interest. The CSA has closed the specification gap. Whether the industry closes the implementation gap is a question about business incentives as much as engineering timelines, and the answer matters for everyone building connected products that depend on interoperability actually working.

A pattern emerges when you talk to enough IoT teams. The pilot was perfect. The devices connected. The data flowed. Leadership approved the budget. Then, between 500 and 50,000 devices, everything started falling apart.

Read more

Most teams treat analytics as a separate problem. As data grows, they add a warehouse, a pipeline, a sync job. By the time data reaches their dashboard, it's already stale.

TimescaleDB takes a different approach: extend Postgres instead of splitting away from it.

Your transactions and your analytics run on the same database, on live data, with no pipeline in between.

Hypertables partition time-series data automatically as volume grows. Hypercore compression cuts storage by up to 95%. Continuous aggregates pre-compute rollups so dashboards stay fast without re-querying everything.

CERN runs it on Postgres to handle sensor data from the Large Hadron Collider.

No second database. No migration. Same Postgres you already know.

Get $1000 Credit To Start

In this episode of the IoT For All Podcast, Martin Nord, Chief Technology and Product Officer at Com4, joins Ryan Chacon to discuss IoT in 2026 and what enterprises need to consider. The conversation covers what enterprise IoT buyers actually need, the crowded IoT connectivity market, the 2G/3G sunset, how roaming in IoT is broken in subtle ways, the nature of IoT connectivity failures, prioritizing financial stability in IoT partners, satellite IoT, and the future of IoT connectivity.

YouTube • Spotify • Apple • YT Music • Amazon

Interested in becoming an IoT For All Partner? Reach out here!