@matter/types 0.12.6-alpha.0-20250304-03716637c → 0.13.0-alpha.0-20250307-ebf84a05a

package/dist/cjs/clusters/general-commissioning.d.ts

@@ -5,14 +5,137 @@
  */
 /*** THIS FILE IS GENERATED, DO NOT EDIT ***/
 import { MutableCluster } from "../cluster/mutation/MutableCluster.js";
-import { WritableAttribute, FixedAttribute, Attribute, Command } from "../cluster/Cluster.js";
+import { Attribute, Command, WritableAttribute, FixedAttribute } from "../cluster/Cluster.js";
 import { TypeFromSchema } from "../tlv/TlvSchema.js";
+import { BitFlag } from "../schema/BitmapSchema.js";
 import { Identity } from "#general";
 export declare namespace GeneralCommissioning {
+    /**
+     * These are optional features supported by GeneralCommissioningCluster.
+     *
+     * @see {@link MatterSpecification.v13.Core} § 11.10.4
+     */
+    enum Feature {
+        /**
+         * TermsAndConditions (TC)
+         *
+         * Supports Terms & Conditions acknowledgement
+         */
+        TermsAndConditions = "TermsAndConditions"
+    }
+    /**
+     * Input to the GeneralCommissioning setTcAcknowledgements command
+     *
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.8
+     */
+    const TlvSetTcAcknowledgementsRequest: import("../tlv/TlvObject.js").ObjectSchema<{
+        /**
+         * This field shall contain the version of the Enhanced Setup Flow Terms & Conditions that were presented to
+         * the user.
+         *
+         * @see {@link MatterSpecification.v13.Core} § 11.10.7.8.1
+         */
+        tcVersion: import("../tlv/TlvObject.js").FieldType<number>;
+        /**
+         * This field shall contain the user responses to the Enhanced Setup Flow Terms & Conditions as a map where
+         * each bit set in the bitmap corresponds to an accepted term in the file located at EnhancedSetupFlowTCUrl.
+         *
+         * ### Effect on Receipt
+         *
+         * This command shall copy the user responses and accepted version to the presented Enhanced Setup Flow Terms &
+         * Conditions from the values provided in the TCUserResponse and TCVersion fields to the TCAcknowledgements
+         * Attribute and the TCAcceptedVersion Attribute fields respectively.
+         *
+         * This command shall result in success with an ErrorCode value of OK in the SetTCAcknowledgementsResponse if
+         * all required terms were accepted by the user. Specifically, all bits have a value of 1 in TCAcknowledgements
+         * whose ordinal is marked as required in the file located at EnhancedSe
+         *
+         * tupFlowTCUrl.
+         *
+         * If the TCVersion field is less than the TCMinRequiredVersion, then the ErrorCode of TCMinVersionNotMet shall
+         * be returned and TCAcknowledgements shall remain unchanged.
+         *
+         * If TCVersion is greater than or equal to TCMinRequiredVersion, but the TCUserResponse value indicates that
+         * not all required terms were accepted by the user, then the ErrorCode of RequiredTCNotAccepted shall be
+         * returned and TCAcknowledgements shall remain unchanged.
+         *
+         * @see {@link MatterSpecification.v13.Core} § 11.10.7.8.2
+         */
+        tcUserResponse: import("../tlv/TlvObject.js").FieldType<number>;
+    }>;
+    /**
+     * Input to the GeneralCommissioning setTcAcknowledgements command
+     *
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.8
+     */
+    interface SetTcAcknowledgementsRequest extends TypeFromSchema<typeof TlvSetTcAcknowledgementsRequest> {
+    }
+    /**
+     * This enumeration is used by several response commands in this cluster to indicate particular errors.
+     *
+     * @see {@link MatterSpecification.v13.Core} § 11.10.5.1
+     */
+    enum CommissioningError {
+        /**
+         * No error
+         */
+        Ok = 0,
+        /**
+         * Attempting to set regulatory configuration to a region or indoor/outdoor mode for which the server does not
+         * have proper configuration.
+         */
+        ValueOutsideRange = 1,
+        /**
+         * Executed CommissioningComplete outside CASE session.
+         */
+        InvalidAuthentication = 2,
+        /**
+         * Executed CommissioningComplete when there was no active Fail-Safe context.
+         */
+        NoFailSafe = 3,
+        /**
+         * Attempting to arm fail- safe or execute CommissioningComplete from a fabric different than the one
+         * associated with the current fail- safe context.
+         */
+        BusyWithOtherAdmin = 4,
+        /**
+         * One or more required TC features from the Enhanced Setup Flow were not accepted.
+         */
+        RequiredTcNotAccepted = 5,
+        /**
+         * No acknowledgements from the user for the TC features were received.
+         */
+        TcAcknowledgementsNotReceived = 6,
+        /**
+         * The version of the TC features acknowledged by the user did not meet the minimum required version.
+         */
+        TcMinVersionNotMet = 7
+    }
+    /**
+     * This command is used to convey the result from SetTCAcknowledgements.
+     *
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.9
+     */
+    const TlvSetTcAcknowledgementsResponse: import("../tlv/TlvObject.js").ObjectSchema<{
+        /**
+         * This field shall contain the result of the operation, based on the behavior specified in the functional
+         * description of the SetTCAcknowledgements command.
+         *
+         * @see {@link MatterSpecification.v13.Core} § 11.10.7.9.1
+         */
+        errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
+    }>;
+    /**
+     * This command is used to convey the result from SetTCAcknowledgements.
+     *
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.9
+     */
+    interface SetTcAcknowledgementsResponse extends TypeFromSchema<typeof TlvSetTcAcknowledgementsResponse> {
+    }
     /**
      * This structure provides some constant values that may be of use to all commissioners.
      *
-     * @see {@link MatterSpecification.v13.Core} § 11.10.4.3
+     * @see {@link MatterSpecification.v13.Core} § 11.10.5.3
      */
     const TlvBasicCommissioningInfo: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
@@ -21,25 +144,25 @@ export declare namespace GeneralCommissioning {
          * Commissionee. This value, if used in the ArmFailSafe command’s ExpiryLengthSeconds field SHOULD allow a
          * Commissioner to proceed with a nominal commissioning without having to-rearm the fail-safe, with some margin.
          *
-         * @see {@link MatterSpecification.v13.Core} § 11.10.4.3.1
+         * @see {@link MatterSpecification.v13.Core} § 11.10.5.3.1
          */
         failSafeExpiryLengthSeconds: import("../tlv/TlvObject.js").FieldType<number>;
         /**
          * This field shall contain a conservative value in seconds denoting the maximum total duration for which a
-         * fail safe timer can be re-armed. See Section 11.10.6.2.1, “Fail Safe Context”.
+         * fail safe timer can be re-armed. See Section 11.10.7.2.1, “Fail Safe Context”.
          *
          * The value of this field shall be greater than or equal to the FailSafeExpiryLengthSeconds. Absent additional
          * guidelines, it is recommended that the value of this field be aligned with the initial Announcement Duration
          * and default to 900 seconds.
          *
-         * @see {@link MatterSpecification.v13.Core} § 11.10.4.3.2
+         * @see {@link MatterSpecification.v13.Core} § 11.10.5.3.2
          */
         maxCumulativeFailsafeSeconds: import("../tlv/TlvObject.js").FieldType<number>;
     }>;
     /**
      * This structure provides some constant values that may be of use to all commissioners.
      *
-     * @see {@link MatterSpecification.v13.Core} § 11.10.4.3
+     * @see {@link MatterSpecification.v13.Core} § 11.10.5.3
      */
     interface BasicCommissioningInfo extends TypeFromSchema<typeof TlvBasicCommissioningInfo> {
     }
@@ -47,7 +170,7 @@ export declare namespace GeneralCommissioning {
      * This enumeration is used by the RegulatoryConfig and LocationCapability attributes to indicate possible radio
      * usage.
      *
-     * @see {@link MatterSpecification.v13.Core} § 11.10.4.2
+     * @see {@link MatterSpecification.v13.Core} § 11.10.5.2
      */
     enum RegulatoryLocationType {
         /**
@@ -66,7 +189,7 @@ export declare namespace GeneralCommissioning {
     /**
      * Input to the GeneralCommissioning armFailSafe command
      *
-     * @see {@link MatterSpecification.v13.Core} § 11.10.6.2
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.2
      */
     const TlvArmFailSafeRequest: import("../tlv/TlvObject.js").ObjectSchema<{
         expiryLengthSeconds: import("../tlv/TlvObject.js").FieldType<number>;
@@ -75,66 +198,37 @@ export declare namespace GeneralCommissioning {
     /**
      * Input to the GeneralCommissioning armFailSafe command
      *
-     * @see {@link MatterSpecification.v13.Core} § 11.10.6.2
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.2
      */
     interface ArmFailSafeRequest extends TypeFromSchema<typeof TlvArmFailSafeRequest> {
     }
     /**
-     * This enumeration is used by several response commands in this cluster to indicate particular errors.
-     *
-     * @see {@link MatterSpecification.v13.Core} § 11.10.4.1
-     */
-    enum CommissioningError {
-        /**
-         * No error
-         */
-        Ok = 0,
-        /**
-         * Attempting to set regulatory configuration to a region or indoor/outdoor mode for which the server does not
-         * have proper configuration.
-         */
-        ValueOutsideRange = 1,
-        /**
-         * Executed CommissioningComplete outside CASE session.
-         */
-        InvalidAuthentication = 2,
-        /**
-         * Executed CommissioningComplete when there was no active Fail-Safe context.
-         */
-        NoFailSafe = 3,
-        /**
-         * Attempting to arm fail- safe or execute CommissioningComplete from a fabric different than the one
-         * associated with the current fail- safe context.
-         */
-        BusyWithOtherAdmin = 4
-    }
-    /**
-     * @see {@link MatterSpecification.v13.Core} § 11.10.6.3
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.3
      */
     const TlvArmFailSafeResponse: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
          * This field shall contain the result of the operation, based on the behavior specified in the functional
          * description of the ArmFailSafe command.
          *
-         * @see {@link MatterSpecification.v13.Core} § 11.10.6.3.1
+         * @see {@link MatterSpecification.v13.Core} § 11.10.7.3.1
          */
         errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
         /**
-         * See Section 11.10.6.1, “Common fields in General Commissioning cluster responses”.
+         * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
          *
-         * @see {@link MatterSpecification.v13.Core} § 11.10.6.3.2
+         * @see {@link MatterSpecification.v13.Core} § 11.10.7.3.2
          */
         debugText: import("../tlv/TlvObject.js").FieldType<string>;
     }>;
     /**
-     * @see {@link MatterSpecification.v13.Core} § 11.10.6.3
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.3
      */
     interface ArmFailSafeResponse extends TypeFromSchema<typeof TlvArmFailSafeResponse> {
     }
     /**
      * Input to the GeneralCommissioning setRegulatoryConfig command
      *
-     * @see {@link MatterSpecification.v13.Core} § 11.10.6.4
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.4
      */
     const TlvSetRegulatoryConfigRequest: import("../tlv/TlvObject.js").ObjectSchema<{
         newRegulatoryConfig: import("../tlv/TlvObject.js").FieldType<RegulatoryLocationType>;
@@ -144,63 +238,197 @@ export declare namespace GeneralCommissioning {
     /**
      * Input to the GeneralCommissioning setRegulatoryConfig command
      *
-     * @see {@link MatterSpecification.v13.Core} § 11.10.6.4
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.4
      */
     interface SetRegulatoryConfigRequest extends TypeFromSchema<typeof TlvSetRegulatoryConfigRequest> {
     }
     /**
-     * @see {@link MatterSpecification.v13.Core} § 11.10.6.5
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.5
      */
     const TlvSetRegulatoryConfigResponse: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
          * This field shall contain the result of the operation, based on the behavior specified in the functional
          * description of the SetRegulatoryConfig command.
          *
-         * @see {@link MatterSpecification.v13.Core} § 11.10.6.5.1
+         * @see {@link MatterSpecification.v13.Core} § 11.10.7.5.1
          */
         errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
         /**
-         * See Section 11.10.6.1, “Common fields in General Commissioning cluster responses”.
+         * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
          *
-         * @see {@link MatterSpecification.v13.Core} § 11.10.6.5.2
+         * @see {@link MatterSpecification.v13.Core} § 11.10.7.5.2
          */
         debugText: import("../tlv/TlvObject.js").FieldType<string>;
     }>;
     /**
-     * @see {@link MatterSpecification.v13.Core} § 11.10.6.5
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.5
      */
     interface SetRegulatoryConfigResponse extends TypeFromSchema<typeof TlvSetRegulatoryConfigResponse> {
     }
     /**
-     * @see {@link MatterSpecification.v13.Core} § 11.10.6.7
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.7
      */
     const TlvCommissioningCompleteResponse: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
          * This field shall contain the result of the operation, based on the behavior specified in the functional
          * description of the CommissioningComplete command.
          *
-         * @see {@link MatterSpecification.v13.Core} § 11.10.6.7.1
+         * @see {@link MatterSpecification.v13.Core} § 11.10.7.7.1
          */
         errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
         /**
-         * See Section 11.10.6.1, “Common fields in General Commissioning cluster responses”.
+         * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
          *
-         * @see {@link MatterSpecification.v13.Core} § 11.10.6.7.2
+         * @see {@link MatterSpecification.v13.Core} § 11.10.7.7.2
          */
         debugText: import("../tlv/TlvObject.js").FieldType<string>;
     }>;
     /**
-     * @see {@link MatterSpecification.v13.Core} § 11.10.6.7
+     * @see {@link MatterSpecification.v13.Core} § 11.10.7.7
      */
     interface CommissioningCompleteResponse extends TypeFromSchema<typeof TlvCommissioningCompleteResponse> {
     }
     /**
-     * @see {@link Cluster}
+     * A GeneralCommissioningCluster supports these elements if it supports feature TermsAndConditions.
      */
-    const ClusterInstance: MutableCluster<{
+    const TermsAndConditionsComponent: {
+        readonly attributes: {
+            /**
+             * Indicates the last version of the T&Cs for which the device received user acknowledgements. On factory
+             * reset this field shall be reset to 0.
+             *
+             * When Custom Commissioning Flow is used to obtain user consent (e. g. because the Commissioner does not
+             * support the TC feature), the manufacturer-provided means for obtaining user consent shall ensure that
+             * this attribute is set to a value which is greater than or equal to TCMinRequiredVersion before returning
+             * the user back to the originating Commissioner (see Enhanced Setup Flow).
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.6
+             */
+            readonly tcAcceptedVersion: Attribute<number, any>;
+            /**
+             * Indicates the minimum version of the texts presented by the Enhanced Setup Flow that need to be accepted
+             * by the user for this device. This attribute may change as the result of an OTA update.
+             *
+             * If an event such as a software update causes TCAcceptedVersion to become less than TCMinRequiredVersion,
+             * then the device shall update TCAcknowledgementsRequired to True so that an administrator can detect that
+             * a newer version of the texts needs to be presented to the user.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.7
+             */
+            readonly tcMinRequiredVersion: Attribute<number, any>;
+            /**
+             * Indicates the user’s response to the presented terms. Each bit position corresponds to a user response
+             * for the associated index of matching text, such that bit 0 (bit value 1) is for text index 0. Bit 15
+             * (bit value 0x8000) is for text index 15. A bit value of 1 indicates acceptance and a value of 0
+             * indicates non-acceptance. For example, if there are two texts that were presented where the first (bit
+             * 0, value 1) was declined and the second accepted (bit 1, value 2), we would expect the resulting value
+             * of the map to be 2.
+             *
+             * Whenever a user provides responses to newly presented terms and conditions, this attribute shall be
+             * updated with the latest responses. This may happen in response to updated terms that were presented to
+             * the user. On a factory reset this field shall be reset with all bits set to 0.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.8
+             */
+            readonly tcAcknowledgements: Attribute<number, any>;
+            /**
+             * Indicates whether SetTCAcknowledgements is currently required to be called with the inclusion of
+             * mandatory terms accepted.
+             *
+             * This attribute may be present and False in the case where no terms and conditions are currently
+             * mandatory to accept for CommissioningComplete to succeed.
+             *
+             * This attribute may appear, or become True after commissioning (e.g. due to a firmware update) to
+             * indicate that new Terms & Conditions are available that the user must accept.
+             *
+             * Upon Factory Data Reset, this attribute shall be set to a value of True.
+             *
+             * When Custom Commissioning Flow is used to obtain user consent (e.g. because the Commissioner does not
+             * support the TC feature), the manufacturer-provided means for obtaining user consent shall ensure that
+             * this attribute is set to False before returning the user back to the original Commissioner (see Enhanced
+             * Setup Flow).
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.9
+             */
+            readonly tcAcknowledgementsRequired: Attribute<boolean, any>;
+            /**
+             * Indicates the System Time in seconds when any functionality limitations will begin due to a lack of
+             * acceptance of updated Terms and Conditions, as described in Section 5.7.4.5, “Presenting Updated Terms
+             * and Conditions”.
+             *
+             * A null value indicates that there is no pending deadline for updated TC acceptance.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.10
+             */
+            readonly tcUpdateDeadline: Attribute<number | null, any>;
+        };
+        readonly commands: {
+            /**
+             * This command sets the user acknowledgements received in the Enhanced Setup Flow Terms & Conditions into
+             * the node.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.7.8
+             */
+            readonly setTcAcknowledgements: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain the version of the Enhanced Setup Flow Terms & Conditions that were presented to
+                 * the user.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.8.1
+                 */
+                tcVersion: import("../tlv/TlvObject.js").FieldType<number>;
+                /**
+                 * This field shall contain the user responses to the Enhanced Setup Flow Terms & Conditions as a map where
+                 * each bit set in the bitmap corresponds to an accepted term in the file located at EnhancedSetupFlowTCUrl.
+                 *
+                 * ### Effect on Receipt
+                 *
+                 * This command shall copy the user responses and accepted version to the presented Enhanced Setup Flow Terms &
+                 * Conditions from the values provided in the TCUserResponse and TCVersion fields to the TCAcknowledgements
+                 * Attribute and the TCAcceptedVersion Attribute fields respectively.
+                 *
+                 * This command shall result in success with an ErrorCode value of OK in the SetTCAcknowledgementsResponse if
+                 * all required terms were accepted by the user. Specifically, all bits have a value of 1 in TCAcknowledgements
+                 * whose ordinal is marked as required in the file located at EnhancedSe
+                 *
+                 * tupFlowTCUrl.
+                 *
+                 * If the TCVersion field is less than the TCMinRequiredVersion, then the ErrorCode of TCMinVersionNotMet shall
+                 * be returned and TCAcknowledgements shall remain unchanged.
+                 *
+                 * If TCVersion is greater than or equal to TCMinRequiredVersion, but the TCUserResponse value indicates that
+                 * not all required terms were accepted by the user, then the ErrorCode of RequiredTCNotAccepted shall be
+                 * returned and TCAcknowledgements shall remain unchanged.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.8.2
+                 */
+                tcUserResponse: import("../tlv/TlvObject.js").FieldType<number>;
+            }>, import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain the result of the operation, based on the behavior specified in the functional
+                 * description of the SetTCAcknowledgements command.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.9.1
+                 */
+                errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
+            }>, any>;
+        };
+    };
+    /**
+     * These elements and properties are present in all GeneralCommissioning clusters.
+     */
+    const Base: {
         readonly id: 48;
         readonly name: "GeneralCommissioning";
-        readonly revision: 1;
+        readonly revision: 2;
+        readonly features: {
+            /**
+             * TermsAndConditions
+             *
+             * Supports Terms & Conditions acknowledgement
+             */
+            readonly termsAndConditions: BitFlag;
+        };
         readonly attributes: {
             /**
              * This attribute allows for the storage of a client-provided small payload which Administrators and
@@ -218,14 +446,14 @@ export declare namespace GeneralCommissioning {
              * functioning of any cluster, other than being set as a side-effect of commands where this behavior is
              * described.
              *
-             * @see {@link MatterSpecification.v13.Core} § 11.10.5.1
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.1
              */
             readonly breadcrumb: WritableAttribute<number | bigint, any>;
             /**
              * This attribute shall describe critical parameters needed at the beginning of commissioning flow. See
              * BasicCommissioningInfo for more information.
              *
-             * @see {@link MatterSpecification.v13.Core} § 11.10.5.2
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.2
              */
             readonly basicCommissioningInfo: FixedAttribute<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
@@ -234,18 +462,18 @@ export declare namespace GeneralCommissioning {
                  * Commissionee. This value, if used in the ArmFailSafe command’s ExpiryLengthSeconds field SHOULD allow a
                  * Commissioner to proceed with a nominal commissioning without having to-rearm the fail-safe, with some margin.
                  *
-                 * @see {@link MatterSpecification.v13.Core} § 11.10.4.3.1
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.5.3.1
                  */
                 failSafeExpiryLengthSeconds: import("../tlv/TlvObject.js").FieldType<number>;
                 /**
                  * This field shall contain a conservative value in seconds denoting the maximum total duration for which a
-                 * fail safe timer can be re-armed. See Section 11.10.6.2.1, “Fail Safe Context”.
+                 * fail safe timer can be re-armed. See Section 11.10.7.2.1, “Fail Safe Context”.
                  *
                  * The value of this field shall be greater than or equal to the FailSafeExpiryLengthSeconds. Absent additional
                  * guidelines, it is recommended that the value of this field be aligned with the initial Announcement Duration
                  * and default to 900 seconds.
                  *
-                 * @see {@link MatterSpecification.v13.Core} § 11.10.4.3.2
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.5.3.2
                  */
                 maxCumulativeFailsafeSeconds: import("../tlv/TlvObject.js").FieldType<number>;
             }>, any>;
@@ -255,15 +483,16 @@ export declare namespace GeneralCommissioning {
              * Note that the country code is part of Basic Information Cluster and therefore NOT listed on the
              * RegulatoryConfig attribute.
              *
-             * @see {@link MatterSpecification.v13.Core} § 11.10.5.3
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.3
              */
             readonly regulatoryConfig: Attribute<RegulatoryLocationType, any>;
             /**
              * LocationCapability is statically set by the manufacturer and indicates if this Node needs to be told an
              * exact RegulatoryLocation. For example a Node which is "Indoor Only" would not be certified for outdoor
              * use at all, and thus there is no need for a commissioner to set or ask the user about whether the device
-             * will be used inside or outside. However a device which states its capability is "Indoor/Outdoor" means
-             * it would like clarification if possible.
+             * will be used inside or outside. However a device which states its capability is
+             *
+             * "Indoor/Outdoor" means it would like clarification if possible.
              *
              * For Nodes without radio network interfaces (e.g. Ethernet-only devices), the value IndoorOutdoor shall
              * always be used.
@@ -272,14 +501,14 @@ export declare namespace GeneralCommissioning {
              * means devices always have a safe default value, and Commissioners which choose to implement smarter
              * handling can.
              *
-             * @see {@link MatterSpecification.v13.Core} § 11.10.5.4
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.4
              */
             readonly locationCapability: FixedAttribute<RegulatoryLocationType, any>;
             /**
              * Indicates whether this device supports "concurrent connection flow" commissioning mode (see Section 5.5,
              * “Commissioning Flows”). If false, the device only supports "non-concurrent connection flow" mode.
              *
-             * @see {@link MatterSpecification.v13.Core} § 11.10.5.5
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.5
              */
             readonly supportsConcurrentConnection: FixedAttribute<boolean, any>;
         };
@@ -298,9 +527,8 @@ export declare namespace GeneralCommissioning {
              * of ExpiryLengthSeconds, or disarm it, depending on the situation:
              *
              *   • If ExpiryLengthSeconds is 0 and the fail-safe timer was already armed and the accessing fabric
-             *     matches the Fabric currently associated with the fail-safe context, then the fail-safe timer
-             *
-             * shall be immediately expired (see further below for side-effects of expiration).
+             *     matches the Fabric currently associated with the fail-safe context, then the fail-safe timer shall
+             *     be immediately expired (see further below for side-effects of expiration).
              *
              *   • If ExpiryLengthSeconds is 0 and the fail-safe timer was not armed, then this command invocation
              *     shall lead to a success response with no side-effects against the fail-safe context.
@@ -316,8 +544,8 @@ export declare namespace GeneralCommissioning {
              *     with ArmFailSafeResponse containing an ErrorCode value of BusyWithOtherAdmin, indicating a likely
              *     conflict between commissioners.
              *
-             * The value of the Breadcrumb field shall be written to the Breadcrumb Attribute on successful execution
-             * of the command.
+             * The value of the Breadcrumb field shall be written to the Breadcrumb on successful execution of the
+             * command.
              *
              * If the receiver restarts unexpectedly (e.g., power interruption, software crash, or other reset) the
              * receiver shall behave as if the fail-safe timer expired and perform the sequence of clean-up steps
@@ -362,7 +590,7 @@ export declare namespace GeneralCommissioning {
              * timer (CFSC timer) serves to limit the lifetime of any particular Fail Safe Context; it shall NOT be
              * extended or modified on subsequent invocations of ArmFailSafe associated with this Fail Safe Context.
              * Upon expiry of the CFSC timer, the receiver shall execute cleanup behavior equivalent to that of
-             * fail-safe timer expiration as detailed in Section 11.10.6.2.2, “Behavior on expiry of Fail-Safe timer”.
+             * fail-safe timer expiration as detailed in Section 11.10.7.2.2, “Behavior on expiry of Fail-Safe timer”.
              * Termination of the session prior to the expiration of that timer for any reason (including a successful
              * end of commissioning or an expiry of a fail-safe timer) shall also delete the CFSC timer.
              *
@@ -375,11 +603,11 @@ export declare namespace GeneralCommissioning {
              *       Server.
              *
              *   2. Revoke the temporary administrative privileges granted to any open PASE session (see Section
-             *       6.6.2.8, “Bootstrapping of the Access Control Cluster”) at the Server.
+             *       6.6.2.9, “Bootstrapping of the Access Control Cluster”) at the Server.
              *
              *   3. If an AddNOC or UpdateNOC command has been successfully invoked, terminate all CASE sessions
-             *       associated with the Fabric whose Fabric Index is recorded in the Fail-Safe context (see Section
-             *       11.10.6.2, “ArmFailSafe Command”) by clearing any associated Secure Session Context at the Server.
+             *       associated with the Fabric whose Fabric Index is recorded in the Fail-Safe context (see
+             *       ArmFailSafe) by clearing any associated Secure Session Context at the Server.
              *
              *   4. Reset the configuration of all Network Commissioning Networks attribute to their state prior to the
              *       Fail-Safe being armed.
@@ -405,11 +633,10 @@ export declare namespace GeneralCommissioning {
              *
              *   9. Reset the Breadcrumb attribute to zero.
              *
-             *   10. Optionally: if no factory-reset resulted from the previous steps, it is recommended that the
+             *   10. Optionally: if no factory-reset resulted from the previous steps, it is recommended that the Node
+             *       rollback the state of all non fabric-scoped data present in the Fail-Safe context.
              *
-             * Node rollback the state of all non fabric-scoped data present in the Fail-Safe context.
-             *
-             * @see {@link MatterSpecification.v13.Core} § 11.10.6.2
+             * @see {@link MatterSpecification.v13.Core} § 11.10.7.2
              */
             readonly armFailSafe: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                 expiryLengthSeconds: import("../tlv/TlvObject.js").FieldType<number>;
@@ -419,13 +646,13 @@ export declare namespace GeneralCommissioning {
                  * This field shall contain the result of the operation, based on the behavior specified in the functional
                  * description of the ArmFailSafe command.
                  *
-                 * @see {@link MatterSpecification.v13.Core} § 11.10.6.3.1
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.3.1
                  */
                 errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
                 /**
-                 * See Section 11.10.6.1, “Common fields in General Commissioning cluster responses”.
+                 * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
                  *
-                 * @see {@link MatterSpecification.v13.Core} § 11.10.6.3.2
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.3.2
                  */
                 debugText: import("../tlv/TlvObject.js").FieldType<string>;
             }>, any>;
@@ -445,8 +672,9 @@ export declare namespace GeneralCommissioning {
              * Location attribute reflected by the Basic Information Cluster configuration, but the
              * SetRegulatoryConfigResponse replied shall have the ErrorCode field set to ValueOutsideRange error.
              *
-             * If the LocationCapability attribute is not Indoor/Outdoor and the NewRegulatoryConfig value received
-             * does not match either the Indoor or Outdoor fixed value in LocationCapability, then the
+             * If the LocationCapability attribute is not Indoor/Outdoor and the NewRegulatoryConfig value
+             *
+             * received does not match either the Indoor or Outdoor fixed value in LocationCapability, then the
              * SetRegulatoryConfigResponse replied shall have the ErrorCode field set to ValueOutsideRange error and
              * the RegulatoryConfig attribute and associated internal radio configuration shall remain unchanged.
              *
@@ -460,7 +688,7 @@ export declare namespace GeneralCommissioning {
              * command, when SetRegulatoryConfigResponse has the ErrorCode field set to OK. If the command fails, the
              * Breadcrumb attribute shall be left unchanged.
              *
-             * @see {@link MatterSpecification.v13.Core} § 11.10.6.4
+             * @see {@link MatterSpecification.v13.Core} § 11.10.7.4
              */
             readonly setRegulatoryConfig: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                 newRegulatoryConfig: import("../tlv/TlvObject.js").FieldType<RegulatoryLocationType>;
@@ -471,13 +699,13 @@ export declare namespace GeneralCommissioning {
                  * This field shall contain the result of the operation, based on the behavior specified in the functional
                  * description of the SetRegulatoryConfig command.
                  *
-                 * @see {@link MatterSpecification.v13.Core} § 11.10.6.5.1
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.5.1
                  */
                 errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
                 /**
-                 * See Section 11.10.6.1, “Common fields in General Commissioning cluster responses”.
+                 * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
                  *
-                 * @see {@link MatterSpecification.v13.Core} § 11.10.6.5.2
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.5.2
                  */
                 debugText: import("../tlv/TlvObject.js").FieldType<string>;
             }>, any>;
@@ -492,15 +720,20 @@ export declare namespace GeneralCommissioning {
              * steps needed during the Fail-Safe period, such as commissioning (see Section 5.5, “Commissioning Flows”)
              * or other Administrator operations requiring usage of the Fail Safe timer. It ensures that the Server is
              * configured in a state such that it still has all necessary elements to be fully operable within a
-             * Fabric, such as ACL entries (see Access Control Cluster) and operational credentials (see Section 6.4,
-             * “Node Operational Credentials Specification”), and that the Node is reach
+             * Fabric, such as ACL entries (see Section 9.10, “Access Control Cluster”) and operational credentials
+             * (see Section 6.4, “Node Operational Credentials Specification”), and that the Node is reachable using
+             * CASE
              *
-             * able using CASE (see Section 4.14.2, “Certificate Authenticated Session Establishment (CASE)”) over an
-             * operational network.
+             * (CASE)”) over an operational network.
              *
              * An ErrorCode of NoFailSafe shall be responded to the invoker if the CommissioningComplete command was
              * received when no Fail-Safe context exists.
              *
+             * If Terms and Conditions are required, then an ErrorCode of TCAcknowledgementsNotReceived shall be
+             * responded to the invoker if the user acknowledgements to the required Terms and Conditions have not been
+             * provided. If the TCAcceptedVersion for the provided acknowledgements is less than TCMinRequiredVersion,
+             * then an ErrorCode of TCMinVersionNotMet shall be responded to the invoker.
+             *
              * This command is fabric-scoped, so cannot be issued over a session that does not have an associated
              * fabric, i.e. over PASE session prior to an AddNOC command. In addition, this command is only permitted
              * over CASE and must be issued by a node associated with the ongoing Fail-Safe context. An ErrorCode of
@@ -527,7 +760,7 @@ export declare namespace GeneralCommissioning {
              *   2. The commissioning window at the Server shall be closed.
              *
              *   3. Any temporary administrative privileges automatically granted to any open PASE session shall be
-             *      revoked (see Section 6.6.2.8, “Bootstrapping of the Access Control Cluster”).
+             *      revoked (see Section 6.6.2.9, “Bootstrapping of the Access Control Cluster”).
              *
              *   4. The Secure Session Context of any PASE session still established at the Server shall be cleared.
              *
@@ -537,38 +770,1110 @@ export declare namespace GeneralCommissioning {
              * any previously established PASE session to still be usable, due to the server having cleared such
              * sessions.
              *
-             * @see {@link MatterSpecification.v13.Core} § 11.10.6.6
+             * @see {@link MatterSpecification.v13.Core} § 11.10.7.6
              */
             readonly commissioningComplete: Command<void, import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
                  * This field shall contain the result of the operation, based on the behavior specified in the functional
                  * description of the CommissioningComplete command.
                  *
-                 * @see {@link MatterSpecification.v13.Core} § 11.10.6.7.1
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.7.1
                  */
                 errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
                 /**
-                 * See Section 11.10.6.1, “Common fields in General Commissioning cluster responses”.
+                 * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
                  *
-                 * @see {@link MatterSpecification.v13.Core} § 11.10.6.7.2
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.7.2
                  */
                 debugText: import("../tlv/TlvObject.js").FieldType<string>;
             }>, any>;
         };
-    }, []>;
+        /**
+         * This metadata controls which GeneralCommissioningCluster elements matter.js activates for specific feature
+         * combinations.
+         */
+        readonly extensions: readonly [{
+            readonly flags: {
+                readonly termsAndConditions: true;
+            };
+            readonly component: {
+                readonly attributes: {
+                    /**
+                     * Indicates the last version of the T&Cs for which the device received user acknowledgements. On factory
+                     * reset this field shall be reset to 0.
+                     *
+                     * When Custom Commissioning Flow is used to obtain user consent (e. g. because the Commissioner does not
+                     * support the TC feature), the manufacturer-provided means for obtaining user consent shall ensure that
+                     * this attribute is set to a value which is greater than or equal to TCMinRequiredVersion before returning
+                     * the user back to the originating Commissioner (see Enhanced Setup Flow).
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.6.6
+                     */
+                    readonly tcAcceptedVersion: Attribute<number, any>;
+                    /**
+                     * Indicates the minimum version of the texts presented by the Enhanced Setup Flow that need to be accepted
+                     * by the user for this device. This attribute may change as the result of an OTA update.
+                     *
+                     * If an event such as a software update causes TCAcceptedVersion to become less than TCMinRequiredVersion,
+                     * then the device shall update TCAcknowledgementsRequired to True so that an administrator can detect that
+                     * a newer version of the texts needs to be presented to the user.
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.6.7
+                     */
+                    readonly tcMinRequiredVersion: Attribute<number, any>;
+                    /**
+                     * Indicates the user’s response to the presented terms. Each bit position corresponds to a user response
+                     * for the associated index of matching text, such that bit 0 (bit value 1) is for text index 0. Bit 15
+                     * (bit value 0x8000) is for text index 15. A bit value of 1 indicates acceptance and a value of 0
+                     * indicates non-acceptance. For example, if there are two texts that were presented where the first (bit
+                     * 0, value 1) was declined and the second accepted (bit 1, value 2), we would expect the resulting value
+                     * of the map to be 2.
+                     *
+                     * Whenever a user provides responses to newly presented terms and conditions, this attribute shall be
+                     * updated with the latest responses. This may happen in response to updated terms that were presented to
+                     * the user. On a factory reset this field shall be reset with all bits set to 0.
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.6.8
+                     */
+                    readonly tcAcknowledgements: Attribute<number, any>;
+                    /**
+                     * Indicates whether SetTCAcknowledgements is currently required to be called with the inclusion of
+                     * mandatory terms accepted.
+                     *
+                     * This attribute may be present and False in the case where no terms and conditions are currently
+                     * mandatory to accept for CommissioningComplete to succeed.
+                     *
+                     * This attribute may appear, or become True after commissioning (e.g. due to a firmware update) to
+                     * indicate that new Terms & Conditions are available that the user must accept.
+                     *
+                     * Upon Factory Data Reset, this attribute shall be set to a value of True.
+                     *
+                     * When Custom Commissioning Flow is used to obtain user consent (e.g. because the Commissioner does not
+                     * support the TC feature), the manufacturer-provided means for obtaining user consent shall ensure that
+                     * this attribute is set to False before returning the user back to the original Commissioner (see Enhanced
+                     * Setup Flow).
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.6.9
+                     */
+                    readonly tcAcknowledgementsRequired: Attribute<boolean, any>;
+                    /**
+                     * Indicates the System Time in seconds when any functionality limitations will begin due to a lack of
+                     * acceptance of updated Terms and Conditions, as described in Section 5.7.4.5, “Presenting Updated Terms
+                     * and Conditions”.
+                     *
+                     * A null value indicates that there is no pending deadline for updated TC acceptance.
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.6.10
+                     */
+                    readonly tcUpdateDeadline: Attribute<number | null, any>;
+                };
+                readonly commands: {
+                    /**
+                     * This command sets the user acknowledgements received in the Enhanced Setup Flow Terms & Conditions into
+                     * the node.
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.7.8
+                     */
+                    readonly setTcAcknowledgements: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                        /**
+                         * This field shall contain the version of the Enhanced Setup Flow Terms & Conditions that were presented to
+                         * the user.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 11.10.7.8.1
+                         */
+                        tcVersion: import("../tlv/TlvObject.js").FieldType<number>;
+                        /**
+                         * This field shall contain the user responses to the Enhanced Setup Flow Terms & Conditions as a map where
+                         * each bit set in the bitmap corresponds to an accepted term in the file located at EnhancedSetupFlowTCUrl.
+                         *
+                         * ### Effect on Receipt
+                         *
+                         * This command shall copy the user responses and accepted version to the presented Enhanced Setup Flow Terms &
+                         * Conditions from the values provided in the TCUserResponse and TCVersion fields to the TCAcknowledgements
+                         * Attribute and the TCAcceptedVersion Attribute fields respectively.
+                         *
+                         * This command shall result in success with an ErrorCode value of OK in the SetTCAcknowledgementsResponse if
+                         * all required terms were accepted by the user. Specifically, all bits have a value of 1 in TCAcknowledgements
+                         * whose ordinal is marked as required in the file located at EnhancedSe
+                         *
+                         * tupFlowTCUrl.
+                         *
+                         * If the TCVersion field is less than the TCMinRequiredVersion, then the ErrorCode of TCMinVersionNotMet shall
+                         * be returned and TCAcknowledgements shall remain unchanged.
+                         *
+                         * If TCVersion is greater than or equal to TCMinRequiredVersion, but the TCUserResponse value indicates that
+                         * not all required terms were accepted by the user, then the ErrorCode of RequiredTCNotAccepted shall be
+                         * returned and TCAcknowledgements shall remain unchanged.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 11.10.7.8.2
+                         */
+                        tcUserResponse: import("../tlv/TlvObject.js").FieldType<number>;
+                    }>, import("../tlv/TlvObject.js").TypeFromFields<{
+                        /**
+                         * This field shall contain the result of the operation, based on the behavior specified in the functional
+                         * description of the SetTCAcknowledgements command.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 11.10.7.9.1
+                         */
+                        errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
+                    }>, any>;
+                };
+            };
+        }];
+    };
     /**
-     * This cluster is used to manage basic commissioning lifecycle.
-     *
-     * This cluster also represents responsibilities related to commissioning that don’t well fit other commissioning
-     * clusters, like Section 11.9, “Network Commissioning Cluster”. It also hosts functionalities those other clusters
-     * may depend on.
-     *
-     * @see {@link MatterSpecification.v13.Core} § 11.10
+     * @see {@link Cluster}
      */
-    interface Cluster extends Identity<typeof ClusterInstance> {
-    }
-    const Cluster: Cluster;
-    const Complete: Cluster;
+    const ClusterInstance: MutableCluster<{
+        readonly id: 48;
+        readonly name: "GeneralCommissioning";
+        readonly revision: 2;
+        readonly features: {
+            /**
+             * TermsAndConditions
+             *
+             * Supports Terms & Conditions acknowledgement
+             */
+            readonly termsAndConditions: BitFlag;
+        };
+        readonly attributes: {
+            /**
+             * This attribute allows for the storage of a client-provided small payload which Administrators and
+             * Commissioners may write and then subsequently read, to keep track of their own progress. This may be
+             * used by the Commissioner to avoid repeating already-executed actions upon re-establishing a
+             * commissioning link after an error.
+             *
+             * On start/restart of the server, such as when a device is power-cycled, this attribute shall be reset to
+             * zero.
+             *
+             * Some commands related to commissioning also have a side-effect of updating or resetting this attribute
+             * and this is specified in their respective functional descriptions.
+             *
+             * The format of the value within this attribute is unspecified and its value is not otherwise used by the
+             * functioning of any cluster, other than being set as a side-effect of commands where this behavior is
+             * described.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.1
+             */
+            readonly breadcrumb: WritableAttribute<number | bigint, any>;
+            /**
+             * This attribute shall describe critical parameters needed at the beginning of commissioning flow. See
+             * BasicCommissioningInfo for more information.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.2
+             */
+            readonly basicCommissioningInfo: FixedAttribute<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain a conservative initial duration (in seconds) to set in the FailSafe for the
+                 * commissioning flow to complete successfully. This may vary depending on the speed or sleepiness of the
+                 * Commissionee. This value, if used in the ArmFailSafe command’s ExpiryLengthSeconds field SHOULD allow a
+                 * Commissioner to proceed with a nominal commissioning without having to-rearm the fail-safe, with some margin.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.5.3.1
+                 */
+                failSafeExpiryLengthSeconds: import("../tlv/TlvObject.js").FieldType<number>;
+                /**
+                 * This field shall contain a conservative value in seconds denoting the maximum total duration for which a
+                 * fail safe timer can be re-armed. See Section 11.10.7.2.1, “Fail Safe Context”.
+                 *
+                 * The value of this field shall be greater than or equal to the FailSafeExpiryLengthSeconds. Absent additional
+                 * guidelines, it is recommended that the value of this field be aligned with the initial Announcement Duration
+                 * and default to 900 seconds.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.5.3.2
+                 */
+                maxCumulativeFailsafeSeconds: import("../tlv/TlvObject.js").FieldType<number>;
+            }>, any>;
+            /**
+             * Indicates the regulatory configuration for the product.
+             *
+             * Note that the country code is part of Basic Information Cluster and therefore NOT listed on the
+             * RegulatoryConfig attribute.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.3
+             */
+            readonly regulatoryConfig: Attribute<RegulatoryLocationType, any>;
+            /**
+             * LocationCapability is statically set by the manufacturer and indicates if this Node needs to be told an
+             * exact RegulatoryLocation. For example a Node which is "Indoor Only" would not be certified for outdoor
+             * use at all, and thus there is no need for a commissioner to set or ask the user about whether the device
+             * will be used inside or outside. However a device which states its capability is
+             *
+             * "Indoor/Outdoor" means it would like clarification if possible.
+             *
+             * For Nodes without radio network interfaces (e.g. Ethernet-only devices), the value IndoorOutdoor shall
+             * always be used.
+             *
+             * The default value of the RegulatoryConfig attribute is the value of LocationCapability attribute. This
+             * means devices always have a safe default value, and Commissioners which choose to implement smarter
+             * handling can.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.4
+             */
+            readonly locationCapability: FixedAttribute<RegulatoryLocationType, any>;
+            /**
+             * Indicates whether this device supports "concurrent connection flow" commissioning mode (see Section 5.5,
+             * “Commissioning Flows”). If false, the device only supports "non-concurrent connection flow" mode.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.6.5
+             */
+            readonly supportsConcurrentConnection: FixedAttribute<boolean, any>;
+        };
+        readonly commands: {
+            /**
+             * Success or failure of this command shall be communicated by the ArmFailSafeResponse command, unless some
+             * data model validations caused a failure status code to be issued during the processing of the command.
+             *
+             * If the fail-safe timer is not currently armed, the commissioning window is open, and the command was
+             * received over a CASE session, the command shall leave the current fail-safe state unchanged and
+             * immediately respond with an ArmFailSafeResponse containing an ErrorCode value of BusyWithOtherAdmin.
+             * This is done to allow commissioners, which use PASE connections, the opportunity to use the failsafe
+             * during the relatively short commissioning window.
+             *
+             * Otherwise, the command shall arm or re-arm the "fail-safe timer" with an expiry time set for a duration
+             * of ExpiryLengthSeconds, or disarm it, depending on the situation:
+             *
+             *   • If ExpiryLengthSeconds is 0 and the fail-safe timer was already armed and the accessing fabric
+             *     matches the Fabric currently associated with the fail-safe context, then the fail-safe timer shall
+             *     be immediately expired (see further below for side-effects of expiration).
+             *
+             *   • If ExpiryLengthSeconds is 0 and the fail-safe timer was not armed, then this command invocation
+             *     shall lead to a success response with no side-effects against the fail-safe context.
+             *
+             *   • If ExpiryLengthSeconds is non-zero and the fail-safe timer was not currently armed, then the
+             *     fail-safe timer shall be armed for that duration.
+             *
+             *   • If ExpiryLengthSeconds is non-zero and the fail-safe timer was currently armed, and the accessing
+             *     Fabric matches the fail-safe context’s associated Fabric, then the fail-safe timer shall be re-
+             *     armed to expire in ExpiryLengthSeconds.
+             *
+             *   • Otherwise, the command shall leave the current fail-safe state unchanged and immediately respond
+             *     with ArmFailSafeResponse containing an ErrorCode value of BusyWithOtherAdmin, indicating a likely
+             *     conflict between commissioners.
+             *
+             * The value of the Breadcrumb field shall be written to the Breadcrumb on successful execution of the
+             * command.
+             *
+             * If the receiver restarts unexpectedly (e.g., power interruption, software crash, or other reset) the
+             * receiver shall behave as if the fail-safe timer expired and perform the sequence of clean-up steps
+             * listed below.
+             *
+             * On successful execution of the command, the ErrorCode field of the ArmFailSafeResponse shall be set to
+             * OK.
+             *
+             * ### Fail Safe Context
+             *
+             * When first arming the fail-safe timer, a 'Fail Safe Context' shall be created on the receiver, to track
+             * the following state information while the fail-safe is armed:
+             *
+             *   • The fail-safe timer duration.
+             *
+             *   • The state of all Network Commissioning Networks attribute configurations, to allow recovery of
+             *     connectivity after Fail-Safe expiry.
+             *
+             *   • Whether an AddNOC command or UpdateNOC command has taken place.
+             *
+             *   • A Fabric Index for the fabric-scoping of the context, starting at the accessing fabric index for the
+             *     ArmFailSafe command, and updated with the Fabric Index associated with an AddNOC command or an
+             *     UpdateNOC command being invoked successfully during the ongoing Fail-Safe timer period.
+             *
+             *   • The operational credentials associated with any Fabric whose configuration is affected by the
+             *     UpdateNOC command.
+             *
+             *   • Optionally: the previous state of non-fabric-scoped data that is mutated during the fail-safe period.
+             *
+             * Note the following to assist in understanding the above state-keeping, which summarizes other normative
+             * requirements in the respective sections:
+             *
+             *   • The AddNOC command can only be invoked once per contiguous non-expiring fail-safe timer period, and
+             *     only if no UpdateNOC command was previously processed within the same fail-safe timer period.
+             *
+             *   • The UpdateNOC command can only be invoked once per contiguous non-expiring fail-safe timer period,
+             *     can only be invoked over a CASE session, and only if no AddNOC command was previously processed in
+             *     the same fail-safe timer period.
+             *
+             * On creation of the Fail Safe Context a second timer shall be created to expire at
+             * MaxCumulativeFailsafeSeconds as specified in BasicCommissioningInfo. This Cumulative Fail Safe Context
+             * timer (CFSC timer) serves to limit the lifetime of any particular Fail Safe Context; it shall NOT be
+             * extended or modified on subsequent invocations of ArmFailSafe associated with this Fail Safe Context.
+             * Upon expiry of the CFSC timer, the receiver shall execute cleanup behavior equivalent to that of
+             * fail-safe timer expiration as detailed in Section 11.10.7.2.2, “Behavior on expiry of Fail-Safe timer”.
+             * Termination of the session prior to the expiration of that timer for any reason (including a successful
+             * end of commissioning or an expiry of a fail-safe timer) shall also delete the CFSC timer.
+             *
+             * ### Behavior on expiry of Fail-Safe timer
+             *
+             * If the fail-safe timer expires before the CommissioningComplete command is successfully invoked, the
+             * following sequence of clean-up steps shall be executed, in order, by the receiver:
+             *
+             *   1. Terminate any open PASE secure session by clearing any associated Secure Session Context at the
+             *       Server.
+             *
+             *   2. Revoke the temporary administrative privileges granted to any open PASE session (see Section
+             *       6.6.2.9, “Bootstrapping of the Access Control Cluster”) at the Server.
+             *
+             *   3. If an AddNOC or UpdateNOC command has been successfully invoked, terminate all CASE sessions
+             *       associated with the Fabric whose Fabric Index is recorded in the Fail-Safe context (see
+             *       ArmFailSafe) by clearing any associated Secure Session Context at the Server.
+             *
+             *   4. Reset the configuration of all Network Commissioning Networks attribute to their state prior to the
+             *       Fail-Safe being armed.
+             *
+             *   5. If an UpdateNOC command had been successfully invoked, revert the state of operational key pair,
+             *       NOC and ICAC for that Fabric to the state prior to the Fail-Safe timer being armed, for the Fabric
+             *       Index that was the subject of the UpdateNOC command.
+             *
+             *   6. If an AddNOC command had been successfully invoked, achieve the equivalent effect of invoking the
+             *       RemoveFabric command against the Fabric Index stored in the Fail-Safe Context for the Fabric Index
+             *       that was the subject of the AddNOC command. This shall remove all associations to that Fabric
+             *       including all fabric-scoped data, and may possibly factory-reset the device depending on current
+             *       device state. This shall only apply to Fabrics added during the fail-safe period as the result of
+             *       the AddNOC command.
+             *
+             *   7. If the CSRRequest command had been successfully invoked, but no AddNOC or UpdateNOC command had
+             *       been successfully invoked, then the new operational key pair temporarily generated for the
+             *       purposes of NOC addition or update (see Node Operational CSR Procedure) shall be removed as it is
+             *       no longer needed.
+             *
+             *   8. Remove any RCACs added by the AddTrustedRootCertificate command that are not currently referenced
+             *       by any entry in the Fabrics attribute.
+             *
+             *   9. Reset the Breadcrumb attribute to zero.
+             *
+             *   10. Optionally: if no factory-reset resulted from the previous steps, it is recommended that the Node
+             *       rollback the state of all non fabric-scoped data present in the Fail-Safe context.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.7.2
+             */
+            readonly armFailSafe: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                expiryLengthSeconds: import("../tlv/TlvObject.js").FieldType<number>;
+                breadcrumb: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+            }>, import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain the result of the operation, based on the behavior specified in the functional
+                 * description of the ArmFailSafe command.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.3.1
+                 */
+                errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
+                /**
+                 * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.3.2
+                 */
+                debugText: import("../tlv/TlvObject.js").FieldType<string>;
+            }>, any>;
+            /**
+             * This shall add or update the regulatory configuration in the RegulatoryConfig Attribute to the value
+             * provided in the NewRegulatoryConfig field.
+             *
+             * Success or failure of this command shall be communicated by the SetRegulatoryConfigResponse command,
+             * unless some data model validations caused a failure status code to be issued during the processing of
+             * the command.
+             *
+             * The CountryCode field shall conforms to ISO 3166-1 alpha-2 and shall be used to set the Location
+             * attribute reflected by the Basic Information Cluster.
+             *
+             * If the server limits some of the values (e.g. locked to a particular country, with no regulatory data
+             * for others), then setting regulatory information outside a valid country or location shall still set the
+             * Location attribute reflected by the Basic Information Cluster configuration, but the
+             * SetRegulatoryConfigResponse replied shall have the ErrorCode field set to ValueOutsideRange error.
+             *
+             * If the LocationCapability attribute is not Indoor/Outdoor and the NewRegulatoryConfig value
+             *
+             * received does not match either the Indoor or Outdoor fixed value in LocationCapability, then the
+             * SetRegulatoryConfigResponse replied shall have the ErrorCode field set to ValueOutsideRange error and
+             * the RegulatoryConfig attribute and associated internal radio configuration shall remain unchanged.
+             *
+             * If the LocationCapability attribute is set to Indoor/Outdoor, then the RegulatoryConfig attribute shall
+             * be set to match the NewRegulatoryConfig field.
+             *
+             * On successful execution of the command, the ErrorCode field of the SetRegulatoryConfigResponse shall be
+             * set to OK.
+             *
+             * The Breadcrumb field shall be used to atomically set the Breadcrumb attribute on success of this
+             * command, when SetRegulatoryConfigResponse has the ErrorCode field set to OK. If the command fails, the
+             * Breadcrumb attribute shall be left unchanged.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.7.4
+             */
+            readonly setRegulatoryConfig: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                newRegulatoryConfig: import("../tlv/TlvObject.js").FieldType<RegulatoryLocationType>;
+                countryCode: import("../tlv/TlvObject.js").FieldType<string>;
+                breadcrumb: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+            }>, import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain the result of the operation, based on the behavior specified in the functional
+                 * description of the SetRegulatoryConfig command.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.5.1
+                 */
+                errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
+                /**
+                 * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.5.2
+                 */
+                debugText: import("../tlv/TlvObject.js").FieldType<string>;
+            }>, any>;
+            /**
+             * This command has no data.
+             *
+             * Success or failure of this command shall be communicated by the CommissioningCompleteResponse command,
+             * unless some data model validations caused a failure status code to be issued during the processing of
+             * the command.
+             *
+             * This command signals the Server that the Commissioner or Administrator has successfully completed all
+             * steps needed during the Fail-Safe period, such as commissioning (see Section 5.5, “Commissioning Flows”)
+             * or other Administrator operations requiring usage of the Fail Safe timer. It ensures that the Server is
+             * configured in a state such that it still has all necessary elements to be fully operable within a
+             * Fabric, such as ACL entries (see Section 9.10, “Access Control Cluster”) and operational credentials
+             * (see Section 6.4, “Node Operational Credentials Specification”), and that the Node is reachable using
+             * CASE
+             *
+             * (CASE)”) over an operational network.
+             *
+             * An ErrorCode of NoFailSafe shall be responded to the invoker if the CommissioningComplete command was
+             * received when no Fail-Safe context exists.
+             *
+             * If Terms and Conditions are required, then an ErrorCode of TCAcknowledgementsNotReceived shall be
+             * responded to the invoker if the user acknowledgements to the required Terms and Conditions have not been
+             * provided. If the TCAcceptedVersion for the provided acknowledgements is less than TCMinRequiredVersion,
+             * then an ErrorCode of TCMinVersionNotMet shall be responded to the invoker.
+             *
+             * This command is fabric-scoped, so cannot be issued over a session that does not have an associated
+             * fabric, i.e. over PASE session prior to an AddNOC command. In addition, this command is only permitted
+             * over CASE and must be issued by a node associated with the ongoing Fail-Safe context. An ErrorCode of
+             * InvalidAuthentication shall be responded to the invoker if the CommissioningComplete command was
+             * received outside a CASE session (e.g., over Group messaging, or PASE session after AddNOC), or if the
+             * accessing fabric is not the one associated with the ongoing Fail-Safe context.
+             *
+             * This command shall only result in success with an ErrorCode value of OK in the
+             * CommissioningCompleteResponse if received over a CASE session and the accessing fabric index matches the
+             * Fabric Index associated with the current Fail-Safe context. In other words:
+             *
+             *   • If no AddNOC command had been successfully invoked, the CommissioningComplete command must originate
+             *     from the Fabric that initiated the Fail-Safe context.
+             *
+             *   • After an AddNOC command has been successfully invoked, the CommissioningComplete command must
+             *     originate from the Fabric which was joined through the execution of that command, which updated the
+             *     Fail-Safe context’s Fabric Index.
+             *
+             * On successful execution of the CommissioningComplete command, where the CommissioningCompleteResponse
+             * has an ErrorCode of OK, the following actions shall be undertaken on the Server:
+             *
+             *   1. The Fail-Safe timer associated with the current Fail-Safe context shall be disarmed.
+             *
+             *   2. The commissioning window at the Server shall be closed.
+             *
+             *   3. Any temporary administrative privileges automatically granted to any open PASE session shall be
+             *      revoked (see Section 6.6.2.9, “Bootstrapping of the Access Control Cluster”).
+             *
+             *   4. The Secure Session Context of any PASE session still established at the Server shall be cleared.
+             *
+             *   5. The Breadcrumb attribute shall be reset to zero.
+             *
+             * After receipt of a CommissioningCompleteResponse with an ErrorCode value of OK, a client cannot expect
+             * any previously established PASE session to still be usable, due to the server having cleared such
+             * sessions.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.7.6
+             */
+            readonly commissioningComplete: Command<void, import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain the result of the operation, based on the behavior specified in the functional
+                 * description of the CommissioningComplete command.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.7.1
+                 */
+                errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
+                /**
+                 * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.7.2
+                 */
+                debugText: import("../tlv/TlvObject.js").FieldType<string>;
+            }>, any>;
+        };
+        /**
+         * This metadata controls which GeneralCommissioningCluster elements matter.js activates for specific feature
+         * combinations.
+         */
+        readonly extensions: readonly [{
+            readonly flags: {
+                readonly termsAndConditions: true;
+            };
+            readonly component: {
+                readonly attributes: {
+                    /**
+                     * Indicates the last version of the T&Cs for which the device received user acknowledgements. On factory
+                     * reset this field shall be reset to 0.
+                     *
+                     * When Custom Commissioning Flow is used to obtain user consent (e. g. because the Commissioner does not
+                     * support the TC feature), the manufacturer-provided means for obtaining user consent shall ensure that
+                     * this attribute is set to a value which is greater than or equal to TCMinRequiredVersion before returning
+                     * the user back to the originating Commissioner (see Enhanced Setup Flow).
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.6.6
+                     */
+                    readonly tcAcceptedVersion: Attribute<number, any>;
+                    /**
+                     * Indicates the minimum version of the texts presented by the Enhanced Setup Flow that need to be accepted
+                     * by the user for this device. This attribute may change as the result of an OTA update.
+                     *
+                     * If an event such as a software update causes TCAcceptedVersion to become less than TCMinRequiredVersion,
+                     * then the device shall update TCAcknowledgementsRequired to True so that an administrator can detect that
+                     * a newer version of the texts needs to be presented to the user.
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.6.7
+                     */
+                    readonly tcMinRequiredVersion: Attribute<number, any>;
+                    /**
+                     * Indicates the user’s response to the presented terms. Each bit position corresponds to a user response
+                     * for the associated index of matching text, such that bit 0 (bit value 1) is for text index 0. Bit 15
+                     * (bit value 0x8000) is for text index 15. A bit value of 1 indicates acceptance and a value of 0
+                     * indicates non-acceptance. For example, if there are two texts that were presented where the first (bit
+                     * 0, value 1) was declined and the second accepted (bit 1, value 2), we would expect the resulting value
+                     * of the map to be 2.
+                     *
+                     * Whenever a user provides responses to newly presented terms and conditions, this attribute shall be
+                     * updated with the latest responses. This may happen in response to updated terms that were presented to
+                     * the user. On a factory reset this field shall be reset with all bits set to 0.
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.6.8
+                     */
+                    readonly tcAcknowledgements: Attribute<number, any>;
+                    /**
+                     * Indicates whether SetTCAcknowledgements is currently required to be called with the inclusion of
+                     * mandatory terms accepted.
+                     *
+                     * This attribute may be present and False in the case where no terms and conditions are currently
+                     * mandatory to accept for CommissioningComplete to succeed.
+                     *
+                     * This attribute may appear, or become True after commissioning (e.g. due to a firmware update) to
+                     * indicate that new Terms & Conditions are available that the user must accept.
+                     *
+                     * Upon Factory Data Reset, this attribute shall be set to a value of True.
+                     *
+                     * When Custom Commissioning Flow is used to obtain user consent (e.g. because the Commissioner does not
+                     * support the TC feature), the manufacturer-provided means for obtaining user consent shall ensure that
+                     * this attribute is set to False before returning the user back to the original Commissioner (see Enhanced
+                     * Setup Flow).
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.6.9
+                     */
+                    readonly tcAcknowledgementsRequired: Attribute<boolean, any>;
+                    /**
+                     * Indicates the System Time in seconds when any functionality limitations will begin due to a lack of
+                     * acceptance of updated Terms and Conditions, as described in Section 5.7.4.5, “Presenting Updated Terms
+                     * and Conditions”.
+                     *
+                     * A null value indicates that there is no pending deadline for updated TC acceptance.
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.6.10
+                     */
+                    readonly tcUpdateDeadline: Attribute<number | null, any>;
+                };
+                readonly commands: {
+                    /**
+                     * This command sets the user acknowledgements received in the Enhanced Setup Flow Terms & Conditions into
+                     * the node.
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 11.10.7.8
+                     */
+                    readonly setTcAcknowledgements: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                        /**
+                         * This field shall contain the version of the Enhanced Setup Flow Terms & Conditions that were presented to
+                         * the user.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 11.10.7.8.1
+                         */
+                        tcVersion: import("../tlv/TlvObject.js").FieldType<number>;
+                        /**
+                         * This field shall contain the user responses to the Enhanced Setup Flow Terms & Conditions as a map where
+                         * each bit set in the bitmap corresponds to an accepted term in the file located at EnhancedSetupFlowTCUrl.
+                         *
+                         * ### Effect on Receipt
+                         *
+                         * This command shall copy the user responses and accepted version to the presented Enhanced Setup Flow Terms &
+                         * Conditions from the values provided in the TCUserResponse and TCVersion fields to the TCAcknowledgements
+                         * Attribute and the TCAcceptedVersion Attribute fields respectively.
+                         *
+                         * This command shall result in success with an ErrorCode value of OK in the SetTCAcknowledgementsResponse if
+                         * all required terms were accepted by the user. Specifically, all bits have a value of 1 in TCAcknowledgements
+                         * whose ordinal is marked as required in the file located at EnhancedSe
+                         *
+                         * tupFlowTCUrl.
+                         *
+                         * If the TCVersion field is less than the TCMinRequiredVersion, then the ErrorCode of TCMinVersionNotMet shall
+                         * be returned and TCAcknowledgements shall remain unchanged.
+                         *
+                         * If TCVersion is greater than or equal to TCMinRequiredVersion, but the TCUserResponse value indicates that
+                         * not all required terms were accepted by the user, then the ErrorCode of RequiredTCNotAccepted shall be
+                         * returned and TCAcknowledgements shall remain unchanged.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 11.10.7.8.2
+                         */
+                        tcUserResponse: import("../tlv/TlvObject.js").FieldType<number>;
+                    }>, import("../tlv/TlvObject.js").TypeFromFields<{
+                        /**
+                         * This field shall contain the result of the operation, based on the behavior specified in the functional
+                         * description of the SetTCAcknowledgements command.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 11.10.7.9.1
+                         */
+                        errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
+                    }>, any>;
+                };
+            };
+        }];
+    }, []>;
+    /**
+     * This cluster is used to manage basic commissioning lifecycle.
+     *
+     * This cluster also represents responsibilities related to commissioning that don’t well fit other commissioning
+     * clusters, like Section 11.9, “Network Commissioning Cluster”. It also hosts functionalities those other clusters
+     * may depend on.
+     *
+     * GeneralCommissioningCluster supports optional features that you can enable with the
+     * GeneralCommissioningCluster.with() factory method.
+     *
+     * @see {@link MatterSpecification.v13.Core} § 11.10
+     */
+    interface Cluster extends Identity<typeof ClusterInstance> {
+    }
+    const Cluster: Cluster;
+    /**
+     * @see {@link Complete}
+     */
+    const CompleteInstance: MutableCluster<{
+        readonly id: import("#general").Branded<48, "ClusterId">;
+        readonly name: "GeneralCommissioning";
+        readonly revision: 2;
+        readonly features: {
+            /**
+             * TermsAndConditions
+             *
+             * Supports Terms & Conditions acknowledgement
+             */
+            readonly termsAndConditions: BitFlag;
+        };
+        readonly attributes: {
+            readonly tcAcceptedVersion: Attribute<number, any> & {
+                readonly optional: true;
+                readonly isConditional: true;
+                readonly optionalIf: [] | import("../cluster/Cluster.js").ConditionalFeatureList<import("../schema/BitmapSchema.js").BitSchema>;
+                readonly mandatoryIf: [] | [{
+                    termsAndConditions: boolean;
+                }];
+            };
+            readonly tcMinRequiredVersion: Attribute<number, any> & {
+                readonly optional: true;
+                readonly isConditional: true;
+                readonly optionalIf: [] | import("../cluster/Cluster.js").ConditionalFeatureList<import("../schema/BitmapSchema.js").BitSchema>;
+                readonly mandatoryIf: [] | [{
+                    termsAndConditions: boolean;
+                }];
+            };
+            readonly tcAcknowledgements: Attribute<number, any> & {
+                readonly optional: true;
+                readonly isConditional: true;
+                readonly optionalIf: [] | import("../cluster/Cluster.js").ConditionalFeatureList<import("../schema/BitmapSchema.js").BitSchema>;
+                readonly mandatoryIf: [] | [{
+                    termsAndConditions: boolean;
+                }];
+            };
+            readonly tcAcknowledgementsRequired: Attribute<boolean, any> & {
+                readonly optional: true;
+                readonly isConditional: true;
+                readonly optionalIf: [] | import("../cluster/Cluster.js").ConditionalFeatureList<import("../schema/BitmapSchema.js").BitSchema>;
+                readonly mandatoryIf: [] | [{
+                    termsAndConditions: boolean;
+                }];
+            };
+            readonly tcUpdateDeadline: Attribute<number | null, any> & {
+                readonly optional: true;
+                readonly isConditional: true;
+                readonly optionalIf: [] | import("../cluster/Cluster.js").ConditionalFeatureList<import("../schema/BitmapSchema.js").BitSchema>;
+                readonly mandatoryIf: [] | [{
+                    termsAndConditions: boolean;
+                }];
+            };
+            readonly breadcrumb: WritableAttribute<number | bigint, any>;
+            readonly basicCommissioningInfo: FixedAttribute<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain a conservative initial duration (in seconds) to set in the FailSafe for the
+                 * commissioning flow to complete successfully. This may vary depending on the speed or sleepiness of the
+                 * Commissionee. This value, if used in the ArmFailSafe command’s ExpiryLengthSeconds field SHOULD allow a
+                 * Commissioner to proceed with a nominal commissioning without having to-rearm the fail-safe, with some margin.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.5.3.1
+                 */
+                failSafeExpiryLengthSeconds: import("../tlv/TlvObject.js").FieldType<number>;
+                /**
+                 * This field shall contain a conservative value in seconds denoting the maximum total duration for which a
+                 * fail safe timer can be re-armed. See Section 11.10.7.2.1, “Fail Safe Context”.
+                 *
+                 * The value of this field shall be greater than or equal to the FailSafeExpiryLengthSeconds. Absent additional
+                 * guidelines, it is recommended that the value of this field be aligned with the initial Announcement Duration
+                 * and default to 900 seconds.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.5.3.2
+                 */
+                maxCumulativeFailsafeSeconds: import("../tlv/TlvObject.js").FieldType<number>;
+            }>, any>;
+            readonly regulatoryConfig: Attribute<RegulatoryLocationType, any>;
+            readonly locationCapability: FixedAttribute<RegulatoryLocationType, any>;
+            readonly supportsConcurrentConnection: FixedAttribute<boolean, any>;
+            readonly clusterRevision: Attribute<number, never>;
+            readonly featureMap: Attribute<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+                /**
+                 * TermsAndConditions
+                 *
+                 * Supports Terms & Conditions acknowledgement
+                 */
+                readonly termsAndConditions: BitFlag;
+            }>, never>;
+            readonly attributeList: Attribute<import("../index.js").AttributeId[], never>;
+            readonly acceptedCommandList: Attribute<import("../index.js").CommandId[], never>;
+            readonly generatedCommandList: Attribute<import("../index.js").CommandId[], never>;
+        };
+        readonly commands: {
+            readonly setTcAcknowledgements: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain the version of the Enhanced Setup Flow Terms & Conditions that were presented to
+                 * the user.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.8.1
+                 */
+                tcVersion: import("../tlv/TlvObject.js").FieldType<number>;
+                /**
+                 * This field shall contain the user responses to the Enhanced Setup Flow Terms & Conditions as a map where
+                 * each bit set in the bitmap corresponds to an accepted term in the file located at EnhancedSetupFlowTCUrl.
+                 *
+                 * ### Effect on Receipt
+                 *
+                 * This command shall copy the user responses and accepted version to the presented Enhanced Setup Flow Terms &
+                 * Conditions from the values provided in the TCUserResponse and TCVersion fields to the TCAcknowledgements
+                 * Attribute and the TCAcceptedVersion Attribute fields respectively.
+                 *
+                 * This command shall result in success with an ErrorCode value of OK in the SetTCAcknowledgementsResponse if
+                 * all required terms were accepted by the user. Specifically, all bits have a value of 1 in TCAcknowledgements
+                 * whose ordinal is marked as required in the file located at EnhancedSe
+                 *
+                 * tupFlowTCUrl.
+                 *
+                 * If the TCVersion field is less than the TCMinRequiredVersion, then the ErrorCode of TCMinVersionNotMet shall
+                 * be returned and TCAcknowledgements shall remain unchanged.
+                 *
+                 * If TCVersion is greater than or equal to TCMinRequiredVersion, but the TCUserResponse value indicates that
+                 * not all required terms were accepted by the user, then the ErrorCode of RequiredTCNotAccepted shall be
+                 * returned and TCAcknowledgements shall remain unchanged.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.8.2
+                 */
+                tcUserResponse: import("../tlv/TlvObject.js").FieldType<number>;
+            }>, import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain the result of the operation, based on the behavior specified in the functional
+                 * description of the SetTCAcknowledgements command.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.9.1
+                 */
+                errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
+            }>, any> & {
+                readonly optional: true;
+                readonly isConditional: true;
+                readonly optionalIf: [] | import("../cluster/Cluster.js").ConditionalFeatureList<import("../schema/BitmapSchema.js").BitSchema>;
+                readonly mandatoryIf: [] | [{
+                    termsAndConditions: boolean;
+                }];
+            };
+            /**
+             * Success or failure of this command shall be communicated by the ArmFailSafeResponse command, unless some
+             * data model validations caused a failure status code to be issued during the processing of the command.
+             *
+             * If the fail-safe timer is not currently armed, the commissioning window is open, and the command was
+             * received over a CASE session, the command shall leave the current fail-safe state unchanged and
+             * immediately respond with an ArmFailSafeResponse containing an ErrorCode value of BusyWithOtherAdmin.
+             * This is done to allow commissioners, which use PASE connections, the opportunity to use the failsafe
+             * during the relatively short commissioning window.
+             *
+             * Otherwise, the command shall arm or re-arm the "fail-safe timer" with an expiry time set for a duration
+             * of ExpiryLengthSeconds, or disarm it, depending on the situation:
+             *
+             *   • If ExpiryLengthSeconds is 0 and the fail-safe timer was already armed and the accessing fabric
+             *     matches the Fabric currently associated with the fail-safe context, then the fail-safe timer shall
+             *     be immediately expired (see further below for side-effects of expiration).
+             *
+             *   • If ExpiryLengthSeconds is 0 and the fail-safe timer was not armed, then this command invocation
+             *     shall lead to a success response with no side-effects against the fail-safe context.
+             *
+             *   • If ExpiryLengthSeconds is non-zero and the fail-safe timer was not currently armed, then the
+             *     fail-safe timer shall be armed for that duration.
+             *
+             *   • If ExpiryLengthSeconds is non-zero and the fail-safe timer was currently armed, and the accessing
+             *     Fabric matches the fail-safe context’s associated Fabric, then the fail-safe timer shall be re-
+             *     armed to expire in ExpiryLengthSeconds.
+             *
+             *   • Otherwise, the command shall leave the current fail-safe state unchanged and immediately respond
+             *     with ArmFailSafeResponse containing an ErrorCode value of BusyWithOtherAdmin, indicating a likely
+             *     conflict between commissioners.
+             *
+             * The value of the Breadcrumb field shall be written to the Breadcrumb on successful execution of the
+             * command.
+             *
+             * If the receiver restarts unexpectedly (e.g., power interruption, software crash, or other reset) the
+             * receiver shall behave as if the fail-safe timer expired and perform the sequence of clean-up steps
+             * listed below.
+             *
+             * On successful execution of the command, the ErrorCode field of the ArmFailSafeResponse shall be set to
+             * OK.
+             *
+             * ### Fail Safe Context
+             *
+             * When first arming the fail-safe timer, a 'Fail Safe Context' shall be created on the receiver, to track
+             * the following state information while the fail-safe is armed:
+             *
+             *   • The fail-safe timer duration.
+             *
+             *   • The state of all Network Commissioning Networks attribute configurations, to allow recovery of
+             *     connectivity after Fail-Safe expiry.
+             *
+             *   • Whether an AddNOC command or UpdateNOC command has taken place.
+             *
+             *   • A Fabric Index for the fabric-scoping of the context, starting at the accessing fabric index for the
+             *     ArmFailSafe command, and updated with the Fabric Index associated with an AddNOC command or an
+             *     UpdateNOC command being invoked successfully during the ongoing Fail-Safe timer period.
+             *
+             *   • The operational credentials associated with any Fabric whose configuration is affected by the
+             *     UpdateNOC command.
+             *
+             *   • Optionally: the previous state of non-fabric-scoped data that is mutated during the fail-safe period.
+             *
+             * Note the following to assist in understanding the above state-keeping, which summarizes other normative
+             * requirements in the respective sections:
+             *
+             *   • The AddNOC command can only be invoked once per contiguous non-expiring fail-safe timer period, and
+             *     only if no UpdateNOC command was previously processed within the same fail-safe timer period.
+             *
+             *   • The UpdateNOC command can only be invoked once per contiguous non-expiring fail-safe timer period,
+             *     can only be invoked over a CASE session, and only if no AddNOC command was previously processed in
+             *     the same fail-safe timer period.
+             *
+             * On creation of the Fail Safe Context a second timer shall be created to expire at
+             * MaxCumulativeFailsafeSeconds as specified in BasicCommissioningInfo. This Cumulative Fail Safe Context
+             * timer (CFSC timer) serves to limit the lifetime of any particular Fail Safe Context; it shall NOT be
+             * extended or modified on subsequent invocations of ArmFailSafe associated with this Fail Safe Context.
+             * Upon expiry of the CFSC timer, the receiver shall execute cleanup behavior equivalent to that of
+             * fail-safe timer expiration as detailed in Section 11.10.7.2.2, “Behavior on expiry of Fail-Safe timer”.
+             * Termination of the session prior to the expiration of that timer for any reason (including a successful
+             * end of commissioning or an expiry of a fail-safe timer) shall also delete the CFSC timer.
+             *
+             * ### Behavior on expiry of Fail-Safe timer
+             *
+             * If the fail-safe timer expires before the CommissioningComplete command is successfully invoked, the
+             * following sequence of clean-up steps shall be executed, in order, by the receiver:
+             *
+             *   1. Terminate any open PASE secure session by clearing any associated Secure Session Context at the
+             *       Server.
+             *
+             *   2. Revoke the temporary administrative privileges granted to any open PASE session (see Section
+             *       6.6.2.9, “Bootstrapping of the Access Control Cluster”) at the Server.
+             *
+             *   3. If an AddNOC or UpdateNOC command has been successfully invoked, terminate all CASE sessions
+             *       associated with the Fabric whose Fabric Index is recorded in the Fail-Safe context (see
+             *       ArmFailSafe) by clearing any associated Secure Session Context at the Server.
+             *
+             *   4. Reset the configuration of all Network Commissioning Networks attribute to their state prior to the
+             *       Fail-Safe being armed.
+             *
+             *   5. If an UpdateNOC command had been successfully invoked, revert the state of operational key pair,
+             *       NOC and ICAC for that Fabric to the state prior to the Fail-Safe timer being armed, for the Fabric
+             *       Index that was the subject of the UpdateNOC command.
+             *
+             *   6. If an AddNOC command had been successfully invoked, achieve the equivalent effect of invoking the
+             *       RemoveFabric command against the Fabric Index stored in the Fail-Safe Context for the Fabric Index
+             *       that was the subject of the AddNOC command. This shall remove all associations to that Fabric
+             *       including all fabric-scoped data, and may possibly factory-reset the device depending on current
+             *       device state. This shall only apply to Fabrics added during the fail-safe period as the result of
+             *       the AddNOC command.
+             *
+             *   7. If the CSRRequest command had been successfully invoked, but no AddNOC or UpdateNOC command had
+             *       been successfully invoked, then the new operational key pair temporarily generated for the
+             *       purposes of NOC addition or update (see Node Operational CSR Procedure) shall be removed as it is
+             *       no longer needed.
+             *
+             *   8. Remove any RCACs added by the AddTrustedRootCertificate command that are not currently referenced
+             *       by any entry in the Fabrics attribute.
+             *
+             *   9. Reset the Breadcrumb attribute to zero.
+             *
+             *   10. Optionally: if no factory-reset resulted from the previous steps, it is recommended that the Node
+             *       rollback the state of all non fabric-scoped data present in the Fail-Safe context.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.7.2
+             */
+            readonly armFailSafe: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                expiryLengthSeconds: import("../tlv/TlvObject.js").FieldType<number>;
+                breadcrumb: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+            }>, import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain the result of the operation, based on the behavior specified in the functional
+                 * description of the ArmFailSafe command.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.3.1
+                 */
+                errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
+                /**
+                 * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.3.2
+                 */
+                debugText: import("../tlv/TlvObject.js").FieldType<string>;
+            }>, any>;
+            /**
+             * This shall add or update the regulatory configuration in the RegulatoryConfig Attribute to the value
+             * provided in the NewRegulatoryConfig field.
+             *
+             * Success or failure of this command shall be communicated by the SetRegulatoryConfigResponse command,
+             * unless some data model validations caused a failure status code to be issued during the processing of
+             * the command.
+             *
+             * The CountryCode field shall conforms to ISO 3166-1 alpha-2 and shall be used to set the Location
+             * attribute reflected by the Basic Information Cluster.
+             *
+             * If the server limits some of the values (e.g. locked to a particular country, with no regulatory data
+             * for others), then setting regulatory information outside a valid country or location shall still set the
+             * Location attribute reflected by the Basic Information Cluster configuration, but the
+             * SetRegulatoryConfigResponse replied shall have the ErrorCode field set to ValueOutsideRange error.
+             *
+             * If the LocationCapability attribute is not Indoor/Outdoor and the NewRegulatoryConfig value
+             *
+             * received does not match either the Indoor or Outdoor fixed value in LocationCapability, then the
+             * SetRegulatoryConfigResponse replied shall have the ErrorCode field set to ValueOutsideRange error and
+             * the RegulatoryConfig attribute and associated internal radio configuration shall remain unchanged.
+             *
+             * If the LocationCapability attribute is set to Indoor/Outdoor, then the RegulatoryConfig attribute shall
+             * be set to match the NewRegulatoryConfig field.
+             *
+             * On successful execution of the command, the ErrorCode field of the SetRegulatoryConfigResponse shall be
+             * set to OK.
+             *
+             * The Breadcrumb field shall be used to atomically set the Breadcrumb attribute on success of this
+             * command, when SetRegulatoryConfigResponse has the ErrorCode field set to OK. If the command fails, the
+             * Breadcrumb attribute shall be left unchanged.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.7.4
+             */
+            readonly setRegulatoryConfig: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                newRegulatoryConfig: import("../tlv/TlvObject.js").FieldType<RegulatoryLocationType>;
+                countryCode: import("../tlv/TlvObject.js").FieldType<string>;
+                breadcrumb: import("../tlv/TlvObject.js").FieldType<number | bigint>;
+            }>, import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain the result of the operation, based on the behavior specified in the functional
+                 * description of the SetRegulatoryConfig command.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.5.1
+                 */
+                errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
+                /**
+                 * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.5.2
+                 */
+                debugText: import("../tlv/TlvObject.js").FieldType<string>;
+            }>, any>;
+            /**
+             * This command has no data.
+             *
+             * Success or failure of this command shall be communicated by the CommissioningCompleteResponse command,
+             * unless some data model validations caused a failure status code to be issued during the processing of
+             * the command.
+             *
+             * This command signals the Server that the Commissioner or Administrator has successfully completed all
+             * steps needed during the Fail-Safe period, such as commissioning (see Section 5.5, “Commissioning Flows”)
+             * or other Administrator operations requiring usage of the Fail Safe timer. It ensures that the Server is
+             * configured in a state such that it still has all necessary elements to be fully operable within a
+             * Fabric, such as ACL entries (see Section 9.10, “Access Control Cluster”) and operational credentials
+             * (see Section 6.4, “Node Operational Credentials Specification”), and that the Node is reachable using
+             * CASE
+             *
+             * (CASE)”) over an operational network.
+             *
+             * An ErrorCode of NoFailSafe shall be responded to the invoker if the CommissioningComplete command was
+             * received when no Fail-Safe context exists.
+             *
+             * If Terms and Conditions are required, then an ErrorCode of TCAcknowledgementsNotReceived shall be
+             * responded to the invoker if the user acknowledgements to the required Terms and Conditions have not been
+             * provided. If the TCAcceptedVersion for the provided acknowledgements is less than TCMinRequiredVersion,
+             * then an ErrorCode of TCMinVersionNotMet shall be responded to the invoker.
+             *
+             * This command is fabric-scoped, so cannot be issued over a session that does not have an associated
+             * fabric, i.e. over PASE session prior to an AddNOC command. In addition, this command is only permitted
+             * over CASE and must be issued by a node associated with the ongoing Fail-Safe context. An ErrorCode of
+             * InvalidAuthentication shall be responded to the invoker if the CommissioningComplete command was
+             * received outside a CASE session (e.g., over Group messaging, or PASE session after AddNOC), or if the
+             * accessing fabric is not the one associated with the ongoing Fail-Safe context.
+             *
+             * This command shall only result in success with an ErrorCode value of OK in the
+             * CommissioningCompleteResponse if received over a CASE session and the accessing fabric index matches the
+             * Fabric Index associated with the current Fail-Safe context. In other words:
+             *
+             *   • If no AddNOC command had been successfully invoked, the CommissioningComplete command must originate
+             *     from the Fabric that initiated the Fail-Safe context.
+             *
+             *   • After an AddNOC command has been successfully invoked, the CommissioningComplete command must
+             *     originate from the Fabric which was joined through the execution of that command, which updated the
+             *     Fail-Safe context’s Fabric Index.
+             *
+             * On successful execution of the CommissioningComplete command, where the CommissioningCompleteResponse
+             * has an ErrorCode of OK, the following actions shall be undertaken on the Server:
+             *
+             *   1. The Fail-Safe timer associated with the current Fail-Safe context shall be disarmed.
+             *
+             *   2. The commissioning window at the Server shall be closed.
+             *
+             *   3. Any temporary administrative privileges automatically granted to any open PASE session shall be
+             *      revoked (see Section 6.6.2.9, “Bootstrapping of the Access Control Cluster”).
+             *
+             *   4. The Secure Session Context of any PASE session still established at the Server shall be cleared.
+             *
+             *   5. The Breadcrumb attribute shall be reset to zero.
+             *
+             * After receipt of a CommissioningCompleteResponse with an ErrorCode value of OK, a client cannot expect
+             * any previously established PASE session to still be usable, due to the server having cleared such
+             * sessions.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 11.10.7.6
+             */
+            readonly commissioningComplete: Command<void, import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall contain the result of the operation, based on the behavior specified in the functional
+                 * description of the CommissioningComplete command.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.7.1
+                 */
+                errorCode: import("../tlv/TlvObject.js").FieldType<CommissioningError>;
+                /**
+                 * See Section 11.10.7.1, “Common fields in General Commissioning cluster responses”.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.10.7.7.2
+                 */
+                debugText: import("../tlv/TlvObject.js").FieldType<string>;
+            }>, any>;
+        };
+    }, []>;
+    /**
+     * This cluster supports all GeneralCommissioning 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.
+     */
+    interface Complete extends Identity<typeof CompleteInstance> {
+    }
+    const Complete: Complete;
 }
 export type GeneralCommissioningCluster = GeneralCommissioning.Cluster;
 export declare const GeneralCommissioningCluster: GeneralCommissioning.Cluster;