What’s New in Matter 1.6.1? From Group Lighting Control to Muting the Doorbell

Explore Matter 1.6.1 Groupcast, chime controls and SDK fixes. Separate specification changes from product support, with checks for Matter bridges.

Tap “Turn on all the living room lights,” but the lights come on one after another, as though they are waiting in line. At night, you want to quiet the doorbell without turning off its visual alert.

These two small frustrations make something clearer than a string of protocol version numbers: there is still a gap between a smart home that “supports interoperability” and one that feels easy to use.

Matter 1.6.1 continues to address details like these. It does not add major new device categories. What deserves attention is the refinement of group control, expanded control of doorbell chimes, and reliability improvements in related software implementations.

A product labeled “Matter 1.6.1,” however, will not necessarily make these problems disappear at home. The specification defines capabilities, device firmware must implement them, and platforms must actually use them.

The opening describes hypothetical scenarios. This article is based on CSA official materials, official SDK release notes, and technical media reports reviewed as of November 7, 2026. No hands-on upgrade, group-control latency, or product compatibility testing was performed. Specification changes, SDK fixes, and platform features are discussed separately.

Concept illustration of grouped lighting and a doorbell chime in a home

AI-generated concept illustration; not a product interface, measured group-control timing or proof of compatibility.

1. First, Distinguish Matter 1.6, 1.6.1, and the SDK Version

As of the date this article’s sources were checked, the latest version listed on CSA’s official specifications download page was Matter 1.6.1, including the Core Specification, Application Cluster Specification, Device Library, and Standard Namespace Specification.[1]

Before that, CSA formally announced Matter 1.6 on June 17, 2026. Its highlights included complete NFC commissioning, Joint Fabric, and thermostat suggestions.[2] Those are major features of 1.6; discussing 1.6.1 now does not make them additions first introduced in this maintenance update.

Name What it represents Misunderstanding to avoid
Matter 1.6 A feature release Do not attribute all its new capabilities to 1.6.1
Matter 1.6.1 A subsequent specification revision, mainly refining existing capabilities A minor version can still affect group communication, device models, and implementation details
Official SDK v1.6.1.0 A release of a specific software implementation SDK fixes are not necessarily new specification requirements, and they do not mean vendors have updated their firmware

The official SDK release notes list changes involving Groupcast, access control, media-related data models, low-power device behavior, and numerous security and stability fixes.[3] These are useful to developers, but the entire development changelog should not be turned directly into a list of new user-facing features.

For example, adding simulated devices to reference applications does not mean the Matter specification added those major device categories at the same time.

2. Groupcast: The Point Is Not That Group Control Finally Exists, but That It Is Better Managed

Matter has supported group messages since its early versions. It would therefore be inaccurate to say that “Matter 1.6.1 supports controlling multiple lights with one command for the first time.”[4]

The more useful question is: How does a group in the controller interface actually work underneath?

One implementation sends a command to each device in turn. The interface shows a single button, but behind it the controller may be “sending one command to A, then one to B, then one to C.” Differences in device processing, network links, and scheduling can add up to lights appearing to turn on sequentially.

Another approach uses protocol-level group communication, with the sender addressing a group. But a group involves more than a name: it also involves membership, keys, permissions, and which devices send and listen.

Matter Alpha’s account of the releases says Groupcast appeared as a provisional feature in 1.6 and was made final in 1.6.1, alongside improvements to group management. The official SDK release notes also confirm updates related to Groupcast, auxiliary access control, and group key management.[3][4]

The report also describes a shared multicast-address mechanism: multiple groups can share a multicast address, with security group keys distinguishing the relevant communications, reducing the burden of maintaining a separate multicast address for every group.[4] Sharing an address does not mean every device can read and execute every group’s commands.

For users, the value is that platforms have a better basis for implementing genuine protocol-level group control. For gateway developers, it also means treating group management, permissions, and security state as one complete capability.

Several distinctions still matter:

  • A platform’s “lighting group” button does not prove it uses Groupcast underneath.
  • A controller sending a group command does not prove every device received and executed it.
  • Reducing the overhead of sending commands individually does not mean every light’s physical action happens at exactly the same time.

An upgrade should therefore not be promised to “eliminate all latency” or make “group control 100% successful.” Local wireless conditions, device implementations, and checks on state after failures still matter.

What should you check first? Confirm whether the control platform implements native Matter group communication and whether the target devices support the relevant mechanism. Then inspect logs to see how commands are actually sent. Compare individual and group control using the same devices, and check behavior when a device goes offline, rejoins a group, or has its permissions changed.

3. Muting the Doorbell: Turn Off the Sound Without Necessarily Turning Off Visual Alerts

A doorbell is not always one indivisible block of functionality. Its camera, button, indoor chime, and indicator light may be spread across different devices or endpoints.

Here, Chime refers to the chime device role. Changes to it should not be generalized into new capabilities for every doorbell or camera.

According to Matter Alpha’s account of 1.6.1, a chime can include an optional Speaker endpoint, allowing volume and mute controls to be expressed separately from visual alerts.[4] Another technical source also confirms the Chime update and mentions the ability to play preloaded notification sounds.[5]

This provides a standardized way to express a specific experience:

When someone rings the doorbell at night, the indoor chime stays silent, while a visual alert remains available if the device implements and provides one. Sound can be restored during the day.

Three things must line up: the chime hardware must have the relevant capability, its firmware must expose it, and the control platform must provide the corresponding operation. A certification version alone is not enough to conclude that a particular product has a volume slider.

Nor does this turn a doorbell chime into a music player. The change addresses control of notification sounds; it should not be extended to capabilities such as multiroom music playback.

