@matter/types 0.16.0-alpha.0-20251104-8c3166ea3 → 0.16.0-alpha.0-20251107-6bcb5baf4

package/dist/esm/clusters/thread-border-router-management.d.ts

@@ -13,7 +13,7 @@ export declare namespace ThreadBorderRouterManagement {
     /**
      * These are optional features supported by ThreadBorderRouterManagementCluster.
      *
-     * @see {@link MatterSpecification.v141.Cluster} § 10.3.4
+     * @see {@link MatterSpecification.v142.Cluster} § 10.3.4
      */
     enum Feature {
         /**
@@ -28,14 +28,14 @@ export declare namespace ThreadBorderRouterManagement {
          *   change, e.g. when the Thread Border Router serves non-Matter devices that do not support PAN change for an
          *   implementation-specific reason.
          *
-         * @see {@link MatterSpecification.v141.Cluster} § 10.3.4.1
+         * @see {@link MatterSpecification.v142.Cluster} § 10.3.4.1
          */
         PanChange = "PanChange"
     }
     /**
      * Input to the ThreadBorderRouterManagement setPendingDatasetRequest command
      *
-     * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.5
+     * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.5
      */
     const TlvSetPendingDatasetRequest: import("../tlv/TlvObject.js").ObjectSchema<{
         pendingDataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
@@ -43,14 +43,14 @@ export declare namespace ThreadBorderRouterManagement {
     /**
      * Input to the ThreadBorderRouterManagement setPendingDatasetRequest command
      *
-     * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.5
+     * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.5
      */
     interface SetPendingDatasetRequest extends TypeFromSchema<typeof TlvSetPendingDatasetRequest> {
     }
     /**
      * This command is sent in response to GetActiveDatasetRequest or GetPendingDatasetRequest command.
      *
-     * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.3
+     * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.3
      */
     const TlvDatasetResponse: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
@@ -60,41 +60,41 @@ export declare namespace ThreadBorderRouterManagement {
          * Router is connected as an octet string containing the raw Thread TLV value of the dataset, as defined in the
          * Thread specification.
          *
-         * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.3.1
+         * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.3.1
          */
         dataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
     }>;
     /**
      * This command is sent in response to GetActiveDatasetRequest or GetPendingDatasetRequest command.
      *
-     * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.3
+     * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.3
      */
     interface DatasetResponse extends TypeFromSchema<typeof TlvDatasetResponse> {
     }
     /**
      * Input to the ThreadBorderRouterManagement setActiveDatasetRequest command
      *
-     * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4
+     * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4
      */
     const TlvSetActiveDatasetRequest: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
          * This field shall contain the active dataset to set of the Thread network to configure in the Border Router as
          * an octet string containing the raw Thread TLV value of the dataset, as defined in the Thread specification.
          *
-         * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4.1
+         * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4.1
          */
         activeDataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
         /**
          * See Breadcrumb Attribute section of General Commissioning Cluster in [MatterCore] for usage.
          *
-         * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4.2
+         * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4.2
          */
         breadcrumb: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
     }>;
     /**
      * Input to the ThreadBorderRouterManagement setActiveDatasetRequest command
      *
-     * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4
+     * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4
      */
     interface SetActiveDatasetRequest extends TypeFromSchema<typeof TlvSetActiveDatasetRequest> {
     }
@@ -121,7 +121,7 @@ export declare namespace ThreadBorderRouterManagement {
              * Router is connected, with the value given in the PendingDataset parameter. The Border Router will manage
              * activation of the pending dataset as defined in the Thread specification.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.5
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.5
              */
             readonly setPendingDatasetRequest: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                 pendingDataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
@@ -146,7 +146,7 @@ export declare namespace ThreadBorderRouterManagement {
              *   change, e.g. when the Thread Border Router serves non-Matter devices that do not support PAN change for
              *   an implementation-specific reason.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.4.1
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.4.1
              */
             readonly panChange: BitFlag;
         };
@@ -157,14 +157,14 @@ export declare namespace ThreadBorderRouterManagement {
              * <VendorName> <ProductName>._meshcop._udp. An example name would be ACME Border Router
              * (74be)._meshcop._udp.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.1
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.1
              */
             readonly borderRouterName: Attribute<string, any>;
             /**
              * Indicates a 16-byte globally unique ID for a Thread Border Router device. This ID is
              * manufacturer-specific, and it is created and managed by the border router’s implementation.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.2
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.2
              */
             readonly borderAgentId: Attribute<AllowSharedBufferSource, any>;
             /**
@@ -173,13 +173,13 @@ export declare namespace ThreadBorderRouterManagement {
              * The format shall match the value mapping defined in the "Version TLV" section of the Thread
              * specification. For example, Thread 1.3.0 would have ThreadVersion set to 4.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.3
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.3
              */
             readonly threadVersion: FixedAttribute<number, any>;
             /**
              * Indicates whether the associated IEEE 802.15.4 Thread interface is enabled or disabled.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.4
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.4
              */
             readonly interfaceEnabled: Attribute<boolean, any>;
             /**
@@ -188,7 +188,7 @@ export declare namespace ThreadBorderRouterManagement {
              * connected. This attribute shall be updated when a new Active dataset is configured on the Thread network
              * to which the border router is connected.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.5
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.5
              */
             readonly activeDatasetTimestamp: Attribute<number | bigint | null, any>;
             /**
@@ -197,7 +197,7 @@ export declare namespace ThreadBorderRouterManagement {
              * is connected. This attribute shall be updated when a new Pending dataset is configured on the Thread
              * network to which the border router is connected.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.6
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.6
              */
             readonly pendingDatasetTimestamp: Attribute<number | bigint | null, any>;
         };
@@ -214,7 +214,7 @@ export declare namespace ThreadBorderRouterManagement {
              *
              * Otherwise, this shall generate a DatasetResponse command.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.1
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.1
              */
             readonly getActiveDatasetRequest: Command<void, import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
@@ -224,7 +224,7 @@ export declare namespace ThreadBorderRouterManagement {
                  * Router is connected as an octet string containing the raw Thread TLV value of the dataset, as defined in the
                  * Thread specification.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.3.1
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.3.1
                  */
                 dataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
             }>, any>;
@@ -240,7 +240,7 @@ export declare namespace ThreadBorderRouterManagement {
              *
              * Otherwise, this shall generate a DatasetResponse command.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.2
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.2
              */
             readonly getPendingDatasetRequest: Command<void, import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
@@ -250,7 +250,7 @@ export declare namespace ThreadBorderRouterManagement {
                  * Router is connected as an octet string containing the raw Thread TLV value of the dataset, as defined in the
                  * Thread specification.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.3.1
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.3.1
                  */
                 dataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
             }>, any>;
@@ -258,20 +258,20 @@ export declare namespace ThreadBorderRouterManagement {
              * This command shall be used to set the active Dataset of the Thread network to which the Border Router is
              * connected, when there is no active dataset already.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4
              */
             readonly setActiveDatasetRequest: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
                  * This field shall contain the active dataset to set of the Thread network to configure in the Border Router as
                  * an octet string containing the raw Thread TLV value of the dataset, as defined in the Thread specification.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4.1
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4.1
                  */
                 activeDataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
                 /**
                  * See Breadcrumb Attribute section of General Commissioning Cluster in [MatterCore] for usage.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4.2
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4.2
                  */
                 breadcrumb: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, void, any>;
@@ -304,7 +304,7 @@ export declare namespace ThreadBorderRouterManagement {
                      * Router is connected, with the value given in the PendingDataset parameter. The Border Router will manage
                      * activation of the pending dataset as defined in the Thread specification.
                      *
-                     * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.5
+                     * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.5
                      */
                     readonly setPendingDatasetRequest: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                         pendingDataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
@@ -331,7 +331,7 @@ export declare namespace ThreadBorderRouterManagement {
              *   change, e.g. when the Thread Border Router serves non-Matter devices that do not support PAN change for
              *   an implementation-specific reason.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.4.1
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.4.1
              */
             readonly panChange: BitFlag;
         };
@@ -342,14 +342,14 @@ export declare namespace ThreadBorderRouterManagement {
              * <VendorName> <ProductName>._meshcop._udp. An example name would be ACME Border Router
              * (74be)._meshcop._udp.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.1
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.1
              */
             readonly borderRouterName: Attribute<string, any>;
             /**
              * Indicates a 16-byte globally unique ID for a Thread Border Router device. This ID is
              * manufacturer-specific, and it is created and managed by the border router’s implementation.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.2
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.2
              */
             readonly borderAgentId: Attribute<AllowSharedBufferSource, any>;
             /**
@@ -358,13 +358,13 @@ export declare namespace ThreadBorderRouterManagement {
              * The format shall match the value mapping defined in the "Version TLV" section of the Thread
              * specification. For example, Thread 1.3.0 would have ThreadVersion set to 4.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.3
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.3
              */
             readonly threadVersion: FixedAttribute<number, any>;
             /**
              * Indicates whether the associated IEEE 802.15.4 Thread interface is enabled or disabled.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.4
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.4
              */
             readonly interfaceEnabled: Attribute<boolean, any>;
             /**
@@ -373,7 +373,7 @@ export declare namespace ThreadBorderRouterManagement {
              * connected. This attribute shall be updated when a new Active dataset is configured on the Thread network
              * to which the border router is connected.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.5
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.5
              */
             readonly activeDatasetTimestamp: Attribute<number | bigint | null, any>;
             /**
@@ -382,7 +382,7 @@ export declare namespace ThreadBorderRouterManagement {
              * is connected. This attribute shall be updated when a new Pending dataset is configured on the Thread
              * network to which the border router is connected.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.6
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.6
              */
             readonly pendingDatasetTimestamp: Attribute<number | bigint | null, any>;
         };
@@ -399,7 +399,7 @@ export declare namespace ThreadBorderRouterManagement {
              *
              * Otherwise, this shall generate a DatasetResponse command.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.1
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.1
              */
             readonly getActiveDatasetRequest: Command<void, import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
@@ -409,7 +409,7 @@ export declare namespace ThreadBorderRouterManagement {
                  * Router is connected as an octet string containing the raw Thread TLV value of the dataset, as defined in the
                  * Thread specification.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.3.1
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.3.1
                  */
                 dataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
             }>, any>;
@@ -425,7 +425,7 @@ export declare namespace ThreadBorderRouterManagement {
              *
              * Otherwise, this shall generate a DatasetResponse command.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.2
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.2
              */
             readonly getPendingDatasetRequest: Command<void, import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
@@ -435,7 +435,7 @@ export declare namespace ThreadBorderRouterManagement {
                  * Router is connected as an octet string containing the raw Thread TLV value of the dataset, as defined in the
                  * Thread specification.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.3.1
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.3.1
                  */
                 dataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
             }>, any>;
@@ -443,20 +443,20 @@ export declare namespace ThreadBorderRouterManagement {
              * This command shall be used to set the active Dataset of the Thread network to which the Border Router is
              * connected, when there is no active dataset already.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4
              */
             readonly setActiveDatasetRequest: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
                  * This field shall contain the active dataset to set of the Thread network to configure in the Border Router as
                  * an octet string containing the raw Thread TLV value of the dataset, as defined in the Thread specification.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4.1
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4.1
                  */
                 activeDataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
                 /**
                  * See Breadcrumb Attribute section of General Commissioning Cluster in [MatterCore] for usage.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4.2
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4.2
                  */
                 breadcrumb: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, void, any>;
@@ -489,7 +489,7 @@ export declare namespace ThreadBorderRouterManagement {
                      * Router is connected, with the value given in the PendingDataset parameter. The Border Router will manage
                      * activation of the pending dataset as defined in the Thread specification.
                      *
-                     * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.5
+                     * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.5
                      */
                     readonly setPendingDatasetRequest: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                         pendingDataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
@@ -506,7 +506,7 @@ export declare namespace ThreadBorderRouterManagement {
      * ThreadBorderRouterManagementCluster supports optional features that you can enable with the
      * ThreadBorderRouterManagementCluster.with() factory method.
      *
-     * @see {@link MatterSpecification.v141.Cluster} § 10.3
+     * @see {@link MatterSpecification.v142.Cluster} § 10.3
      */
     interface Cluster extends Identity<typeof ClusterInstance> {
     }
@@ -529,7 +529,7 @@ export declare namespace ThreadBorderRouterManagement {
              *   change, e.g. when the Thread Border Router serves non-Matter devices that do not support PAN change for
              *   an implementation-specific reason.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.4.1
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.4.1
              */
             readonly panChange: BitFlag;
         };
@@ -540,14 +540,14 @@ export declare namespace ThreadBorderRouterManagement {
              * <VendorName> <ProductName>._meshcop._udp. An example name would be ACME Border Router
              * (74be)._meshcop._udp.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.1
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.1
              */
             readonly borderRouterName: Attribute<string, any>;
             /**
              * Indicates a 16-byte globally unique ID for a Thread Border Router device. This ID is
              * manufacturer-specific, and it is created and managed by the border router’s implementation.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.2
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.2
              */
             readonly borderAgentId: Attribute<AllowSharedBufferSource, any>;
             /**
@@ -556,13 +556,13 @@ export declare namespace ThreadBorderRouterManagement {
              * The format shall match the value mapping defined in the "Version TLV" section of the Thread
              * specification. For example, Thread 1.3.0 would have ThreadVersion set to 4.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.3
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.3
              */
             readonly threadVersion: FixedAttribute<number, any>;
             /**
              * Indicates whether the associated IEEE 802.15.4 Thread interface is enabled or disabled.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.4
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.4
              */
             readonly interfaceEnabled: Attribute<boolean, any>;
             /**
@@ -571,7 +571,7 @@ export declare namespace ThreadBorderRouterManagement {
              * connected. This attribute shall be updated when a new Active dataset is configured on the Thread network
              * to which the border router is connected.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.5
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.5
              */
             readonly activeDatasetTimestamp: Attribute<number | bigint | null, any>;
             /**
@@ -580,7 +580,7 @@ export declare namespace ThreadBorderRouterManagement {
              * is connected. This attribute shall be updated when a new Pending dataset is configured on the Thread
              * network to which the border router is connected.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.6
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.6
              */
             readonly pendingDatasetTimestamp: Attribute<number | bigint | null, any>;
         }, import("../cluster/Cluster.js").GlobalAttributes<{
@@ -594,7 +594,7 @@ export declare namespace ThreadBorderRouterManagement {
              *   change, e.g. when the Thread Border Router serves non-Matter devices that do not support PAN change for
              *   an implementation-specific reason.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.4.1
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.4.1
              */
             readonly panChange: BitFlag;
         }>>;
@@ -621,7 +621,7 @@ export declare namespace ThreadBorderRouterManagement {
              *
              * Otherwise, this shall generate a DatasetResponse command.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.1
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.1
              */
             readonly getActiveDatasetRequest: Command<void, import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
@@ -631,7 +631,7 @@ export declare namespace ThreadBorderRouterManagement {
                  * Router is connected as an octet string containing the raw Thread TLV value of the dataset, as defined in the
                  * Thread specification.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.3.1
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.3.1
                  */
                 dataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
             }>, any>;
@@ -647,7 +647,7 @@ export declare namespace ThreadBorderRouterManagement {
              *
              * Otherwise, this shall generate a DatasetResponse command.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.2
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.2
              */
             readonly getPendingDatasetRequest: Command<void, import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
@@ -657,7 +657,7 @@ export declare namespace ThreadBorderRouterManagement {
                  * Router is connected as an octet string containing the raw Thread TLV value of the dataset, as defined in the
                  * Thread specification.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.3.1
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.3.1
                  */
                 dataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
             }>, any>;
@@ -665,20 +665,20 @@ export declare namespace ThreadBorderRouterManagement {
              * This command shall be used to set the active Dataset of the Thread network to which the Border Router is
              * connected, when there is no active dataset already.
              *
-             * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4
+             * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4
              */
             readonly setActiveDatasetRequest: Command<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
                  * This field shall contain the active dataset to set of the Thread network to configure in the Border Router as
                  * an octet string containing the raw Thread TLV value of the dataset, as defined in the Thread specification.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4.1
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4.1
                  */
                 activeDataset: import("../tlv/TlvObject.js").FieldType<AllowSharedBufferSource>;
                 /**
                  * See Breadcrumb Attribute section of General Commissioning Cluster in [MatterCore] for usage.
                  *
-                 * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4.2
+                 * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4.2
                  */
                 breadcrumb: import("../tlv/TlvObject.js").OptionalFieldType<number | bigint>;
             }>, void, any>;

package/dist/esm/clusters/thread-border-router-management.js

@@ -31,7 +31,7 @@ var ThreadBorderRouterManagement;
      * Router is connected as an octet string containing the raw Thread TLV value of the dataset, as defined in the
      * Thread specification.
      *
-     * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.3.1
+     * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.3.1
      */
     dataset: TlvField(0, TlvByteString.bound({ maxLength: 254 }))
   });
@@ -40,13 +40,13 @@ var ThreadBorderRouterManagement;
      * This field shall contain the active dataset to set of the Thread network to configure in the Border Router as
      * an octet string containing the raw Thread TLV value of the dataset, as defined in the Thread specification.
      *
-     * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4.1
+     * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4.1
      */
     activeDataset: TlvField(0, TlvByteString.bound({ maxLength: 254 })),
     /**
      * See Breadcrumb Attribute section of General Commissioning Cluster in [MatterCore] for usage.
      *
-     * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4.2
+     * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4.2
      */
     breadcrumb: TlvOptionalField(1, TlvUInt64)
   });
@@ -70,7 +70,7 @@ var ThreadBorderRouterManagement;
        * Router is connected, with the value given in the PendingDataset parameter. The Border Router will manage
        * activation of the pending dataset as defined in the Thread specification.
        *
-       * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.5
+       * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.5
        */
       setPendingDatasetRequest: Command(
         4,
@@ -96,7 +96,7 @@ var ThreadBorderRouterManagement;
        *   change, e.g. when the Thread Border Router serves non-Matter devices that do not support PAN change for
        *   an implementation-specific reason.
        *
-       * @see {@link MatterSpecification.v141.Cluster} § 10.3.4.1
+       * @see {@link MatterSpecification.v142.Cluster} § 10.3.4.1
        */
       panChange: BitFlag(0)
     },
@@ -107,14 +107,14 @@ var ThreadBorderRouterManagement;
        * <VendorName> <ProductName>._meshcop._udp. An example name would be ACME Border Router
        * (74be)._meshcop._udp.
        *
-       * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.1
+       * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.1
        */
       borderRouterName: Attribute(0, TlvString.bound({ minLength: 1, maxLength: 63 })),
       /**
        * Indicates a 16-byte globally unique ID for a Thread Border Router device. This ID is
        * manufacturer-specific, and it is created and managed by the border router’s implementation.
        *
-       * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.2
+       * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.2
        */
       borderAgentId: Attribute(1, TlvByteString.bound({ length: 16 })),
       /**
@@ -123,13 +123,13 @@ var ThreadBorderRouterManagement;
        * The format shall match the value mapping defined in the "Version TLV" section of the Thread
        * specification. For example, Thread 1.3.0 would have ThreadVersion set to 4.
        *
-       * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.3
+       * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.3
        */
       threadVersion: FixedAttribute(2, TlvUInt16),
       /**
        * Indicates whether the associated IEEE 802.15.4 Thread interface is enabled or disabled.
        *
-       * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.4
+       * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.4
        */
       interfaceEnabled: Attribute(3, TlvBoolean, { persistent: true }),
       /**
@@ -138,7 +138,7 @@ var ThreadBorderRouterManagement;
        * connected. This attribute shall be updated when a new Active dataset is configured on the Thread network
        * to which the border router is connected.
        *
-       * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.5
+       * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.5
        */
       activeDatasetTimestamp: Attribute(4, TlvNullable(TlvUInt64), { persistent: true }),
       /**
@@ -147,7 +147,7 @@ var ThreadBorderRouterManagement;
        * is connected. This attribute shall be updated when a new Pending dataset is configured on the Thread
        * network to which the border router is connected.
        *
-       * @see {@link MatterSpecification.v141.Cluster} § 10.3.5.6
+       * @see {@link MatterSpecification.v142.Cluster} § 10.3.5.6
        */
       pendingDatasetTimestamp: Attribute(5, TlvNullable(TlvUInt64), { persistent: true })
     },
@@ -164,7 +164,7 @@ var ThreadBorderRouterManagement;
        *
        * Otherwise, this shall generate a DatasetResponse command.
        *
-       * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.1
+       * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.1
        */
       getActiveDatasetRequest: Command(
         0,
@@ -185,7 +185,7 @@ var ThreadBorderRouterManagement;
        *
        * Otherwise, this shall generate a DatasetResponse command.
        *
-       * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.2
+       * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.2
        */
       getPendingDatasetRequest: Command(
         1,
@@ -198,7 +198,7 @@ var ThreadBorderRouterManagement;
        * This command shall be used to set the active Dataset of the Thread network to which the Border Router is
        * connected, when there is no active dataset already.
        *
-       * @see {@link MatterSpecification.v141.Cluster} § 10.3.6.4
+       * @see {@link MatterSpecification.v142.Cluster} § 10.3.6.4
        */
       setActiveDatasetRequest: Command(
         3,