Matter - smart home connectivity standard (formerly Project CHIP)

jkp · April 4, 2025, 3:01pm

the Z-Wave Alliance is now working on the structure and framework needed to bridge Matter and Z-Wave.

jkp · April 4, 2025, 6:00pm

jkp · April 9, 2025, 2:05pm

Paul_Oliver · April 10, 2025, 2:44pm

Paul_Oliver · April 10, 2025, 2:48pm

mocelet · April 10, 2025, 3:13pm

Regarding the all-Matter demo house…

These devices are either Matter-native or Matter-compatible via a bridge

pressing a button on the SmartThings Station opens the Samsung TV, while curtains close and secondary spotlights and TV backlighting set the ambiance, all controlled via Matter

That’s… not Matter? The button that starts it all is not Matter compatible and the TV is not Matter compatible either AFAIK.

JDRoberts · April 10, 2025, 6:12pm

Are you sure? I thought specifically the buttons on the SmartThings station are now exposed as some kind of matter switch. And the TV is also supposed to be exposed to matter. But maybe I’m wrong.

@Automated_House might know.

mocelet · April 10, 2025, 6:56pm

Would be news to me, I’ve never read anything about Samsung having Matter compatible devices other than hubs.

In CSA site there are no certified Samsung TVs or bridges either, just hub platforms and the app. Other brands like Philips or Hisense have certified TVs with the Media cluster, would have been a better showcase of Matter.

Andreas_Roedl · April 10, 2025, 7:02pm

Yep.

Automated_House · April 11, 2025, 1:57am

i’ve never heard of the Station button or any Samsung TVs being Matter devices.

JDRoberts · April 11, 2025, 4:25am

OK, maybe I just got confused.

h0ckeysk8er · April 11, 2025, 7:55pm

Andreas_Roedl · April 12, 2025, 3:37pm

Do you hate the XML files in the CSA compliance documents?

Just ask ChatGPT to convert them to a table!

XML

