After Connecting to Matter, Why Do Some Features Disappear?

Why do features disappear after pairing with Matter? Understand device, bridge and platform support with Hue, Home Assistant and Google Home examples and a checklist.

Suppose you buy a color-changing light. In the manufacturer’s app, you can dim it, switch between dynamic scenes, and coordinate lighting effects with other devices. After connecting it to another smart home platform, the light appears and you can turn it on and off, but there is no way to access your favorite effect.

It is easy to wonder: Did pairing go wrong? Should you factory-reset it and try again?

Don’t reset it just yet. Successful Matter pairing means the device has established a connection. It does not mean every feature in the original app will appear on the new platform.

The light above is a hypothetical example used to illustrate the issue. This article draws on official documentation to explain the boundaries of feature support; it does not report hands-on comparative testing of these products.

What Steps Does a Feature Have to Pass Through?

Between a feature on a device and a button on your phone, there are at least several things to check.

First, does the device itself support the feature? A light that can only adjust brightness will not gain color control by connecting to a new platform.

Second, which capabilities does the device expose through Matter? Features available in the manufacturer’s app may rely on product-specific interfaces. You cannot assume that Matter offers the same operation just because there is a button for it in the app.

Third, if the device connects through a bridge, does the bridge map that capability to Matter? Bridging an older device does not mean every manufacturer-specific command is fully translated.

Fourth, does the target platform recognize and use that capability, and where does it make the capability available? Even within the same platform, support may differ between the phone app, voice assistant, and smart display.

So “the device supports it,” “the Matter interface exposes it,” and “this app can control it” are three separate things to verify. If a bridge is involved, there is another layer of mapping to check.

The Hue Example: A Native Integration May Retain More Features

Home Assistant’s Matter documentation specifically cautions that, if a device already has a native integration based on a local API, Matter may not be the connection method with the most complete feature support.[1]

The documentation uses Philips Hue as an example: the Matter path provides basic lighting controls, while the native Hue integration also provides Hue-specific capabilities such as dynamic scenes and Entertainment mode.

Here, “native integration” means Home Assistant’s integration for the Hue interface, not a “native Matter device.” The two uses of “native” refer to different things.

Hue’s official guide also describes the bridge as an important component for using advanced features such as gradient lighting, dynamic scenes, and entertainment synchronization.[3] But “the bridge enables advanced features” should not be read as “every advanced feature will appear through Matter in every third-party app.” Those features may still require the Hue app or a dedicated partner integration.

This does not mean Matter can only ever turn lights on and off, or that every platform lacks the same features. The accurate conclusion is: when choosing a connection method, compare the features you need, not just whether you can add the device.

If your main goal is to turn lights on and off and dim them across different platforms, Matter may be a good fit. If you need full access to a particular set of proprietary lighting effects, check what the manufacturer’s app or native integration supports.

The Google Home Example: Pairing Does Not Guarantee the Operation You Expect

Google’s official support list explicitly states that the Google Home ecosystem supports many Matter device types, but not all of them have full support.[2]

One example that is easy to misunderstand is the Matter device type called On/Off Light Switch. It is a controller type that sends control commands to other devices. Google’s documentation says that such a device can be added, but the Google Home app does not provide users with a way to configure Matter Binding, so they cannot bind it to another device endpoint in the app.

You can think of binding here as telling the switch which target it should control.

Note that this concerns a specific Matter device type. It does not mean “no wall switches work in Google Home.” Two devices may both look like wall switches while declaring different device types and operating in different ways.

The value of this example is that it separates “paired successfully” from “meets the intended need.” A device appearing in the list completes only part of the acceptance check.

Google’s list also shows support separately for the voice assistant, Google Home app, and smart displays. When shopping, check the interface you will actually use; do not assume support in one interface carries over to the others.

Why Check Each Feature More Carefully When Using a Bridge?

A native Matter device exposes capabilities directly to a Matter platform. For a bridged device, the bridge exposes capabilities on behalf of the device connected through it.

