Matter 1.6 vs 1.4: What Actually Changed? (2026)

Matter 1.6 dropped yesterday (June 17, 2026) via the CSA, and the jump from 1.4 is substantial. Not in new device types (there are none), but in how devices set up, share across platforms, and handle automation conflicts.

Here’s a clean, detailed comparison of what changed between versions so you know exactly what you’re getting.

Quick Recap: What Matter 1.4 Brought

Matter 1.4 was the previous major release. It introduced several important features:

• Enhanced Multi-Admin: Simplified the process of sharing device access between platforms. Still used separate fabrics per platform, but made the sharing workflow smoother.
• Energy management features: Devices could report energy consumption data. Smart plugs and switches could communicate power draw.
• Additional device types: Water leak sensors, rain sensors, and additional sensor categories got official support.
• EMA (Enhanced Multi-Admin) commissioning flow: Reduced the steps needed to add a device to a second platform.

Then came two point releases:

Matter 1.4.1 added:

• NFC onboarding payload: devices could store setup information on an NFC tag, replacing QR code scanning. But BLE was still required for the actual commissioning handshake.
• Minor setup flow improvements and bug fixes.

Matter 1.4.2 added:

• Certificate Revocation List (CRL) support: the system could now check if a device’s security certificate had been revoked.
• Security improvements and protocol hardening.
• Bug fixes from field deployments.

What Matter 1.6 Adds

Three headline features and several core improvements:

NFC-Based Commissioning (Full)

Builds on 1.4.1’s NFC payload but goes all the way. The entire commissioning exchange happens over NFC. No BLE required. Works even when the device is unpowered. This is a complete replacement for the old BLE setup flow, not just an enhancement.

Key difference from 1.4.1: in 1.4.1, NFC stored the setup payload (discriminator + passcode) but still needed BLE for the PASE handshake and credential transfer. In 1.6, all of that happens over NFC. The BLE radio isn’t needed at any point during setup.

Joint Fabric

A fundamentally new architecture for multi-ecosystem support. Instead of each platform maintaining its own separate fabric (connection) to each device, multiple platforms share a single fabric through a central Datastore.

Key difference from Enhanced Multi-Admin (1.4): EMA let platforms share access but each maintained their own fabric. Joint Fabric creates one fabric that all platforms co-administer. One fabric slot used total, regardless of how many platforms participate.

Thermostat Suggestions

Brand new interaction model for thermostats. Automations send suggestions instead of commands. The thermostat evaluates suggestions against user preferences, recent manual adjustments, and demand-response commitments before deciding whether to accept.

This didn’t exist in any form in Matter 1.4. It’s a completely new cluster type.

Core Improvements

• Device capability/limits communication: Devices can now advertise what they support and what their limits are. Controllers know upfront what a device can and can’t do.
• Security sensor event history: Security sensors maintain a log of events accessible by any controller.
• Smoke/CO alarm unmounted detection: Alarms report when physically removed from their mount.
• Partitioned Certificate Revocation Lists: More efficient CRL lookups (builds on 1.4.2’s CRL support).

Feature-by-Feature Comparison Table

Feature	Matter 1.4 (inc. 1.4.1, 1.4.2)	Matter 1.6	Change
Device setup method	QR code + BLE (primary), NFC payload + BLE (1.4.1)	Full NFC commissioning (no BLE needed)	Major upgrade
Multi-ecosystem support	Enhanced Multi-Admin (separate fabrics per platform)	Joint Fabric (shared fabric, central Datastore)	Architecture overhaul
Thermostat automation	Direct commands only	Suggestion model with accept/reject logic	New capability
Pre-power commissioning	Not possible (BLE needs power)	Supported via NFC	New capability
Device capability reporting	Limited (basic cluster advertisement)	Full capability and limits communication	Significant improvement
Security sensor history	Not available (current state only)	Event history log accessible by controllers	New capability
Smoke/CO alarm tamper	Not detected	Unmounted state reported	New capability
Certificate revocation	Full CRL download required (1.4.2)	Partitioned CRLs (faster, lighter)	Optimization
Fabric usage (3 platforms)	3 fabric slots used	1 fabric slot used (Joint Fabric)	Major improvement
Bulk device provisioning	30-60 sec per device (BLE)	5-10 sec per device (NFC)	5-6x faster
Automation conflict resolution	None (last command wins)	Thermostat evaluates and arbitrates	New capability
Energy management	Device-level reporting	Device-level reporting (unchanged)	No change
New device categories	Water leak, rain sensor, etc. (in 1.4)	None added in 1.6	No change
Camera support	No	No	Still missing
Robot vacuum support	No	No	Still missing