<?xml version="1.0" encoding="utf-8"?><!--
Autogenerated xml file - Version No:V_24_SVE_1.2
Generated date:2023-09-09 07:41:59
Cluster Name -Door lock Test Plan
XML PICS -Ref Document:
version master 0cb6035,
Draft
2023-09-08 12:46:22 -0700
--><clusterPICS xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="Generic-PICS-XML-Schema.xsd">
	<!--General cluster information-->
	<name>Door lock Test Plan</name>
	<clusterId> </clusterId>
	<picsRoot> </picsRoot>
	<!--Cluster role information-->
	<usage>
		<picsItem>
			<itemNumber>DRLK.S</itemNumber>
			<feature>Does the device implement the DoorLock cluster as a server?</feature>
			<reference>121.1. Role - allclusters.html[pdf]</reference>
			<status>O</status>
			<support>true</support>
		</picsItem>
		<picsItem>
			<itemNumber>DRLK.C</itemNumber>
			<feature>Does the device implement the DoorLock cluster as a client?</feature>
			<reference>121.1. Role - allclusters.html[pdf]</reference>
			<status>O</status>
			<support>false</support>
		</picsItem>
	</usage>
	<!--PIXIT-->
	<pixit>
		<pixitItem>
			<itemNumber>PIXIT.DRLK.WrongCodeEntryLimit</itemNumber>
			<feature>The number of incorrect Pin codes or RFID presentment attempts a user is allowed to enter before the lock will enter a lockout state.</feature>
			<reference>122. PIXIT Definition - allclusters.html[pdf]</reference>
			<status cond="DRLK.S.F00  OR  DRLK.S.F01">M</status>
			<support>0x00</support>
		</pixitItem>
		<pixitItem>
			<itemNumber>PIXIT.DRLK.UserCodeTemporaryDisableTime</itemNumber>
			<feature>The number of seconds that the lock shuts down following wrong code entry.</feature>
			<reference>122. PIXIT Definition - allclusters.html[pdf]</reference>
			<status cond="DRLK.S.F00  OR  DRLK.S.F01">M</status>
			<support>0x00</support>
		</pixitItem>
	</pixit>
	<!--Server side PICS-->
	<clusterSide type="Server">
		<!--Attributes PICS write-->
		<attributes>
			<picsItem>
				<itemNumber>DRLK.S.A0000</itemNumber>
				<feature>Does the device implement LockState attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0001</itemNumber>
				<feature>Does the device implement LockType attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0002</itemNumber>
				<feature>Does the device implement ActuatorEnabled attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0003</itemNumber>
				<feature>Does the device implement DoorState attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F05">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0004</itemNumber>
				<feature>Does the device implement DoorOpenEvents attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F05">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0005</itemNumber>
				<feature>Does the device implement DoorClosedEvents attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F05">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0006</itemNumber>
				<feature>Does the device implement OpenPeriod attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F05">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0011</itemNumber>
				<feature>Does the device implement NumberOfTotalUsersSupported attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F08">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0012</itemNumber>
				<feature>Does the device implement NumberOfPINUsersSupported attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F00">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0013</itemNumber>
				<feature>Does the device implement NumberOfRFIDUsersSupported attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F01">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0014</itemNumber>
				<feature>Does the device implement NumberOfWeekDaysSchedulesSupported attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F04">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0015</itemNumber>
				<feature>Does the device implement NumberOfYearDaysSchedulesSupported attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F0a">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0016</itemNumber>
				<feature>Does the device implement NumberOfHolidaySchedulesSupported attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F0b">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0017</itemNumber>
				<feature>Does the device implement MaxPINCodeLength attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F00">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0018</itemNumber>
				<feature>Does the device implement MinPINCodeLength attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F00">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0019</itemNumber>
				<feature>Does the device implement MaxRFIDCodeLength attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F01">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A001a</itemNumber>
				<feature>Does the device implement MinRFIDCodeLength attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F01">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A001b</itemNumber>
				<feature>Does the device implement CredentialRulesSupportattribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F08">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A001c</itemNumber>
				<feature>Does the device implement NumberOfCredentialsSupportedPerUser attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F08">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0021</itemNumber>
				<feature>Does the device implement Language attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0022</itemNumber>
				<feature>Does the device implement LEDSettings attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0023</itemNumber>
				<feature>Does the device implement AutoRelockTime attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0024</itemNumber>
				<feature>Does the device implement SoundVolume attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0025</itemNumber>
				<feature>Does the device implement OperatingModeattribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0026</itemNumber>
				<feature>Does the device implement SupportedOperatingModes attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0027</itemNumber>
				<feature>Does the device implement DefaultConfigurationRegister attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0028</itemNumber>
				<feature>Does the device implement EnableLocalProgramming attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0029</itemNumber>
				<feature>Does the device implement EnableOneTouchLocking attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A002a</itemNumber>
				<feature>Does the device implement EnableInsideStatusLED attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A002b</itemNumber>
				<feature>Does the device implement EnablePrivacyModeButton attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A002c</itemNumber>
				<feature>Does the device implement LocalProgrammingFeatures attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0030</itemNumber>
				<feature>Does the device implement WrongCodeEntryLimitattribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F00 OR DRLK.S.F01">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0031</itemNumber>
				<feature>Does the device implement UserCodedTemporaryDisableTime attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F00 OR DRLK.S.F01">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0032</itemNumber>
				<feature>Does the device implement SendPINOverTheAir attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="NOT DRLK.S.F08  AND  DRLK.S.F00">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0033</itemNumber>
				<feature>Does the device implement RequirePINForRemoteOperation attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F07  AND  DRLK.S.F00">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.A0035</itemNumber>
				<feature>Does the device implement ExpiringUserTimeOut attribute ?</feature>
				<reference>121.2.2. Attributes - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F08">O</status>
				<support>false</support>
			</picsItem>
		</attributes>
		<!--Events PICS write-->
		<events>
			<picsItem>
				<itemNumber>DRLK.S.E00</itemNumber>
				<feature>Does the device implement DoorLockAlarm event?</feature>
				<reference>121.2.4. Events - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.E01</itemNumber>
				<feature>Does the device implement DoorStateChange event?</feature>
				<reference>121.2.4. Events - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F05">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.E02</itemNumber>
				<feature>Does the device implement LockOperation event?</feature>
				<reference>121.2.4. Events - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.E03</itemNumber>
				<feature>Does the device implement LockOperationError event?</feature>
				<reference>121.2.4. Events - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.E04</itemNumber>
				<feature>Does the device implement LockUserChange event?</feature>
				<reference>121.2.4. Events - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F08">M</status>
				<support>false</support>
			</picsItem>
		</events>
		<!--Commands generated PICS write-->
		<commandsGenerated>
			<picsItem>
				<itemNumber>DRLK.S.C0c.Tx</itemNumber>
				<feature>Does the device implement transmitting of Get Week Day Schedule Response command?</feature>
				<reference>121.2.6. Commands generated - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F04">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C0f.Tx</itemNumber>
				<feature>Does the device implement transmitting of Get Year Day Response Schedule command?</feature>
				<reference>121.2.6. Commands generated - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F0a">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C12.Tx</itemNumber>
				<feature>Does the device implement transmitting of Get Holiday Schedule Response command?</feature>
				<reference>121.2.6. Commands generated - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F0b">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C1c.Tx</itemNumber>
				<feature>Does the device implement transmitting of Get User Response command?</feature>
				<reference>121.2.6. Commands generated - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F08">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C23.Tx</itemNumber>
				<feature>Does the device implement transmitting of Set Credential Response command?</feature>
				<reference>121.2.6. Commands generated - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F08">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C25.Tx</itemNumber>
				<feature>Does the device implement transmitting of Get Credential Response command?</feature>
				<reference>121.2.6. Commands generated - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F08">M</status>
				<support>false</support>
			</picsItem>
		</commandsGenerated>
		<!--Commands received PICS write-->
		<commandsReceived>
			<picsItem>
				<itemNumber>DRLK.S.C00.Rsp</itemNumber>
				<feature>Does the device implement receiving of Lock Door command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C01.Rsp</itemNumber>
				<feature>Does the device implement receiving of Unlock Door command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">M</status>
				<support>true</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C03.Rsp</itemNumber>
				<feature>Does the device implement receiving of Unlock with Timeout command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S">O</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C0b.Rsp</itemNumber>
				<feature>Does the device implement receiving of Set Week Day Schedule command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F04">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C0c.Rsp</itemNumber>
				<feature>Does the device implement receiving of Get Week Day Schedule command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F04">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C0d.Rsp</itemNumber>
				<feature>Does the device implement receiving of Clear Week Day Schedule command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F04">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C0e.Rsp</itemNumber>
				<feature>Does the device implement receiving of Set Year Day Schedule command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F0a">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C0f.Rsp</itemNumber>
				<feature>Does the device implement receiving of Get Year Day Schedule command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F0a">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C10.Rsp</itemNumber>
				<feature>Does the device implement receiving of Clear Year Day Schedule command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F0a">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C11.Rsp</itemNumber>
				<feature>Does the device implement receiving of Set Holiday Schedule command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F0b">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C12.Rsp</itemNumber>
				<feature>Does the device implement receiving of Get Holiday Schedule command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F0b">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C13.Rsp</itemNumber>
				<feature>Does the device implement receiving of Clear Holiday Schedule command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F0b">M</status>
				<support>false</support>
			</picsItem>
			<picsItem>
				<itemNumber>DRLK.S.C1a.Rsp</itemNumber>
				<feature>Does the device implement receiving of Set User command?</feature>
				<reference>121.2.5. Commands received - allclusters.html[pdf]</reference>
				<status cond="DRLK.S.F08">M