What should you check first? Examine which endpoints and features the product actually exposes, then test “mute,” “turn off the entire device,” and “adjust volume” separately. If the product has a visual alert, confirm whether it continues to work as designed while muted and how the mute state is restored after a restart.

4. Developers Should Pay Closer Attention to These SDK Fixes

Some upgrades add no button to an app but affect whether the system runs reliably.

The official SDK v1.6.1.0 release notes record the following improvements.[3] These are changes to this SDK implementation. They do not mean every Matter product uses this code, or that other implementations necessarily had the same problems.

Area Example from the release notes What to check in a project
Sessions and access control Update a session’s peer address only after authentication succeeds; strengthen filtering of Fabric-related attributes Check data isolation and handling of malformed messages in multi-Fabric scenarios
Cameras and media transport Fix PushAV buffer, double-free, and partial-initialization issues Determine whether the project enables the relevant paths; regression-test playback, stream interruption, and recording
Intermittently Connected Devices (ICDs) Defer certain ActiveMode and Check-In behavior while the Thread network is disconnected Test state progression during network loss, reconnection, and commissioning
Transport and resource management BDX bounds checks and resource release on chunked-write error paths, among other changes Test failure and recovery paths for the transport features actually in use

The table is meant to help identify which code to read and which scenarios to test, not to label older devices “insecure.”

Before upgrading, record the SDK, vendor branch, commit version, and feature configuration used by the project, then compare them with the relevant changes. A vendor may already have backported a fix, or a project may not compile the affected module at all.

5. For a Bluetooth Mesh-to-Matter Gateway, Which Layer Needs to Be Upgraded?

For the bridging gateways we are concerned with, one of the most useful questions about 1.6.1 is whether group control works effectively across the entire path.

Consider this control path:

Matter controller → Matter bridge → Bluetooth Mesh network → actual lights.

Even if the upstream side uses Matter group communication, how the bridge maps that operation downstream still depends on its implementation. It might send a suitable downstream group command, or it might operate devices one by one. Group membership, addresses, security systems, and state feedback on the two sides cannot automatically be treated as the same system.

Upgrading the Matter SDK therefore does not automatically optimize Bluetooth Mesh group control. At a minimum, check:

  1. How the upstream side sends. Does the platform send multiple single-device commands, or an actual group operation?
  2. How the bridge maps the operation. Can it identify the correct target endpoints and downstream devices, and which group operations does it support?
  3. How the downstream side executes. Does it use a group address or send commands individually, and are there extra retries or duplicate traffic?
  4. How the result is confirmed. Does the state shown to the platform come from actual reports, query results, or optimistic updates?

This is another layer of the engineering problem discussed in “If One Light Fails to Turn On, Should the Whole Group Be Retried?”: the protocol provides better tools, but the system still needs to distinguish between sent, executed, and awaiting verification.

6. How Can You Tell Whether This Upgrade Is Useful to You?

If you are a user, ask the brand and platform three specific questions: Which new capability is supported? Which device models and firmware versions can use it? How do you operate it in the app? These are more likely to produce verifiable answers than asking only whether a product has “the latest Matter.”

If you are a developer, you can define upgrade acceptance criteria like these:

What to verify Evidence to retain at a minimum
Group control Actual communication method, participating devices, state reports, handling of offline devices, and results after rejoining a group
Chime Exposed endpoints and features, volume and mute tests, visual-alert behavior, and state restoration after a restart
Bridging gateway Mapping from Matter operations to downstream commands, and end-to-end state consistency
SDK update Pinned version and configuration, scope of relevant fixes, and regression records for failure and recovery paths

Complete NFC commissioning, Joint Fabric, and thermostat suggestions remain worth examining, but they were introduced in 1.6. They did not suddenly appear in this maintenance release.[2]

The practical value of Matter 1.6.1 comes down to which behavior improved and what evidence demonstrates it. Whether group control reduces unnecessary per-device operations, a doorbell can be muted independently as needed, and a gateway maintains a clear account of state when something goes wrong: these are the upgrades users ultimately experience.

Sources and Scope of Verification

Sources checked: 2026-11-07. “Latest version” refers to the version listed as of that date. This article did not review every provision of the 1.6.1 specifications. Its account of feature changes is based on the official announcement, SDK release notes, and clearly identified technical media reports consulted; media interpretations are not presented as the text of the specification.

  1. CSA: Specifications Download Directory. Confirms that four categories of Matter 1.6.1 specification documents are currently listed; the directory alone cannot establish the specific requirements of each feature.
  2. CSA: Official Matter 1.6 Announcement, 2026-06-17. Used to distinguish NFC commissioning, Joint Fabric, and thermostat suggestions introduced in 1.6, as well as the respective rollout timelines for vendors and platforms.
  3. Project CHIP: Official SDK v1.6.1.0 Release Notes. Used to check Groupcast, access control, group keys, media transport, ICDs, and implementation fixes; the full list of changes should not be treated as newly added formal device capabilities.
  4. Matter Alpha: Matter 1.6.1 finalizes Groupcast and adds chime sound controls, 2026-09-22. Technical media source for Groupcast becoming final, shared multicast addresses, and optional chime volume/mute mechanisms; its wording about “eliminating latency” is not adopted as a performance guarantee.
  5. matter-smarthome: Matter 1.6.1 Arrives on the First Platforms, 2026-10-21. Used to cross-check the maintenance-release characterization and the Groupcast and Chime updates; its account of platform progress is not treated as evidence that all platforms support these features today.

Discussion

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

Loading comments…