@matter/types 0.17.4 → 0.17.5-alpha.0-20260704-9ea70abfa

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

@@ -18,7 +18,7 @@ import type { Bytes, MaybePromise } from "@matter/general";
  * Privileged nodes within the same fabric as a Thread Border Router can use these interfaces to request and set
  * credentials information to the Thread network.
  *
- * @see {@link MatterSpecification.v151.Cluster} § 10.3
+ * @see {@link MatterSpecification.v16.Cluster} § 10.3
  */
 export declare namespace ThreadBorderRouterManagement {
     /**
@@ -32,7 +32,7 @@ export declare namespace ThreadBorderRouterManagement {
     export const name: "ThreadBorderRouterManagement";
 
     /**
-     * The cluster revision assigned by {@link MatterSpecification.v151.Cluster}.
+     * The cluster revision assigned by {@link MatterSpecification.v16.Cluster}.
      */
     export const revision: 1;
 
@@ -52,7 +52,7 @@ export declare namespace ThreadBorderRouterManagement {
          * (DNS-SD service name) as defined in the Thread specification, and has the following recommended format:
          * <VendorName> <ProductName>._meshcop._udp. An example name would be ACME Border Router (74be)._meshcop._udp.
          *
-         * @see {@link MatterSpecification.v151.Cluster} § 10.3.5.1
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.1
          */
         borderRouterName: string;
 
@@ -60,7 +60,7 @@ export declare namespace ThreadBorderRouterManagement {
          * 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.v151.Cluster} § 10.3.5.2
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.2
          */
         borderAgentId: Bytes;
 
@@ -70,14 +70,14 @@ 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.v151.Cluster} § 10.3.5.3
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.3
          */
         threadVersion: number;
 
         /**
          * Indicates whether the associated IEEE 802.15.4 Thread interface is enabled or disabled.
          *
-         * @see {@link MatterSpecification.v151.Cluster} § 10.3.5.4
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.4
          */
         interfaceEnabled: boolean;
 
@@ -87,7 +87,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.v151.Cluster} § 10.3.5.5
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.5
          */
         activeDatasetTimestamp: number | bigint | null;
 
@@ -97,7 +97,7 @@ export declare namespace ThreadBorderRouterManagement {
          * 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.v151.Cluster} § 10.3.5.6
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.6
          */
         pendingDatasetTimestamp: number | bigint | null;
     }
@@ -114,7 +114,7 @@ export declare namespace ThreadBorderRouterManagement {
          * (DNS-SD service name) as defined in the Thread specification, and has the following recommended format:
          * <VendorName> <ProductName>._meshcop._udp. An example name would be ACME Border Router (74be)._meshcop._udp.
          *
-         * @see {@link MatterSpecification.v151.Cluster} § 10.3.5.1
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.1
          */
         borderRouterName: string;
 
@@ -122,7 +122,7 @@ export declare namespace ThreadBorderRouterManagement {
          * 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.v151.Cluster} § 10.3.5.2
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.2
          */
         borderAgentId: Bytes;
 
@@ -132,14 +132,14 @@ 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.v151.Cluster} § 10.3.5.3
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.3
          */
         threadVersion: number;
 
         /**
          * Indicates whether the associated IEEE 802.15.4 Thread interface is enabled or disabled.
          *
-         * @see {@link MatterSpecification.v151.Cluster} § 10.3.5.4
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.4
          */
         interfaceEnabled: boolean;
 
@@ -149,7 +149,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.v151.Cluster} § 10.3.5.5
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.5
          */
         activeDatasetTimestamp: number | bigint | null;
 
@@ -159,7 +159,7 @@ export declare namespace ThreadBorderRouterManagement {
          * 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.v151.Cluster} § 10.3.5.6
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.5.6
          */
         pendingDatasetTimestamp: number | bigint | null;
     }
@@ -180,7 +180,7 @@ export declare namespace ThreadBorderRouterManagement {
          *
          * Otherwise, this shall generate a DatasetResponse command.
          *
-         * @see {@link MatterSpecification.v151.Cluster} § 10.3.6.1
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.6.1
          */
         getActiveDatasetRequest(): MaybePromise<DatasetResponse>;
 
@@ -196,7 +196,7 @@ export declare namespace ThreadBorderRouterManagement {
          *
          * Otherwise, this shall generate a DatasetResponse command.
          *
-         * @see {@link MatterSpecification.v151.Cluster} § 10.3.6.2
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.6.2
          */
         getPendingDatasetRequest(): MaybePromise<DatasetResponse>;
 
@@ -204,7 +204,7 @@ 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.v151.Cluster} § 10.3.6.4
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.6.4
          */
         setActiveDatasetRequest(request: SetActiveDatasetRequest): MaybePromise;
     }
@@ -231,7 +231,7 @@ export declare namespace ThreadBorderRouterManagement {
          * 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.v151.Cluster} § 10.3.6.5
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.6.5
          */
         setPendingDatasetRequest(request: SetPendingDatasetRequest): MaybePromise;
     }
@@ -253,7 +253,7 @@ export declare namespace ThreadBorderRouterManagement {
     /**
      * These are optional features supported by ThreadBorderRouterManagementCluster.
      *
-     * @see {@link MatterSpecification.v151.Cluster} § 10.3.4
+     * @see {@link MatterSpecification.v16.Cluster} § 10.3.4
      */
     export enum Feature {
         /**
@@ -268,7 +268,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.v151.Cluster} § 10.3.4.1
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.4.1
          */
         PanChange = "PanChange"
     }
@@ -276,7 +276,7 @@ export declare namespace ThreadBorderRouterManagement {
     /**
      * This command is sent in response to GetActiveDatasetRequest or GetPendingDatasetRequest command.
      *
-     * @see {@link MatterSpecification.v151.Cluster} § 10.3.6.3
+     * @see {@link MatterSpecification.v16.Cluster} § 10.3.6.3
      */
     export class DatasetResponse {
         constructor(values?: Partial<DatasetResponse>);
@@ -288,7 +288,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.v151.Cluster} § 10.3.6.3.1
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.6.3.1
          */
         dataset: Bytes;
     }
@@ -297,7 +297,7 @@ 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.v151.Cluster} § 10.3.6.4
+     * @see {@link MatterSpecification.v16.Cluster} § 10.3.6.4
      */
     export class SetActiveDatasetRequest {
         constructor(values?: Partial<SetActiveDatasetRequest>);
@@ -306,7 +306,7 @@ export declare namespace 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.v151.Cluster} § 10.3.6.4.1
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.6.4.1
          */
         activeDataset: Bytes;
 
@@ -314,7 +314,7 @@ export declare namespace ThreadBorderRouterManagement {
          * See Breadcrumb Attribute section of General Commissioning Cluster in [[MatterCore]](#ref_MatterCore) for
          * usage.
          *
-         * @see {@link MatterSpecification.v151.Cluster} § 10.3.6.4.2
+         * @see {@link MatterSpecification.v16.Cluster} § 10.3.6.4.2
          */
         breadcrumb?: number | bigint;
     }
@@ -337,7 +337,7 @@ export declare namespace ThreadBorderRouterManagement {
      * 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.v151.Cluster} § 10.3.6.5
+     * @see {@link MatterSpecification.v16.Cluster} § 10.3.6.5
      */
     export class SetPendingDatasetRequest {
         constructor(values?: Partial<SetPendingDatasetRequest>);