What’s Still NOT in Matter (Even After 1.6)

Let’s be honest about the gaps. Matter 1.6 is a big step forward in usability, but it doesn’t expand what types of devices Matter supports:

Cameras: The single most-requested device category. Your Ring, Arlo, Eufy, Reolink, and Nest cameras cannot be cross-platform via Matter. The CSA hasn’t committed to a timeline. Cameras involve streaming protocols, cloud storage, and bandwidth requirements that are fundamentally different from controlling a light switch. This one is hard.

Robot vacuums: Roborock, Dreame, iRobot, Ecovacs. All stuck in their proprietary apps or limited platform integrations. No Matter support, no timeline announced.

Audio/video streaming: Smart speakers, media players, TVs. You can’t control playback, route audio, or manage media through Matter. Chromecast, AirPlay, and Alexa Cast remain platform-specific.

Garage door openers: Conspicuously absent. Some brands (Meross, Chamberlain) have workarounds through other protocols, but there’s no official Matter device type for garage doors.

Large appliances: Washers, dryers, dishwashers, ovens. Some manufacturers (Samsung, LG) have their own smart features, but these aren’t Matter devices.

Irrigation systems: Smart sprinkler controllers remain platform-specific. No Matter device type.

The pattern is clear: Matter 1.6 focused on making existing supported devices (lights, switches, sensors, locks, thermostats) work better together. Expanding to new categories is a future-release problem.

The Architecture Shift: Why 1.6 Matters More Than It Looks

If you just read the feature list, Matter 1.6 might seem incremental. Three new features, some infrastructure improvements, no new device types. But the architectural changes are significant.

Joint Fabric changes the fundamental model of how Matter networks work. It’s not a tweak to multi-admin. It’s a new paradigm: shared infrastructure instead of parallel connections. This will influence every future Matter release and every future device interaction.

Thermostat Suggestions introduce the concept of device agency. Devices can now evaluate and reject commands based on local context. This pattern will likely expand to other device types in future releases. It’s the foundation for smarter device behavior across the board.

Full NFC commissioning eliminates Matter’s weakest link (BLE setup) entirely. It’s not just faster; it changes what’s physically possible (pre-power setup, zero-range commissioning). This makes professional installation viable at scale.

Together, these three features address the top three complaints about Matter: setup is painful, multi-ecosystem is tedious, and automations conflict with each other. That’s not incremental improvement. That’s addressing the core pain points head-on.

Upgrade Path: How to Get From 1.4 to 1.6

There’s no “upgrade” button you’ll press. Here’s what actually happens:

Your hubs/controllers (HomePod, Nest Hub, Echo, SmartThings Hub): These will receive firmware updates from Apple, Google, Amazon, and Samsung over the next 3-6 months. Most updates happen automatically in the background. Once updated, your hub speaks Matter 1.6 and can use Joint Fabric, send Thermostat Suggestions, and handle NFC commissioning.

Your existing devices (bulbs, switches, sensors): Most won’t need updates for Joint Fabric (that’s hub-side). For Thermostat Suggestions, your thermostat needs a firmware update from its manufacturer. For NFC commissioning, you need new hardware with NFC tags built in.

