@matter/types 0.16.0-alpha.0-20251022-5a69ce65a → 0.16.0-alpha.0-20251027-17770fb28

package/src/clusters/access-control.ts

@@ -53,8 +53,8 @@ export namespace AccessControl {
          *
          * This feature is for a device that is managed by a service associated with the device vendor and which imposes
          * default access restrictions upon each new fabric added to it. This could arise, for example, if the device is
-         * managed by a service provider under contract to an end-user, in such a way that the manager of the device
-         * does not unconditionally grant universal access to all of a device’s functionality, even for fabric
+         * managed by a service provider under contract to an end-user, in such away that the manager of the device does
+         * not unconditionally grant universal access to all of a device’s functionality, even for fabric
          * administrators. For example, many Home Routers are managed by an Internet Service Provider (a service), and
          * these services often have a policy that requires them to obtain user consent before certain administrative
          * functions can be delegated to a third party (e.g., a fabric Administrator). These restrictions are expressed
@@ -87,10 +87,11 @@ export namespace AccessControl {
          * communication between external services and the user, and may take an unpredictable amount of time to
          * complete since an end-user may need to visit some resources, such as a mobile application or web site. A
          * FabricRestrictionReviewUpdate event will be generated by the device within a predictable time period of the
-         * ReviewFabricRestrictionsResponse (see ReviewFabricRestrictions for specification of this time period), and
-         * this event can be correlated with the ReviewFabricRestrictionsResponse using a token provided in both. The
-         * device may provide instructions or a Redirect URL in the FabricRestrictionReviewUpdate event in order to help
-         * the user access the features required for managing per-fabric restrictions.
+         * ReviewFabricRestrictionsResponse (see Section 9.10.8.1, “ReviewFabricRestrictions Command” for specification
+         * of this time period), and this event can be correlated with the ReviewFabricRestrictionsResponse using a
+         * token provided in both. The device may provide instructions or a Redirect URL in the
+         * FabricRestrictionReviewUpdate event in order to help the user access the features required for managing
+         * per-fabric restrictions.
          *
          * See Section 6.6.2, “Model” for a description of how access control is impacted by the ARL attribute.
          *
@@ -487,8 +488,8 @@ export namespace AccessControl {
          *   • The key-value pairs shall in the format name=<value> where name is the key name, and <value> is the
          *     contents of the value encoded with proper URL-encoded escaping.
          *
-         *   • If key MTcu is present, it shall have a value of "_" (i.e. MTcu=_). This is the "callback URL
-         *     (CallbackUrl) placeholder".
+         *   • If key MTcu is present, it shall have a value of "_" (i.e. MTcu=_). This is the "callback URL (Call
+         *     backUrl) placeholder".
          *
          *   • Any key whose name begins with MT not mentioned in the previous bullets shall be reserved for future use
          *     by this specification. Manufacturers shall NOT include query keys starting with MT in the
@@ -497,6 +498,8 @@ export namespace AccessControl {
          * Any other element in the ARLRequestFlowUrl query field not covered by the above rules, as well as the
          * fragment field (if present), shall remain including the order of query key/value pairs present.
          *
+         * ### Expansion of ARLRequestFlowUrl by client
+         *
          * Once the URL is obtained, it shall be expanded to form a final URL (ExpandedARLRequestFlowUrl) by proceeding
          * with the following substitution algorithm on the original ARLRequestFlowUrl:
          *
@@ -535,6 +538,8 @@ export namespace AccessControl {
          * field (if present), shall remain as provided by the client through embedding within the
          * ExpandedARLRequestFlowUrl, including the order of query key/value pairs present.
          *
+         * ### Expansion of CallbackUrl by the manufacturer custom flow
+         *
          * Once the CallbackUrl is obtained by the manufacturer flow, it may be expanded to form a final
          * ExpandedARLRequestCallbackUrl URL to be used by proceeding with the following substitution algorithm on the
          * provided CallbackUrl:
@@ -614,20 +619,16 @@ export namespace AccessControl {
     export interface FabricRestrictionReviewUpdateEvent extends TypeFromSchema<typeof TlvFabricRestrictionReviewUpdateEvent> {}
 
     /**
-     * ### Proxy View Value
-     *
-     * ### This value implicitly grants View privileges
-     *
      * @see {@link MatterSpecification.v141.Core} § 9.10.5.2
      */
     export enum AccessControlEntryPrivilege {
         /**
-         * Can read and observe all (except Access Control Cluster and as seen by a non-Proxy)
+         * Can read and observe all (except Access Control Cluster)
          */
         View = 1,
 
         /**
-         * Can read and observe all (as seen by a Proxy)
+         * @deprecated
          */
         ProxyView = 2,
 
@@ -652,7 +653,7 @@ export namespace AccessControl {
         /**
          * Manage privileges, and can observe and modify the Access Control Cluster
          *
-         * This value implicitly grants Manage, Operate, Proxy View & View privileges
+         * This value implicitly grants Manage, Operate & View privileges
          *
          * @see {@link MatterSpecification.v141.Core} § 9.10.5.2.3
          */
@@ -738,6 +739,8 @@ export namespace AccessControl {
          *
          * ### Subject ID shall be of type uint64 with semantics depending on the entry’s AuthMode as follows:
          *
+         * ### Subject Semantics
+         *
          * An empty subjects list indicates a wildcard; that is, this entry shall grant access to any Node that
          * successfully authenticates via AuthMode. The subjects list shall NOT be empty if the entry’s AuthMode is
          * PASE.
@@ -777,6 +780,8 @@ export namespace AccessControl {
          *
          * A target grants access based on the presence of fields as follows:
          *
+         * ### Target Semantics
+         *
          * An empty targets list indicates a wildcard: that is, this entry shall grant access to all cluster instances
          * on all endpoints on this Node.
          *
@@ -1004,7 +1009,7 @@ export namespace AccessControl {
             /**
              * This feature is for a device that is managed by a service associated with the device vendor and which
              * imposes default access restrictions upon each new fabric added to it. This could arise, for example, if
-             * the device is managed by a service provider under contract to an end-user, in such a way that the manager
+             * the device is managed by a service provider under contract to an end-user, in such away that the manager
              * of the device does not unconditionally grant universal access to all of a device’s functionality, even
              * for fabric administrators. For example, many Home Routers are managed by an Internet Service Provider (a
              * service), and these services often have a policy that requires them to obtain user consent before certain
@@ -1039,11 +1044,11 @@ export namespace AccessControl {
              * process may involve communication between external services and the user, and may take an unpredictable
              * amount of time to complete since an end-user may need to visit some resources, such as a mobile
              * application or web site. A FabricRestrictionReviewUpdate event will be generated by the device within a
-             * predictable time period of the ReviewFabricRestrictionsResponse (see ReviewFabricRestrictions for
-             * specification of this time period), and this event can be correlated with the
-             * ReviewFabricRestrictionsResponse using a token provided in both. The device may provide instructions or a
-             * Redirect URL in the FabricRestrictionReviewUpdate event in order to help the user access the features
-             * required for managing per-fabric restrictions.
+             * predictable time period of the ReviewFabricRestrictionsResponse (see Section 9.10.8.1,
+             * “ReviewFabricRestrictions Command” for specification of this time period), and this event can be
+             * correlated with the ReviewFabricRestrictionsResponse using a token provided in both. The device may
+             * provide instructions or a Redirect URL in the FabricRestrictionReviewUpdate event in order to help the
+             * user access the features required for managing per-fabric restrictions.
              *
              * See Section 6.6.2, “Model” for a description of how access control is impacted by the ARL attribute.
              *

package/src/clusters/account-login.ts

@@ -41,15 +41,15 @@ export namespace AccountLogin {
     export interface GetSetupPinRequest extends TypeFromSchema<typeof TlvGetSetupPinRequest> {}
 
     /**
-     * This message is sent in response to the GetSetupPIN command, and contains the Setup PIN code, or null when the
-     * account identified in the request does not match the active account of the running Content App.
+     * This message is sent in response to the GetSetupPIN command, and contains the Setup PIN, or null when the account
+     * identified in the request does not match the active account of the running Content App.
      *
      * @see {@link MatterSpecification.v141.Cluster} § 6.2.4.2
      */
     export const TlvGetSetupPinResponse = TlvObject({
         /**
-         * This field shall provide the setup PIN code as a text string at least 8 characters in length or empty string
-         * to indicate that the accounts do not match.
+         * This field shall provide the Setup PIN as a text string at least 8 characters in length or empty string to
+         * indicate that the accounts do not match.
          *
          * > [!NOTE]
          *
@@ -62,8 +62,8 @@ export namespace AccountLogin {
     });
 
     /**
-     * This message is sent in response to the GetSetupPIN command, and contains the Setup PIN code, or null when the
-     * account identified in the request does not match the active account of the running Content App.
+     * This message is sent in response to the GetSetupPIN command, and contains the Setup PIN, or null when the account
+     * identified in the request does not match the active account of the running Content App.
      *
      * @see {@link MatterSpecification.v141.Cluster} § 6.2.4.2
      */
@@ -83,11 +83,11 @@ export namespace AccountLogin {
         tempAccountIdentifier: TlvField(0, TlvString.bound({ minLength: 16, maxLength: 100 })),
 
         /**
-         * This field shall provide the setup PIN code as a text string at least 8 characters in length.
+         * This field shall provide the Setup PIN as a text string at least 8 characters in length.
          *
          * > [!NOTE]
          *
-         * > Newer cluster clients should be aware that AccountLogin cluster version 1 specified an 11 digit minimum
+         * > Newer cluster clients should be aware that AccountLogin cluster revision 1 specified an 11 digit minimum
          *   length.
          *
          * @see {@link MatterSpecification.v141.Cluster} § 6.2.4.3.2
@@ -165,13 +165,13 @@ export namespace AccountLogin {
         commands: {
             /**
              * The purpose of this command is to determine if the active user account of the given Content App matches
-             * the active user account of a given Commissionee, and when it does, return a Setup PIN code which can be
-             * used for password-authenticated session establishment (PASE) with the Commissionee.
+             * the active user account of a given Commissionee, and when it does, return a Setup PIN which can be used
+             * for password-authenticated session establishment (PASE) with the Commissionee.
              *
              * For example, a Video Player with a Content App Platform may invoke this command on one of its Content App
              * endpoints to facilitate commissioning of a Phone App made by the same vendor as the Content App. If the
-             * accounts match, then the Content App may return a setup code that can be used by the Video Player to
-             * commission the Phone App without requiring the user to physically input a setup code.
+             * accounts match, then the Content App may return a Setup PIN that can be used by the Video Player to
+             * commission the Phone App without requiring the user to physically input a Setup PIN.
              *
              * The account match is determined by the Content App using a method which is outside the scope of this
              * specification and will typically involve a central service which is in communication with both the
@@ -198,7 +198,7 @@ export namespace AccountLogin {
              * The Setup PIN is a character string so that it can accommodate different future formats, including
              * alpha-numeric encodings. For a Commissionee it shall be populated with the Manual Pairing Code (see
              * Manual Pairing Code section in [MatterCore]) encoded as a string (11 characters) or the Passcode portion
-             * of the Manual Pairing Code (when less than 11 characters) .
+             * of the Manual Pairing Code (when less than 11 characters).
              *
              * The server shall implement rate limiting to prevent brute force attacks. No more than 10 unique requests
              * in a 10 minute period shall be allowed; a command response status of FAILURE should sent for additional
@@ -220,7 +220,7 @@ export namespace AccountLogin {
 
             /**
              * The purpose of this command is to allow the Content App to assume the user account of a given
-             * Commissionee by leveraging the Setup PIN code input by the user during the commissioning process.
+             * Commissionee by leveraging the Setup PIN input by the user during the commissioning process.
              *
              * For example, a Video Player with a Content App Platform may invoke this command on one of its Content App
              * endpoints after the commissioning has completed of a Phone App made by the same vendor as the Content
@@ -248,12 +248,12 @@ export namespace AccountLogin {
              *
              * The Setup PIN for a Commissionee may be populated with the Manual Pairing Code encoded as a string of
              * decimal numbers (11 characters) or the Passcode portion of the Manual Pairing Code encoded as a string of
-             * decimal numbers (8 characters) .
+             * decimal numbers (8 characters).
              *
              * The server shall implement rate limiting to prevent brute force attacks. No more than 10 unique requests
              * in a 10 minute period shall be allowed; a command response status of FAILURE should sent for additional
              * commands received within the 10 minute period. Because access to this command is limited to nodes with
-             * Admin-level access, and the user is involved when obtaining the SetupPIN, there are in place multiple
+             * Admin-level access, and the user is involved when obtaining the Setup PIN, there are in place multiple
              * obstacles to successfully mounting a brute force attack. A Content App that supports this command shall
              * ensure that the Temporary Account Identifier used by its clients is not valid for more than 10 minutes.
              *

package/src/clusters/actions.ts

@@ -38,7 +38,8 @@ export namespace Actions {
          * voice controller could use "set" (to map to InstantAction) or "play" (to map to StartAction) to trigger such
          * actions.
          *
-         * Example: see examples 1 and 2.
+         * Example: see Section 9.14.8.1, “Example 1: Scene recall” and Section 9.14.8.2, “Example 2: Set dynamic light
+         * effect”.
          *
          * @see {@link MatterSpecification.v141.Core} § 9.14.4.2.1
          */
@@ -50,7 +51,7 @@ export namespace Actions {
          * Indicates an action which involves a sequence of events/states of the associated endpoints, such as a wake-up
          * experience.
          *
-         * Example: see example 4.
+         * Example: see Section 9.14.8.4, “Example 4: Wake-up routine”.
          *
          * @see {@link MatterSpecification.v141.Core} § 9.14.4.2.2
          */
@@ -60,7 +61,9 @@ export namespace Actions {
          * Control an automation (e.g. motion sensor controlling lights)
          *
          * Indications an automation (e.g. a motion sensor controlling lights, an alarm system) which can bee.g.
-         * started, stopped, paused, resumed. Example: see example 3.
+         * started, stopped, paused, resumed.
+         *
+         * Example: see Section 9.14.8.3, “Example 3: Pause sensor automation”.
          *
          * @see {@link MatterSpecification.v141.Core} § 9.14.4.2.3
          */
@@ -738,6 +741,8 @@ export namespace Actions {
 
         commands: {
             /**
+             * This command is used to trigger an instantaneous action.
+             *
              * This command triggers an action (state change) on the involved endpoints, in a "fire and forget" manner.
              * Afterwards, the action’s state shall be Inactive.
              *
@@ -748,6 +753,8 @@ export namespace Actions {
             instantAction: OptionalCommand(0x0, TlvInstantActionRequest, 0x0, TlvNoResponse),
 
             /**
+             * This command is used to trigger an instantaneous action with a transition over a given time.
+             *
              * It is recommended that, where possible (e.g., it is not possible for attributes with Boolean data type),
              * a gradual transition SHOULD take place from the old to the new state over this time period. However, the
              * exact transition is manufacturer dependent.
@@ -768,6 +775,8 @@ export namespace Actions {
             ),
 
             /**
+             * This command is used to trigger the commencement of an action.
+             *
              * This command triggers the commencement of an action on the involved endpoints. Afterwards, the action’s
              * state shall be Active.
              *
@@ -782,6 +791,8 @@ export namespace Actions {
             startAction: OptionalCommand(0x2, TlvStartActionRequest, 0x2, TlvNoResponse),
 
             /**
+             * This command is used to trigger the commencement of an action with a duration.
+             *
              * This command triggers the commencement of an action on the involved endpoints, and shall change the
              * action’s state to Active. After the specified Duration, the action will stop, and the action’s state
              * shall change to Inactive.
@@ -794,6 +805,8 @@ export namespace Actions {
             startActionWithDuration: OptionalCommand(0x3, TlvStartActionWithDurationRequest, 0x3, TlvNoResponse),
 
             /**
+             * This command is used to stop an action.
+             *
              * This command stops the ongoing action on the involved endpoints. Afterwards, the action’s state shall be
              * Inactive.
              *
@@ -804,6 +817,8 @@ export namespace Actions {
             stopAction: OptionalCommand(0x4, TlvStopActionRequest, 0x4, TlvNoResponse),
 
             /**
+             * This command is used to pause an action.
+             *
              * This command pauses an ongoing action, and shall change the action’s state to Paused.
              *
              * Example: pause a dynamic lighting effect (the lights stay at their current color) which was previously
@@ -814,6 +829,8 @@ export namespace Actions {
             pauseAction: OptionalCommand(0x5, TlvPauseActionRequest, 0x5, TlvNoResponse),
 
             /**
+             * This command is used to pause an action with a duration.
+             *
              * This command pauses an ongoing action, and shall change the action’s state to Paused. After the specified
              * Duration, the ongoing action will be automatically resumed. which shall change the action’s state to
              * Active.
@@ -832,6 +849,8 @@ export namespace Actions {
             pauseActionWithDuration: OptionalCommand(0x6, TlvPauseActionWithDurationRequest, 0x6, TlvNoResponse),
 
             /**
+             * This command is used to resume an action.
+             *
              * This command resumes a previously paused action, and shall change the action’s state to Active.
              *
              * The difference between ResumeAction and StartAction is that ResumeAction will continue the action from
@@ -845,6 +864,8 @@ export namespace Actions {
             resumeAction: OptionalCommand(0x7, TlvResumeActionRequest, 0x7, TlvNoResponse),
 
             /**
+             * This command is used to enable an action.
+             *
              * This command enables a certain action or automation. Afterwards, the action’s state shall be Active.
              *
              * Example: enable a motion sensor to control the lights in an area.
@@ -854,6 +875,8 @@ export namespace Actions {
             enableAction: OptionalCommand(0x8, TlvEnableActionRequest, 0x8, TlvNoResponse),
 
             /**
+             * This command is used to enable an action with a duration.
+             *
              * This command enables a certain action or automation, and shall change the action’s state to be Active.
              * After the specified Duration, the action or automation will stop, and the action’s state shall change to
              * Disabled.
@@ -867,6 +890,8 @@ export namespace Actions {
             enableActionWithDuration: OptionalCommand(0x9, TlvEnableActionWithDurationRequest, 0x9, TlvNoResponse),
 
             /**
+             * This command is used to disable an action.
+             *
              * This command disables a certain action or automation, and shall change the action’s state to Inactive.
              *
              * Example: disable a motion sensor to no longer control the lights in an area.
@@ -876,9 +901,12 @@ export namespace Actions {
             disableAction: OptionalCommand(0xa, TlvDisableActionRequest, 0xa, TlvNoResponse),
 
             /**
+             * This command is used to disable an action with a duration.
+             *
              * This command disables a certain action or automation, and shall change the action’s state to Disabled.
              * After the specified Duration, the action or automation will re-start, and the action’s state shall change
-             * to either Inactive or Active, depending on the actions (see examples 4 and 6).
+             * to either Inactive or Active, depending on the actions (see Section 9.14.8.4, “Example 4: Wake-up
+             * routine” and Section 9.14.8.6, “Example 6: Alarm system”).
              *
              * Example: disable a "wakeup" experience for a period of 1 week when going on holiday (to prevent them from
              * turning on in the morning while you’re not at home). After this period, the wakeup experience will
@@ -939,7 +967,10 @@ export namespace Actions {
     });
 
     /**
-     * This cluster provides a standardized way for a Node (typically a Bridge, but could be any Node) to expose
+     * This cluster provides a standardized way for a Node (typically a Bridge, but could be any Node) to expose logical
+     * grouping and actions.
+     *
+     * Specifically this cluster provides:
      *
      *   • Information about logical grouping of endpoints on the Node (example: lights in a room)
      *

package/src/clusters/administrator-commissioning.ts

@@ -107,7 +107,7 @@ export namespace AdministratorCommissioning {
         commissioningTimeout: TlvField(0, TlvUInt16),
 
         /**
-         * This field shall specify an ephemeral PAKE passcode verifier (see Section 3.10, “Password- Authenticated Key
+         * This field shall specify an ephemeral PAKE passcode verifier (see Section 3.10, “Password-Authenticated Key
          * Exchange (PAKE)”) computed by the existing Administrator to be used for this commissioning. The field is
          * concatenation of two values (w0 || L) shall be (CRYPTO_GROUP_SIZE_BYTES +
          * CRYPTO_PUBLIC_KEY_SIZE_BYTES)-octets long as detailed in Crypto_PAKEValues_Responder. It shall be derived
@@ -120,9 +120,9 @@ export namespace AdministratorCommissioning {
         pakePasscodeVerifier: TlvField(1, TlvByteString.bound({ length: 97 })),
 
         /**
-         * This field shall be used by the Node as the long discriminator for DNS-SD advertisement (see Commissioning
-         * Discriminator) for discovery by the new Administrator. The new Administrator can find and filter DNS-SD
-         * records by long discriminator to locate and initiate commissioning with the appropriate Node.
+         * This field shall be used by the Node as the long discriminator for DNS-SD advertisement (see Section 4.3.1.5,
+         * “TXT key for discriminator (D)”) for discovery by the new Administrator. The new Administrator can find and
+         * filter DNS-SD records by long discriminator to locate and initiate commissioning with the appropriate Node.
          *
          * @see {@link MatterSpecification.v141.Core} § 11.19.8.1.3
          */
@@ -146,8 +146,9 @@ export namespace AdministratorCommissioning {
          * specified in Section 3.9, “Password-Based Key Derivation Function (PBKDF)”, within the definition of the
          * Crypto_PBKDFParameterSet.
          *
-         * When a Node receives the Open Commissioning Window command, it shall begin advertising on DNS-SD as described
+         * When a Node receives the OpenCommissioningWindow command, it shall begin advertising on DNS-SD as described
          * in Section 4.3.1, “Commissionable Node Discovery” and for a time period as described in CommissioningTimeout.
+         *
          * When the command is received by a ICD, it shall enter into active mode. The ICD shall remain in Active Mode
          * as long as one of these conditions is met:
          *
@@ -303,7 +304,7 @@ export namespace AdministratorCommissioning {
             /**
              * When the WindowStatus attribute is not set to WindowNotOpen, this attribute shall indicate the
              * FabricIndex associated with the Fabric scoping of the Administrator that opened the window. This may be
-             * used to cross-reference in the Fabrics attribute of the Node Operational Credentials cluster.
+             * used to cross-reference in the Fabrics attribute of the Operational Credentials cluster.
              *
              * If, during an open commissioning window, the fabric for the Administrator that opened the window is
              * removed, then this attribute shall be set to null.
@@ -416,8 +417,8 @@ export namespace AdministratorCommissioning {
      * 5.6.2, “Basic Commissioning Method (BCM)” and Enhanced Commissioning which shall be supported and is described in
      * Section 5.6.3, “Enhanced Commissioning Method (ECM)”.
      *
-     * For the management of Operational Credentials and Trusted Root Certificates, the Node Operational Credentials
-     * cluster is used.
+     * For the management of Operational Credentials and Trusted Root Certificates, the Operational Credentials cluster
+     * is used.
      *
      * If the Administrator Commissioning Cluster server instance is present on an endpoint with the Root Node device
      * type in the Descriptor cluster DeviceTypeList, then:

package/src/clusters/air-quality.ts

@@ -128,7 +128,7 @@ export namespace AirQuality {
              *
              * @see {@link MatterSpecification.v141.Cluster} § 2.9.6.1
              */
-            airQuality: Attribute(0x0, TlvEnum<AirQualityEnum>(), { default: AirQualityEnum.Unknown })
+            airQuality: Attribute(0x0, TlvEnum<AirQualityEnum>())
         },
 
         /**

package/src/clusters/alarm-base.ts

@@ -177,7 +177,7 @@ export namespace AlarmBase {
         },
 
         name: "AlarmBase",
-        revision: 1,
+        revision: 2,
 
         attributes: {
             /**
@@ -218,7 +218,7 @@ export namespace AlarmBase {
 
         events: {
             /**
-             * This event shall be generated when one or more alarms change state, and shall have these fields:
+             * This event shall be generated when one or more alarms change state.
              *
              * @see {@link MatterSpecification.v141.Cluster} § 1.15.8.1
              */

package/src/clusters/application-launcher.ts

@@ -44,7 +44,8 @@ export namespace ApplicationLauncher {
      */
     export const TlvApplication = TlvObject({
         /**
-         * This field shall indicate the CSA-issued vendor ID for the catalog. The DIAL registry shall use value 0x0000.
+         * This field shall indicate the Connectivity Standards Alliance-issued vendor ID for the catalog. The DIAL
+         * registry shall use value 0x0000.
          *
          * Content App Platform providers will have their own catalog vendor ID (set to their own Vendor ID) and will
          * assign an ApplicationID to each Content App.
@@ -310,7 +311,8 @@ export namespace ApplicationLauncher {
         attributes: {
             /**
              * This attribute shall specify the list of supported application catalogs, where each entry in the list is
-             * the CSA-issued vendor ID for the catalog. The DIAL registry (see [DIAL Registry]) shall use value 0x0000.
+             * the Connectivity Standards Alliance-issued vendor ID for the catalog. The DIAL registry (see [DIAL
+             * Registry]) shall use value 0x0000.
              *
              * It is expected that Content App Platform providers will have their own catalog vendor ID (set to their
              * own Vendor ID) and will assign an ApplicationID to each Content App.
@@ -398,7 +400,9 @@ export namespace ApplicationLauncher {
              * constraints if any. The Status attribute shall be updated to ActiveHidden or Stopped, depending on the
              * action taken, on the Application Basic cluster of the Endpoint corresponding to the application on which
              * the action was taken. The Status attribute shall be updated on any other application whose Status may
-             * have changed as a result of this command. This command returns a Launcher Response.
+             * have changed as a result of this command.
+             *
+             * This command returns a Launcher Response.
              *
              * @see {@link MatterSpecification.v141.Cluster} § 6.4.7.3
              */

package/src/clusters/basic-information.ts

@@ -13,6 +13,7 @@ import {
     OptionalFixedAttribute,
     OptionalWritableAttribute,
     OptionalAttribute,
+    Attribute,
     Event,
     OptionalEvent
 } from "../cluster/Cluster.js";
@@ -274,7 +275,7 @@ export namespace BasicInformation {
      */
     export const TlvLeaveEvent = TlvObject({
         /**
-         * This field shall contain the local Fabric Index of the fabric which the node is about to leave.
+         * This field shall contain the local fabric-index of the fabric which the node is about to leave.
          *
          * @see {@link MatterSpecification.v141.Core} § 11.1.6.3.1
          */
@@ -315,7 +316,7 @@ export namespace BasicInformation {
     export const ClusterInstance = MutableCluster({
         id: 0x28,
         name: "BasicInformation",
-        revision: 4,
+        revision: 5,
 
         attributes: {
             /**
@@ -406,11 +407,10 @@ export namespace BasicInformation {
             hardwareVersionString: FixedAttribute(0x8, TlvString.bound({ minLength: 1, maxLength: 64 })),
 
             /**
-             * This attribute shall contain the current version number for the software running on this Node. The
-             * version number can be compared using a total ordering to determine if a version is logically newer than
-             * another one. A larger value of SoftwareVersion is newer than a lower value, from the perspective of
-             * software updates (see Section 11.20.3.3, “Availability of Software Images”). Nodes may query this field
-             * to determine the currently running version of software on another given Node.
+             * This attribute shall contain the current version number for the software running on this Node. A larger
+             * value of SoftwareVersion is newer than a lower value, from the perspective of software updates (see
+             * Section 11.20.3.3, “Availability of Software Images”). Nodes may query this field to determine the
+             * currently running version of software on another given Node.
              *
              * @see {@link MatterSpecification.v141.Core} § 11.1.5.10
              */
@@ -562,8 +562,7 @@ export namespace BasicInformation {
 
             /**
              * This attribute shall contain the current version number for the specification version this Node was
-             * certified against. The version number can be compared using a total ordering to determine if a version is
-             * logically newer than another one. A larger value of SpecificationVersion is newer than a lower value.
+             * certified against. A larger value of SpecificationVersion is newer than a lower value.
              *
              * Nodes may query this field to determine the currently supported version of the specification on another
              * given Node.
@@ -571,18 +570,18 @@ export namespace BasicInformation {
              * The format of this number is segmented as its four component bytes. Bit positions for the fields are as
              * follows:
              *
-             * For example, a SpecificationVersion value of 0x0102AA00 is composed of 4 version components, representing
-             * a version 1.2.170.0.
+             * For example, a SpecificationVersion value of 0x01040200 is composed of 4 version components, representing
+             * a version 1.4.2.0.
              *
              * In the example above:
              *
-             *   • Major version is the uppermost byte (0x01).
+             *   • Major version is the most significant byte (0x01).
              *
-             *   • Minor version is the following byte (0x02).
+             *   • Minor version is the second most significant byte (0x04).
              *
-             *   • Patch version is 170/0xAA.
+             *   • Dot version is the third most significant byte (0x02).
              *
-             *   • Reserved1 value is 0.
+             *   • Reserved1 value is the least significant byte (0x00).
              *
              * The initial revision (1.0) of this specification (1.0) was 0x01000000. Matter Spring 2024 release (1.3)
              * was 0x01030000.
@@ -609,7 +608,15 @@ export namespace BasicInformation {
              *
              * @see {@link MatterSpecification.v141.Core} § 11.1.5.23
              */
-            maxPathsPerInvoke: FixedAttribute(0x16, TlvUInt16.bound({ min: 1 }), { default: 1 })
+            maxPathsPerInvoke: FixedAttribute(0x16, TlvUInt16.bound({ min: 1 }), { default: 1 }),
+
+            /**
+             * This attribute shall contain the current version number for the configuration of the Node. A larger value
+             * of ConfigurationVersion shall indicate a newer configuration than a lower value.
+             *
+             * @see {@link MatterSpecification.v141.Core} § 11.1.5.24
+             */
+            configurationVersion: Attribute(0x18, TlvUInt32.bound({ min: 1 }), { persistent: true, default: 1 })
         },
 
         events: {
@@ -647,8 +654,6 @@ export namespace BasicInformation {
             leave: OptionalEvent(0x2, Priority.Info, TlvLeaveEvent),
 
             /**
-             * This event shall be supported if and only if the Reachable attribute is supported.
-             *
              * This event (when supported) shall be generated when there is a change in the Reachable attribute.
              *
              * Its main use case is in the derived Bridged Device Basic Information cluster.

package/src/clusters/boolean-state-configuration.ts

@@ -258,10 +258,10 @@ export namespace BooleanStateConfiguration {
             alarmsActive: Attribute(0x3, TlvBitmap(TlvUInt8, AlarmMode)),
 
             /**
-             * Indicates the alarm modes that will be emitted if the sensor is triggered.
+             * Indicates the alarm modes that will be emitted if the sensor is triggered. If an alarm mode is not
+             * supported, the bit indicating this alarm mode shall always be 0.
              *
-             * If an alarm mode is not supported, the bit indicating this alarm mode shall always be 0. A bit shall
-             * indicate whether the alarm mode is enabled or disabled:
+             * A bit shall indicate whether the alarm mode is enabled or disabled:
              *
              *   • 0 = Disabled
              *