For example, an older light might join Matter through the manufacturer’s hub. The target platform sees the lighting capabilities exposed by the hub; it does not receive a copy of the manufacturer’s entire app interface.

Whether the hub supports that particular light, maps brightness and color, or exposes a certain sensor event must be checked against the specific product’s support information. “The hub supports Matter” is not enough to conclude that the target platform can use every device and every feature connected to the hub.

Likewise, a version number cannot replace a feature list. A capability appearing in a version of the standard does not mean your device firmware, bridge, and platform have all implemented it. A Matter logo on a product page can be a clue about connection compatibility, but it cannot replace confirmation of specific features.

If a Feature Is Missing, Diagnose Before Resetting

You can troubleshoot in this order:

  1. Check the manufacturer’s app. If the feature is missing there too, first check the specific model, firmware, region, and conditions required for the feature. If it works there, focus on the external interface and target platform.
  2. Confirm which connection method you are using. Is the device connected directly through Matter, bridged through a hub, or integrated through a manufacturer account? These methods may offer different features.
  3. Check the exact device type and model. Do not search only for “switch support” or “light support.” Check the manufacturer’s information for that model and the platform’s restrictions for the corresponding device type.
  4. Check the intended interface. Is the feature merely absent from the device card, or is it also unavailable as an automation condition? Check voice control, manual control, and automation separately.
  5. Then decide whether to change the connection method. If official documentation clearly says the current method does not support the feature you need, repeated pairing will usually not add it. If necessary, choose a native integration with more complete feature support.

Resetting can help with some device-state or connection problems, but it means doing the pairing and configuration again. For a device that is reliably online but missing just one capability, checking the scope of support first is more targeted.

If you also run into pairing problems when adding a second platform, see “How Can One Matter Device Connect to Two Smart Home Platforms?”. Giving multiple platforms their own control permissions does not mean they will synchronize all rooms, scenes, and automation settings.

Before Buying, List the Features You Actually Need to Verify

“Does it support Matter?” is worth asking, but it is better to follow up with: “After connecting it through Matter to the platform I use, which of these specific features will work?”

The table below is a checklist template. Results need to be filled in for the particular model, firmware, platform, and connection method; they are not results from testing for this article.

Feature you need What to ask or verify Result
On/off control and status display Can you control it, and are status changes reported back? To verify/test
Brightness, color temperature, and color Which capabilities does the device itself have, and which controls does the target app expose? To verify/test
Dynamic scenes and proprietary effects Do they require the manufacturer’s app or a dedicated integration? To verify/test
Button and sensor events Are the required events exposed, and can they be used as automation conditions? To verify/test
Settings and firmware updates Where must settings and updates be managed? To verify/test
Automation execution Are both triggers and actions available, and what do they depend on? To verify/test

Whether an automation continues to run without an internet connection also needs to be tested separately. A feature appearing in the interface and whether it depends on the internet are different questions. See “Does Matter Still Work Without Internet?”.

When choosing a device, write down three operations you cannot compromise on and verify each one. That is usually more useful than looking only at the protocol logo on the box. Matter can help devices connect across platforms; whether the final experience meets your expectations still comes down to the specific device, connection method, and features available in practice.

References

Sources checked on November 8, 2026. Platform and firmware support can change; when buying or configuring a device, consult the latest information for the relevant model.

  1. Home Assistant: Matter integration documentation, including differences in feature support between Matter and product-native integrations, and the Hue example.
  2. Google Home: Supported Matter device types, including limitations for different control interfaces, bridges, and On/Off Light Switch devices.
  3. Philips Hue: Matter setup and support guide, used to check the relationship between the bridge and advanced features; it is not a basis for assuming that all advanced features are exposed through Matter.

AI-generated conceptual cover showing feature differences between integration paths; not an actual product interface or test result.

Discussion

Share a question or your experience. Comments appear after moderation. Your email is never displayed publicly. Comment privacy

Loading comments…