Short Answer: Matter Matches the Basics, Not Every Feature
Your device is probably not broken. A Matter accessory can work perfectly in Home Assistant and still show fewer controls than it shows elsewhere. Matter standardizes device types and clusters—small bundles of capabilities such as on/off, brightness, lock state, fan speed, or temperature. It does not force every manufacturer to put every private feature into Matter, and it does not force every controller to display every optional cluster on the same day.
A Matter controller is the app or system controlling the device. The practical check has three parts. First, did the device or bridge software expose the feature through Matter? Second, does the current Home Assistant Matter integration support that device type and cluster? Third, did Home Assistant turn it into a visible control, sensor reading, button press, or automation choice? The same three questions apply to Apple Home, Google Home, Alexa, and SmartThings.
That is why a reset is usually the wrong first move. Resetting clears pairing and controller relationships; it cannot teach an app a feature it does not support. Update the device, Home Assistant Core, Matter Server, and any other controller first. Then check the official support tables and choose between Matter, a brand-specific local Home Assistant integration, or a vendor maintenance app.
The Three Places a Matter Feature Can Disappear
| Layer | What it means in the house | What to check | What can fix it |
|---|---|---|---|
| 1. Device or bridge | The hardware decides which standard and vendor-specific capabilities it publishes. | Exact model, firmware, Matter version, and whether a bridge exposes that child device at all. | Vendor firmware or a different integration path. Resetting rarely adds a missing capability. |
| 2. Matter controller | Home Assistant, Apple, Google, Alexa, or SmartThings must understand the device type and cluster. | Current official device-type and cluster support, plus release notes. | Update the controller or wait for support. A native integration may already handle it. |
| 3. App and automation layer | The controller may read a capability but still lack a visible control, sensor reading, button press, or automation choice. | Device page, disabled or hidden controls, actions, button events, automation choices, and known issues. | A controller, Home Assistant app, or dashboard update. Advanced users can follow a confirmed issue; homeowners should not guess with raw cluster commands. |
Think of a Matter cluster as a page in a shared instruction book. The device has to include the page, the controller has to know how to read it, and the app has to give you a useful control. A gap at any one step produces the same homeowner symptom: “The feature is missing.”
What the Matter Badge Does and Does Not Promise
The Connectivity Standards Alliance describes Matter as a common way to set up and control devices across compatible platforms. It also says vendor apps can continue to offer advanced configuration and differentiated features. That is the boundary in one sentence: Matter gives you an interoperable foundation, while brands and controllers can build more around it.
A Matter badge therefore does not promise that:
- every vendor-only mode, map, effect, calibration, or diagnostic will appear in every controller;
- Apple Home, Google Home, Alexa, SmartThings, and Home Assistant will ship support for a new device type together;
- a Matter bridge will expose every older device behind it;
- firmware updates will arrive through Matter, because Matter over-the-air updating is optional;
- you will never need the vendor app for initial activation, firmware, or advanced settings.
Home Assistant's Matter support is official. Home Assistant and the Open Home Foundation Matter Server are certified by the Connectivity Standards Alliance. “Missing feature” does not mean “unofficial controller”; it means one of the three support layers still has a gap.
What Each Major Platform Officially Supports
Support moves quickly, so use these as July 11, 2026 boundaries rather than permanent promises.
| Control path | Official support and local control | Cloud or account boundary | Matter, HomeKit, and practical caveat |
|---|---|---|---|
| Home Assistant Matter | Officially certified controller. Normal Matter commands stay on the local Wi-Fi, Ethernet, or Thread network. Thread is the low-power home network used by many Matter devices. Matter Server 9 supports Matter 1.5.1. | Some vendors still require an account to enable Matter, and remote access is a separate choice. | Use Matter for standard controls. Prefer a mature native local integration when it exposes important extras. |
| Apple Home | Apple lists supported categories including bridges, lights, locks, outlets, switches, thermostats, blinds, shades, and several sensor types. | Apple Account, iCloud Keychain, and a home hub are part of syncing and the best remote experience. | HomeKit and Matter are separate protocols. A HomeKit-only feature does not automatically become a Matter feature in another controller. |
| Google Home | Google says many Matter device types are supported, but not all are fully supported. Local Matter control uses a compatible Google hub. | Google account, app, voice, and remote services remain part of the wider experience. | Google does not expose several clusters to users, including Binding; Groups and Scenes are handled through Routines instead of direct Matter controls. |
| Amazon Alexa | Amazon publishes a current device-category and cluster-to-Alexa-capability table for compatible Echo and eero Matter hubs. | Alexa app, voice, and remote services use an Amazon account and cloud services around the local Matter connection. | Only clusters mapped to Alexa capabilities become usable Alexa controls. Amazon also applies security limits to locks and other sensitive devices. |
| Samsung SmartThings | Matter over Thread, Wi-Fi, and Ethernet connects through compatible SmartThings hubs. Device profiles and capabilities define what SmartThings can represent. | The hub handles local device traffic; the SmartThings account and app remain part of setup, presentation, and remote use. | A Matter cluster still needs a matching SmartThings capability and app presentation. Community-made SmartThings drivers do not equal official product support. |
| Vendor app or native integration | Can expose proprietary features that do not exist in Matter. A native Home Assistant integration may be local or cloud-based, depending on the brand. | Firmware, diagnostics, and advanced setup may require the vendor account or cloud. | Keep the app as a maintenance tool when necessary. Do not let both the vendor app and Home Assistant run duplicate automations. |
Four Real Examples That Explain the Mismatch
Philips Hue: Native Local Control Is Richer Than Matter
Home Assistant's own Matter documentation uses Philips Hue as the clearest example. Hue through Matter provides basic light controls. The native Home Assistant Hue integration also runs locally and adds Hue-specific features such as dynamic scenes and entertainment mode. For Home Assistant, Matter is not automatically the better path just because it is newer.
SwitchBot Bridge: The Bridge Chooses What Crosses
Home Assistant warns that a Matter bridge does not guarantee every device behind it will appear. Its documentation uses SwitchBot Hub 2 version 1.5 as an example: curtains, locks, and blinds could cross through Matter, while lights could not. The missing light was a bridge-exposure limit, not a reason to reset Home Assistant.
Robot Vacuums: The Feature Existed Before Home Assistant Displayed It
A Home Assistant GitHub discussion documented an ECOVACS DEEBOT X8 PRO OMNI exposing Matter's ServiceArea information while Apple Home already showed room controls. Home Assistant did not yet present that cluster. Home Assistant 2026.3 later added area cleaning for supported Matter vacuums. Same device, same standard, different controller timing—then an update closed the gap.
Google Home: A Device Can Pair but Still Have No Useful Control
Google's official Matter table says an on/off light switch can be paired, but Google Home does not expose the Binding cluster that tells it which light to control. The switch can therefore appear without a useful end-user setup path. Pairing succeeded; controller presentation did not finish the job.
Feature Support Changes With Updates
Home Assistant's recent releases make the moving target visible. Version 2026.3 added Matter vacuum area cleaning, carbon monoxide alarm states, and total volatile organic compound (TVOC) air-quality sensors. Version 2026.7 added Matter soil-moisture sensors. Matter Server 9 moved Home Assistant to Matter 1.5.1 on June 23, 2026.
That does not mean every Matter 1.5.1 feature instantly becomes a visible Home Assistant control or reading, called an entity. It means the controller foundation can understand that specification. Work on how that control appears, its actions, testing, and the user interface can land separately.
The Safe Troubleshooting Order
- Name the exact missing feature. “My vacuum works” is too broad. Write down “room selection appears in Apple Home but not Home Assistant,” or “the vendor app has a transition effect that Matter does not show.”
- Record where it works. Test the vendor app and each Matter controller separately. Matter multi-admin gives each controller its own direct relationship; one app working does not prove another app supports the same cluster.
- Update without resetting. Update device or bridge firmware, Home Assistant Core, Matter Server, and the other ecosystem controllers. Save setup codes and make a backup first.
- Check the device or bridge boundary. Confirm the exact model is exposed through Matter. A bridge may publish only a subset of its children or features.
- Check the controller's official support. Use Home Assistant release notes and the Apple, Google, Amazon, or SmartThings documentation for the device type and capability.
- Check Home Assistant's presentation. Look for entities, disabled entities, events, actions, and automation choices on the device page. Download diagnostics only when you are ready to open a careful issue and remove private information before sharing.
- Compare the native path. If Home Assistant has a mature local integration with more useful controls, use it. Keep Matter for the platforms where its common controls and multi-admin sharing help.
Do not factory-reset for a missing control. Reset only when you have evidence of a secure setup or pairing-record problem. A reset can erase working controller relationships and setup state without adding a single feature.
Local Control and Cloud Dependency Are Separate Questions
Home Assistant's Matter documentation is clear that normal Matter control is local and does not require the vendor cloud. It is equally clear that some vendors require an account before they let you enable Matter on a bridge or product. The Connectivity Standards Alliance also allows vendor apps to provide advanced features outside the common Matter experience.
Ask four separate questions before buying or changing a path:
- Does daily control work during an internet outage?
- Is a vendor login required to turn on Matter or pair the bridge?
- Where do firmware and security updates come from?
- Which advanced controls disappear if the vendor cloud or app goes away?
A device can have local Matter control and still need cloud-backed maintenance. A native Home Assistant integration can also be either local or cloud-based. Check the exact integration instead of treating “native” or “Matter” as automatic proof.
Which Control Path Should You Choose?
- Choose Matter when you need common controls to stay local and the same device to join several major platforms.
- Choose a native local Home Assistant integration when it is stable, officially maintained, and exposes important features Matter does not.
- Keep the vendor app for maintenance when firmware, calibration, maps, or special modes live there. Turn off duplicate schedules and automations.
- Avoid the vendor cloud path when a proven local Matter or native integration gives you everything the household needs.
Tara's default is one automation owner. Let Home Assistant run the household logic. Use Apple Home, Google Home, Alexa, or SmartThings as family-facing controls where helpful. Use the vendor app for the smallest maintenance role it genuinely needs.
Locks, Garage Doors, and Safety Devices Need a Slower Test
For a lock, garage door, alarm, smoke detector, or water shutoff, a missing control can be an intentional security limit rather than an unfinished feature. Google and Amazon publish platform-specific restrictions for sensitive device types. Do not try to bypass them with unverified custom commands.
Keep a physical key, manual release, local alarm behavior, or another safe fallback. Test alerts and automations while someone is home. Never remove the last working controller or factory-reset the only working entry device merely to make two apps look identical.
Related Tara Reading
- How to Share One Matter Device Across Home Assistant, Apple Home, Google Home, Alexa, and SmartThings
- Should You Pair Matter Devices to Home Assistant or Apple/Google First?
- Philips Hue in Home Assistant: Bridge, Matter, or Zigbee?
- Can Home Assistant Update Matter Device Firmware Without the Vendor App?
- Where Should Your Smart Home Automations Live?
FAQ
Why does the vendor app have more features than Home Assistant?
The vendor app can use private controls outside Matter. Home Assistant can present only what the product exposes through Matter and what the current Matter integration maps into entities, actions, and automations. Compare the native Home Assistant integration before assuming Matter is the richest path.
Is Home Assistant's Matter support unofficial?
No. Home Assistant and the Open Home Foundation Matter Server are officially certified by the Connectivity Standards Alliance. A missing control can still be a product-firmware, Matter-version, controller, or app-presentation gap.
Will sharing the device from Apple Home or Google Home unlock the feature in Home Assistant?
No. Multi-admin gives each controller its own secure relationship with the device. Apple or Google does not copy its user interface or feature mapping into Home Assistant.
Should I factory-reset when one feature is missing?
Usually not. Update first, identify the exact missing capability, check official controller support, and compare the brand-specific Home Assistant integration. Reset only for a confirmed secure setup or pairing-record problem.
Does Matter still work locally if the vendor app needs the cloud?
Normal Matter control is local. The vendor may still require an account to enable Matter, install firmware, or configure advanced features. Local daily control and fully cloud-free setup are separate promises.