Table

Comprehensive Summary Table: Door Lock Test Plan (V_24_SVE_1.2)

1. General Information

Field	Value
Cluster Name	Door Lock Test Plan
Version	V_24_SVE_1.2
Generated Date	2023-09-09 07:41:59
Reference Document	version master 0cb6035

2. Cluster Role Implementation

Item Number	Feature	Support	Status
DRLK.S	Implements DoorLock cluster as a server	true	O
DRLK.C	Implements DoorLock cluster as a client	false	O

3. PIXIT Configuration

Item Number	Feature	Support	Status
PIXIT.DRLK.WrongCodeEntryLimit	Max wrong PIN/RFID attempts before lockout	0x00	M

PIXIT.DRLK.UserCodeTemporaryDisableTime	Lock shutdown duration after wrong code entry	0x00
M

4. Server Attributes Summary (Selected Highlights)

Attribute ID	Feature	Support	Status
A0000	LockState	true	M
A0001	LockType	true	M
A0002	ActuatorEnabled	true	M
A0003	DoorState	true	M*
A0025	OperatingMode	true	M
A0026	SupportedOperatingModes	true	M
A0004-A0035	Multiple advanced or optional attributes (e.g., schedules, users, RFID, audio)	mostly false	M/O
*Conditional Mandatory based on feature flags

5. Events

