@matter/types 0.11.0-alpha.0-20241005-e3e4e4a7a

package/dist/esm/clusters/oven-cavity-operational-state.js

@@ -0,0 +1,268 @@
+/**
+ * @license
+ * Copyright 2022-2024 Matter.js Authors
+ * SPDX-License-Identifier: Apache-2.0
+ */
+import { MutableCluster } from "../cluster/mutation/MutableCluster.js";
+import {
+  Attribute,
+  OptionalAttribute,
+  OptionalCommand,
+  TlvNoResponse,
+  Event,
+  EventPriority,
+  OptionalEvent
+} from "../cluster/Cluster.js";
+import { TlvArray } from "../tlv/TlvArray.js";
+import { TlvString } from "../tlv/TlvString.js";
+import { TlvNullable } from "../tlv/TlvNullable.js";
+import { TlvUInt8, TlvUInt32 } from "../tlv/TlvNumber.js";
+import { OperationalState } from "./operational-state.js";
+import { TlvNoArguments } from "../tlv/TlvNoArguments.js";
+import { ClusterRegistry } from "../cluster/ClusterRegistry.js";
+var OvenCavityOperationalState;
+((OvenCavityOperationalState2) => {
+  OvenCavityOperationalState2.ClusterInstance = MutableCluster({
+    id: 72,
+    name: "OvenCavityOperationalState",
+    revision: 1,
+    attributes: {
+      /**
+       * Indicates a list of names of different phases that the device can go through for the selected function
+       * or mode. The list may not be in sequence order. For example in a washing machine this could include
+       * items such as "pre-soak", "rinse", and "spin". These phases are manufacturer specific and may change
+       * when a different function or mode is selected.
+       *
+       * A null value indicates that the device does not present phases during its operation. When this
+       * attribute’s value is null, the CurrentPhase attribute shall also be set to null.
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.5.1
+       */
+      phaseList: Attribute(0, TlvNullable(TlvArray(TlvString, { maxLength: 32 }))),
+      /**
+       * This attribute represents the current phase of operation being performed by the server. This shall be
+       * the positional index representing the value from the set provided in the PhaseList Attribute, where the
+       * first item in that list is an index of 0. Thus, this attribute shall have a maximum value that is
+       * "length(PhaseList) - 1".
+       *
+       * Null if the PhaseList attribute is null or if the PhaseList attribute is an empty list.
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.5.2
+       */
+      currentPhase: Attribute(1, TlvNullable(TlvUInt8)),
+      /**
+       * Indicates the estimated time left before the operation is completed, in seconds. Changes to this value
+       * shall NOT be reported in a subscription (note the C Quality). A Client implementation may periodically
+       * poll this value to ensure alignment of any local rendering of the CountdownTime with the device provided
+       * value.
+       *
+       * A value of 0 means that the operation has completed.
+       *
+       * When this attribute is null, that represents that there is no time currently defined until operation
+       * completion. This may happen, for example, because no operation is in progress or because the completion
+       * time is unknown.
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.5.3
+       */
+      countdownTime: OptionalAttribute(
+        2,
+        TlvNullable(TlvUInt32.bound({ max: 259200 })),
+        { omitChanges: true, default: null }
+      ),
+      /**
+       * This attribute describes the set of possible operational states that the device exposes. An operational
+       * state is a fundamental device state such as Running or Error. Details of the phase of a device when, for
+       * example, in a state of Running are provided by the CurrentPhase attribute.
+       *
+       * All devices shall, at a minimum, expose the set of states matching the commands that are also supported
+       * by the cluster instance, in addition to Error. The set of possible device states are defined in the
+       * OperationalStateEnum. A device type requiring implementation of this cluster shall define the set of
+       * states that are applicable to that specific device type.
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.5.4
+       */
+      operationalStateList: Attribute(3, TlvArray(OperationalState.TlvOperationalStateStruct), { default: [] }),
+      /**
+       * This attribute specifies the current operational state of a device. This shall be populated with a valid
+       * OperationalStateID from the set of values in the OperationalStateList Attribute.
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.5.5
+       */
+      operationalState: Attribute(4, TlvUInt8),
+      /**
+       * This attribute shall specify the details of any current error condition being experienced on the device
+       * when the OperationalState attribute is populated with Error. Please see ErrorStateStruct for general
+       * requirements on the population of this attribute.
+       *
+       * When there is no error detected, this shall have an ErrorStateID of NoError.
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.5.6
+       */
+      operationalError: Attribute(5, OperationalState.TlvErrorState)
+    },
+    commands: {
+      /**
+       * This command shall be supported if the device supports remotely pausing the operation. If this command
+       * is supported, the Resume command shall also be supported.
+       *
+       * On receipt of this command, the device shall pause its operation if it is possible based on the current
+       * function of the server. For example, if it is at a point where it is safe to do so and/or permitted, but
+       * can be restarted from the point at which pause occurred.
+       *
+       * If this command is received when already in the Paused state the device shall respond with an
+       * OperationalCommandResponse command with an ErrorStateID of NoError but take no further action.
+       *
+       * A device that receives this command in any state which is not Pause-compatible shall respond
+       *
+       * with an OperationalCommandResponse command with an ErrorStateID of CommandInvalidInState and shall take
+       * no further action.
+       *
+       * States are defined as Pause-compatible as follows:
+       *
+       *   • For states defined in this cluster specification, in Table 3, “Pause Compatibility”.
+       *
+       *   • For states defined by derived cluster specifications, in the corresponding specifications.
+       *
+       *   • For manufacturer-specific states, by the manufacturer.
+       *
+       * A device that is unable to honor the Pause command for whatever reason shall respond with an
+       * OperationalCommandResponse command with an ErrorStateID of CommandInvalidInState but take no further
+       * action.
+       *
+       * Otherwise, on success:
+       *
+       *   • The OperationalState attribute shall be set to Paused.
+       *
+       *   • The device shall respond with an OperationalCommandResponse command with an ErrorStateID of NoError.
+       *
+       * The following table defines the compatibility of this cluster’s states with the Pause command.
+       *
+       * ### Table 3. Pause Compatibility
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.6.1
+       */
+      pause: OptionalCommand(0, TlvNoArguments, 0, TlvNoResponse),
+      /**
+       * This command shall be supported if the device supports remotely stopping the operation.
+       *
+       * On receipt of this command, the device shall stop its operation if it is at a position where it is safe
+       * to do so and/or permitted. Restart of the device following the receipt of the Stop command shall require
+       * attended operation unless remote start is allowed by the device type and any jurisdiction governing
+       * remote operation of the device.
+       *
+       * If this command is received when already in the Stopped state the device shall respond with an
+       * OperationalCommandResponse command with an ErrorStateID of NoError but take no further action.
+       *
+       * A device that is unable to honor the Stop command for whatever reason shall respond with an
+       * OperationalCommandResponse command with an ErrorStateID of CommandInvalidInState but take no further
+       * action.
+       *
+       * Otherwise, on success:
+       *
+       *   • The OperationalState attribute shall be set to Stopped.
+       *
+       *   • The device shall respond with an OperationalCommandResponse command with an ErrorStateID of NoError.
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.6.2
+       */
+      stop: OptionalCommand(1, TlvNoArguments, 1, TlvNoResponse),
+      /**
+       * This command shall be supported if the device supports remotely starting the operation. If this command
+       * is supported, the 'Stop command shall also be supported.
+       *
+       * On receipt of this command, the device shall start its operation if it is safe to do so and the device
+       * is in an operational state from which it can be started. There may be either regulatory or
+       * manufacturer-imposed safety and security requirements that first necessitate some specific action at the
+       * device before a Start command can be honored. In such instances, a device shall respond with a status
+       * code of CommandInvalidInState if a Start command is received prior to the required on- device action.
+       *
+       * If this command is received when already in the Running state the device shall respond with an
+       * OperationalCommandResponse command with an ErrorStateID of NoError but take no further action.
+       *
+       * A device that is unable to honor the Start command for whatever reason shall respond with an
+       * OperationalCommandResponse command with an ErrorStateID of UnableToStartOrResume but take no further
+       * action.
+       *
+       * Otherwise, on success:
+       *
+       *   • The OperationalState attribute shall be set to Running.
+       *
+       *   • The device shall respond with an OperationalCommandResponse command with an ErrorStateID of NoError.
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.6.3
+       */
+      start: OptionalCommand(2, TlvNoArguments, 2, TlvNoResponse),
+      /**
+       * This command shall be supported if the device supports remotely resuming the operation. If this command
+       * is supported, the Pause command shall also be supported.
+       *
+       * On receipt of this command, the device shall resume its operation from the point it was at when it
+       * received the Pause command, or from the point when it was paused by means outside of this cluster (for
+       * example by manual button press).
+       *
+       * If this command is received when already in the Running state the device shall respond with an
+       * OperationalCommandResponse command with an ErrorStateID of NoError but take no further action.
+       *
+       * A device that receives this command in any state which is not Resume-compatible shall respond with an
+       * OperationalCommandResponse command with an ErrorStateID of CommandInvalidInState and shall take no
+       * further action.
+       *
+       * States are defined as Resume-compatible as follows:
+       *
+       *   • For states defined in this cluster specification, in Table 4, “Resume Compatibility”.
+       *
+       *   • For states defined by derived cluster specifications, in the corresponding specifications.
+       *
+       *   • For manufacturer-specific states, by the manufacturer.
+       *
+       * The following table defines the compatibility of this cluster’s states with the Resume command.
+       *
+       * ### Table 4. Resume Compatibility
+       *
+       * A device that is unable to honor the Resume command for any other reason shall respond with an
+       * OperationalCommandResponse command with an ErrorStateID of UnableToStartOrResume but take no further
+       * action.
+       *
+       * Otherwise, on success:
+       *
+       *   • The OperationalState attribute shall be set to the most recent non-Error operational state prior to
+       *     entering the Paused state.
+       *
+       *   • The device shall respond with an OperationalCommandResponse command with an ErrorStateID of NoError.
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.6.4
+       */
+      resume: OptionalCommand(3, TlvNoArguments, 3, TlvNoResponse)
+    },
+    events: {
+      /**
+       * This event is generated when a reportable error condition is detected. A device that generates this
+       * event shall also set the OperationalState attribute to Error, indicating an error condition.
+       *
+       * This event shall contain the following fields:
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.7.1
+       */
+      operationalError: Event(0, EventPriority.Critical, OperationalState.TlvOperationalErrorEvent),
+      /**
+       * This event is generated when the overall operation ends, successfully or otherwise. For example, the
+       * completion of a cleaning operation in a Robot Vacuum Cleaner, or the completion of a wash cycle in a
+       * Washing Machine.
+       *
+       * This event shall contain the following fields:
+       *
+       * @see {@link MatterSpecification.v13.Cluster} § 1.14.7.2
+       */
+      operationCompletion: OptionalEvent(1, EventPriority.Info, OperationalState.TlvOperationCompletionEvent)
+    }
+  });
+  OvenCavityOperationalState2.Cluster = OvenCavityOperationalState2.ClusterInstance;
+  OvenCavityOperationalState2.Complete = OvenCavityOperationalState2.Cluster;
+})(OvenCavityOperationalState || (OvenCavityOperationalState = {}));
+const OvenCavityOperationalStateCluster = OvenCavityOperationalState.Cluster;
+ClusterRegistry.register(OvenCavityOperationalState.Complete);
+export {
+  OvenCavityOperationalState,
+  OvenCavityOperationalStateCluster
+};
+//# sourceMappingURL=oven-cavity-operational-state.js.map

