Matter - smart home connectivity standard (formerly Project CHIP)

orangebucket · March 19, 2025, 4:44pm

That would explain a lot. While it is valuable to bear in mind that multi-admin is going to multiply the traffic, two or three times next to nothing is still next to nothing so there must be something significant going on.

jkp · March 19, 2025, 8:34pm

Andrew_Bartlett · March 22, 2025, 2:04am

Article doesn’t mention Matter however HomeOS will obviously support it.

jkp · March 26, 2025, 10:35pm

mocelet · March 27, 2025, 8:41am

I’m curious about that IKEA button since there are two ways to expose buttons to Matter:

As momentary switch (Generic Switch), like native Matter smart buttons or the way they bridge Zigbee buttons.
As on/off control or scene controllers for lights like they do in Zigbee to bind to their Zigbee lights or some devices like the Tapo S200B are bridged.

If they pick the binding approach, which coming from IKEA would be expected, it won’t work in SmartThings: Support for Matter OnOff and Level clients?

They may as well implement both ways of operation so it is exposed as Generic Switch to work with any platform and also allows binding.

orangebucket · March 27, 2025, 9:01am

I can’t get a sense of scale with it. It would be quite a departure if it were mounted on a back box and permanently wired, but if it is AAA battery powered it would have to be quite a chunky monkey.

mocelet · March 27, 2025, 9:05am

I believe it’s a prototype because as you’ve noticed is too thin. If it’s a wireless button I would expect it to be like the existing RODRET or SOMRIG which have two buttons and already run on NiMH batteries.

Andreas_Roedl · March 27, 2025, 9:21am

github.com/SmartThingsCommunity/SmartThingsEdgeDrivers

Fix button configuration not occuring when a fingerprint exists for a button device

main ← fix/supported-button-events-issue-following-profile-switch

opened 09:27PM - 20 Mar 25 UTC

nickolas-deboom

+119 -111

# Type of Change - [ ] WWST Certification Request - If this is your fir…st time contributing code: - [ ] I have reviewed the README.md file - [ ] I have reviewed the CODE_OF_CONDUCT.md file - [ ] I have signed the CLA - [ ] I plan on entering a WWST Certification Request or have entered a request through the WWST Certification console at developer.smartthings.com - [x] Bug fix - [ ] New feature - [ ] Refactor # Checklist - [x] I have performed a self-review of my code - [x] I have commented my code in hard-to-understand areas - [x] I have verified my changes by testing with a device or have communicated a plan for testing - [x] I am adding new behavior, such as adding a sub-driver, and have added and run new unit tests to cover the new behavior # Description of Change When a fingerprint for a button device exists, and matches the profile that the switch driver would select for the device, the `info_changed` event occurs after attempting to update the profile, but since the profile did not change, `configure_buttons` is not called. This leads to the following issues: - `MultiPressMax` is not read and the driver reports multiple events for a double/multi button press ("Pressed" and "Double pressed" for example) - `supportedButtonValues` is not emitted, and the button capabilities display all of the possible values for this attribute rather than the ones supported by the device This change addresses this by always calling `configure_buttons` during button initialization. Then, inside `configure_buttons`, events are only emitted if the profile contains the corresponding component for a given endpoint. This is done to prevent errors if the profile has not been updated yet. If an event is not sent, that is okay because `configure_buttons` is called again in `info_changed` if a profile change occurs. # Summary of Completed Tests Updated unit tests and tested with Ikea button. The issue can be reproduced by creating a fingerprint for the device for the same profile that the driver would match the device to. `configure_buttons` would not run previously in this case, so `supportedButtonValues` would never be emitted and this attribute would display all of its possible values in the device card.

mocelet · March 27, 2025, 9:24am

That’s a fix for the Generic Switch cluster though, which most buttons use. Bindings are not supported in Matter by SmartThings and that’s why the Tapo S200B cannot work in SmartThings.

The switch cluster is used by the bridged IKEA buttons, because the purpose is exposing them to other platforms and run automations. But we’ll have to see how IKEA implements their own native Matter buttons. I don’t think they’ll want to lose features when changing protocols so they’ll probably use bindings matching what they do in Zigbee.

Andreas_Roedl · March 27, 2025, 9:33am

I always forget that they have a Matter bridge…

jkp · March 31, 2025, 3:40pm

First light with Matter Bindings from Lifx

jkp · March 31, 2025, 3:41pm