Event ID	Feature	Support	Status
E00	DoorLockAlarm	true	M
E01	DoorStateChange	true	M*
E02	LockOperation	true	M
E03	LockOperationError	true	M
E04	LockUserChange	false	M*

6. Commands - Generated by Server

Command ID	Feature	Support	Status
C0c.Tx	Get Week Day Schedule Response	false	M*
C0f.Tx	Get Year Day Response Schedule	false	M*
C12.Tx	Get Holiday Schedule Response	false	M*
C1c.Tx	Get User Response	false	M*
C23.Tx	Set Credential Response	false	M*
C25.Tx	Get Credential Response	false	M*

7. Commands - Received by Server

Command ID	Feature	Support	Status
C00.Rsp	Lock Door	true	M
C01.Rsp	Unlock Door	true	M
C03.Rsp	Unlock with Timeout	false	O
C27.Rsp	Unbolt Door	true	M*

8. Feature Flags

Feature ID	Feature Description	Support
F00	Supports PIN credentials	false
F01	Supports RFID credentials	false
F04	Supports weekday access schedules	false
F05	Supports door position sensor (e.g. open/closed)	true
F08	Supports user commands and database	false
F0a	Supports yearday access schedules	false
F0b	Supports holiday access schedules	false
F0c	Supports unbolting	true

9. Manual Controls (Server)

Manual ID	Feature Description	Support
M.SimulateNotFullyLocked	Simulate Not Fully Locked State	false
M.DetectLockJammed	Detect Lock Jammed State	false
M.OperatingModeAttributeWritable	Operating Mode attribute writable	true

10. Client-Side Summary

All features, commands, attributes, and events for client-side are unsupported (support=false).

TapioX · April 15, 2025, 1:17pm

Matter WiFi support has been added to Shelly Gen 3 devices.
Matter support has been added to the beta firmware.

Setting up Gen3 devices via Matter

jkp · April 21, 2025, 6:58pm

Andreas_Roedl · April 22, 2025, 2:03pm

Tapo Hub/Bridge H110 Matter 1.3 certified:

Water leak detector support added:

@mocelet

mocelet · April 22, 2025, 2:07pm

Just saw it! And they’ve completely removed the S200B smart button from the bridged devices . I don’t get why they don’t add the Switch cluster so it’s compatible with smart home platforms.

jkp · April 23, 2025, 11:18pm

Automated_House · April 24, 2025, 12:41am

hmm, I don’t know if FCC particularly cares what flavor of low powered 2.4ghz a device is using. Looking at the FCC docs for Aqara’s new wall switches that can run Thread or Zigbee wouldn’t be an interesting comparison.

Edit: The Aqara T2 bulb was easy to find.
The test doc titles DO call out Bluetooth, Zigbee and Thread separately

Andreas_Roedl · April 24, 2025, 6:58am

Not too long ago in an interview:

Philips Hue uses Zigbee and Matter will be integrated via the system’s bridge. Wouldn’t Thread be an alternative? Thread is part of the standard, and a Thread wireless network could do without a bridge.

Yianni: The Hue Bridge is not just a Wi-Fi to Zigbee translator. It has never been. It’s also the local intelligence of the system. It coordinates that your switches work well with the lights, it is what makes sure that the network is well managed. Entertainment streams, cloud services, automations, schedules … all that and more is managed by the bridge. Such a small, reliable “edge computer“ in the home is essential. Matter does not offer a solution for it. Building all the functionalities directly into lamps would make things much more complicated, and we don’t want to move them to the cloud. That is, even if we used Thread, we would still need a bridge.

Second: Mesh networking with Zigbee in an efficient and reliable way is really hard. We have been working on getting that to work well for a decade. And Thread at scale in the complexity of users homes is not yet proven. I’m a bit afraid of how open Thread will be. There will be many, many companies with many different implementations in the same network. So, I see a lot of risk, and we don’t have plans to build Thread light bulbs. I don’t say never, but we have very much a “wait and see“ approach towards it.

Topic		Replies	Views
[....Duplicate Thread....] Connected Things	1	639	December 19, 2019
Smarthings Homekit - new announcements? Devices & Integrations	3	1662	June 29, 2020
Connected home over IPv6 Devices & Integrations	9	2246	January 9, 2020
Coexistance of smartthings with google home Connected Things	2	401	May 8, 2023
New Device Purchases In The Context of Project CHIP Devices & Integrations iotfuture , iotindustry	3	696	November 28, 2020