package/dist/esm/clusters/oven-cavity-operational-state.js.map

@@ -0,0 +1,6 @@
+{
+  "version": 3,
+  "sources": ["../../../src/clusters/oven-cavity-operational-state.ts"],
+  "mappings": "AAAA;AAAA;AAAA;AAAA;AAAA;AAQA,SAAS,sBAAsB;AAC/B;AAAA,EACI;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,OACG;AACP,SAAS,gBAAgB;AACzB,SAAS,iBAAiB;AAC1B,SAAS,mBAAmB;AAC5B,SAAS,UAAU,iBAAiB;AACpC,SAAS,wBAAwB;AACjC,SAAS,sBAAsB;AAE/B,SAAS,uBAAuB;AAEzB,IAAU;AAAA,CAAV,CAAUA,gCAAV;AAII,EAAMA,4BAAA,kBAAkB,eAAe;AAAA,IAC1C,IAAI;AAAA,IACJ,MAAM;AAAA,IACN,UAAU;AAAA,IAEV,YAAY;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MAYR,WAAW,UAAU,GAAK,YAAY,SAAS,WAAW,EAAE,WAAW,GAAG,CAAC,CAAC,CAAC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MAY7E,cAAc,UAAU,GAAK,YAAY,QAAQ,CAAC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MAgBlD,eAAe;AAAA,QACX;AAAA,QACA,YAAY,UAAU,MAAM,EAAE,KAAK,OAAO,CAAC,CAAC;AAAA,QAC5C,EAAE,aAAa,MAAM,SAAS,KAAK;AAAA,MACvC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MAcA,sBAAsB,UAAU,GAAK,SAAS,iBAAiB,yBAAyB,GAAG,EAAE,SAAS,CAAC,EAAE,CAAC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MAQ1G,kBAAkB,UAAU,GAAK,QAAQ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MAWzC,kBAAkB,UAAU,GAAK,iBAAiB,aAAa;AAAA,IACnE;AAAA,IAEA,UAAU;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MAyCN,OAAO,gBAAgB,GAAK,gBAAgB,GAAK,aAAa;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MAyB9D,MAAM,gBAAgB,GAAK,gBAAgB,GAAK,aAAa;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MA2B7D,OAAO,gBAAgB,GAAK,gBAAgB,GAAK,aAAa;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MA0C9D,QAAQ,gBAAgB,GAAK,gBAAgB,GAAK,aAAa;AAAA,IACnE;AAAA,IAEA,QAAQ;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MASJ,kBAAkB,MAAM,GAAK,cAAc,UAAU,iBAAiB,wBAAwB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,MAW9F,qBAAqB,cAAc,GAAK,cAAc,MAAM,iBAAiB,2BAA2B;AAAA,IAC5G;AAAA,EACJ,CAAC;AASM,EAAMA,4BAAA,UAAmBA,4BAAA;AACzB,EAAMA,4BAAA,WAAWA,4BAAA;AAAA,GAnQX;AAuQV,MAAM,oCAAoC,2BAA2B;AAC5E,gBAAgB,SAAS,2BAA2B,QAAQ;",
+  "names": ["OvenCavityOperationalState"]
+}

