Bottom line: "Matter certified" tells you almost nothing about whether the feature you actually want will work

This page contains affiliate links. We may earn a commission at no extra cost to you.

If you’re looking at a box that says “Works with Matter” and trying to decide whether it’ll do what you want once it’s connected to your Apple Home, Google Home, Alexa, or SmartThings setup, here’s the honest answer: the Matter logo only promises that the device speaks a common local-network language and can be added to more than one app. It does not promise that any specific feature - voice-unlocking a door, changing a light’s color effects, viewing a camera feed, reading a sensor’s full data - survives the trip into your particular app. That’s confirmed directly by the organization that runs Matter certification itself: the Connectivity Standards Alliance’s own FAQ states that “Matter-only devices require an internet-connected controller…to be present in the home to enable control when away from the home” - certification covers the local connection, not what your specific hub chooses to expose. The question you actually need answered isn’t “is it Matter certified,” it’s “does this app support this feature of this device category, today.”

Why a certified device can still lose features

Matter defines a shared language for a device category (a “lock,” a “light,” a “sensor”), but each controller app - Google Home, Apple Home, Alexa, SmartThings - decides independently which parts of that shared language it actually implements, and on what timeline. Three concrete, documented examples of what that looks like in practice:

  • Google Home explicitly disables voice and remote unlock for Matter locks that don’t require a PIN. Google’s own developer documentation states it directly: “Remote unlock is disabled on all surfaces for Matter door locks in the Google ecosystem that don’t mandate a PIN code. Likewise, voice unlock for door locks is disabled.” That’s not a bug or a missing update - it’s a deliberate policy choice baked into Google’s implementation, and it applies regardless of which lock brand you bought.
  • A light can lose its personality on the way into a different app. One documented case: a Govee light connected via Matter to Apple Home showed up with only on/off, dimming, and solid-color control - the effects and scenes available in Govee’s own app simply weren’t part of what Matter (or Apple’s implementation of it) carried over.
  • A lock’s advanced setup can require the manufacturer’s app no matter what. An Aqara U400 lock, in the same account, still needed the Aqara app specifically to enroll fingerprints and reach advanced settings - Matter got the lock talking to the hub, but not every configuration screen came with it.

None of this means Matter “doesn’t work.” It means Matter guarantees a floor (basic on/off-level control across apps), not a ceiling (every feature the device is capable of).

The version-gap problem, and why it matters for what you’re buying today

Matter itself keeps adding device categories and capabilities (version 1.0 covered the basics; later versions added things like air purifiers, dishwashers, robot vacuums, and - most recently - security cameras). The problem for you as a buyer: each platform updates on its own schedule, and multiple independent sources describing 2026’s landscape note that Google Home was still running an older version of the spec than Apple Home, Alexa, and SmartThings, meaning device categories added in newer versions simply wouldn’t appear as controllable in Google Home until Google shipped an update. As of the most recent reporting I could verify, Matter security cameras were supported only by Samsung SmartThings - anyone on Alexa, Google Home, Apple Home, or Home Assistant was waiting on that platform to catch up. If you’re buying a device in a newer Matter category (cameras, robot vacuums, air purifiers), the platform-version gap matters more than the Matter logo does.

The checklist: run this before you buy, not after

  1. Identify your controller, specifically - not “I use Matter,” but “I use Google Home” or “I use Apple Home” or “I use SmartThings.” The feature gaps above are per-platform, not per-Matter.
  2. Check that platform’s own supported-device-types page, not the retailer’s product description. Google publishes its list at developers.home.google.com/matter/supported-devices; Apple, Amazon, and Samsung publish equivalents through their own developer sites. These pages are written for developers, not shoppers, which is exactly why they’re worth the five minutes - they say what the platform actually implements, not what a marketing page implies.
  3. Name the one feature you actually care about, and search that platform’s documentation or forums for that feature by name (e.g., “voice unlock,” “camera,” “light effects”) rather than trusting that “Matter support” implies it. If a platform’s own docs don’t mention it, assume it’s not there yet.
  4. If the feature isn’t covered, decide whether the manufacturer’s own app is an acceptable fallback. Several of the gaps above (fingerprint enrollment, light effects) are only unavailable inside the unified app - they still work in the brand’s own app. If you’re fine running one extra app for that one feature, the Matter gap may not matter to you.
  5. For a brand-new device category (cameras, robot vacuums, air purifiers as Matter accessories), assume the newest platforms support it first and check specifically, since spec version lag is the most common reason a “Matter certified” box still doesn’t do what you expected on day one.

Who this doesn’t fit

This is about ordinary consumer setups - one or two ecosystems, off-the-shelf devices. If you’re already running Home Assistant or another local automation hub, your situation is different: local automation platforms often expose far more of a device’s native capability than a corporate app does, and the constraints described here (Google’s lock policy, Apple’s light-effects handling) may not apply to you the same way. This also isn’t a guide to which single ecosystem to pick - that decision depends on which voice assistant and other devices you already own, which is outside what a compatibility checklist can answer for you.

Summary

A “Matter compatible” label is a real, useful signal - it means a device can join more than one app instead of being locked to one manufacturer’s ecosystem forever. It is not a promise that every feature the device has will show up, or work the same way, inside whichever app you use. Before you buy, find your specific platform’s own supported-device documentation, check for the one feature you actually want by name, and treat a missing mention as a real gap rather than an oversight in the product listing. The companion piece on how Matter smart locks specifically differ across Apple Home, Google Home, Alexa, and SmartThings goes deeper on the single category where this gap causes the most buyer regret: [matter-smart-home-buying-guide].