JDRoberts · March 31, 2025, 5:53pm

Availability varies depending on the region. The products are already widely available in the European Union. The US shop lists them, but is currently unable to deliver. Buyers in Canada and Latin America also have to be patient at the moment.

Automated_House · March 31, 2025, 6:00pm

I wonder what the new “matter door lock experience” is on SmartThings?

Andreas_Roedl · March 31, 2025, 6:17pm

Create a diff between:

github.com/SmartThingsCommunity/SmartThingsEdgeDrivers

drivers/SmartThings/matter-lock/src/init.lua

0942f1663

-- Copyright 2022 SmartThings
--
-- Licensed under the Apache License, Version 2.0 (the "License");
-- you may not use this file except in compliance with the License.
-- You may obtain a copy of the License at
--
--     http://www.apache.org/licenses/LICENSE-2.0
--
-- Unless required by applicable law or agreed to in writing, software
-- distributed under the License is distributed on an "AS IS" BASIS,
-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-- See the License for the specific language governing permissions and
-- limitations under the License.

local MatterDriver = require "st.matter.driver"
local clusters = require "st.matter.clusters"

local DoorLock = clusters.DoorLock
local PowerSource = clusters.PowerSource

This file has been truncated. show original

and:

github.com/SmartThingsCommunity/SmartThingsEdgeDrivers

drivers/SmartThings/matter-lock/src/new-matter-lock/init.lua

0942f1663

-- Copyright 2024 SmartThings
--
-- Licensed under the Apache License, Version 2.0 (the "License");
-- you may not use this file except in compliance with the License.
-- You may obtain a copy of the License at
--
--     http://www.apache.org/licenses/LICENSE-2.0
--
-- Unless required by applicable law or agreed to in writing, software
-- distributed under the License is distributed on an "AS IS" BASIS,
-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-- See the License for the specific language governing permissions and
-- limitations under the License.

local device_lib = require "st.device"
local capabilities = require "st.capabilities"
local clusters = require "st.matter.clusters"
local im = require "st.matter.interaction_model"
local utils = require "st.utils"
local lock_utils = require "lock_utils"

This file has been truncated. show original

orangebucket · March 31, 2025, 6:47pm

I have read that the SLGA is being sunset in favour of managing users in the device details. Presumably there will be some other things.

h0ckeysk8er · March 31, 2025, 8:38pm

Yes, the following locks are already using the new sub-driver:

local NEW_MATTER_LOCK_PRODUCTS = {
  {0x115f, 0x2802}, -- AQARA, U200
  {0x115f, 0x2801}, -- AQARA, U300
  {0x147F, 0x0001}, -- U-tec
  {0x1533, 0x0001}, -- eufy, E31
  {0x1533, 0x0002}, -- eufy, E30
  {0x1533, 0x0003}, -- eufy, C34
  {0x10E1, 0x2002}  -- VDA

The sub-driver also dynamically builds the appropriate profile based on querying the lock for the features it supports such as latch/unlatch, schedules, power source, etc. And for the locks that support users and pins, the lockCodes capability is replaced with:

  - id: lockUsers
    version: 1
  - id: lockCredentials

so that codes can be entered on the device details as you mentioned instead of SLGA.

mocelet · March 31, 2025, 8:49pm

Looking at the Matter compliance document of Luna, it looks like bindings only allow on/off commands as well as the Step Hue to cycle the colour. Can’t see support for controlling brightness for instance but maybe the compliance document is incomplete since there’s no Level control for the light either.

It also supports the Switch cluster so some buttons are exposed to Matter and can be used in automations (well, that’s on the video too).

Automated_House · April 1, 2025, 3:40pm

Anyone have screen shots of what managing lock users/codes from device details looks like?

Automated_House · April 1, 2025, 4:54pm

Here’s what a Matter robot vacuum looks like in SmartThings. ECOVACS X8 Pro Omni in my case. Not the prettiest implementation. No room settings like in the Apple Home app.

Topic		Replies	Views
Matter question Connected Things	63	4709	May 31, 2023
Samsung Developer Conference (SDC21) (October 26, 2021) Groups & Events	50	2945	October 27, 2021
Matter Device Support - ST platform Devices & Integrations thread , matter	169	9576	January 8, 2025
Does Z-Wave Have a Future? Connected Things	63	6639	August 17, 2024
Questions about Matter over WiFi Connected Things	21	1511	May 21, 2024

Related topics