@matter/types 0.13.0-alpha.0-20250304-d4a7592a4 → 0.13.0-alpha.0-20250311-3eb0af5f2

package/dist/esm/clusters/bridged-device-basic-information.d.ts

@@ -5,15 +5,98 @@
  */
 /*** THIS FILE IS GENERATED, DO NOT EDIT ***/
 import { MutableCluster } from "../cluster/mutation/MutableCluster.js";
-import { OptionalFixedAttribute, OptionalWritableAttribute, Attribute, OptionalEvent, Event } from "../cluster/Cluster.js";
-import { BasicInformation } from "./basic-information.js";
+import { Command, Event, OptionalFixedAttribute, OptionalWritableAttribute, Attribute, FixedAttribute, OptionalEvent } from "../cluster/Cluster.js";
 import { TypeFromSchema } from "../tlv/TlvSchema.js";
+import { BitFlag } from "../schema/BitmapSchema.js";
+import { BasicInformation } from "./basic-information.js";
 import { Identity } from "#general";
 export declare namespace BridgedDeviceBasicInformation {
+    /**
+     * These are optional features supported by BridgedDeviceBasicInformationCluster.
+     *
+     * @see {@link MatterSpecification.v13.Core} § 9.13.4
+     */
+    enum Feature {
+        /**
+         * BridgedIcdSupport (BIS)
+         *
+         * Support bridged ICDs.
+         */
+        BridgedIcdSupport = "BridgedIcdSupport"
+    }
+    /**
+     * Input to the BridgedDeviceBasicInformation keepActive command
+     *
+     * @see {@link MatterSpecification.v13.Core} § 9.13.6.1
+     */
+    const TlvKeepActiveRequest: import("../tlv/TlvObject.js").ObjectSchema<{
+        /**
+         * This field shall indicate the duration, in milliseconds, that the device is requested to remain active, once
+         * the device becomes active again.
+         *
+         * The value of this field may be longer than the value supported by the bridged device and would, typically,
+         * be used by the client to request the server of the bridged device to stay active and responsive for this
+         * period to allow a sequence of message exchanges during that period.
+         *
+         * The client may slightly overestimate the duration it wants the bridged device to be active for, in order to
+         * account for network delays.
+         *
+         * @see {@link MatterSpecification.v13.Core} § 9.13.6.1.1
+         */
+        stayActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
+        /**
+         * This field shall indicate the period, in milliseconds, that the server will wait before the "pending active"
+         * state expires. See the KeepActive Command description for details.
+         *
+         * NOTE
+         *
+         * TimeoutMs is a timeout for the request, NOT the time the device will be awake for. The server will wait for
+         * up to TimeoutMs for the device. If after TimeoutMs the ICD
+         *
+         * device does NOT check-in, the server will not perform any actions.
+         *
+         * @see {@link MatterSpecification.v13.Core} § 9.13.6.1.2
+         */
+        timeoutMs: import("../tlv/TlvObject.js").FieldType<number>;
+    }>;
+    /**
+     * Input to the BridgedDeviceBasicInformation keepActive command
+     *
+     * @see {@link MatterSpecification.v13.Core} § 9.13.6.1
+     */
+    interface KeepActiveRequest extends TypeFromSchema<typeof TlvKeepActiveRequest> {
+    }
+    /**
+     * Body of the BridgedDeviceBasicInformation activeChanged event
+     *
+     * @see {@link MatterSpecification.v13.Core} § 9.13.7.3
+     */
+    const TlvActiveChangedEvent: import("../tlv/TlvObject.js").ObjectSchema<{
+        /**
+         * This field shall indicate the minimum duration, in milliseconds, that the bridged device will remain active
+         * after receiving the initial request from the KeepActive processing steps.
+         *
+         * If the bridged device is a Matter Intermittently Connected Device, PromisedActiveDuration shall be set to
+         * the PromisedActiveDuration value returned in the StayActiveResponse command.
+         *
+         * If the bridged device is not a Matter Intermittently Connected Device, the implementation of this is
+         * best-effort since it may interact with non-native protocol.
+         *
+         * @see {@link MatterSpecification.v13.Core} § 9.13.7.3.1
+         */
+        promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
+    }>;
+    /**
+     * Body of the BridgedDeviceBasicInformation activeChanged event
+     *
+     * @see {@link MatterSpecification.v13.Core} § 9.13.7.3
+     */
+    interface ActiveChangedEvent extends TypeFromSchema<typeof TlvActiveChangedEvent> {
+    }
     /**
      * Body of the BridgedDeviceBasicInformation startUp event
      *
-     * @see {@link MatterSpecification.v13.Core} § 9.13.5
+     * @see {@link MatterSpecification.v13.Core} § 9.13.7
      */
     const TlvStartUpEvent: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
@@ -26,14 +109,14 @@ export declare namespace BridgedDeviceBasicInformation {
     /**
      * Body of the BridgedDeviceBasicInformation startUp event
      *
-     * @see {@link MatterSpecification.v13.Core} § 9.13.5
+     * @see {@link MatterSpecification.v13.Core} § 9.13.7
      */
     interface StartUpEvent extends TypeFromSchema<typeof TlvStartUpEvent> {
     }
     /**
      * Body of the BridgedDeviceBasicInformation reachableChanged event
      *
-     * @see {@link MatterSpecification.v13.Core} § 9.13.5.2
+     * @see {@link MatterSpecification.v13.Core} § 9.13.7.2
      */
     const TlvReachableChangedEvent: import("../tlv/TlvObject.js").ObjectSchema<{
         /**
@@ -46,80 +129,450 @@ export declare namespace BridgedDeviceBasicInformation {
     /**
      * Body of the BridgedDeviceBasicInformation reachableChanged event
      *
-     * @see {@link MatterSpecification.v13.Core} § 9.13.5.2
+     * @see {@link MatterSpecification.v13.Core} § 9.13.7.2
      */
     interface ReachableChangedEvent extends TypeFromSchema<typeof TlvReachableChangedEvent> {
     }
+    /**
+     * A BridgedDeviceBasicInformationCluster supports these elements if it supports feature BridgedIcdSupport.
+     */
+    const BridgedIcdSupportComponent: {
+        readonly commands: {
+            /**
+             * Upon receipt, the server shall attempt to keep the bridged device active for the duration specified by
+             * the command, when the device is next active.
+             *
+             * The implementation of this is best-effort since it may interact with non-native protocols. However,
+             * several specific protocol requirements are:
+             *
+             *   • If the bridged device is a Matter Intermittently Connected Device, then the server shall send a
+             *     StayActiveRequest command with the StayActiveDuration field set to value of the StayActiveDuration
+             *     field in the received command to the bridged device when the bridged device next sends a checks-in
+             *     message or subscription report. See Intermittently Connected Devices Behavior for details on ICD
+             *     state management.
+             *
+             * When the bridge detects that the bridged device goes into an active state, an ActiveChanged event shall
+             * be generated.
+             *
+             * In order to avoid unnecessary power consumption in the bridged device:
+             *
+             *   • The server shall enter a "pending active" state for the associated device when the KeepActive
+             *     command is received. The server "pending active" state shall expire after the amount of time defined
+             *     by the TimeoutMs field, in milliseconds, if no subsequent KeepActive command is received. When a
+             *     KeepActive command is received, the "pending active" state is set, the StayActiveDuration is updated
+             *     to the greater of the new value and the previously stored value, and the TimeoutMs is updated to the
+             *     greater of the new value and the remaining time until the prior "pending active" state expires.
+             *
+             *   • The server shall only keep the bridged device active once for a request. (The server shall only
+             *     consider the operation performed if an associated ActiveChanged event was generated.)
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.6.1
+             */
+            readonly keepActive: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall indicate the duration, in milliseconds, that the device is requested to remain active, once
+                 * the device becomes active again.
+                 *
+                 * The value of this field may be longer than the value supported by the bridged device and would, typically,
+                 * be used by the client to request the server of the bridged device to stay active and responsive for this
+                 * period to allow a sequence of message exchanges during that period.
+                 *
+                 * The client may slightly overestimate the duration it wants the bridged device to be active for, in order to
+                 * account for network delays.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 9.13.6.1.1
+                 */
+                stayActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
+                /**
+                 * This field shall indicate the period, in milliseconds, that the server will wait before the "pending active"
+                 * state expires. See the KeepActive Command description for details.
+                 *
+                 * NOTE
+                 *
+                 * TimeoutMs is a timeout for the request, NOT the time the device will be awake for. The server will wait for
+                 * up to TimeoutMs for the device. If after TimeoutMs the ICD
+                 *
+                 * device does NOT check-in, the server will not perform any actions.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 9.13.6.1.2
+                 */
+                timeoutMs: import("../tlv/TlvObject.js").FieldType<number>;
+            }>, void, any>;
+        };
+        readonly events: {
+            /**
+             * This event (when supported) shall be generated the next time a bridged device becomes active after a
+             * KeepActive command is received.
+             *
+             * See KeepActive for more details.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7.3
+             */
+            readonly activeChanged: Event<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall indicate the minimum duration, in milliseconds, that the bridged device will remain active
+                 * after receiving the initial request from the KeepActive processing steps.
+                 *
+                 * If the bridged device is a Matter Intermittently Connected Device, PromisedActiveDuration shall be set to
+                 * the PromisedActiveDuration value returned in the StayActiveResponse command.
+                 *
+                 * If the bridged device is not a Matter Intermittently Connected Device, the implementation of this is
+                 * best-effort since it may interact with non-native protocol.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 9.13.7.3.1
+                 */
+                promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
+            }>, any>;
+        };
+    };
+    /**
+     * These elements and properties are present in all BridgedDeviceBasicInformation clusters.
+     */
+    const Base: {
+        readonly id: 57;
+        readonly name: "BridgedDeviceBasicInformation";
+        readonly revision: 4;
+        readonly features: {
+            /**
+             * BridgedIcdSupport
+             *
+             * Support bridged ICDs.
+             */
+            readonly bridgedIcdSupport: BitFlag;
+        };
+        readonly attributes: {
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly vendorName: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly vendorId: OptionalFixedAttribute<import("../datatype/VendorId.js").VendorId, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly productName: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly productId: OptionalFixedAttribute<number, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly nodeLabel: OptionalWritableAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly hardwareVersion: OptionalFixedAttribute<number, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly hardwareVersionString: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly softwareVersion: OptionalFixedAttribute<number, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly softwareVersionString: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly manufacturingDate: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly partNumber: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly productUrl: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly productLabel: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly serialNumber: OptionalFixedAttribute<string, any>;
+            /**
+             * This attribute shall be used to indicate whether the bridged device is reachable by the bridge, so a
+             * Matter Node which wants to communicate with a bridged device can get an indication that this might fail
+             * (when the attribute is False). Determination of reachability might not be perfect (e.g. depending on
+             * technology employed), so the Matter Node SHOULD be aware of the risk of false positives and negatives on
+             * reachability determination. For example, a bridged device may be marked as unreachable while it could
+             * actually be reached, and vice-versa. Also, detection (and indication) that a bridged device is not
+             * longer reachable may be delayed due to the technique employed (e.g. detecting that a number of expected
+             * messages from the bridged device did not arrive). Also see event ReachableChanged below.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5.1
+             */
+            readonly reachable: Attribute<boolean, any>;
+            /**
+             * This attribute shall, for a Bridged Device, be updated when the Bridge is factory reset. If the bridged
+             * device does not provide some unique id (e.g. in the case of bridging from non-Matter devices, or in case
+             * of bridging Matter devices from an earlier revision which were not required to provide a UniqueID
+             * attribute), the bridge shall generate a unique id on behalf of the bridged device.
+             *
+             * NOTE The UniqueID attribute was optional in cluster revisions prior to revision 4.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5.2
+             */
+            readonly uniqueId: FixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly productAppearance: OptionalFixedAttribute<import("../tlv/TlvObject.js").TypeFromFields<{
+                finish: import("../tlv/TlvObject.js").FieldType<BasicInformation.ProductFinish>;
+                primaryColor: import("../tlv/TlvObject.js").FieldType<BasicInformation.Color | null>;
+            }>, any>;
+        };
+        readonly events: {
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7
+             */
+            readonly startUp: OptionalEvent<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall be set to the same value as the one available in the SoftwareVersion attribute.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.1.6.1.1
+                 */
+                softwareVersion: import("../tlv/TlvObject.js").FieldType<number>;
+            }>, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7
+             */
+            readonly shutDown: OptionalEvent<void, any>;
+            /**
+             * The Leave event SHOULD be generated by the bridge when it detects that the associated device has left
+             * the non-Matter network.
+             *
+             * NOTE
+             *
+             * The FabricIndex field has the X conformance, indicating it shall NOT be present. This event, in the
+             * context of Bridged Device Basic Information cluster, has no usable fields, but the original Basic
+             * Information cluster’s field definition is kept for completeness.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7.1
+             */
+            readonly leave: OptionalEvent<void, any>;
+            /**
+             * This event shall be generated when there is a change in the Reachable attribute. Its purpose is to
+             * provide an indication towards interested parties that the reachability of a bridged device has changed
+             * over its native connectivity technology, so they may take appropriate action.
+             *
+             * After (re)start of a bridge this event may be generated.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7.2
+             */
+            readonly reachableChanged: Event<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall indicate the value of the Reachable attribute after it was changed.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.1.6.4.1
+                 */
+                reachableNewValue: import("../tlv/TlvObject.js").FieldType<boolean>;
+            }>, any>;
+        };
+        /**
+         * This metadata controls which BridgedDeviceBasicInformationCluster elements matter.js activates for specific
+         * feature combinations.
+         */
+        readonly extensions: readonly [{
+            readonly flags: {
+                readonly bridgedIcdSupport: true;
+            };
+            readonly component: {
+                readonly commands: {
+                    /**
+                     * Upon receipt, the server shall attempt to keep the bridged device active for the duration specified by
+                     * the command, when the device is next active.
+                     *
+                     * The implementation of this is best-effort since it may interact with non-native protocols. However,
+                     * several specific protocol requirements are:
+                     *
+                     *   • If the bridged device is a Matter Intermittently Connected Device, then the server shall send a
+                     *     StayActiveRequest command with the StayActiveDuration field set to value of the StayActiveDuration
+                     *     field in the received command to the bridged device when the bridged device next sends a checks-in
+                     *     message or subscription report. See Intermittently Connected Devices Behavior for details on ICD
+                     *     state management.
+                     *
+                     * When the bridge detects that the bridged device goes into an active state, an ActiveChanged event shall
+                     * be generated.
+                     *
+                     * In order to avoid unnecessary power consumption in the bridged device:
+                     *
+                     *   • The server shall enter a "pending active" state for the associated device when the KeepActive
+                     *     command is received. The server "pending active" state shall expire after the amount of time defined
+                     *     by the TimeoutMs field, in milliseconds, if no subsequent KeepActive command is received. When a
+                     *     KeepActive command is received, the "pending active" state is set, the StayActiveDuration is updated
+                     *     to the greater of the new value and the previously stored value, and the TimeoutMs is updated to the
+                     *     greater of the new value and the remaining time until the prior "pending active" state expires.
+                     *
+                     *   • The server shall only keep the bridged device active once for a request. (The server shall only
+                     *     consider the operation performed if an associated ActiveChanged event was generated.)
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 9.13.6.1
+                     */
+                    readonly keepActive: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                        /**
+                         * This field shall indicate the duration, in milliseconds, that the device is requested to remain active, once
+                         * the device becomes active again.
+                         *
+                         * The value of this field may be longer than the value supported by the bridged device and would, typically,
+                         * be used by the client to request the server of the bridged device to stay active and responsive for this
+                         * period to allow a sequence of message exchanges during that period.
+                         *
+                         * The client may slightly overestimate the duration it wants the bridged device to be active for, in order to
+                         * account for network delays.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 9.13.6.1.1
+                         */
+                        stayActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
+                        /**
+                         * This field shall indicate the period, in milliseconds, that the server will wait before the "pending active"
+                         * state expires. See the KeepActive Command description for details.
+                         *
+                         * NOTE
+                         *
+                         * TimeoutMs is a timeout for the request, NOT the time the device will be awake for. The server will wait for
+                         * up to TimeoutMs for the device. If after TimeoutMs the ICD
+                         *
+                         * device does NOT check-in, the server will not perform any actions.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 9.13.6.1.2
+                         */
+                        timeoutMs: import("../tlv/TlvObject.js").FieldType<number>;
+                    }>, void, any>;
+                };
+                readonly events: {
+                    /**
+                     * This event (when supported) shall be generated the next time a bridged device becomes active after a
+                     * KeepActive command is received.
+                     *
+                     * See KeepActive for more details.
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 9.13.7.3
+                     */
+                    readonly activeChanged: Event<import("../tlv/TlvObject.js").TypeFromFields<{
+                        /**
+                         * This field shall indicate the minimum duration, in milliseconds, that the bridged device will remain active
+                         * after receiving the initial request from the KeepActive processing steps.
+                         *
+                         * If the bridged device is a Matter Intermittently Connected Device, PromisedActiveDuration shall be set to
+                         * the PromisedActiveDuration value returned in the StayActiveResponse command.
+                         *
+                         * If the bridged device is not a Matter Intermittently Connected Device, the implementation of this is
+                         * best-effort since it may interact with non-native protocol.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 9.13.7.3.1
+                         */
+                        promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
+                    }>, any>;
+                };
+            };
+        }];
+    };
     /**
      * @see {@link Cluster}
      */
     const ClusterInstance: MutableCluster<{
         readonly id: 57;
         readonly name: "BridgedDeviceBasicInformation";
-        readonly revision: 3;
+        readonly revision: 4;
+        readonly features: {
+            /**
+             * BridgedIcdSupport
+             *
+             * Support bridged ICDs.
+             */
+            readonly bridgedIcdSupport: BitFlag;
+        };
         readonly attributes: {
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly vendorName: OptionalFixedAttribute<string, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly vendorId: OptionalFixedAttribute<import("../datatype/VendorId.js").VendorId, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly productName: OptionalFixedAttribute<string, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly productId: OptionalFixedAttribute<number, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly nodeLabel: OptionalWritableAttribute<string, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly hardwareVersion: OptionalFixedAttribute<number, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly hardwareVersionString: OptionalFixedAttribute<string, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly softwareVersion: OptionalFixedAttribute<number, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly softwareVersionString: OptionalFixedAttribute<string, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly manufacturingDate: OptionalFixedAttribute<string, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly partNumber: OptionalFixedAttribute<string, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly productUrl: OptionalFixedAttribute<string, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly productLabel: OptionalFixedAttribute<string, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly serialNumber: OptionalFixedAttribute<string, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * This attribute shall be used to indicate whether the bridged device is reachable by the bridge, so a
+             * Matter Node which wants to communicate with a bridged device can get an indication that this might fail
+             * (when the attribute is False). Determination of reachability might not be perfect (e.g. depending on
+             * technology employed), so the Matter Node SHOULD be aware of the risk of false positives and negatives on
+             * reachability determination. For example, a bridged device may be marked as unreachable while it could
+             * actually be reached, and vice-versa. Also, detection (and indication) that a bridged device is not
+             * longer reachable may be delayed due to the technique employed (e.g. detecting that a number of expected
+             * messages from the bridged device did not arrive). Also see event ReachableChanged below.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5.1
              */
             readonly reachable: Attribute<boolean, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * This attribute shall, for a Bridged Device, be updated when the Bridge is factory reset. If the bridged
+             * device does not provide some unique id (e.g. in the case of bridging from non-Matter devices, or in case
+             * of bridging Matter devices from an earlier revision which were not required to provide a UniqueID
+             * attribute), the bridge shall generate a unique id on behalf of the bridged device.
+             *
+             * NOTE The UniqueID attribute was optional in cluster revisions prior to revision 4.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5.2
              */
-            readonly uniqueId: OptionalFixedAttribute<string, any>;
+            readonly uniqueId: FixedAttribute<string, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.4
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
              */
             readonly productAppearance: OptionalFixedAttribute<import("../tlv/TlvObject.js").TypeFromFields<{
                 finish: import("../tlv/TlvObject.js").FieldType<BasicInformation.ProductFinish>;
@@ -128,7 +581,7 @@ export declare namespace BridgedDeviceBasicInformation {
         };
         readonly events: {
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7
              */
             readonly startUp: OptionalEvent<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
@@ -139,7 +592,7 @@ export declare namespace BridgedDeviceBasicInformation {
                 softwareVersion: import("../tlv/TlvObject.js").FieldType<number>;
             }>, any>;
             /**
-             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7
              */
             readonly shutDown: OptionalEvent<void, any>;
             /**
@@ -152,17 +605,17 @@ export declare namespace BridgedDeviceBasicInformation {
              * context of Bridged Device Basic Information cluster, has no usable fields, but the original Basic
              * Information cluster’s field definition is kept for completeness.
              *
-             * @see {@link MatterSpecification.v13.Core} § 9.13.5.1
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7.1
              */
             readonly leave: OptionalEvent<void, any>;
             /**
              * This event shall be generated when there is a change in the Reachable attribute. Its purpose is to
-             * provide an indication towards interested parties that the reachability of a bridged device (over the
-             * non-Matter network) has changed, so they may take appropriate action.
+             * provide an indication towards interested parties that the reachability of a bridged device has changed
+             * over its native connectivity technology, so they may take appropriate action.
              *
              * After (re)start of a bridge this event may be generated.
              *
-             * @see {@link MatterSpecification.v13.Core} § 9.13.5.2
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7.2
              */
             readonly reachableChanged: Event<import("../tlv/TlvObject.js").TypeFromFields<{
                 /**
@@ -173,12 +626,110 @@ export declare namespace BridgedDeviceBasicInformation {
                 reachableNewValue: import("../tlv/TlvObject.js").FieldType<boolean>;
             }>, any>;
         };
+        /**
+         * This metadata controls which BridgedDeviceBasicInformationCluster elements matter.js activates for specific
+         * feature combinations.
+         */
+        readonly extensions: readonly [{
+            readonly flags: {
+                readonly bridgedIcdSupport: true;
+            };
+            readonly component: {
+                readonly commands: {
+                    /**
+                     * Upon receipt, the server shall attempt to keep the bridged device active for the duration specified by
+                     * the command, when the device is next active.
+                     *
+                     * The implementation of this is best-effort since it may interact with non-native protocols. However,
+                     * several specific protocol requirements are:
+                     *
+                     *   • If the bridged device is a Matter Intermittently Connected Device, then the server shall send a
+                     *     StayActiveRequest command with the StayActiveDuration field set to value of the StayActiveDuration
+                     *     field in the received command to the bridged device when the bridged device next sends a checks-in
+                     *     message or subscription report. See Intermittently Connected Devices Behavior for details on ICD
+                     *     state management.
+                     *
+                     * When the bridge detects that the bridged device goes into an active state, an ActiveChanged event shall
+                     * be generated.
+                     *
+                     * In order to avoid unnecessary power consumption in the bridged device:
+                     *
+                     *   • The server shall enter a "pending active" state for the associated device when the KeepActive
+                     *     command is received. The server "pending active" state shall expire after the amount of time defined
+                     *     by the TimeoutMs field, in milliseconds, if no subsequent KeepActive command is received. When a
+                     *     KeepActive command is received, the "pending active" state is set, the StayActiveDuration is updated
+                     *     to the greater of the new value and the previously stored value, and the TimeoutMs is updated to the
+                     *     greater of the new value and the remaining time until the prior "pending active" state expires.
+                     *
+                     *   • The server shall only keep the bridged device active once for a request. (The server shall only
+                     *     consider the operation performed if an associated ActiveChanged event was generated.)
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 9.13.6.1
+                     */
+                    readonly keepActive: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                        /**
+                         * This field shall indicate the duration, in milliseconds, that the device is requested to remain active, once
+                         * the device becomes active again.
+                         *
+                         * The value of this field may be longer than the value supported by the bridged device and would, typically,
+                         * be used by the client to request the server of the bridged device to stay active and responsive for this
+                         * period to allow a sequence of message exchanges during that period.
+                         *
+                         * The client may slightly overestimate the duration it wants the bridged device to be active for, in order to
+                         * account for network delays.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 9.13.6.1.1
+                         */
+                        stayActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
+                        /**
+                         * This field shall indicate the period, in milliseconds, that the server will wait before the "pending active"
+                         * state expires. See the KeepActive Command description for details.
+                         *
+                         * NOTE
+                         *
+                         * TimeoutMs is a timeout for the request, NOT the time the device will be awake for. The server will wait for
+                         * up to TimeoutMs for the device. If after TimeoutMs the ICD
+                         *
+                         * device does NOT check-in, the server will not perform any actions.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 9.13.6.1.2
+                         */
+                        timeoutMs: import("../tlv/TlvObject.js").FieldType<number>;
+                    }>, void, any>;
+                };
+                readonly events: {
+                    /**
+                     * This event (when supported) shall be generated the next time a bridged device becomes active after a
+                     * KeepActive command is received.
+                     *
+                     * See KeepActive for more details.
+                     *
+                     * @see {@link MatterSpecification.v13.Core} § 9.13.7.3
+                     */
+                    readonly activeChanged: Event<import("../tlv/TlvObject.js").TypeFromFields<{
+                        /**
+                         * This field shall indicate the minimum duration, in milliseconds, that the bridged device will remain active
+                         * after receiving the initial request from the KeepActive processing steps.
+                         *
+                         * If the bridged device is a Matter Intermittently Connected Device, PromisedActiveDuration shall be set to
+                         * the PromisedActiveDuration value returned in the StayActiveResponse command.
+                         *
+                         * If the bridged device is not a Matter Intermittently Connected Device, the implementation of this is
+                         * best-effort since it may interact with non-native protocol.
+                         *
+                         * @see {@link MatterSpecification.v13.Core} § 9.13.7.3.1
+                         */
+                        promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
+                    }>, any>;
+                };
+            };
+        }];
     }, []>;
     /**
-     * This Cluster serves two purposes towards a Node communicating with a Bridge:
+     * This cluster is a derived cluster of the Basic Information cluster and serves two purposes towards a Node
+     * communicating with a Bridge:
      *
-     *   • Indicate that the functionality on the Endpoint where it is placed (and its Parts) is bridged from a
-     *     non-Matter technology, and
+     *   • Indicate that the functionality on the Endpoint where it is placed (and its Parts) is bridged, and
      *
      *   • Provide a centralized collection of attributes that the Node may collect to aid in conveying information
      *     regarding the Bridged Device to a user, such as the vendor name, the model name, or user-assigned name.
@@ -198,12 +749,243 @@ export declare namespace BridgedDeviceBasicInformation {
      * particular attribute is not available, the Bridge SHOULD NOT include the attribute in the cluster for this
      * Bridged Device. See below for Conformance details.
      *
+     * BridgedDeviceBasicInformationCluster supports optional features that you can enable with the
+     * BridgedDeviceBasicInformationCluster.with() factory method.
+     *
      * @see {@link MatterSpecification.v13.Core} § 9.13
      */
     interface Cluster extends Identity<typeof ClusterInstance> {
     }
     const Cluster: Cluster;
-    const Complete: Cluster;
+    /**
+     * @see {@link Complete}
+     */
+    const CompleteInstance: MutableCluster<{
+        readonly id: import("#general").Branded<57, "ClusterId">;
+        readonly name: "BridgedDeviceBasicInformation";
+        readonly revision: 4;
+        readonly features: {
+            /**
+             * BridgedIcdSupport
+             *
+             * Support bridged ICDs.
+             */
+            readonly bridgedIcdSupport: BitFlag;
+        };
+        readonly attributes: import("#general").Merge<{
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly vendorName: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly vendorId: OptionalFixedAttribute<import("../datatype/VendorId.js").VendorId, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly productName: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly productId: OptionalFixedAttribute<number, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly nodeLabel: OptionalWritableAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly hardwareVersion: OptionalFixedAttribute<number, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly hardwareVersionString: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly softwareVersion: OptionalFixedAttribute<number, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly softwareVersionString: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly manufacturingDate: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly partNumber: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly productUrl: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly productLabel: OptionalFixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly serialNumber: OptionalFixedAttribute<string, any>;
+            /**
+             * This attribute shall be used to indicate whether the bridged device is reachable by the bridge, so a
+             * Matter Node which wants to communicate with a bridged device can get an indication that this might fail
+             * (when the attribute is False). Determination of reachability might not be perfect (e.g. depending on
+             * technology employed), so the Matter Node SHOULD be aware of the risk of false positives and negatives on
+             * reachability determination. For example, a bridged device may be marked as unreachable while it could
+             * actually be reached, and vice-versa. Also, detection (and indication) that a bridged device is not
+             * longer reachable may be delayed due to the technique employed (e.g. detecting that a number of expected
+             * messages from the bridged device did not arrive). Also see event ReachableChanged below.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5.1
+             */
+            readonly reachable: Attribute<boolean, any>;
+            /**
+             * This attribute shall, for a Bridged Device, be updated when the Bridge is factory reset. If the bridged
+             * device does not provide some unique id (e.g. in the case of bridging from non-Matter devices, or in case
+             * of bridging Matter devices from an earlier revision which were not required to provide a UniqueID
+             * attribute), the bridge shall generate a unique id on behalf of the bridged device.
+             *
+             * NOTE The UniqueID attribute was optional in cluster revisions prior to revision 4.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5.2
+             */
+            readonly uniqueId: FixedAttribute<string, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.5
+             */
+            readonly productAppearance: OptionalFixedAttribute<import("../tlv/TlvObject.js").TypeFromFields<{
+                finish: import("../tlv/TlvObject.js").FieldType<BasicInformation.ProductFinish>;
+                primaryColor: import("../tlv/TlvObject.js").FieldType<BasicInformation.Color | null>;
+            }>, any>;
+        }, import("../cluster/Cluster.js").GlobalAttributes<{
+            /**
+             * BridgedIcdSupport
+             *
+             * Support bridged ICDs.
+             */
+            readonly bridgedIcdSupport: BitFlag;
+        }>>;
+        readonly commands: {
+            readonly keepActive: Command<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall indicate the duration, in milliseconds, that the device is requested to remain active, once
+                 * the device becomes active again.
+                 *
+                 * The value of this field may be longer than the value supported by the bridged device and would, typically,
+                 * be used by the client to request the server of the bridged device to stay active and responsive for this
+                 * period to allow a sequence of message exchanges during that period.
+                 *
+                 * The client may slightly overestimate the duration it wants the bridged device to be active for, in order to
+                 * account for network delays.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 9.13.6.1.1
+                 */
+                stayActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
+                /**
+                 * This field shall indicate the period, in milliseconds, that the server will wait before the "pending active"
+                 * state expires. See the KeepActive Command description for details.
+                 *
+                 * NOTE
+                 *
+                 * TimeoutMs is a timeout for the request, NOT the time the device will be awake for. The server will wait for
+                 * up to TimeoutMs for the device. If after TimeoutMs the ICD
+                 *
+                 * device does NOT check-in, the server will not perform any actions.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 9.13.6.1.2
+                 */
+                timeoutMs: import("../tlv/TlvObject.js").FieldType<number>;
+            }>, void, any> & {
+                readonly optional: true;
+                readonly isConditional: true;
+                readonly optionalIf: [] | import("../cluster/Cluster.js").ConditionalFeatureList<import("../schema/BitmapSchema.js").BitSchema>;
+                readonly mandatoryIf: [] | [{
+                    bridgedIcdSupport: boolean;
+                }];
+            };
+        };
+        readonly events: {
+            readonly activeChanged: Event<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall indicate the minimum duration, in milliseconds, that the bridged device will remain active
+                 * after receiving the initial request from the KeepActive processing steps.
+                 *
+                 * If the bridged device is a Matter Intermittently Connected Device, PromisedActiveDuration shall be set to
+                 * the PromisedActiveDuration value returned in the StayActiveResponse command.
+                 *
+                 * If the bridged device is not a Matter Intermittently Connected Device, the implementation of this is
+                 * best-effort since it may interact with non-native protocol.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 9.13.7.3.1
+                 */
+                promisedActiveDuration: import("../tlv/TlvObject.js").FieldType<number>;
+            }>, any> & {
+                readonly optional: true;
+                readonly isConditional: true;
+                readonly optionalIf: [] | import("../cluster/Cluster.js").ConditionalFeatureList<import("../schema/BitmapSchema.js").BitSchema>;
+                readonly mandatoryIf: [] | [{
+                    bridgedIcdSupport: boolean;
+                }];
+            };
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7
+             */
+            readonly startUp: OptionalEvent<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall be set to the same value as the one available in the SoftwareVersion attribute.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.1.6.1.1
+                 */
+                softwareVersion: import("../tlv/TlvObject.js").FieldType<number>;
+            }>, any>;
+            /**
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7
+             */
+            readonly shutDown: OptionalEvent<void, any>;
+            /**
+             * The Leave event SHOULD be generated by the bridge when it detects that the associated device has left
+             * the non-Matter network.
+             *
+             * NOTE
+             *
+             * The FabricIndex field has the X conformance, indicating it shall NOT be present. This event, in the
+             * context of Bridged Device Basic Information cluster, has no usable fields, but the original Basic
+             * Information cluster’s field definition is kept for completeness.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7.1
+             */
+            readonly leave: OptionalEvent<void, any>;
+            /**
+             * This event shall be generated when there is a change in the Reachable attribute. Its purpose is to
+             * provide an indication towards interested parties that the reachability of a bridged device has changed
+             * over its native connectivity technology, so they may take appropriate action.
+             *
+             * After (re)start of a bridge this event may be generated.
+             *
+             * @see {@link MatterSpecification.v13.Core} § 9.13.7.2
+             */
+            readonly reachableChanged: Event<import("../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field shall indicate the value of the Reachable attribute after it was changed.
+                 *
+                 * @see {@link MatterSpecification.v13.Core} § 11.1.6.4.1
+                 */
+                reachableNewValue: import("../tlv/TlvObject.js").FieldType<boolean>;
+            }>, any>;
+        };
+    }, []>;
+    /**
+     * This cluster supports all BridgedDeviceBasicInformation 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 BridgedDeviceBasicInformationCluster = BridgedDeviceBasicInformation.Cluster;
 export declare const BridgedDeviceBasicInformationCluster: BridgedDeviceBasicInformation.Cluster;