Your phone: Needs an updated app (Apple Home, Google Home, Alexa) to handle NFC commissioning and Joint Fabric setup. These updates come alongside the hub firmware updates.

Timeline expectations:

• Home Assistant: Weeks to months (open-source community moves fast)
• Google Home: 3-6 months (background hub updates)
• Amazon Alexa: 3-6 months
• Apple Home: 6 months (likely tied to iOS 20 fall release)
• Thermostat firmware: 6-12 months (manufacturer dependent)
• New NFC-equipped devices: 6-9 months for first models

Should You Wait for 1.6 Before Buying?

No. Here’s why:

1. Joint Fabric doesn’t require new devices. Your current Matter bulbs and switches will participate in a Joint Fabric once your hub updates. No device replacement needed.

2. Thermostat Suggestions need thermostat firmware updates, not new thermostats. If your thermostat manufacturer supports it (and most major ones will), you’ll get it via update.

3. NFC commissioning is nice-to-have, not essential. The old setup method (QR + BLE) keeps working fine. NFC is more convenient, but your devices still function perfectly without it.

4. Matter is backward compatible. A 1.6 hub works with 1.0 devices. A 1.4 device works with a 1.6 hub. You never get locked out by version differences.

The only reason to wait would be if you’re planning a massive installation (20+ devices) where NFC setup would save significant time. Even then, 6-9 months is a long wait for a convenience feature.

Check our detailed breakdown on whether to wait for Matter or buy now. The answer is almost always: buy now.

What to Expect Next (Matter 1.7 and Beyond)

The CSA hasn’t announced a 1.7 timeline, but based on the current pace (major releases roughly every 12-18 months), we’d expect it in late 2027 or early 2028. Likely candidates:

• Camera support (the most-demanded feature)
• Robot vacuum device type
• Extension of the Suggestions model to other devices
• Media/audio control
• Possibly garage door openers

For now, Matter 1.6 gives us a much more usable standard. The focus on practical improvements over feature expansion was the right call. You need the foundation to be solid before building higher.

For more context on where Matter fits in the broader protocol landscape, check our protocol comparison guide. And if you’re ready to build your Matter smart home today, our getting started guide walks you through it step by step. Our best Matter-compatible devices list stays updated with the latest hardware, and the Matter compatibility guide covers which features each device supports.

See how we compare products for our full methodology.

Frequently Asked Questions

Is Matter 1.6 backward compatible with 1.4 devices?

Yes, fully. A Matter 1.6 hub works perfectly with Matter 1.0, 1.1, 1.2, 1.3, and 1.4 devices. Older devices won’t gain new features (they can’t suddenly do NFC commissioning), but they continue working exactly as before. You never need to replace devices due to a version mismatch.

Do I need to re-commission my devices for Joint Fabric?

The CSA spec includes migration paths, but details depend on platform implementation. Ideally, your hub will offer to migrate existing devices to a Joint Fabric without re-commissioning. Worst case, you might need to reset and re-add some devices. We’ll know more once platforms ship their implementations.

Why did Matter skip from 1.4 to 1.6? What happened to 1.5?

The CSA consolidated planned 1.5 features into the larger 1.6 release. This is common in standards development. Point releases (1.4.1, 1.4.2) addressed urgent fixes, while the next major version combined multiple feature sets. There was no public 1.5 release.

Will Joint Fabric work between Apple Home and Home Assistant?

Yes, assuming both implement Joint Fabric support. Home Assistant’s open-source Matter stack is actively developed, and the community has expressed strong interest in Joint Fabric. Expect support relatively quickly after the reference implementation is available.

Can I use Matter 1.6 features with a Thread network?

Yes. Matter 1.6 features work regardless of the underlying transport protocol (Wi-Fi or Thread). NFC commissioning works for both Wi-Fi and Thread devices. Joint Fabric manages both Wi-Fi and Thread devices on the same fabric. Your Thread border router continues to work exactly as before, just with easier device onboarding and better multi-platform support.