/**
 * @license
 * Copyright 2022-2026 Matter.js Authors
 * SPDX-License-Identifier: Apache-2.0
 */
/*** THIS FILE IS GENERATED, DO NOT EDIT ***/
import { MutableCluster } from "../cluster/mutation/MutableCluster.js";
import { Attribute, OptionalAttribute, OptionalCommand, Event, OptionalEvent } from "../cluster/Cluster.js";
import { TypeFromSchema } from "../tlv/TlvSchema.js";
import { Identity } from "@matter/general";
export declare namespace OperationalState {
    /**
     * This type defines the set of known operational state values, and is derived from enum8. The following table
     * defines the applicable ranges for values that are defined within this type. All values that are undefined shall
     * be treated as reserved. As shown by the table, states that may be specific to a certain Device Type or other
     * modality shall be defined in a derived cluster of this cluster.
     *
     * The derived cluster-specific state definitions shall NOT duplicate any general state definitions. That is, a
     * derived cluster specification of this cluster cannot define states with the same semantics as the general states
     * defined below.
     *
     * A manufacturer-specific state definition shall NOT duplicate the general state definitions or derived cluster
     * state definitions. That is, a manufacturer-defined state defined for this cluster or a derived cluster thereof
     * cannot define a state with the same semantics as the general states defined below or states defined in a derived
     * cluster. Such manufacturer-specific state definitions shall be scoped in the context of the Vendor ID present in
     * the Basic Information cluster.
     *
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.1
     */
    enum OperationalStateEnum {
        /**
         * The device is stopped
         */
        Stopped = 0,
        /**
         * The device is operating
         */
        Running = 1,
        /**
         * The device is paused during an operation
         */
        Paused = 2,
        /**
         * The device is in an error state
         */
        Error = 3
    }
    /**
     * The OperationalStateStruct is used to indicate a possible state of the device.
     *
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.2
     */
    const TlvOperationalStateStruct: import("../tlv/TlvObject.js").ObjectSchema<{
        /**
         * This shall be populated with a value from the OperationalStateEnum.
         *
         * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.2.1
         */
        operationalStateId: import("../tlv/TlvObject.js").FieldType<OperationalStateEnum>;
        /**
         * This field is present when the OperationalStateID is from the set reserved for Manufacturer Specific States.
         * If present, this shall contain a human-readable description of the operational state.
         *
         * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.2.2
         */
        operationalStateLabel: import("../tlv/TlvObject.js").OptionalFieldType<string>;
    }>;
    /**
     * The OperationalStateStruct is used to indicate a possible state of the device.
     *
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.2
     */
    interface OperationalStateStruct extends TypeFromSchema<typeof TlvOperationalStateStruct> {
    }
    /**
     * This type defines the set of known operational error values, and is derived from enum8. The following table
     * defines the applicable ranges for values that are defined within this type. All values that are undefined shall
     * be treated as reserved. As shown by the table, errors that may be specific to a certain Device Type or other
     * modality shall be defined in a derived cluster of this cluster.
     *
     * The derived cluster-specific error definitions shall NOT duplicate the general error definitions. That is, a
     * derived cluster specification of this cluster cannot define errors with the same semantics as the general errors
     * defined below.
     *
     * The manufacturer-specific error definitions shall NOT duplicate the general error definitions or derived
     * cluster-specific error definitions. That is, a manufacturer-defined error defined for this cluster or a derived
     * cluster thereof cannot define errors with the same semantics as the general errors defined below or errors
     * defined in a derived cluster. Such manufacturer-specific error definitions shall be scoped in the context of the
     * Vendor ID present in the Basic Information cluster.
     *
     * The set of ErrorStateID field values defined in each of the generic or derived Operational State cluster
     * specifications is called ErrorState.
     *
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.3
     */
    enum ErrorState {
        /**
         * The device is not in an error state
         */
        NoError = 0,
        /**
         * The device is unable to start or resume operation
         */
        UnableToStartOrResume = 1,
        /**
         * The device was unable to complete the current operation
         */
        UnableToCompleteOperation = 2,
        /**
         * The device cannot process the command in its current state
         */
        CommandInvalidInState = 3
    }
    /**
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4
     */
    const TlvErrorStateStruct: import("../tlv/TlvObject.js").ObjectSchema<{
        /**
         * This shall be populated with a value from the ErrorStateEnum.
         *
         * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.1
         */
        errorStateId: import("../tlv/TlvObject.js").FieldType<ErrorState>;
        /**
         * This field is present when the ErrorStateID is from the set reserved for Manufacturer Specific errors. If
         * present, this shall contain a human-readable description of the error state.
         *
         * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.2
         */
        errorStateLabel: import("../tlv/TlvObject.js").OptionalFieldType<string>;
        /**
         * This shall be a human-readable string that provides details about the error condition. As an example, if the
         * ErrorStateID indicates that the device is a Robotic Vacuum that is stuck, the ErrorStateDetails contains
         * "left wheel blocked".
         *
         * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.3
         */
        errorStateDetails: import("../tlv/TlvObject.js").OptionalFieldType<string>;
    }>;
    /**
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4
     */
    interface ErrorStateStruct extends TypeFromSchema<typeof TlvErrorStateStruct> {
    }
    /**
     * This command shall be supported by an implementation if any of the other commands defined by this cluster are
     * supported (i.e. listed in the AcceptedCommandList global attribute). This command shall also be supported by an
     * implementation of a derived cluster as a response to any commands that may be additionally defined therein.
     *
     * This command shall be generated in response to any of the Start, Stop, Pause, or Resume commands.
     *
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.6.5
     */
    const TlvOperationalCommandResponse: import("../tlv/TlvObject.js").ObjectSchema<{
        /**
         * This shall indicate the success or otherwise of the attempted command invocation. On a successful invocation
         * of the attempted command, the ErrorStateID shall be populated with NoError. See the individual command
         * sections for additional specific requirements on population.
         *
         * @see {@link MatterSpecification.v142.Cluster} § 1.14.6.5.1
         */
        commandResponseState: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
            /**
             * This shall be populated with a value from the ErrorStateEnum.
             *
             * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.1
             */
            errorStateId: import("../tlv/TlvObject.js").FieldType<ErrorState>;
            /**
             * This field is present when the ErrorStateID is from the set reserved for Manufacturer Specific errors. If
             * present, this shall contain a human-readable description of the error state.
             *
             * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.2
             */
            errorStateLabel: import("../tlv/TlvObject.js").OptionalFieldType<string>;
            /**
             * This shall be a human-readable string that provides details about the error condition. As an example, if the
             * ErrorStateID indicates that the device is a Robotic Vacuum that is stuck, the ErrorStateDetails contains
             * "left wheel blocked".
             *
             * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.3
             */
            errorStateDetails: import("../tlv/TlvObject.js").OptionalFieldType<string>;
        }>>;
    }>;
    /**
     * This command shall be supported by an implementation if any of the other commands defined by this cluster are
     * supported (i.e. listed in the AcceptedCommandList global attribute). This command shall also be supported by an
     * implementation of a derived cluster as a response to any commands that may be additionally defined therein.
     *
     * This command shall be generated in response to any of the Start, Stop, Pause, or Resume commands.
     *
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.6.5
     */
    interface OperationalCommandResponse extends TypeFromSchema<typeof TlvOperationalCommandResponse> {
    }
    /**
     * Body of the OperationalState operationalError event
     *
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.7.1
     */
    const TlvOperationalErrorEvent: import("../tlv/TlvObject.js").ObjectSchema<{
        errorState: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
            /**
             * This shall be populated with a value from the ErrorStateEnum.
             *
             * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.1
             */
            errorStateId: import("../tlv/TlvObject.js").FieldType<ErrorState>;
            /**
             * This field is present when the ErrorStateID is from the set reserved for Manufacturer Specific errors. If
             * present, this shall contain a human-readable description of the error state.
             *
             * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.2
             */
            errorStateLabel: import("../tlv/TlvObject.js").OptionalFieldType<string>;
            /**
             * This shall be a human-readable string that provides details about the error condition. As an example, if the
             * ErrorStateID indicates that the device is a Robotic Vacuum that is stuck, the ErrorStateDetails contains
             * "left wheel blocked".
             *
             * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.3
             */
            errorStateDetails: import("../tlv/TlvObject.js").OptionalFieldType<string>;
        }>>;
    }>;
    /**
     * Body of the OperationalState operationalError event
     *
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.7.1
     */
    interface OperationalErrorEvent extends TypeFromSchema<typeof TlvOperationalErrorEvent> {
    }
    /**
     * Body of the OperationalState operationCompletion event
     *
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.7.2
     */
    const TlvOperationCompletionEvent: import("../tlv/TlvObject.js").ObjectSchema<{
        /**
         * This field provides an indication of the state at the end of the operation. This field shall have a value
         * from the ErrorStateEnum set. A value of NoError indicates success, that is, no error has been detected.
         *
         * @see {@link MatterSpecification.v142.Cluster} § 1.14.7.2.1
         */
        completionErrorCode: import("../tlv/TlvObject.js").FieldType<number>;
        /**
         * The total operational time, in seconds, from when the operation was started via an initial Start command or
         * autonomous/manual starting action, until the operation completed. This includes any time spent while paused.
         * There may be cases whereby the total operational time exceeds the maximum value that can be conveyed by this
         * attribute, in such instances, this attribute shall be populated with null.
         *
         * @see {@link MatterSpecification.v142.Cluster} § 1.14.7.2.2
         */
        totalOperationalTime: import("../tlv/TlvObject.js").OptionalFieldType<number | null>;
        /**
         * The total time spent in the paused state, in seconds. There may be cases whereby the total paused time
         * exceeds the maximum value that can be conveyed by this attribute, in such instances, this attribute shall be
         * populated with null.
         *
         * @see {@link MatterSpecification.v142.Cluster} § 1.14.7.2.3
         */
        pausedTime: import("../tlv/TlvObject.js").OptionalFieldType<number | null>;
    }>;
    /**
     * Body of the OperationalState operationCompletion event
     *
     * @see {@link MatterSpecification.v142.Cluster} § 1.14.7.2
     */
    interface OperationCompletionEvent extends TypeFromSchema<typeof TlvOperationCompletionEvent> {
    }
    /**
     * @see {@link Cluster}
     */
    const ClusterInstance: MutableCluster<{
        readonly id: 96;
        readonly name: "OperationalState";
        readonly revision: 3;
        readonly 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.v142.Cluster} § 1.14.5.1
             */
            readonly phaseList: Attribute<string[] | null, any>;
            /**
             * 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.v142.Cluster} § 1.14.5.2
             */
            readonly currentPhase: Attribute<number | null, any>;
            /**
             * Indicates the estimated time left before the operation is completed, in seconds.
             *
             * A value of 0 (zero) means that the operation has completed.
             *
             * A value of null 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.
             *
             * Changes to this attribute shall only be marked as reportable in the following cases:
             *
             *   - If it has changed due to a change in the CurrentPhase or OperationalState attributes, or
             *
             *   - When it changes from 0 to any other value and vice versa, or
             *
             *   - When it changes from null to any other value and vice versa, or
             *
             *   - When it increases, or
             *
             *   - When there is any increase or decrease in the estimated time remaining that was due to progressing
             *     insight of the server’s control logic, or
             *
             *   - When it changes at a rate significantly different from one unit per second.
             *
             * Changes to this attribute merely due to the normal passage of time with no other dynamic change of device
             * state shall NOT be reported.
             *
             * As this attribute is not being reported during a regular countdown, clients SHOULD NOT rely on the
             * reporting of this attribute in order to keep track of the remaining duration.
             *
             * @see {@link MatterSpecification.v142.Cluster} § 1.14.5.3
             */
            readonly countdownTime: OptionalAttribute<number | null, any>;
            /**
             * 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.v142.Cluster} § 1.14.5.4
             */
            readonly operationalStateList: Attribute<import("../tlv/TlvObject.js").TypeFromFields<{
                /**
                 * This shall be populated with a value from the OperationalStateEnum.
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.2.1
                 */
                operationalStateId: import("../tlv/TlvObject.js").FieldType<OperationalStateEnum>;
                /**
                 * This field is present when the OperationalStateID is from the set reserved for Manufacturer Specific States.
                 * If present, this shall contain a human-readable description of the operational state.
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.2.2
                 */
                operationalStateLabel: import("../tlv/TlvObject.js").OptionalFieldType<string>;
            }>[], any>;
            /**
             * 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.v142.Cluster} § 1.14.5.5
             */
            readonly operationalState: Attribute<OperationalStateEnum, any>;
            /**
             * This attribute shall specify the details of any current error condition being experienced on the device
             * when the OperationalState attribute is populated with Error. See Section 1.14.4.4, “ErrorStateStruct
             * Type” 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.v142.Cluster} § 1.14.5.6
             */
            readonly operationalError: Attribute<import("../tlv/TlvObject.js").TypeFromFields<{
                /**
                 * This shall be populated with a value from the ErrorStateEnum.
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.1
                 */
                errorStateId: import("../tlv/TlvObject.js").FieldType<ErrorState>;
                /**
                 * This field is present when the ErrorStateID is from the set reserved for Manufacturer Specific errors. If
                 * present, this shall contain a human-readable description of the error state.
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.2
                 */
                errorStateLabel: import("../tlv/TlvObject.js").OptionalFieldType<string>;
                /**
                 * This shall be a human-readable string that provides details about the error condition. As an example, if the
                 * ErrorStateID indicates that the device is a Robotic Vacuum that is stuck, the ErrorStateDetails contains
                 * "left wheel blocked".
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.3
                 */
                errorStateDetails: import("../tlv/TlvObject.js").OptionalFieldType<string>;
            }>, any>;
        };
        readonly 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.
             *
             * @see {@link MatterSpecification.v142.Cluster} § 1.14.6.1
             */
            readonly pause: OptionalCommand<void, import("../tlv/TlvObject.js").TypeFromFields<{
                /**
                 * This shall indicate the success or otherwise of the attempted command invocation. On a successful invocation
                 * of the attempted command, the ErrorStateID shall be populated with NoError. See the individual command
                 * sections for additional specific requirements on population.
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.6.5.1
                 */
                commandResponseState: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                    /**
                     * This shall be populated with a value from the ErrorStateEnum.
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.1
                     */
                    errorStateId: import("../tlv/TlvObject.js").FieldType<ErrorState>;
                    /**
                     * This field is present when the ErrorStateID is from the set reserved for Manufacturer Specific errors. If
                     * present, this shall contain a human-readable description of the error state.
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.2
                     */
                    errorStateLabel: import("../tlv/TlvObject.js").OptionalFieldType<string>;
                    /**
                     * This shall be a human-readable string that provides details about the error condition. As an example, if the
                     * ErrorStateID indicates that the device is a Robotic Vacuum that is stuck, the ErrorStateDetails contains
                     * "left wheel blocked".
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.3
                     */
                    errorStateDetails: import("../tlv/TlvObject.js").OptionalFieldType<string>;
                }>>;
            }>, any>;
            /**
             * 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.v142.Cluster} § 1.14.6.2
             */
            readonly stop: OptionalCommand<void, import("../tlv/TlvObject.js").TypeFromFields<{
                /**
                 * This shall indicate the success or otherwise of the attempted command invocation. On a successful invocation
                 * of the attempted command, the ErrorStateID shall be populated with NoError. See the individual command
                 * sections for additional specific requirements on population.
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.6.5.1
                 */
                commandResponseState: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                    /**
                     * This shall be populated with a value from the ErrorStateEnum.
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.1
                     */
                    errorStateId: import("../tlv/TlvObject.js").FieldType<ErrorState>;
                    /**
                     * This field is present when the ErrorStateID is from the set reserved for Manufacturer Specific errors. If
                     * present, this shall contain a human-readable description of the error state.
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.2
                     */
                    errorStateLabel: import("../tlv/TlvObject.js").OptionalFieldType<string>;
                    /**
                     * This shall be a human-readable string that provides details about the error condition. As an example, if the
                     * ErrorStateID indicates that the device is a Robotic Vacuum that is stuck, the ErrorStateDetails contains
                     * "left wheel blocked".
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.3
                     */
                    errorStateDetails: import("../tlv/TlvObject.js").OptionalFieldType<string>;
                }>>;
            }>, any>;
            /**
             * 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.v142.Cluster} § 1.14.6.3
             */
            readonly start: OptionalCommand<void, import("../tlv/TlvObject.js").TypeFromFields<{
                /**
                 * This shall indicate the success or otherwise of the attempted command invocation. On a successful invocation
                 * of the attempted command, the ErrorStateID shall be populated with NoError. See the individual command
                 * sections for additional specific requirements on population.
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.6.5.1
                 */
                commandResponseState: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                    /**
                     * This shall be populated with a value from the ErrorStateEnum.
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.1
                     */
                    errorStateId: import("../tlv/TlvObject.js").FieldType<ErrorState>;
                    /**
                     * This field is present when the ErrorStateID is from the set reserved for Manufacturer Specific errors. If
                     * present, this shall contain a human-readable description of the error state.
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.2
                     */
                    errorStateLabel: import("../tlv/TlvObject.js").OptionalFieldType<string>;
                    /**
                     * This shall be a human-readable string that provides details about the error condition. As an example, if the
                     * ErrorStateID indicates that the device is a Robotic Vacuum that is stuck, the ErrorStateDetails contains
                     * "left wheel blocked".
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.3
                     */
                    errorStateDetails: import("../tlv/TlvObject.js").OptionalFieldType<string>;
                }>>;
            }>, any>;
            /**
             * 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.
             *
             * 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.v142.Cluster} § 1.14.6.4
             */
            readonly resume: OptionalCommand<void, import("../tlv/TlvObject.js").TypeFromFields<{
                /**
                 * This shall indicate the success or otherwise of the attempted command invocation. On a successful invocation
                 * of the attempted command, the ErrorStateID shall be populated with NoError. See the individual command
                 * sections for additional specific requirements on population.
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.6.5.1
                 */
                commandResponseState: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                    /**
                     * This shall be populated with a value from the ErrorStateEnum.
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.1
                     */
                    errorStateId: import("../tlv/TlvObject.js").FieldType<ErrorState>;
                    /**
                     * This field is present when the ErrorStateID is from the set reserved for Manufacturer Specific errors. If
                     * present, this shall contain a human-readable description of the error state.
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.2
                     */
                    errorStateLabel: import("../tlv/TlvObject.js").OptionalFieldType<string>;
                    /**
                     * This shall be a human-readable string that provides details about the error condition. As an example, if the
                     * ErrorStateID indicates that the device is a Robotic Vacuum that is stuck, the ErrorStateDetails contains
                     * "left wheel blocked".
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.3
                     */
                    errorStateDetails: import("../tlv/TlvObject.js").OptionalFieldType<string>;
                }>>;
            }>, any>;
        };
        readonly 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.v142.Cluster} § 1.14.7.1
             */
            readonly operationalError: Event<import("../tlv/TlvObject.js").TypeFromFields<{
                errorState: import("../tlv/TlvObject.js").FieldType<import("../tlv/TlvObject.js").TypeFromFields<{
                    /**
                     * This shall be populated with a value from the ErrorStateEnum.
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.1
                     */
                    errorStateId: import("../tlv/TlvObject.js").FieldType<ErrorState>;
                    /**
                     * This field is present when the ErrorStateID is from the set reserved for Manufacturer Specific errors. If
                     * present, this shall contain a human-readable description of the error state.
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.2
                     */
                    errorStateLabel: import("../tlv/TlvObject.js").OptionalFieldType<string>;
                    /**
                     * This shall be a human-readable string that provides details about the error condition. As an example, if the
                     * ErrorStateID indicates that the device is a Robotic Vacuum that is stuck, the ErrorStateDetails contains
                     * "left wheel blocked".
                     *
                     * @see {@link MatterSpecification.v142.Cluster} § 1.14.4.4.3
                     */
                    errorStateDetails: import("../tlv/TlvObject.js").OptionalFieldType<string>;
                }>>;
            }>, any>;
            /**
             * This event SHOULD be 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.
             *
             * It is highly recommended that appliances device types employing the Operational State cluster support
             * this event, even if it is optional. This assists clients in executing automations or issuing
             * notifications at critical points in the device operation cycles.
             *
             * This event shall contain the following fields:
             *
             * @see {@link MatterSpecification.v142.Cluster} § 1.14.7.2
             */
            readonly operationCompletion: OptionalEvent<import("../tlv/TlvObject.js").TypeFromFields<{
                /**
                 * This field provides an indication of the state at the end of the operation. This field shall have a value
                 * from the ErrorStateEnum set. A value of NoError indicates success, that is, no error has been detected.
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.7.2.1
                 */
                completionErrorCode: import("../tlv/TlvObject.js").FieldType<number>;
                /**
                 * The total operational time, in seconds, from when the operation was started via an initial Start command or
                 * autonomous/manual starting action, until the operation completed. This includes any time spent while paused.
                 * There may be cases whereby the total operational time exceeds the maximum value that can be conveyed by this
                 * attribute, in such instances, this attribute shall be populated with null.
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.7.2.2
                 */
                totalOperationalTime: import("../tlv/TlvObject.js").OptionalFieldType<number | null>;
                /**
                 * The total time spent in the paused state, in seconds. There may be cases whereby the total paused time
                 * exceeds the maximum value that can be conveyed by this attribute, in such instances, this attribute shall be
                 * populated with null.
                 *
                 * @see {@link MatterSpecification.v142.Cluster} § 1.14.7.2.3
                 */
                pausedTime: import("../tlv/TlvObject.js").OptionalFieldType<number | null>;
            }>, any>;
        };
    }, []>;
    /**
     * This cluster supports remotely monitoring and, where supported, changing the operational state of any device
     * where a state machine is a part of the operation.
     *
     * This cluster defines common states, scoped to this cluster (e.g. Stopped, Running, Paused, Error). A derived
     * cluster specification may define more states scoped to the derivation. Manufacturer specific states are supported
     * in this cluster and any derived clusters thereof. When defined in a derived instance, such states are scoped to
     * the derivation.
     *
     * Actual state transitions are dependent on both the implementation, and the requirements that may additionally be
     * imposed by a derived cluster.
     *
     * An implementation that supports remotely starting its operation can make use of this cluster’s Start command to
     * do so. A device that supports remote pause or stop of its currently selected operation can similarly make use of
     * this cluster’s Pause and Stop commands to do so. The ability to remotely pause or stop is independent of how the
     * operation was started (for example, an operation started by using a manual button press can be stopped by using a
     * Stop command if the device supports remotely stopping the operation).
     *
     * Additionally, this cluster provides events for monitoring the operational state of the device.
     *
     * @see {@link MatterSpecification.v142.Cluster} § 1.14
     */
    interface Cluster extends Identity<typeof ClusterInstance> {
    }
    const Cluster: Cluster;
    const Complete: Cluster;
}
export type OperationalStateCluster = OperationalState.Cluster;
export declare const OperationalStateCluster: OperationalState.Cluster;
//# sourceMappingURL=operational-state.d.ts.map