FIELD NOTE / 2026.09.135 MIN READ / 5 SOURCES

Matter and the Attempt to Make the Smart Home Interoperable

Matter brought major smart-home ecosystems together around an IP-based application standard intended to make devices easier to commission, secure and control across brands.

The smart home had many radios but too few shared application agreements

By the late 2010s consumers could buy connected locks, lights, thermostats and sensors, yet products often worked only with selected apps, hubs or voice assistants. The problem was not simply wireless connectivity. Wi-Fi, Bluetooth, Thread and Zigbee could move bits, but ecosystems still differed in commissioning, security and application semantics. Major platform companies therefore began Project Connected Home over IP, or Project CHIP, to create a common application layer built around Internet Protocol rather than another proprietary smart-home silo.

Interoperability sits above connectivity

Two devices can share the same radio technology and still fail to understand one another if they disagree on discovery, security or the meaning of commands.

Project CHIP became Matter under the Connectivity Standards Alliance in 2021

In May 2021 the former Zigbee Alliance renamed itself the Connectivity Standards Alliance and introduced Matter as the new name for Project CHIP.[1] The project brought together companies that normally competed at the ecosystem layer, including major platform, semiconductor and device vendors. The promise was ambitious: manufacturers could build to one interoperable standard while consumers could use devices across multiple compatible ecosystems.

Matter chose IP as the common network layer

The Matter architecture uses Internet Protocol over transports such as Wi-Fi, Ethernet and Thread, while Bluetooth Low Energy has been used for commissioning. The Matter 1.0 Core Specification defines the requirements for an interoperable application-layer solution for smart-home devices over IP.[2] This choice reuses mature networking concepts rather than inventing a complete proprietary stack from radio to application. A Matter device is therefore part of an IP network, but Matter specifies the higher-level behavior that makes a smart-home product recognizable and controllable.

IP provided a common waist between different physical networks and device models

A low-power Thread sensor and a Wi-Fi appliance can participate in the same application ecosystem without using the same radio.

Matter 1.0 paired the specification with certification and an open-source SDK

The Alliance released Matter 1.0 and opened the certification program in October 2022.[3] Test labs, test harnesses and an open-source reference SDK were part of the launch. This institutional machinery matters because interoperability standards fail if each vendor interprets them differently. Certification gives manufacturers a shared target and gives ecosystem providers evidence that a device implements the required behaviors.

Commissioning and shared control were designed around multi-admin homes

Matter devices can be commissioned into one or more compatible ecosystems, allowing a household to avoid choosing one permanent platform for every device. This multi-admin concept is strategically important. Traditional smart-home products often tied device identity and control to one cloud account or hub vendor. Matter tries to separate the device’s core interoperability from the business relationship surrounding it, making local-network control and cross-ecosystem participation normal parts of the architecture.

Interoperability changes the balance of power in an ecosystem

If the same device can join several controllers, consumers and manufacturers are less dependent on one proprietary home platform.

Security had to become part of onboarding, identity and lifecycle management

Matter treats device identity, authenticated commissioning and encrypted communication as baseline features rather than optional add-ons. Its certification model includes security requirements, while later revisions have strengthened certificate management and deployment guidance. Matter 1.4.2, for example, focused heavily on security, certification and infrastructure improvements learned from real products in the field.[2] The standard’s security work reflects the risk of making locks, cameras and sensors interoperable: ease of connection cannot mean anonymous trust.

The specification has evolved rapidly as real deployments exposed missing features

Matter has followed a regular revision cycle, adding device categories and refining implementation behavior. Matter 1.5 in 2025 added cameras, closures and new energy-management capabilities, followed by Matter 1.5.1 in March 2026 with camera and media improvements.[4] These revisions show that interoperability is not achieved once at version 1.0. Real products reveal performance gaps, ambiguous behaviors and new device needs that standards bodies must absorb without breaking existing deployments.

Backward compatibility is part of the product experience

A smart-home standard succeeds only if older certified devices continue to work while controllers and newer products adopt later revisions.

Matter 1.6 shows the project moving from basic compatibility toward richer coordination

As of September 2026, the current major release is Matter 1.6, announced on June 17, 2026.[5] It added features including NFC-based commissioning, Joint Fabric support for coordinated multi-ecosystem management, thermostat suggestions and richer device-state communication. The release is historically significant because it moves beyond simply making a light switchable from several platforms. Matter is beginning to standardize how ecosystems cooperate around setup, context and management.

Why Matter belongs in the history of ubiquitous computing

Matter belongs in computing history because it represents a large-scale attempt to solve the social problem created by successful smart-home computing: too many connected products became isolated by ecosystem boundaries. Project CHIP/Matter used IP, common device models, certification and cross-vendor governance to make interoperability an industry project rather than a feature owned by one company.[1][3]

The outcome is still evolving. Matter has not erased every platform difference, and support for features varies by ecosystem and device revision. But the standard has changed the direction of the market. By Matter 1.6, the question is increasingly not whether major ecosystems will support a shared smart-home layer, but how far that layer can expand while preserving security, compatibility and room for vendor innovation.[5]

RESEARCH / PROVENANCE

Works Cited

5 SOURCES
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05

CodeHistory is a living archive. Citations document the evidence used for this edition; later evidence may refine the account.

Contribute / Corrections

Improve the record.

Use this moderated submission form to suggest a correction, provide a source, challenge a priority claim or identify a missing contributor. Submissions are treated as research leads, not automatically published comments.

Submit a research lead

Please do not submit confidential material or claims you cannot support.