package/dist/esm/clusters/oven-mode.d.ts

@@ -0,0 +1,399 @@
+/**
+ * @license
+ * Copyright 2022-2024 Matter.js Authors
+ * SPDX-License-Identifier: Apache-2.0
+ */
+/*** THIS FILE IS GENERATED, DO NOT EDIT ***/
+import { MutableCluster } from "../cluster/mutation/MutableCluster.js";
+import { WritableAttribute, FixedAttribute, Attribute, OptionalWritableAttribute, Command } from "../cluster/Cluster.js";
+import { BitFlag } from "../schema/BitmapSchema.js";
+import { Identity } from "#general";
+export declare namespace OvenMode {
+    /**
+     * These are optional features supported by OvenModeCluster.
+     *
+     * @see {@link MatterSpecification.v13.Cluster} § 1.10.4
+     */
+    enum Feature {
+        /**
+         * OnOff (DEPONOFF)
+         *
+         * This feature creates a dependency between an OnOff cluster instance and this cluster instance on the same
+         * endpoint. See OnMode for more information.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 1.10.4.1
+         */
+        OnOff = "OnOff"
+    }
+    enum ModeTag {
+        /**
+         * This mode sets the device into baking mode for baking food items.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 8.11.4.1.1
+         */
+        Bake = 16384,
+        /**
+         * This mode sets the device into convection mode which creates an airflow within the device during the cooking
+         * duration.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 8.11.4.1.2
+         */
+        Convection = 16385,
+        /**
+         * This mode sets the device into grill mode for grilling food items. This is the same as Broil for many
+         * regions.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 8.11.4.1.3
+         */
+        Grill = 16386,
+        /**
+         * This mode sets the device into roast mode for roasting food items.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 8.11.4.1.4
+         */
+        Roast = 16387,
+        /**
+         * This mode sets the device into cleaning mode to clean the internal components of the appliance.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 8.11.4.1.5
+         */
+        Clean = 16388,
+        /**
+         * @see {@link MatterSpecification.v13.Cluster} § 8.11.4.1
+         */
+        ConvectionBake = 16389,
+        /**
+         * @see {@link MatterSpecification.v13.Cluster} § 8.11.4.1
+         */
+        ConvectionRoast = 16390,
+        /**
+         * This mode sets the device into a warming mode which begins warming the cavity.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 8.11.4.1.8
+         */
+        Warming = 16391,
+        /**
+         * This mode sets the device into proofing mode which creates an environment ready for proofing.
+         *
+         * @see {@link MatterSpecification.v13.Cluster} § 8.11.4.1.9
+         */
+        Proofing = 16392,
+        /**
+         * @see {@link MatterSpecification.v13.Cluster} § 8.11.4.1
+         */
+        Steam = 16393
+    }
+    /**
+     * A OvenModeCluster supports these elements if it supports feature OnOff.
+     */
+    const OnOffComponent: {
+        readonly attributes: {
+            /**
+             * Indicates whether the value of CurrentMode depends on the state of the On/Off cluster on the same
+             * endpoint. If this attribute is not present or is set to null, there is no dependency, otherwise the
+             * CurrentMode attribute shall depend on the OnOff attribute in the On/Off cluster
+             *
+             * The value of this field shall match the Mode field of one of the entries in the SupportedModes attribute.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.6.5
+             */
+            readonly onMode: WritableAttribute<number | null, any>;
+        };
+    };
+    /**
+     * These elements and properties are present in all OvenMode clusters.
+     */
+    const Base: {
+        readonly id: 73;
+        readonly name: "OvenMode";
+        readonly revision: 1;
+        readonly features: {
+            /**
+             * OnOff
+             *
+             * This feature creates a dependency between an OnOff cluster instance and this cluster instance on the
+             * same endpoint. See OnMode for more information.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.4.1
+             */
+            readonly onOff: BitFlag;
+        };
+        readonly attributes: {
+            /**
+             * This attribute shall contain the list of supported modes that may be selected for the CurrentMode
+             * attribute. Each item in this list represents a unique mode as indicated by the Mode field of the
+             * ModeOptionStruct.
+             *
+             * Each entry in this list shall have a unique value for the Mode field. Each entry in this list shall have
+             * a unique value for the Label field.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.6.2
+             */
+            readonly supportedModes: FixedAttribute<import("../index.js").TypeFromFields<{
+                label: import("../index.js").FieldType<string>;
+                mode: import("../index.js").FieldType<number>;
+                modeTags: import("../index.js").FieldType<import("../index.js").TypeFromFields<{
+                    mfgCode: import("../index.js").OptionalFieldType<import("../index.js").VendorId>;
+                    value: import("../index.js").FieldType<number>;
+                }>[]>;
+            }>[], any>;
+            /**
+             * Indicates the current mode of the server.
+             *
+             * The value of this field shall match the Mode field of one of the entries in the SupportedModes attribute.
+             *
+             * The value of this attribute may change at any time via an out-of-band interaction outside of the server,
+             * such as interactions with a user interface, via internal mode changes due to autonomously progressing
+             * through a sequence of operations, on system time-outs or idle delays, or via interactions coming from a
+             * fabric other than the one which last executed a ChangeToMode.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.6.3
+             */
+            readonly currentMode: Attribute<number, any>;
+            /**
+             * Indicates the desired startup mode for the server when it is supplied with power.
+             *
+             * If this attribute is not null, the CurrentMode attribute shall be set to the StartUpMode value, when the
+             * server is powered up, except in the case when the OnMode attribute overrides the StartUpMode attribute
+             * (see OnModeWithPowerUp).
+             *
+             * This behavior does not apply to reboots associated with OTA. After an OTA restart, the CurrentMode
+             * attribute shall return to its value prior to the restart.
+             *
+             * The value of this field shall match the Mode field of one of the entries in the SupportedModes attribute.
+             *
+             * If this attribute is not implemented, or is set to the null value, it shall have no effect.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.6.4
+             */
+            readonly startUpMode: OptionalWritableAttribute<number | null, any>;
+        };
+        readonly commands: {
+            /**
+             * This command is used to change device modes.
+             *
+             * On receipt of this command the device shall respond with a ChangeToModeResponse command.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.7.1
+             */
+            readonly changeToMode: Command<import("../index.js").TypeFromFields<{
+                newMode: import("../index.js").FieldType<number>;
+            }>, void, any>;
+        };
+        /**
+         * This metadata controls which OvenModeCluster elements matter.js activates for specific feature combinations.
+         */
+        readonly extensions: readonly [{
+            readonly flags: {
+                readonly onOff: true;
+            };
+            readonly component: {
+                readonly attributes: {
+                    /**
+                     * Indicates whether the value of CurrentMode depends on the state of the On/Off cluster on the same
+                     * endpoint. If this attribute is not present or is set to null, there is no dependency, otherwise the
+                     * CurrentMode attribute shall depend on the OnOff attribute in the On/Off cluster
+                     *
+                     * The value of this field shall match the Mode field of one of the entries in the SupportedModes attribute.
+                     *
+                     * @see {@link MatterSpecification.v13.Cluster} § 1.10.6.5
+                     */
+                    readonly onMode: WritableAttribute<number | null, any>;
+                };
+            };
+        }];
+    };
+    /**
+     * @see {@link Cluster}
+     */
+    const ClusterInstance: MutableCluster<{
+        readonly id: 73;
+        readonly name: "OvenMode";
+        readonly revision: 1;
+        readonly features: {
+            /**
+             * OnOff
+             *
+             * This feature creates a dependency between an OnOff cluster instance and this cluster instance on the
+             * same endpoint. See OnMode for more information.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.4.1
+             */
+            readonly onOff: BitFlag;
+        };
+        readonly attributes: {
+            /**
+             * This attribute shall contain the list of supported modes that may be selected for the CurrentMode
+             * attribute. Each item in this list represents a unique mode as indicated by the Mode field of the
+             * ModeOptionStruct.
+             *
+             * Each entry in this list shall have a unique value for the Mode field. Each entry in this list shall have
+             * a unique value for the Label field.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.6.2
+             */
+            readonly supportedModes: FixedAttribute<import("../index.js").TypeFromFields<{
+                label: import("../index.js").FieldType<string>;
+                mode: import("../index.js").FieldType<number>;
+                modeTags: import("../index.js").FieldType<import("../index.js").TypeFromFields<{
+                    mfgCode: import("../index.js").OptionalFieldType<import("../index.js").VendorId>;
+                    value: import("../index.js").FieldType<number>;
+                }>[]>;
+            }>[], any>;
+            /**
+             * Indicates the current mode of the server.
+             *
+             * The value of this field shall match the Mode field of one of the entries in the SupportedModes attribute.
+             *
+             * The value of this attribute may change at any time via an out-of-band interaction outside of the server,
+             * such as interactions with a user interface, via internal mode changes due to autonomously progressing
+             * through a sequence of operations, on system time-outs or idle delays, or via interactions coming from a
+             * fabric other than the one which last executed a ChangeToMode.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.6.3
+             */
+            readonly currentMode: Attribute<number, any>;
+            /**
+             * Indicates the desired startup mode for the server when it is supplied with power.
+             *
+             * If this attribute is not null, the CurrentMode attribute shall be set to the StartUpMode value, when the
+             * server is powered up, except in the case when the OnMode attribute overrides the StartUpMode attribute
+             * (see OnModeWithPowerUp).
+             *
+             * This behavior does not apply to reboots associated with OTA. After an OTA restart, the CurrentMode
+             * attribute shall return to its value prior to the restart.
+             *
+             * The value of this field shall match the Mode field of one of the entries in the SupportedModes attribute.
+             *
+             * If this attribute is not implemented, or is set to the null value, it shall have no effect.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.6.4
+             */
+            readonly startUpMode: OptionalWritableAttribute<number | null, any>;
+        };
+        readonly commands: {
+            /**
+             * This command is used to change device modes.
+             *
+             * On receipt of this command the device shall respond with a ChangeToModeResponse command.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.7.1
+             */
+            readonly changeToMode: Command<import("../index.js").TypeFromFields<{
+                newMode: import("../index.js").FieldType<number>;
+            }>, void, any>;
+        };
+        /**
+         * This metadata controls which OvenModeCluster elements matter.js activates for specific feature combinations.
+         */
+        readonly extensions: readonly [{
+            readonly flags: {
+                readonly onOff: true;
+            };
+            readonly component: {
+                readonly attributes: {
+                    /**
+                     * Indicates whether the value of CurrentMode depends on the state of the On/Off cluster on the same
+                     * endpoint. If this attribute is not present or is set to null, there is no dependency, otherwise the
+                     * CurrentMode attribute shall depend on the OnOff attribute in the On/Off cluster
+                     *
+                     * The value of this field shall match the Mode field of one of the entries in the SupportedModes attribute.
+                     *
+                     * @see {@link MatterSpecification.v13.Cluster} § 1.10.6.5
+                     */
+                    readonly onMode: WritableAttribute<number | null, any>;
+                };
+            };
+        }];
+    }, []>;
+    /**
+     * This cluster is derived from the Mode Base cluster, defining additional mode tags and namespaced enumerated
+     * values for oven devices.
+     *
+     * OvenModeCluster supports optional features that you can enable with the OvenModeCluster.with() factory method.
+     *
+     * @see {@link MatterSpecification.v13.Cluster} § 8.11
+     */
+    interface Cluster extends Identity<typeof ClusterInstance> {
+    }
+    const Cluster: Cluster;
+    /**
+     * @see {@link Complete}
+     */
+    const CompleteInstance: MutableCluster<{
+        readonly id: import("#general").Branded<73, "ClusterId">;
+        readonly name: "OvenMode";
+        readonly revision: 1;
+        readonly features: {
+            /**
+             * OnOff
+             *
+             * This feature creates a dependency between an OnOff cluster instance and this cluster instance on the
+             * same endpoint. See OnMode for more information.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.4.1
+             */
+            readonly onOff: BitFlag;
+        };
+        readonly attributes: {
+            readonly onMode: WritableAttribute<number | null, any> & {
+                readonly optional: true;
+                readonly isConditional: true;
+                readonly optionalIf: [] | import("../cluster/Cluster.js").ConditionalFeatureList<import("../schema/BitmapSchema.js").BitSchema>;
+                readonly mandatoryIf: [] | [{
+                    onOff: boolean;
+                }];
+            };
+            readonly supportedModes: FixedAttribute<import("../index.js").TypeFromFields<{
+                label: import("../index.js").FieldType<string>;
+                mode: import("../index.js").FieldType<number>;
+                modeTags: import("../index.js").FieldType<import("../index.js").TypeFromFields<{
+                    mfgCode: import("../index.js").OptionalFieldType<import("../index.js").VendorId>;
+                    value: import("../index.js").FieldType<number>;
+                }>[]>;
+            }>[], any>;
+            readonly currentMode: Attribute<number, any>;
+            readonly startUpMode: OptionalWritableAttribute<number | null, any>;
+            readonly clusterRevision: Attribute<number, never>;
+            readonly featureMap: Attribute<import("../schema/BitmapSchema.js").TypeFromPartialBitSchema<{
+                /**
+                 * OnOff
+                 *
+                 * This feature creates a dependency between an OnOff cluster instance and this cluster instance on the
+                 * same endpoint. See OnMode for more information.
+                 *
+                 * @see {@link MatterSpecification.v13.Cluster} § 1.10.4.1
+                 */
+                readonly onOff: BitFlag;
+            }>, never>;
+            readonly attributeList: Attribute<import("../index.js").AttributeId[], never>;
+            readonly eventList: Attribute<import("../index.js").EventId[], never>;
+            readonly acceptedCommandList: Attribute<import("../index.js").CommandId[], never>;
+            readonly generatedCommandList: Attribute<import("../index.js").CommandId[], never>;
+        };
+        readonly commands: {
+            /**
+             * This command is used to change device modes.
+             *
+             * On receipt of this command the device shall respond with a ChangeToModeResponse command.
+             *
+             * @see {@link MatterSpecification.v13.Cluster} § 1.10.7.1
+             */
+            readonly changeToMode: Command<import("../index.js").TypeFromFields<{
+                newMode: import("../index.js").FieldType<number>;
+            }>, void, any>;
+        };
+    }, []>;
+    /**
+     * This cluster supports all OvenMode 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 OvenModeCluster = OvenMode.Cluster;
+export declare const OvenModeCluster: OvenMode.Cluster;
+//# sourceMappingURL=oven-mode.d.ts.map