What Matter 2.0 Would Need to Actually Fix Smart Home Interop

Matter was supposed to fix smart home interoperability: one standard, one app, devices that work across ecosystems. In practice, adoption has been messy—certified devices that still require brand apps, bridges that half-work, and ecosystems that treat Matter as an afterthought. So what would Matter 2.0 need to do to actually fix smart home interop?

Where Matter 1.x Fell Short

Matter 1.0 and 1.1 brought a common application layer over IP: same data models, same commissioning flow, same security model. In theory, any Matter controller (phone, hub, or speaker) can talk to any Matter device. In reality, many devices still ship with “Matter support” that feels bolted on. You add the device via Matter, but advanced features or firmware updates still require the manufacturer’s app. Multi-admin was supposed to let you share devices across Apple Home, Google Home, Alexa, and others—but implementation has been inconsistent, and some ecosystems still push you toward their own stack first.

Another gap: the standard has been slow to cover device types that people actually buy in volume. Robots, appliances, and more complex sensors have taken time to standardize. So “Matter support” today often means “lights and plugs and thermostats,” while the rest of your smart home stays in silos. For Matter 2.0 to feel like a real fix, it has to close these gaps and make the multi-ecosystem promise real.

Unified Setup and Zero Brand Lock-In

Matter 2.0 would need to make “add device once, use anywhere” the default. That means: no mandatory manufacturer app for setup or updates. Commissioning via any Matter controller, with optional manufacturer apps only for extra features (e.g. robot maps or energy dashboards). Firmware updates should be deliverable through the Matter fabric or a generic update mechanism, not only through a single vendor app. If you still have to open three apps to set up and maintain three Matter devices, the standard hasn’t won.

Multi-admin also has to work reliably. Today, adding the same device to a second ecosystem can be hit-or-miss. Matter 2.0 should define clear, testable behavior: when you add a device to a second controller, it should just work—same state, same controls—without re-commissioning or losing the first connection. Certification should include multi-admin tests so that “works with Matter” means “works with more than one home ecosystem at once.”

More Device Types and Clearer Extensions

Lights, plugs, thermostats, and locks are a start. Matter 2.0 needs to bring more device types into the core spec so that robots, appliances, sensors, and cameras don’t stay in proprietary land. That doesn’t mean every feature of every device has to be in the spec—but the basics (on/off, status, alerts, maybe basic scheduling) should be standardized so that any controller can do the everyday stuff without a custom integration.

For vendor-specific features, Matter’s extension mechanism has to be clear and optional. Manufacturers can add custom clusters for advanced functionality, but the device should still be usable and updatable through standard Matter means. If “Matter support” means “Matter for the basics, our app for everything else,” interop is only half-solved.

Local-First and Reliability

Matter is already local-first: devices and controllers talk on the LAN. But reliability in the real world depends on how well different stacks implement it. Matter 2.0 could strengthen the spec around offline behavior, failover, and state consistency. When the internet drops, your smart home should keep working; when a controller goes away, another should be able to take over without re-pairing. Clearer requirements and certification around these scenarios would push the industry toward “it just works” instead of “it works when the cloud and the app are happy.”

Today, many users still run into “Matter device added but doesn’t show up in the other app” or “works in one ecosystem, flaky in another.” That’s an implementation and testing problem. Matter 2.0 could mandate stricter interoperability testing: every certified device tested against multiple controllers and multiple ecosystems, with clear pass/fail criteria for multi-admin and local control. Without that, “Matter certified” will continue to mean “meets the spec on paper” rather than “works in your home with your mix of gear.”

What Would Success Look Like

Success for Matter 2.0 would look like this: you buy a smart device, bring it home, and add it with the controller you already use (Apple, Google, Alexa, or a third-party hub). You never have to install the manufacturer’s app unless you want a niche feature. You can add the same device to a second ecosystem and control it from both. Updates roll out through your chosen controller or a standard mechanism. New device types (robots, appliances, etc.) are part of the standard, not exceptions. And when the internet is down, everything that can work locally does.

We’re not there yet. Matter 2.0 would need to tighten the spec, expand device coverage, and make multi-admin and local-first behavior non-negotiable for certification. If the industry commits to that, smart home interop could finally live up to the promise. If not, we’ll keep living in a world where “Matter compatible” is a start—but not yet the fix.

The Bottom Line

Matter 2.0 would need to deliver true multi-ecosystem support, optional manufacturer apps, more device types, and robust local-first behavior. Until then, the smart home will remain a patchwork of ecosystems with Matter as a promising but incomplete layer. The standard has the right ideas; the next version has to make them real in every device and every home.