@matter/types 0.13.0-alpha.0-20250311-3eb0af5f2 → 0.13.0-alpha.0-20250322-f085fa576

package/dist/esm/clusters/actions.d.ts

@@ -36,8 +36,8 @@ export declare namespace Actions {
         /**
          * A sequence of states with a certain time pattern
          *
-         * Indicates an action which involves a sequence of events/states of the associated endpoints, such as a
-         * wake-up experience.
+         * Indicates an action which involves a sequence of events/states of the associated endpoints, such as a wake-up
+         * experience.
          *
          * Example: see example 4.
          *
@@ -56,8 +56,8 @@ export declare namespace Actions {
         /**
          * Sequence that will run when something doesn’t happen
          *
-         * Indicates some action which the server will execute when a certain condition (which normally does not
-         * happen) is not met.
+         * Indicates some action which the server will execute when a certain condition (which normally does not happen)
+         * is not met.
          *
          * Example: lock the doors when the server’s system has detected no one is at home while the doors are in the
          * 'unlocked' state.
@@ -201,9 +201,9 @@ export declare namespace Actions {
          */
         endpointListId: import("../tlv/TlvObject.js").FieldType<number>;
         /**
-         * This field is a bitmap which shall be used to indicate which of the cluster’s commands are supported for
-         * this particular action, with a bit set to 1 for each supported command according to the table below. Other
-         * bits shall be set to 0.
+         * This field is a bitmap which shall be used to indicate which of the cluster’s commands are supported for this
+         * particular action, with a bit set to 1 for each supported command according to the table below. Other bits
+         * shall be set to 0.
          *
          * @see {@link MatterSpecification.v13.Core} § 9.14.4.6.5
          */
@@ -291,11 +291,11 @@ export declare namespace Actions {
         /**
          * User-configured group of endpoints where an endpoint can be in only one room
          *
-         * Is used for the situation where an endpoint can only be part of one such rooms (e.g. physical mapping).
-         * Using these exposed logical groups, a Matter controller who has a similar grouping concept can use it to
-         * place each endpoint (bridged device) in the right room automatically, without user having to redo that setup
-         * for each device in each system - both at first contact and upon later updates to the endpoints (e.g. user
-         * adds a bridged device or creates a new room).
+         * Is used for the situation where an endpoint can only be part of one such rooms (e.g. physical mapping). Using
+         * these exposed logical groups, a Matter controller who has a similar grouping concept can use it to place each
+         * endpoint (bridged device) in the right room automatically, without user having to redo that setup for each
+         * device in each system - both at first contact and upon later updates to the endpoints (e.g. user adds a
+         * bridged device or creates a new room).
          *
          * @see {@link MatterSpecification.v13.Core} § 9.14.4.5.2
          */
@@ -708,9 +708,9 @@ export declare namespace Actions {
                  */
                 endpointListId: import("../tlv/TlvObject.js").FieldType<number>;
                 /**
-                 * This field is a bitmap which shall be used to indicate which of the cluster’s commands are supported for
-                 * this particular action, with a bit set to 1 for each supported command according to the table below. Other
-                 * bits shall be set to 0.
+                 * This field is a bitmap which shall be used to indicate which of the cluster’s commands are supported for this
+                 * particular action, with a bit set to 1 for each supported command according to the table below. Other bits
+                 * shall be set to 0.
                  *
                  * @see {@link MatterSpecification.v13.Core} § 9.14.4.6.5
                  */
@@ -819,13 +819,13 @@ export declare namespace Actions {
              *
              *   • When used with a suffix of "/?a=" and the decimal value of ActionID for one of the actions, it may
              *     provide information about that particular action. This could be a deeplink to
-             *     manufacturer-app/website (associated somehow to the server node) with the information/edit-screen
-             *     for this action so that the user can view and update details of the action, e.g. edit the scene, or
+             *     manufacturer-app/website (associated somehow to the server node) with the information/edit-screen for
+             *     this action so that the user can view and update details of the action, e.g. edit the scene, or
              *     change the wake-up experience time period.
              *
              *     ◦ Example of SetupURL with suffix added: example://Actions/?a=12345 or
-             *       https://domain.example/Matter/bridgev1/Actions/?a=12345 for linking to specific info/editing of
-             *       the action with ActionID 0x3039.
+             *       https://domain.example/Matter/bridgev1/Actions/?a=12345 for linking to specific info/editing of the
+             *       action with ActionID 0x3039.
              *
              * @see {@link MatterSpecification.v13.Core} § 9.14.5.3
              */
@@ -928,18 +928,18 @@ export declare namespace Actions {
                 invokeId: import("../tlv/TlvObject.js").OptionalFieldType<number>;
             }>, void, any>;
             /**
-             * 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.
+             * 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.
              *
              * Example: pause a dynamic lighting effect (the lights stay at their current color) for 10 minutes
              * (Duration=600).
              *
-             * The difference between Pause/Resume and Disable/Enable is on the one hand semantic (the former is more
-             * of a transitionary nature while the latter is more permanent) and on the other hand these can be
-             * implemented slightly differently in the implementation of the action (e.g. a Pause would be
-             * automatically resumed after some hours or during a nightly reset, while an Disable would remain in
-             * effect until explicitly enabled again).
+             * The difference between Pause/Resume and Disable/Enable is on the one hand semantic (the former is more of
+             * a transitionary nature while the latter is more permanent) and on the other hand these can be implemented
+             * slightly differently in the implementation of the action (e.g. a Pause would be automatically resumed
+             * after some hours or during a nightly reset, while an Disable would remain in effect until explicitly
+             * enabled again).
              *
              * @see {@link MatterSpecification.v13.Core} § 9.14.6.7
              */
@@ -985,8 +985,8 @@ export declare namespace Actions {
              * Disabled.
              *
              * Example: enable a "presence mimicking" behavior for the lights in your home during a vacation; the
-             * Duration field is used to indicated the length of your absence from home. After that period, the
-             * presence mimicking behavior will no longer control these lights.
+             * Duration field is used to indicated the length of your absence from home. After that period, the presence
+             * mimicking behavior will no longer control these lights.
              *
              * @see {@link MatterSpecification.v13.Core} § 9.14.6.10
              */
@@ -1013,11 +1013,11 @@ export declare namespace Actions {
             }>, void, any>;
             /**
              * 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).
+             * 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).
              *
-             * 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
+             * 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
              * control the lights as before.
              *
              * @see {@link MatterSpecification.v13.Core} § 9.14.6.12
@@ -1150,14 +1150,14 @@ export declare namespace Actions {
      * After defining the attributes, commands and events for this cluster, and the associated data types, several
      * examples are provided to illustrate the capabilities of this cluster.
      *
-     * Actions can be defined in a flexible manner to suit the needs of the various nodes implementing this cluster.
-     * For each action, the commands available for that particular action are defined.
+     * Actions can be defined in a flexible manner to suit the needs of the various nodes implementing this cluster. For
+     * each action, the commands available for that particular action are defined.
      *
      * This cluster can be used to expose only the grouping of endpoints without any actions defined by populating the
      * EndpointList attribute accordingly and providing an empty list for ActionList.
      *
-     * The term 'action' in the description of this cluster should not be confused with the term 'action' as used in
-     * the Interaction Model.
+     * The term 'action' in the description of this cluster should not be confused with the term 'action' as used in the
+     * Interaction Model.
      *
      * @see {@link MatterSpecification.v13.Core} § 9.14
      */

package/dist/esm/clusters/actions.js

@@ -119,9 +119,9 @@ var Actions;
      */
     endpointListId: TlvField(3, TlvUInt16),
     /**
-     * This field is a bitmap which shall be used to indicate which of the cluster’s commands are supported for
-     * this particular action, with a bit set to 1 for each supported command according to the table below. Other
-     * bits shall be set to 0.
+     * This field is a bitmap which shall be used to indicate which of the cluster’s commands are supported for this
+     * particular action, with a bit set to 1 for each supported command according to the table below. Other bits
+     * shall be set to 0.
      *
      * @see {@link MatterSpecification.v13.Core} § 9.14.4.6.5
      */
@@ -331,13 +331,13 @@ var Actions;
        *
        *   • When used with a suffix of "/?a=" and the decimal value of ActionID for one of the actions, it may
        *     provide information about that particular action. This could be a deeplink to
-       *     manufacturer-app/website (associated somehow to the server node) with the information/edit-screen
-       *     for this action so that the user can view and update details of the action, e.g. edit the scene, or
+       *     manufacturer-app/website (associated somehow to the server node) with the information/edit-screen for
+       *     this action so that the user can view and update details of the action, e.g. edit the scene, or
        *     change the wake-up experience time period.
        *
        *     ◦ Example of SetupURL with suffix added: example://Actions/?a=12345 or
-       *       https://domain.example/Matter/bridgev1/Actions/?a=12345 for linking to specific info/editing of
-       *       the action with ActionID 0x3039.
+       *       https://domain.example/Matter/bridgev1/Actions/?a=12345 for linking to specific info/editing of the
+       *       action with ActionID 0x3039.
        *
        * @see {@link MatterSpecification.v13.Core} § 9.14.5.3
        */
@@ -415,18 +415,18 @@ var Actions;
        */
       pauseAction: OptionalCommand(5, Actions2.TlvPauseActionRequest, 5, TlvNoResponse),
       /**
-       * 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.
+       * 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.
        *
        * Example: pause a dynamic lighting effect (the lights stay at their current color) for 10 minutes
        * (Duration=600).
        *
-       * The difference between Pause/Resume and Disable/Enable is on the one hand semantic (the former is more
-       * of a transitionary nature while the latter is more permanent) and on the other hand these can be
-       * implemented slightly differently in the implementation of the action (e.g. a Pause would be
-       * automatically resumed after some hours or during a nightly reset, while an Disable would remain in
-       * effect until explicitly enabled again).
+       * The difference between Pause/Resume and Disable/Enable is on the one hand semantic (the former is more of
+       * a transitionary nature while the latter is more permanent) and on the other hand these can be implemented
+       * slightly differently in the implementation of the action (e.g. a Pause would be automatically resumed
+       * after some hours or during a nightly reset, while an Disable would remain in effect until explicitly
+       * enabled again).
        *
        * @see {@link MatterSpecification.v13.Core} § 9.14.6.7
        */
@@ -457,8 +457,8 @@ var Actions;
        * Disabled.
        *
        * Example: enable a "presence mimicking" behavior for the lights in your home during a vacation; the
-       * Duration field is used to indicated the length of your absence from home. After that period, the
-       * presence mimicking behavior will no longer control these lights.
+       * Duration field is used to indicated the length of your absence from home. After that period, the presence
+       * mimicking behavior will no longer control these lights.
        *
        * @see {@link MatterSpecification.v13.Core} § 9.14.6.10
        */
@@ -473,11 +473,11 @@ var Actions;
       disableAction: OptionalCommand(10, Actions2.TlvDisableActionRequest, 10, TlvNoResponse),
       /**
        * 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).
+       * 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).
        *
-       * 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
+       * 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
        * control the lights as before.
        *
        * @see {@link MatterSpecification.v13.Core} § 9.14.6.12

package/dist/esm/clusters/activated-carbon-filter-monitoring.d.ts

@@ -105,8 +105,8 @@ export declare namespace ActivatedCarbonFilterMonitoring {
     /**
      * This cluster supports all ActivatedCarbonFilterMonitoring features. It may support illegal feature combinations.
      *
-     * If you use this cluster you must manually specify which features are active and ensure the set of active
-     * features is legal per the Matter specification.
+     * If you use this cluster you must manually specify which features are active and ensure the set of active features
+     * is legal per the Matter specification.
      */
     const CompleteInstance: MutableCluster<{
         readonly id: 114;

package/dist/esm/clusters/administrator-commissioning.d.ts

@@ -117,16 +117,16 @@ export declare namespace AdministratorCommissioning {
          */
         iterations: import("../tlv/TlvObject.js").FieldType<number>;
         /**
-         * This field shall be used by the Node as the PAKE Salt associated with the ephemeral PAKE passcode verifier
-         * to be used for this commissioning, which shall be sent by the Node to the new Administrator’s software as
+         * This field shall be used by the Node as the PAKE Salt associated with the ephemeral PAKE passcode verifier to
+         * be used for this commissioning, which shall be sent by the Node to the new Administrator’s software as
          * response to the PBKDFParamRequest during PASE negotiation. The constraints on the value shall match those
          * 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 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:
+         * When a Node receives the Open Commissioning Window 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:
          *
          *   • A commissioning window is open.
          *
@@ -174,15 +174,15 @@ export declare namespace AdministratorCommissioning {
              * If a commissioning window is already currently open, this command shall fail with a cluster specific
              * status code of Busy.
              *
-             * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code
-             * of Busy, since it is likely that concurrent commissioning operations from multiple separate
-             * Commissioners are about to take place.
+             * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code of
+             * Busy, since it is likely that concurrent commissioning operations from multiple separate Commissioners
+             * are about to take place.
              *
              * In case of any other parameter error, this command shall fail with a status code of COMMAND_INVALID.
              *
-             * The commissioning into a new Fabric completes when the Node successfully receives a
-             * CommissioningComplete command, see Section 5.5, “Commissioning Flows”. The new Administrator shall
-             * discover the Node on the IP network using DNS-based Service Discovery (DNS-SD) for commissioning.
+             * The commissioning into a new Fabric completes when the Node successfully receives a CommissioningComplete
+             * command, see Section 5.5, “Commissioning Flows”. The new Administrator shall discover the Node on the IP
+             * network using DNS-based Service Discovery (DNS-SD) for commissioning.
              *
              * @see {@link MatterSpecification.v13.Core} § 11.19.8.2
              */
@@ -285,15 +285,15 @@ export declare namespace AdministratorCommissioning {
              * Administrator shall discover the Node on the IP network using DNS-based Service Discovery (DNS-SD) for
              * commissioning.
              *
-             * If any format or validity errors related to the PAKEPasscodeVerifier, Iterations or Salt arguments
-             * arise, this command shall fail with a cluster specific status code of PAKEParameterError.
+             * If any format or validity errors related to the PAKEPasscodeVerifier, Iterations or Salt arguments arise,
+             * this command shall fail with a cluster specific status code of PAKEParameterError.
              *
              * If a commissioning window is already currently open, this command shall fail with a cluster specific
              * status code of Busy.
              *
-             * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code
-             * of Busy, since it is likely that concurrent commissioning operations from multiple separate
-             * Commissioners are about to take place.
+             * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code of
+             * Busy, since it is likely that concurrent commissioning operations from multiple separate Commissioners
+             * are about to take place.
              *
              * In case of any other parameter error, this command shall fail with a status code of COMMAND_INVALID.
              *
@@ -341,16 +341,16 @@ export declare namespace AdministratorCommissioning {
                  */
                 iterations: import("../tlv/TlvObject.js").FieldType<number>;
                 /**
-                 * This field shall be used by the Node as the PAKE Salt associated with the ephemeral PAKE passcode verifier
-                 * to be used for this commissioning, which shall be sent by the Node to the new Administrator’s software as
+                 * This field shall be used by the Node as the PAKE Salt associated with the ephemeral PAKE passcode verifier to
+                 * be used for this commissioning, which shall be sent by the Node to the new Administrator’s software as
                  * response to the PBKDFParamRequest during PASE negotiation. The constraints on the value shall match those
                  * 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 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:
+                 * When a Node receives the Open Commissioning Window 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:
                  *
                  *   • A commissioning window is open.
                  *
@@ -398,15 +398,15 @@ export declare namespace AdministratorCommissioning {
                      * If a commissioning window is already currently open, this command shall fail with a cluster specific
                      * status code of Busy.
                      *
-                     * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code
-                     * of Busy, since it is likely that concurrent commissioning operations from multiple separate
-                     * Commissioners are about to take place.
+                     * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code of
+                     * Busy, since it is likely that concurrent commissioning operations from multiple separate Commissioners
+                     * are about to take place.
                      *
                      * In case of any other parameter error, this command shall fail with a status code of COMMAND_INVALID.
                      *
-                     * The commissioning into a new Fabric completes when the Node successfully receives a
-                     * CommissioningComplete command, see Section 5.5, “Commissioning Flows”. The new Administrator shall
-                     * discover the Node on the IP network using DNS-based Service Discovery (DNS-SD) for commissioning.
+                     * The commissioning into a new Fabric completes when the Node successfully receives a CommissioningComplete
+                     * command, see Section 5.5, “Commissioning Flows”. The new Administrator shall discover the Node on the IP
+                     * network using DNS-based Service Discovery (DNS-SD) for commissioning.
                      *
                      * @see {@link MatterSpecification.v13.Core} § 11.19.8.2
                      */
@@ -511,15 +511,15 @@ export declare namespace AdministratorCommissioning {
              * Administrator shall discover the Node on the IP network using DNS-based Service Discovery (DNS-SD) for
              * commissioning.
              *
-             * If any format or validity errors related to the PAKEPasscodeVerifier, Iterations or Salt arguments
-             * arise, this command shall fail with a cluster specific status code of PAKEParameterError.
+             * If any format or validity errors related to the PAKEPasscodeVerifier, Iterations or Salt arguments arise,
+             * this command shall fail with a cluster specific status code of PAKEParameterError.
              *
              * If a commissioning window is already currently open, this command shall fail with a cluster specific
              * status code of Busy.
              *
-             * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code
-             * of Busy, since it is likely that concurrent commissioning operations from multiple separate
-             * Commissioners are about to take place.
+             * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code of
+             * Busy, since it is likely that concurrent commissioning operations from multiple separate Commissioners
+             * are about to take place.
              *
              * In case of any other parameter error, this command shall fail with a status code of COMMAND_INVALID.
              *
@@ -567,16 +567,16 @@ export declare namespace AdministratorCommissioning {
                  */
                 iterations: import("../tlv/TlvObject.js").FieldType<number>;
                 /**
-                 * This field shall be used by the Node as the PAKE Salt associated with the ephemeral PAKE passcode verifier
-                 * to be used for this commissioning, which shall be sent by the Node to the new Administrator’s software as
+                 * This field shall be used by the Node as the PAKE Salt associated with the ephemeral PAKE passcode verifier to
+                 * be used for this commissioning, which shall be sent by the Node to the new Administrator’s software as
                  * response to the PBKDFParamRequest during PASE negotiation. The constraints on the value shall match those
                  * 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 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:
+                 * When a Node receives the Open Commissioning Window 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:
                  *
                  *   • A commissioning window is open.
                  *
@@ -624,15 +624,15 @@ export declare namespace AdministratorCommissioning {
                      * If a commissioning window is already currently open, this command shall fail with a cluster specific
                      * status code of Busy.
                      *
-                     * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code
-                     * of Busy, since it is likely that concurrent commissioning operations from multiple separate
-                     * Commissioners are about to take place.
+                     * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code of
+                     * Busy, since it is likely that concurrent commissioning operations from multiple separate Commissioners
+                     * are about to take place.
                      *
                      * In case of any other parameter error, this command shall fail with a status code of COMMAND_INVALID.
                      *
-                     * The commissioning into a new Fabric completes when the Node successfully receives a
-                     * CommissioningComplete command, see Section 5.5, “Commissioning Flows”. The new Administrator shall
-                     * discover the Node on the IP network using DNS-based Service Discovery (DNS-SD) for commissioning.
+                     * The commissioning into a new Fabric completes when the Node successfully receives a CommissioningComplete
+                     * command, see Section 5.5, “Commissioning Flows”. The new Administrator shall discover the Node on the IP
+                     * network using DNS-based Service Discovery (DNS-SD) for commissioning.
                      *
                      * @see {@link MatterSpecification.v13.Core} § 11.19.8.2
                      */
@@ -663,8 +663,8 @@ export declare namespace AdministratorCommissioning {
      * Commands and Responses needed for this purpose.
      *
      * There are two methods of commissioning, Basic Commissioning which may be supported and is described in Section
-     * 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)”.
+     * 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.
@@ -676,8 +676,8 @@ export declare namespace AdministratorCommissioning {
      *
      *   • The attributes shall indicate the state of the node that the Root Node endpoint is on.
      *
-     * If the Administrator Commissioning Cluster server instance is present on an endpoint with the Bridged Node
-     * device type in the Descriptor cluster DeviceTypeList, then:
+     * If the Administrator Commissioning Cluster server instance is present on an endpoint with the Bridged Node device
+     * type in the Descriptor cluster DeviceTypeList, then:
      *
      *   • The Commissioning Window shall be opened or closed on the node represented by the Bridged Node.
      *
@@ -802,15 +802,15 @@ export declare namespace AdministratorCommissioning {
              * Administrator shall discover the Node on the IP network using DNS-based Service Discovery (DNS-SD) for
              * commissioning.
              *
-             * If any format or validity errors related to the PAKEPasscodeVerifier, Iterations or Salt arguments
-             * arise, this command shall fail with a cluster specific status code of PAKEParameterError.
+             * If any format or validity errors related to the PAKEPasscodeVerifier, Iterations or Salt arguments arise,
+             * this command shall fail with a cluster specific status code of PAKEParameterError.
              *
              * If a commissioning window is already currently open, this command shall fail with a cluster specific
              * status code of Busy.
              *
-             * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code
-             * of Busy, since it is likely that concurrent commissioning operations from multiple separate
-             * Commissioners are about to take place.
+             * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code of
+             * Busy, since it is likely that concurrent commissioning operations from multiple separate Commissioners
+             * are about to take place.
              *
              * In case of any other parameter error, this command shall fail with a status code of COMMAND_INVALID.
              *
@@ -858,16 +858,16 @@ export declare namespace AdministratorCommissioning {
                  */
                 iterations: import("../tlv/TlvObject.js").FieldType<number>;
                 /**
-                 * This field shall be used by the Node as the PAKE Salt associated with the ephemeral PAKE passcode verifier
-                 * to be used for this commissioning, which shall be sent by the Node to the new Administrator’s software as
+                 * This field shall be used by the Node as the PAKE Salt associated with the ephemeral PAKE passcode verifier to
+                 * be used for this commissioning, which shall be sent by the Node to the new Administrator’s software as
                  * response to the PBKDFParamRequest during PASE negotiation. The constraints on the value shall match those
                  * 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 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:
+                 * When a Node receives the Open Commissioning Window 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:
                  *
                  *   • A commissioning window is open.
                  *
@@ -900,8 +900,8 @@ export declare namespace AdministratorCommissioning {
     /**
      * This cluster supports all AdministratorCommissioning features. It may support illegal feature combinations.
      *
-     * If you use this cluster you must manually specify which features are active and ensure the set of active
-     * features is legal per the Matter specification.
+     * If you use this cluster you must manually specify which features are active and ensure the set of active features
+     * is legal per the Matter specification.
      */
     interface Complete extends Identity<typeof CompleteInstance> {
     }

package/dist/esm/clusters/administrator-commissioning.js

@@ -87,16 +87,16 @@ var AdministratorCommissioning;
      */
     iterations: TlvField(3, TlvUInt32.bound({ min: 1e3, max: 1e5 })),
     /**
-     * This field shall be used by the Node as the PAKE Salt associated with the ephemeral PAKE passcode verifier
-     * to be used for this commissioning, which shall be sent by the Node to the new Administrator’s software as
+     * This field shall be used by the Node as the PAKE Salt associated with the ephemeral PAKE passcode verifier to
+     * be used for this commissioning, which shall be sent by the Node to the new Administrator’s software as
      * response to the PBKDFParamRequest during PASE negotiation. The constraints on the value shall match those
      * 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 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:
+     * When a Node receives the Open Commissioning Window 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:
      *
      *   • A commissioning window is open.
      *
@@ -123,15 +123,15 @@ var AdministratorCommissioning;
        * If a commissioning window is already currently open, this command shall fail with a cluster specific
        * status code of Busy.
        *
-       * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code
-       * of Busy, since it is likely that concurrent commissioning operations from multiple separate
-       * Commissioners are about to take place.
+       * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code of
+       * Busy, since it is likely that concurrent commissioning operations from multiple separate Commissioners
+       * are about to take place.
        *
        * In case of any other parameter error, this command shall fail with a status code of COMMAND_INVALID.
        *
-       * The commissioning into a new Fabric completes when the Node successfully receives a
-       * CommissioningComplete command, see Section 5.5, “Commissioning Flows”. The new Administrator shall
-       * discover the Node on the IP network using DNS-based Service Discovery (DNS-SD) for commissioning.
+       * The commissioning into a new Fabric completes when the Node successfully receives a CommissioningComplete
+       * command, see Section 5.5, “Commissioning Flows”. The new Administrator shall discover the Node on the IP
+       * network using DNS-based Service Discovery (DNS-SD) for commissioning.
        *
        * @see {@link MatterSpecification.v13.Core} § 11.19.8.2
        */
@@ -220,15 +220,15 @@ var AdministratorCommissioning;
        * Administrator shall discover the Node on the IP network using DNS-based Service Discovery (DNS-SD) for
        * commissioning.
        *
-       * If any format or validity errors related to the PAKEPasscodeVerifier, Iterations or Salt arguments
-       * arise, this command shall fail with a cluster specific status code of PAKEParameterError.
+       * If any format or validity errors related to the PAKEPasscodeVerifier, Iterations or Salt arguments arise,
+       * this command shall fail with a cluster specific status code of PAKEParameterError.
        *
        * If a commissioning window is already currently open, this command shall fail with a cluster specific
        * status code of Busy.
        *
-       * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code
-       * of Busy, since it is likely that concurrent commissioning operations from multiple separate
-       * Commissioners are about to take place.
+       * If the fail-safe timer is currently armed, this command shall fail with a cluster specific status code of
+       * Busy, since it is likely that concurrent commissioning operations from multiple separate Commissioners
+       * are about to take place.
        *
        * In case of any other parameter error, this command shall fail with a status code of COMMAND_INVALID.
        *

package/dist/esm/clusters/alarm-base.d.ts

@@ -188,8 +188,8 @@ export declare namespace AlarmBase {
              */
             readonly state: Attribute<number, any>;
             /**
-             * Indicates a bitmap where each bit shall represent whether or not an alarm is supported. The value of
-             * true means the alarm is supported, otherwise the alarm is not supported.
+             * Indicates a bitmap where each bit shall represent whether or not an alarm is supported. The value of true
+             * means the alarm is supported, otherwise the alarm is not supported.
              *
              * If an alarm is not supported, the corresponding bit in Mask, Latch, and State shall be false.
              *
@@ -342,8 +342,8 @@ export declare namespace AlarmBase {
              */
             readonly state: Attribute<number, any>;
             /**
-             * Indicates a bitmap where each bit shall represent whether or not an alarm is supported. The value of
-             * true means the alarm is supported, otherwise the alarm is not supported.
+             * Indicates a bitmap where each bit shall represent whether or not an alarm is supported. The value of true
+             * means the alarm is supported, otherwise the alarm is not supported.
              *
              * If an alarm is not supported, the corresponding bit in Mask, Latch, and State shall be false.
              *
@@ -438,8 +438,8 @@ export declare namespace AlarmBase {
     /**
      * This cluster supports all AlarmBase features. It may support illegal feature combinations.
      *
-     * If you use this cluster you must manually specify which features are active and ensure the set of active
-     * features is legal per the Matter specification.
+     * If you use this cluster you must manually specify which features are active and ensure the set of active features
+     * is legal per the Matter specification.
      */
     interface Complete extends Identity<typeof CompleteInstance> {
     }