@matter/types 0.13.1-alpha.0-20250508-047aa0277 → 0.13.1-alpha.0-20250509-28e1567e1

package/dist/esm/clusters/door-lock.d.ts

@@ -100,7 +100,6 @@ export declare namespace DoorLock {
          * CredentialOverTheAirAccess (COTA)
          *
          * If this feature is supported then the lock supports the ability to verify a credential provided in a
-         *
          * lock/unlock command. Currently the cluster only supports providing the PIN credential to the lock/unlock
          * commands. If this feature is supported then the PIN Credential feature shall also be supported.
          *
@@ -1009,10 +1008,9 @@ export declare namespace DoorLock {
         /**
          * This field shall indicate the next occupied index in the database for the credential type requested, which is
          * useful for quickly identifying occupied credential slots in the database. This shall NOT be null if there is
-         * at least one occupied entry after the requested credential index in the corresponding
-         *
-         * database and shall be null if there are no more occupied entries. The NextCredentialIndex reported shall NOT
-         * exceed the maximum number of credentials for a particular credential type.
+         * at least one occupied entry after the requested credential index in the corresponding database and shall be
+         * null if there are no more occupied entries. The NextCredentialIndex reported shall NOT exceed the maximum
+         * number of credentials for a particular credential type.
          *
          * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.5
          */
@@ -1028,10 +1026,10 @@ export declare namespace DoorLock {
          * Otherwise, the value of this field shall be the value of the relevant credential, as a 65-byte uncompressed
          * elliptic curve public key as defined in section 2.3.3 of SEC 1.
          *
-         * NOTE
+         * > [!NOTE]
          *
-         * Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
-         * Possession of the credential octet string does not allow operating the lock.
+         * > Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
+         *   Possession of the credential octet string does not allow operating the lock.
          *
          * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.6
          */
@@ -1679,12 +1677,12 @@ export declare namespace DoorLock {
      *
      * * Interface Operational: Yes, No or N/A
      *
-     * NOTE
+     * > [!NOTE]
      *
-     * For modes that disable the remote interface, the door lock shall respond to Lock, Unlock, Toggle, and Unlock with
-     * Timeout commands with a response status Failure and not take the action requested by those commands. The door
-     * lock shall NOT disable the radio or otherwise unbind or leave the network. It shall still respond to all other
-     * commands and requests.
+     * > For modes that disable the remote interface, the door lock shall respond to Lock, Unlock, Toggle, and Unlock
+     *   with Timeout commands with a response status Failure and not take the action requested by those commands. The
+     *   door lock shall NOT disable the radio or otherwise unbind or leave the network. It shall still respond to all
+     *   other commands and requests.
      *
      * @see {@link MatterSpecification.v14.Cluster} § 5.2.6.15
      */
@@ -3062,7 +3060,6 @@ export declare namespace DoorLock {
              * Fields used for different use cases:
              *
              * Return status is a global status code or a cluster-specific status code from the Status Codes table and
-             *
              * shall be one of the following values:
              *
              *   • SUCCESS, if setting User was successful.
@@ -3173,10 +3170,8 @@ export declare namespace DoorLock {
             /**
              * Retrieve user.
              *
-             * An InvokeResponse command shall be sent with an appropriate error
-             *
-             * COMMAND, etc.) as needed otherwise the GetUserResponse Command shall be sent implying a status of
-             * SUCCESS.
+             * An InvokeResponse command shall be sent with an appropriate error (e.g. FAILURE, INVALID_COMMAND, etc.)
+             * as needed otherwise the GetUserResponse Command shall be sent implying a status of SUCCESS.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.33
              */
@@ -3478,10 +3473,9 @@ export declare namespace DoorLock {
                 /**
                  * This field shall indicate the next occupied index in the database for the credential type requested, which is
                  * useful for quickly identifying occupied credential slots in the database. This shall NOT be null if there is
-                 * at least one occupied entry after the requested credential index in the corresponding
-                 *
-                 * database and shall be null if there are no more occupied entries. The NextCredentialIndex reported shall NOT
-                 * exceed the maximum number of credentials for a particular credential type.
+                 * at least one occupied entry after the requested credential index in the corresponding database and shall be
+                 * null if there are no more occupied entries. The NextCredentialIndex reported shall NOT exceed the maximum
+                 * number of credentials for a particular credential type.
                  *
                  * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.5
                  */
@@ -3497,10 +3491,10 @@ export declare namespace DoorLock {
                  * Otherwise, the value of this field shall be the value of the relevant credential, as a 65-byte uncompressed
                  * elliptic curve public key as defined in section 2.3.3 of SEC 1.
                  *
-                 * NOTE
+                 * > [!NOTE]
                  *
-                 * Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
-                 * Possession of the credential octet string does not allow operating the lock.
+                 * > Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
+                 *   Possession of the credential octet string does not allow operating the lock.
                  *
                  * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.6
                  */
@@ -4177,11 +4171,10 @@ export declare namespace DoorLock {
              * door lock server to send PINs over the air. This attribute determines the behavior of the server’s TX
              * operation. If it is false, then it is not ok for the device to send PIN in any messages over the air.
              *
-             * The PIN field within any door lock cluster message shall keep the first octet unchanged and
-             *
-             * masks the actual code by replacing with 0xFF. For example (PIN "1234" ): If the attribute value is True,
-             * 0x04 0x31 0x32 0x33 0x34 shall be used in the PIN field in any door lock cluster message payload. If the
-             * attribute value is False, 0x04 0xFF 0xFF 0xFF 0xFF shall be used.
+             * The PIN field within any door lock cluster message shall keep the first octet unchanged and masks the
+             * actual code by replacing with 0xFF. For example (PIN "1234" ): If the attribute value is True, 0x04 0x31
+             * 0x32 0x33 0x34 shall be used in the PIN field in any door lock cluster message payload. If the attribute
+             * value is False, 0x04 0xFF 0xFF 0xFF 0xFF shall be used.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.9.34
              */
@@ -4254,10 +4247,10 @@ export declare namespace DoorLock {
             /**
              * Clear out all PINs on the lock.
              *
-             * NOTE
+             * > [!NOTE]
              *
-             * On the server, the clear all PIN codes command SHOULD have the same effect as the ClearPINCode command
-             * with respect to the setting of user status, user type and schedules.
+             * > On the server, the clear all PIN codes command SHOULD have the same effect as the ClearPINCode command
+             *   with respect to the setting of user status, user type and schedules.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.8
              */
@@ -4324,13 +4317,13 @@ export declare namespace DoorLock {
              * applies to the sum of the number of AliroEvictableEndpointKey credentials and the number of
              * AliroNonEvictableEndpointKey credentials.
              *
-             * NOTE
+             * > [!NOTE]
              *
-             * The credential indices used for these two credential types are independent of each other, similar to all
-             * other credential types. As long as NumberOfAliroEndpointKeysSupported is at least 2 a client could add a
-             * credential of type AliroEvictableEndpointKey at any index from 1 to NumberOfAliroEndpointKeysSupported
-             * and also add a credential of type AliroNonEvictableEndpointKey at the same index, and both credentials
-             * would exist on the server.
+             * > The credential indices used for these two credential types are independent of each other, similar to
+             *   all other credential types. As long as NumberOfAliroEndpointKeysSupported is at least 2 a client could
+             *   add a credential of type AliroEvictableEndpointKey at any index from 1 to
+             *   NumberOfAliroEndpointKeysSupported and also add a credential of type AliroNonEvictableEndpointKey at
+             *   the same index, and both credentials would exist on the server.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.9.46
              */
@@ -4373,11 +4366,11 @@ export declare namespace DoorLock {
              * This command allows clearing an existing Aliro Reader configuration for the lock. Administrators shall
              * NOT clear an Aliro Reader configuration without explicit user permission.
              *
-             * NOTE
+             * > [!NOTE]
              *
-             * Using this command will revoke the ability of all existing Aliro user devices that have the old
-             * verification key to interact with the lock. This effect is not restricted to a single fabric or otherwise
-             * scoped in any way.
+             * > Using this command will revoke the ability of all existing Aliro user devices that have the old
+             *   verification key to interact with the lock. This effect is not restricted to a single fabric or
+             *   otherwise scoped in any way.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.43
              */
@@ -4604,10 +4597,10 @@ export declare namespace DoorLock {
              * an optional code for the lock. The door lock may require a code depending on the value of the
              * RequirePINForRemoteOperation attribute.
              *
-             * NOTE
+             * > [!NOTE]
              *
-             * If the attribute AutoRelockTime is supported, the lock will transition to the locked state when the auto
-             * relock time has expired.
+             * > If the attribute AutoRelockTime is supported, the lock will transition to the locked state when the
+             *   auto relock time has expired.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.41
              */
@@ -4714,7 +4707,6 @@ export declare namespace DoorLock {
              * CredentialOverTheAirAccess
              *
              * If this feature is supported then the lock supports the ability to verify a credential provided in a
-             *
              * lock/unlock command. Currently the cluster only supports providing the PIN credential to the lock/unlock
              * commands. If this feature is supported then the PIN Credential feature shall also be supported.
              *
@@ -4841,7 +4833,7 @@ export declare namespace DoorLock {
              */
             readonly soundVolume: OptionalWritableAttribute<SoundVolume, any>;
             /**
-             * Indicates the current operating mode of the lock as defined in OperatingModeEnum.
+             * This attribute shall indicate the current operating mode of the lock as defined in OperatingModeEnum.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.9.24
              */
@@ -4881,10 +4873,8 @@ export declare namespace DoorLock {
             }>, any>;
             /**
              * Indicates the default configurations as they are physically set on the device (example: hardware dip
-             * switch setting, etc…) and represents the default setting for some of the
-             *
-             * attributes within this cluster (for example: LED, Auto Lock, Sound Volume, and Operating Mode
-             * attributes).
+             * switch setting, etc…) and represents the default setting for some of the attributes within this cluster
+             * (for example: LED, Auto Lock, Sound Volume, and Operating Mode attributes).
              *
              * This is a read-only attribute and is intended to allow clients to determine what changes may need to be
              * made without having to query all the included attributes. It may be beneficial for the clients to know
@@ -5132,10 +5122,10 @@ export declare namespace DoorLock {
              * lock. The door lock may require a code depending on the value of the RequirePINForRemoteOperation
              * attribute.
              *
-             * NOTE
+             * > [!NOTE]
              *
-             * If the attribute AutoRelockTime is supported the lock will transition to the locked state when the auto
-             * relock time has expired.
+             * > If the attribute AutoRelockTime is supported the lock will transition to the locked state when the auto
+             *   relock time has expired.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.2
              */
@@ -5211,9 +5201,8 @@ export declare namespace DoorLock {
              *     ◦ shall generate a LockOperation event of LockOperationType Unlatch when it is actuated from the
              *       outside.
              *
-             *     ◦ may generate a LockOperation event of LockOperationType Unlatch when it is actuated
-             *
-             * from the inside.
+             *     ◦ may generate a LockOperation event of LockOperationType Unlatch when it is actuated from the
+             *       inside.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.11.3
              */
@@ -5464,7 +5453,6 @@ export declare namespace DoorLock {
                      * Fields used for different use cases:
                      *
                      * Return status is a global status code or a cluster-specific status code from the Status Codes table and
-                     *
                      * shall be one of the following values:
                      *
                      *   • SUCCESS, if setting User was successful.
@@ -5575,10 +5563,8 @@ export declare namespace DoorLock {
                     /**
                      * Retrieve user.
                      *
-                     * An InvokeResponse command shall be sent with an appropriate error
-                     *
-                     * COMMAND, etc.) as needed otherwise the GetUserResponse Command shall be sent implying a status of
-                     * SUCCESS.
+                     * An InvokeResponse command shall be sent with an appropriate error (e.g. FAILURE, INVALID_COMMAND, etc.)
+                     * as needed otherwise the GetUserResponse Command shall be sent implying a status of SUCCESS.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.33
                      */
@@ -5880,10 +5866,9 @@ export declare namespace DoorLock {
                         /**
                          * This field shall indicate the next occupied index in the database for the credential type requested, which is
                          * useful for quickly identifying occupied credential slots in the database. This shall NOT be null if there is
-                         * at least one occupied entry after the requested credential index in the corresponding
-                         *
-                         * database and shall be null if there are no more occupied entries. The NextCredentialIndex reported shall NOT
-                         * exceed the maximum number of credentials for a particular credential type.
+                         * at least one occupied entry after the requested credential index in the corresponding database and shall be
+                         * null if there are no more occupied entries. The NextCredentialIndex reported shall NOT exceed the maximum
+                         * number of credentials for a particular credential type.
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.5
                          */
@@ -5899,10 +5884,10 @@ export declare namespace DoorLock {
                          * Otherwise, the value of this field shall be the value of the relevant credential, as a 65-byte uncompressed
                          * elliptic curve public key as defined in section 2.3.3 of SEC 1.
                          *
-                         * NOTE
+                         * > [!NOTE]
                          *
-                         * Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
-                         * Possession of the credential octet string does not allow operating the lock.
+                         * > Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
+                         *   Possession of the credential octet string does not allow operating the lock.
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.6
                          */
@@ -6618,11 +6603,10 @@ export declare namespace DoorLock {
                      * door lock server to send PINs over the air. This attribute determines the behavior of the server’s TX
                      * operation. If it is false, then it is not ok for the device to send PIN in any messages over the air.
                      *
-                     * The PIN field within any door lock cluster message shall keep the first octet unchanged and
-                     *
-                     * masks the actual code by replacing with 0xFF. For example (PIN "1234" ): If the attribute value is True,
-                     * 0x04 0x31 0x32 0x33 0x34 shall be used in the PIN field in any door lock cluster message payload. If the
-                     * attribute value is False, 0x04 0xFF 0xFF 0xFF 0xFF shall be used.
+                     * The PIN field within any door lock cluster message shall keep the first octet unchanged and masks the
+                     * actual code by replacing with 0xFF. For example (PIN "1234" ): If the attribute value is True, 0x04 0x31
+                     * 0x32 0x33 0x34 shall be used in the PIN field in any door lock cluster message payload. If the attribute
+                     * value is False, 0x04 0xFF 0xFF 0xFF 0xFF shall be used.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.9.34
                      */
@@ -6695,10 +6679,10 @@ export declare namespace DoorLock {
                     /**
                      * Clear out all PINs on the lock.
                      *
-                     * NOTE
+                     * > [!NOTE]
                      *
-                     * On the server, the clear all PIN codes command SHOULD have the same effect as the ClearPINCode command
-                     * with respect to the setting of user status, user type and schedules.
+                     * > On the server, the clear all PIN codes command SHOULD have the same effect as the ClearPINCode command
+                     *   with respect to the setting of user status, user type and schedules.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.8
                      */
@@ -6768,13 +6752,13 @@ export declare namespace DoorLock {
                      * applies to the sum of the number of AliroEvictableEndpointKey credentials and the number of
                      * AliroNonEvictableEndpointKey credentials.
                      *
-                     * NOTE
+                     * > [!NOTE]
                      *
-                     * The credential indices used for these two credential types are independent of each other, similar to all
-                     * other credential types. As long as NumberOfAliroEndpointKeysSupported is at least 2 a client could add a
-                     * credential of type AliroEvictableEndpointKey at any index from 1 to NumberOfAliroEndpointKeysSupported
-                     * and also add a credential of type AliroNonEvictableEndpointKey at the same index, and both credentials
-                     * would exist on the server.
+                     * > The credential indices used for these two credential types are independent of each other, similar to
+                     *   all other credential types. As long as NumberOfAliroEndpointKeysSupported is at least 2 a client could
+                     *   add a credential of type AliroEvictableEndpointKey at any index from 1 to
+                     *   NumberOfAliroEndpointKeysSupported and also add a credential of type AliroNonEvictableEndpointKey at
+                     *   the same index, and both credentials would exist on the server.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.9.46
                      */
@@ -6817,11 +6801,11 @@ export declare namespace DoorLock {
                      * This command allows clearing an existing Aliro Reader configuration for the lock. Administrators shall
                      * NOT clear an Aliro Reader configuration without explicit user permission.
                      *
-                     * NOTE
+                     * > [!NOTE]
                      *
-                     * Using this command will revoke the ability of all existing Aliro user devices that have the old
-                     * verification key to interact with the lock. This effect is not restricted to a single fabric or otherwise
-                     * scoped in any way.
+                     * > Using this command will revoke the ability of all existing Aliro user devices that have the old
+                     *   verification key to interact with the lock. This effect is not restricted to a single fabric or
+                     *   otherwise scoped in any way.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.43
                      */
@@ -7055,10 +7039,10 @@ export declare namespace DoorLock {
                      * an optional code for the lock. The door lock may require a code depending on the value of the
                      * RequirePINForRemoteOperation attribute.
                      *
-                     * NOTE
+                     * > [!NOTE]
                      *
-                     * If the attribute AutoRelockTime is supported, the lock will transition to the locked state when the auto
-                     * relock time has expired.
+                     * > If the attribute AutoRelockTime is supported, the lock will transition to the locked state when the
+                     *   auto relock time has expired.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.41
                      */
@@ -7190,7 +7174,6 @@ export declare namespace DoorLock {
                  * CredentialOverTheAirAccess
                  *
                  * If this feature is supported then the lock supports the ability to verify a credential provided in a
-                 *
                  * lock/unlock command. Currently the cluster only supports providing the PIN credential to the lock/unlock
                  * commands. If this feature is supported then the PIN Credential feature shall also be supported.
                  *
@@ -7317,7 +7300,7 @@ export declare namespace DoorLock {
                  */
                 readonly soundVolume: OptionalWritableAttribute<SoundVolume, any>;
                 /**
-                 * Indicates the current operating mode of the lock as defined in OperatingModeEnum.
+                 * This attribute shall indicate the current operating mode of the lock as defined in OperatingModeEnum.
                  *
                  * @see {@link MatterSpecification.v14.Cluster} § 5.2.9.24
                  */
@@ -7357,10 +7340,8 @@ export declare namespace DoorLock {
                 }>, any>;
                 /**
                  * Indicates the default configurations as they are physically set on the device (example: hardware dip
-                 * switch setting, etc…) and represents the default setting for some of the
-                 *
-                 * attributes within this cluster (for example: LED, Auto Lock, Sound Volume, and Operating Mode
-                 * attributes).
+                 * switch setting, etc…) and represents the default setting for some of the attributes within this cluster
+                 * (for example: LED, Auto Lock, Sound Volume, and Operating Mode attributes).
                  *
                  * This is a read-only attribute and is intended to allow clients to determine what changes may need to be
                  * made without having to query all the included attributes. It may be beneficial for the clients to know
@@ -7608,10 +7589,10 @@ export declare namespace DoorLock {
                  * lock. The door lock may require a code depending on the value of the RequirePINForRemoteOperation
                  * attribute.
                  *
-                 * NOTE
+                 * > [!NOTE]
                  *
-                 * If the attribute AutoRelockTime is supported the lock will transition to the locked state when the auto
-                 * relock time has expired.
+                 * > If the attribute AutoRelockTime is supported the lock will transition to the locked state when the auto
+                 *   relock time has expired.
                  *
                  * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.2
                  */
@@ -7687,9 +7668,8 @@ export declare namespace DoorLock {
                  *     ◦ shall generate a LockOperation event of LockOperationType Unlatch when it is actuated from the
                  *       outside.
                  *
-                 *     ◦ may generate a LockOperation event of LockOperationType Unlatch when it is actuated
-                 *
-                 * from the inside.
+                 *     ◦ may generate a LockOperation event of LockOperationType Unlatch when it is actuated from the
+                 *       inside.
                  *
                  * @see {@link MatterSpecification.v14.Cluster} § 5.2.11.3
                  */
@@ -7940,7 +7920,6 @@ export declare namespace DoorLock {
                          * Fields used for different use cases:
                          *
                          * Return status is a global status code or a cluster-specific status code from the Status Codes table and
-                         *
                          * shall be one of the following values:
                          *
                          *   • SUCCESS, if setting User was successful.
@@ -8051,10 +8030,8 @@ export declare namespace DoorLock {
                         /**
                          * Retrieve user.
                          *
-                         * An InvokeResponse command shall be sent with an appropriate error
-                         *
-                         * COMMAND, etc.) as needed otherwise the GetUserResponse Command shall be sent implying a status of
-                         * SUCCESS.
+                         * An InvokeResponse command shall be sent with an appropriate error (e.g. FAILURE, INVALID_COMMAND, etc.)
+                         * as needed otherwise the GetUserResponse Command shall be sent implying a status of SUCCESS.
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.33
                          */
@@ -8356,10 +8333,9 @@ export declare namespace DoorLock {
                             /**
                              * This field shall indicate the next occupied index in the database for the credential type requested, which is
                              * useful for quickly identifying occupied credential slots in the database. This shall NOT be null if there is
-                             * at least one occupied entry after the requested credential index in the corresponding
-                             *
-                             * database and shall be null if there are no more occupied entries. The NextCredentialIndex reported shall NOT
-                             * exceed the maximum number of credentials for a particular credential type.
+                             * at least one occupied entry after the requested credential index in the corresponding database and shall be
+                             * null if there are no more occupied entries. The NextCredentialIndex reported shall NOT exceed the maximum
+                             * number of credentials for a particular credential type.
                              *
                              * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.5
                              */
@@ -8375,10 +8351,10 @@ export declare namespace DoorLock {
                              * Otherwise, the value of this field shall be the value of the relevant credential, as a 65-byte uncompressed
                              * elliptic curve public key as defined in section 2.3.3 of SEC 1.
                              *
-                             * NOTE
+                             * > [!NOTE]
                              *
-                             * Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
-                             * Possession of the credential octet string does not allow operating the lock.
+                             * > Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
+                             *   Possession of the credential octet string does not allow operating the lock.
                              *
                              * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.6
                              */
@@ -9094,11 +9070,10 @@ export declare namespace DoorLock {
                          * door lock server to send PINs over the air. This attribute determines the behavior of the server’s TX
                          * operation. If it is false, then it is not ok for the device to send PIN in any messages over the air.
                          *
-                         * The PIN field within any door lock cluster message shall keep the first octet unchanged and
-                         *
-                         * masks the actual code by replacing with 0xFF. For example (PIN "1234" ): If the attribute value is True,
-                         * 0x04 0x31 0x32 0x33 0x34 shall be used in the PIN field in any door lock cluster message payload. If the
-                         * attribute value is False, 0x04 0xFF 0xFF 0xFF 0xFF shall be used.
+                         * The PIN field within any door lock cluster message shall keep the first octet unchanged and masks the
+                         * actual code by replacing with 0xFF. For example (PIN "1234" ): If the attribute value is True, 0x04 0x31
+                         * 0x32 0x33 0x34 shall be used in the PIN field in any door lock cluster message payload. If the attribute
+                         * value is False, 0x04 0xFF 0xFF 0xFF 0xFF shall be used.
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 5.2.9.34
                          */
@@ -9171,10 +9146,10 @@ export declare namespace DoorLock {
                         /**
                          * Clear out all PINs on the lock.
                          *
-                         * NOTE
+                         * > [!NOTE]
                          *
-                         * On the server, the clear all PIN codes command SHOULD have the same effect as the ClearPINCode command
-                         * with respect to the setting of user status, user type and schedules.
+                         * > On the server, the clear all PIN codes command SHOULD have the same effect as the ClearPINCode command
+                         *   with respect to the setting of user status, user type and schedules.
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.8
                          */
@@ -9244,13 +9219,13 @@ export declare namespace DoorLock {
                          * applies to the sum of the number of AliroEvictableEndpointKey credentials and the number of
                          * AliroNonEvictableEndpointKey credentials.
                          *
-                         * NOTE
+                         * > [!NOTE]
                          *
-                         * The credential indices used for these two credential types are independent of each other, similar to all
-                         * other credential types. As long as NumberOfAliroEndpointKeysSupported is at least 2 a client could add a
-                         * credential of type AliroEvictableEndpointKey at any index from 1 to NumberOfAliroEndpointKeysSupported
-                         * and also add a credential of type AliroNonEvictableEndpointKey at the same index, and both credentials
-                         * would exist on the server.
+                         * > The credential indices used for these two credential types are independent of each other, similar to
+                         *   all other credential types. As long as NumberOfAliroEndpointKeysSupported is at least 2 a client could
+                         *   add a credential of type AliroEvictableEndpointKey at any index from 1 to
+                         *   NumberOfAliroEndpointKeysSupported and also add a credential of type AliroNonEvictableEndpointKey at
+                         *   the same index, and both credentials would exist on the server.
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 5.2.9.46
                          */
@@ -9293,11 +9268,11 @@ export declare namespace DoorLock {
                          * This command allows clearing an existing Aliro Reader configuration for the lock. Administrators shall
                          * NOT clear an Aliro Reader configuration without explicit user permission.
                          *
-                         * NOTE
+                         * > [!NOTE]
                          *
-                         * Using this command will revoke the ability of all existing Aliro user devices that have the old
-                         * verification key to interact with the lock. This effect is not restricted to a single fabric or otherwise
-                         * scoped in any way.
+                         * > Using this command will revoke the ability of all existing Aliro user devices that have the old
+                         *   verification key to interact with the lock. This effect is not restricted to a single fabric or
+                         *   otherwise scoped in any way.
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.43
                          */
@@ -9531,10 +9506,10 @@ export declare namespace DoorLock {
                          * an optional code for the lock. The door lock may require a code depending on the value of the
                          * RequirePINForRemoteOperation attribute.
                          *
-                         * NOTE
+                         * > [!NOTE]
                          *
-                         * If the attribute AutoRelockTime is supported, the lock will transition to the locked state when the auto
-                         * relock time has expired.
+                         * > If the attribute AutoRelockTime is supported, the lock will transition to the locked state when the
+                         *   auto relock time has expired.
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.41
                          */
@@ -9661,7 +9636,6 @@ export declare namespace DoorLock {
              * CredentialOverTheAirAccess
              *
              * If this feature is supported then the lock supports the ability to verify a credential provided in a
-             *
              * lock/unlock command. Currently the cluster only supports providing the PIN credential to the lock/unlock
              * commands. If this feature is supported then the PIN Credential feature shall also be supported.
              *
@@ -9788,7 +9762,7 @@ export declare namespace DoorLock {
              */
             readonly soundVolume: OptionalWritableAttribute<SoundVolume, any>;
             /**
-             * Indicates the current operating mode of the lock as defined in OperatingModeEnum.
+             * This attribute shall indicate the current operating mode of the lock as defined in OperatingModeEnum.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.9.24
              */
@@ -9828,10 +9802,8 @@ export declare namespace DoorLock {
             }>, any>;
             /**
              * Indicates the default configurations as they are physically set on the device (example: hardware dip
-             * switch setting, etc…) and represents the default setting for some of the
-             *
-             * attributes within this cluster (for example: LED, Auto Lock, Sound Volume, and Operating Mode
-             * attributes).
+             * switch setting, etc…) and represents the default setting for some of the attributes within this cluster
+             * (for example: LED, Auto Lock, Sound Volume, and Operating Mode attributes).
              *
              * This is a read-only attribute and is intended to allow clients to determine what changes may need to be
              * made without having to query all the included attributes. It may be beneficial for the clients to know
@@ -10079,10 +10051,10 @@ export declare namespace DoorLock {
              * lock. The door lock may require a code depending on the value of the RequirePINForRemoteOperation
              * attribute.
              *
-             * NOTE
+             * > [!NOTE]
              *
-             * If the attribute AutoRelockTime is supported the lock will transition to the locked state when the auto
-             * relock time has expired.
+             * > If the attribute AutoRelockTime is supported the lock will transition to the locked state when the auto
+             *   relock time has expired.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.2
              */
@@ -10158,9 +10130,8 @@ export declare namespace DoorLock {
              *     ◦ shall generate a LockOperation event of LockOperationType Unlatch when it is actuated from the
              *       outside.
              *
-             *     ◦ may generate a LockOperation event of LockOperationType Unlatch when it is actuated
-             *
-             * from the inside.
+             *     ◦ may generate a LockOperation event of LockOperationType Unlatch when it is actuated from the
+             *       inside.
              *
              * @see {@link MatterSpecification.v14.Cluster} § 5.2.11.3
              */
@@ -10411,7 +10382,6 @@ export declare namespace DoorLock {
                      * Fields used for different use cases:
                      *
                      * Return status is a global status code or a cluster-specific status code from the Status Codes table and
-                     *
                      * shall be one of the following values:
                      *
                      *   • SUCCESS, if setting User was successful.
@@ -10522,10 +10492,8 @@ export declare namespace DoorLock {
                     /**
                      * Retrieve user.
                      *
-                     * An InvokeResponse command shall be sent with an appropriate error
-                     *
-                     * COMMAND, etc.) as needed otherwise the GetUserResponse Command shall be sent implying a status of
-                     * SUCCESS.
+                     * An InvokeResponse command shall be sent with an appropriate error (e.g. FAILURE, INVALID_COMMAND, etc.)
+                     * as needed otherwise the GetUserResponse Command shall be sent implying a status of SUCCESS.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.33
                      */
@@ -10827,10 +10795,9 @@ export declare namespace DoorLock {
                         /**
                          * This field shall indicate the next occupied index in the database for the credential type requested, which is
                          * useful for quickly identifying occupied credential slots in the database. This shall NOT be null if there is
-                         * at least one occupied entry after the requested credential index in the corresponding
-                         *
-                         * database and shall be null if there are no more occupied entries. The NextCredentialIndex reported shall NOT
-                         * exceed the maximum number of credentials for a particular credential type.
+                         * at least one occupied entry after the requested credential index in the corresponding database and shall be
+                         * null if there are no more occupied entries. The NextCredentialIndex reported shall NOT exceed the maximum
+                         * number of credentials for a particular credential type.
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.5
                          */
@@ -10846,10 +10813,10 @@ export declare namespace DoorLock {
                          * Otherwise, the value of this field shall be the value of the relevant credential, as a 65-byte uncompressed
                          * elliptic curve public key as defined in section 2.3.3 of SEC 1.
                          *
-                         * NOTE
+                         * > [!NOTE]
                          *
-                         * Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
-                         * Possession of the credential octet string does not allow operating the lock.
+                         * > Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
+                         *   Possession of the credential octet string does not allow operating the lock.
                          *
                          * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.6
                          */
@@ -11565,11 +11532,10 @@ export declare namespace DoorLock {
                      * door lock server to send PINs over the air. This attribute determines the behavior of the server’s TX
                      * operation. If it is false, then it is not ok for the device to send PIN in any messages over the air.
                      *
-                     * The PIN field within any door lock cluster message shall keep the first octet unchanged and
-                     *
-                     * masks the actual code by replacing with 0xFF. For example (PIN "1234" ): If the attribute value is True,
-                     * 0x04 0x31 0x32 0x33 0x34 shall be used in the PIN field in any door lock cluster message payload. If the
-                     * attribute value is False, 0x04 0xFF 0xFF 0xFF 0xFF shall be used.
+                     * The PIN field within any door lock cluster message shall keep the first octet unchanged and masks the
+                     * actual code by replacing with 0xFF. For example (PIN "1234" ): If the attribute value is True, 0x04 0x31
+                     * 0x32 0x33 0x34 shall be used in the PIN field in any door lock cluster message payload. If the attribute
+                     * value is False, 0x04 0xFF 0xFF 0xFF 0xFF shall be used.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.9.34
                      */
@@ -11642,10 +11608,10 @@ export declare namespace DoorLock {
                     /**
                      * Clear out all PINs on the lock.
                      *
-                     * NOTE
+                     * > [!NOTE]
                      *
-                     * On the server, the clear all PIN codes command SHOULD have the same effect as the ClearPINCode command
-                     * with respect to the setting of user status, user type and schedules.
+                     * > On the server, the clear all PIN codes command SHOULD have the same effect as the ClearPINCode command
+                     *   with respect to the setting of user status, user type and schedules.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.8
                      */
@@ -11715,13 +11681,13 @@ export declare namespace DoorLock {
                      * applies to the sum of the number of AliroEvictableEndpointKey credentials and the number of
                      * AliroNonEvictableEndpointKey credentials.
                      *
-                     * NOTE
+                     * > [!NOTE]
                      *
-                     * The credential indices used for these two credential types are independent of each other, similar to all
-                     * other credential types. As long as NumberOfAliroEndpointKeysSupported is at least 2 a client could add a
-                     * credential of type AliroEvictableEndpointKey at any index from 1 to NumberOfAliroEndpointKeysSupported
-                     * and also add a credential of type AliroNonEvictableEndpointKey at the same index, and both credentials
-                     * would exist on the server.
+                     * > The credential indices used for these two credential types are independent of each other, similar to
+                     *   all other credential types. As long as NumberOfAliroEndpointKeysSupported is at least 2 a client could
+                     *   add a credential of type AliroEvictableEndpointKey at any index from 1 to
+                     *   NumberOfAliroEndpointKeysSupported and also add a credential of type AliroNonEvictableEndpointKey at
+                     *   the same index, and both credentials would exist on the server.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.9.46
                      */
@@ -11764,11 +11730,11 @@ export declare namespace DoorLock {
                      * This command allows clearing an existing Aliro Reader configuration for the lock. Administrators shall
                      * NOT clear an Aliro Reader configuration without explicit user permission.
                      *
-                     * NOTE
+                     * > [!NOTE]
                      *
-                     * Using this command will revoke the ability of all existing Aliro user devices that have the old
-                     * verification key to interact with the lock. This effect is not restricted to a single fabric or otherwise
-                     * scoped in any way.
+                     * > Using this command will revoke the ability of all existing Aliro user devices that have the old
+                     *   verification key to interact with the lock. This effect is not restricted to a single fabric or
+                     *   otherwise scoped in any way.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.43
                      */
@@ -12002,10 +11968,10 @@ export declare namespace DoorLock {
                      * an optional code for the lock. The door lock may require a code depending on the value of the
                      * RequirePINForRemoteOperation attribute.
                      *
-                     * NOTE
+                     * > [!NOTE]
                      *
-                     * If the attribute AutoRelockTime is supported, the lock will transition to the locked state when the auto
-                     * relock time has expired.
+                     * > If the attribute AutoRelockTime is supported, the lock will transition to the locked state when the
+                     *   auto relock time has expired.
                      *
                      * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.41
                      */
@@ -12048,8 +12014,6 @@ export declare namespace DoorLock {
      * the locking functionality is abstracted from the cluster. The cluster has a small list of mandatory attributes
      * and functions and a list of optional features.
      *
-     * Figure 16. Typical Usage of the Door Lock Cluster
-     *
      * DoorLockCluster supports optional features that you can enable with the DoorLockCluster.with() factory method.
      *
      * @see {@link MatterSpecification.v14.Cluster} § 5.2
@@ -12150,7 +12114,6 @@ export declare namespace DoorLock {
              * CredentialOverTheAirAccess
              *
              * If this feature is supported then the lock supports the ability to verify a credential provided in a
-             *
              * lock/unlock command. Currently the cluster only supports providing the PIN credential to the lock/unlock
              * commands. If this feature is supported then the PIN Credential feature shall also be supported.
              *
@@ -12570,7 +12533,6 @@ export declare namespace DoorLock {
                  * CredentialOverTheAirAccess
                  *
                  * If this feature is supported then the lock supports the ability to verify a credential provided in a
-                 *
                  * lock/unlock command. Currently the cluster only supports providing the PIN credential to the lock/unlock
                  * commands. If this feature is supported then the PIN Credential feature shall also be supported.
                  *
@@ -13913,10 +13875,9 @@ export declare namespace DoorLock {
                 /**
                  * This field shall indicate the next occupied index in the database for the credential type requested, which is
                  * useful for quickly identifying occupied credential slots in the database. This shall NOT be null if there is
-                 * at least one occupied entry after the requested credential index in the corresponding
-                 *
-                 * database and shall be null if there are no more occupied entries. The NextCredentialIndex reported shall NOT
-                 * exceed the maximum number of credentials for a particular credential type.
+                 * at least one occupied entry after the requested credential index in the corresponding database and shall be
+                 * null if there are no more occupied entries. The NextCredentialIndex reported shall NOT exceed the maximum
+                 * number of credentials for a particular credential type.
                  *
                  * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.5
                  */
@@ -13932,10 +13893,10 @@ export declare namespace DoorLock {
                  * Otherwise, the value of this field shall be the value of the relevant credential, as a 65-byte uncompressed
                  * elliptic curve public key as defined in section 2.3.3 of SEC 1.
                  *
-                 * NOTE
+                 * > [!NOTE]
                  *
-                 * Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
-                 * Possession of the credential octet string does not allow operating the lock.
+                 * > Since the Aliro credentials are public keys, there is no security risk in allowing them to be read.
+                 *   Possession of the credential octet string does not allow operating the lock.
                  *
                  * @see {@link MatterSpecification.v14.Cluster} § 5.2.10.39.6
                  */