@project-chip/matter.js 0.4.0 → 0.5.0

package/dist/cjs/cluster/definitions/ThermostatCluster.d.ts

@@ -0,0 +1,2885 @@
+/**
+ * @license
+ * Copyright 2022-2023 Project CHIP Authors
+ * SPDX-License-Identifier: Apache-2.0
+ */
+import { BaseClusterComponent, ClusterComponent, ExtensibleCluster, ClusterForBaseCluster, AsConditional } from "../../cluster/ClusterFactory.js";
+import { BitFlag, BitFlags, TypeFromPartialBitSchema } from "../../schema/BitmapSchema.js";
+import { Attribute, OptionalAttribute, OptionalWritableAttribute, WritableAttribute, Command, OptionalCommand, OptionalFixedAttribute, FixedAttribute, Cluster as CreateCluster } from "../../cluster/Cluster.js";
+export declare namespace Thermostat {
+    /**
+     * The value of the Thermostat remoteSensing attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.22
+     */
+    const RemoteSensing: {
+        /**
+         * When set, LocalTemperature Value is derived from a remote node
+         */
+        localTemperature: BitFlag;
+        /**
+         * When set, OutdoorTemperature is derived from a remote node
+         */
+        outdoorTemperature: BitFlag;
+        /**
+         * When set, Occupancy is derived from a remote node
+         */
+        occupancy: BitFlag;
+    };
+    /**
+     * The value of the Thermostat controlSequenceOfOperation attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.23
+     */
+    const enum ControlSequenceOfOperation {
+        /**
+         * Heat and Emergency are not possible
+         */
+        CoolingOnly = 0,
+        /**
+         * Heat and Emergency are not possible
+         */
+        CoolingWithReheat = 1,
+        /**
+         * Cool and precooling (see Terms) are not possible
+         */
+        HeatingOnly = 2,
+        /**
+         * Cool and precooling are not possible
+         */
+        HeatingWithReheat = 3,
+        /**
+         * All modes are possible
+         */
+        CoolingAndHeating = 4,
+        /**
+         * All modes are possible
+         */
+        CoolingAndHeatingWithReheat = 5
+    }
+    /**
+     * The value of the Thermostat systemMode attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.24
+     */
+    const enum SystemMode {
+        /**
+         * The Thermostat does not generate demand for Cooling or Heating
+         */
+        Off = 0,
+        /**
+         * Demand is generated for either Cooling or Heating, as required
+         */
+        Auto = 1,
+        /**
+         * Demand is only generated for Cooling
+         */
+        Cool = 3,
+        /**
+         * Demand is only generated for Heating
+         */
+        Heat = 4,
+        /**
+         * 2nd stage heating is in use to achieve desired temperature
+         */
+        EmergencyHeat = 5,
+        /**
+         * (see Terms)
+         */
+        Precooling = 6,
+        FanOnly = 7,
+        Dry = 8,
+        Sleep = 9
+    }
+    /**
+     * The value of the Thermostat alarmMask attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.25
+     */
+    const AlarmMask: {
+        initializationFailure: BitFlag;
+        hardwareFailure: BitFlag;
+        selfCalibrationFailure: BitFlag;
+    };
+    /**
+     * The value of the Thermostat temperatureSetpointHold attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.30
+     */
+    const enum TemperatureSetpointHold {
+        /**
+         * Follow scheduling program
+         */
+        SetpointHoldOff = 0,
+        /**
+         * Maintain current setpoint, regardless of schedule transitions
+         */
+        SetpointHoldOn = 1
+    }
+    /**
+     * The value of the Thermostat thermostatProgrammingOperationMode attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.32
+     */
+    const ThermostatProgrammingOperationMode: {
+        /**
+         * Schedule programming mode. This enables any programmed weekly schedule configurations.
+         */
+        scheduleActive: BitFlag;
+        /**
+         * Auto/recovery mode
+         */
+        autoRecovery: BitFlag;
+        /**
+         * Economy/EnergyStar mode
+         */
+        economy: BitFlag;
+    };
+    /**
+     * The value of the Thermostat thermostatRunningState attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.33
+     */
+    const ThermostatRunningState: {
+        /**
+         * Heat State On
+         */
+        heat: BitFlag;
+        /**
+         * Cool State On
+         */
+        cool: BitFlag;
+        /**
+         * Fan State On
+         */
+        fan: BitFlag;
+        /**
+         * Heat 2nd Stage State On
+         */
+        heatStage2: BitFlag;
+        /**
+         * Cool 2nd Stage State On
+         */
+        coolStage2: BitFlag;
+        /**
+         * Fan 2nd Stage State On
+         */
+        fanStage2: BitFlag;
+        /**
+         * Fan 3rd Stage Stage On
+         */
+        fanStage3: BitFlag;
+    };
+    /**
+     * The value of the Thermostat setpointChangeSource attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.34
+     */
+    const enum SetpointChangeSource {
+        /**
+         * Manual, user-initiated setpoint change via the thermostat
+         */
+        Manual = 0,
+        /**
+         * Schedule/internal programming-initiated setpoint change
+         */
+        Schedule = 1,
+        /**
+         * Externally-initiated setpoint change (e.g., DRLC cluster command, attribute write)
+         */
+        External = 2
+    }
+    /**
+     * The value of the Thermostat acType attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.44
+     */
+    const enum AcType {
+        /**
+         * Unknown AC Type
+         */
+        Unknown = 0,
+        /**
+         * Cooling and Fixed Speed
+         */
+        CoolingFixed = 1,
+        /**
+         * Heat Pump and Fixed Speed
+         */
+        HeatPumpFixed = 2,
+        /**
+         * Cooling and Inverter
+         */
+        CoolingInverter = 3,
+        /**
+         * Heat Pump and Inverter
+         */
+        HeatPumpInverter = 4
+    }
+    /**
+     * The value of the Thermostat acRefrigerantType attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.46
+     */
+    const enum AcRefrigerantType {
+        /**
+         * Unknown Refrigerant Type
+         */
+        Unknown = 0,
+        /**
+         * R22 Refrigerant
+         */
+        R22 = 1,
+        /**
+         * R410a Refrigerant
+         */
+        R410A = 2,
+        /**
+         * R407c Refrigerant
+         */
+        R407C = 3
+    }
+    /**
+     * The value of the Thermostat acCompressorType attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.47
+     */
+    const enum AcCompressorType {
+        /**
+         * Unknown compressor type
+         */
+        Unknown = 0,
+        /**
+         * Max working ambient 43 °C
+         */
+        T1 = 1,
+        /**
+         * Max working ambient 35 °C
+         */
+        T2 = 2,
+        /**
+         * Max working ambient 52 °C
+         */
+        T3 = 3
+    }
+    /**
+     * The value of the Thermostat acErrorCode attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.48
+     */
+    const AcErrorCode: {
+        /**
+         * Compressor Failure or Refrigerant Leakage
+         */
+        compressorFail: BitFlag;
+        /**
+         * Room Temperature Sensor Failure
+         */
+        roomSensorFail: BitFlag;
+        /**
+         * Outdoor Temperature Sensor Failure
+         */
+        outdoorSensorFail: BitFlag;
+        /**
+         * Indoor Coil Temperature Sensor Failure
+         */
+        coilSensorFail: BitFlag;
+        /**
+         * Fan Failure
+         */
+        fanFail: BitFlag;
+    };
+    /**
+     * The value of the Thermostat acLouverPosition attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.49
+     */
+    const enum AcLouverPosition {
+        /**
+         * Fully Closed
+         */
+        Closed = 1,
+        /**
+         * Fully Open
+         */
+        Open = 2,
+        /**
+         * Quarter Open
+         */
+        Quarter = 3,
+        /**
+         * Half Open
+         */
+        Half = 4,
+        /**
+         * Three Quarters Open
+         */
+        ThreeQuarters = 5
+    }
+    /**
+     * The value of the Thermostat acCapacityFormat attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.51
+     */
+    const enum AcCapacityFormat {
+        /**
+         * British Thermal Unit per Hour
+         */
+        BtUh = 0
+    }
+    const enum SetpointAdjustMode {
+        Heat = 0,
+        Cool = 1,
+        Both = 2
+    }
+    /**
+     * Input to the Thermostat setpointRaiseLower command
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+     */
+    const TlvSetpointRaiseLowerRequest: import("../../tlv/TlvObject.js").ObjectSchema<{
+        mode: import("../../tlv/TlvObject.js").FieldType<SetpointAdjustMode>;
+        amount: import("../../tlv/TlvObject.js").FieldType<number>;
+    }>;
+    /**
+     * The value of the Thermostat occupancy attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.4
+     */
+    const Occupancy: {
+        occupied: BitFlag;
+    };
+    /**
+     * The value of the Thermostat thermostatRunningMode attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7
+     */
+    const enum ThermostatRunningMode {
+        Off = 0,
+        Cool = 3,
+        Heat = 4
+    }
+    /**
+     * The value of the Thermostat startOfWeek attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.27
+     */
+    const enum StartOfWeek {
+        Sunday = 0,
+        Monday = 1,
+        Tuesday = 2,
+        Wednesday = 3,
+        Thursday = 4,
+        Friday = 5,
+        Saturday = 6
+    }
+    const DayOfWeek: {
+        sunday: BitFlag;
+        monday: BitFlag;
+        tuesday: BitFlag;
+        wednesday: BitFlag;
+        thursday: BitFlag;
+        friday: BitFlag;
+        saturday: BitFlag;
+        away: BitFlag;
+    };
+    const ModeForSequence: {
+        heatSetpointPresent: BitFlag;
+        coolSetpointPresent: BitFlag;
+    };
+    /**
+     * This represents a single transition in a Thermostat schedule
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.9.5
+     */
+    const TlvThermostatScheduleTransition: import("../../tlv/TlvObject.js").ObjectSchema<{
+        /**
+         * This field represents the start time of the schedule transition during the associated day. The time will be
+         * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
+         * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.9.5.1
+         */
+        transitionTime: import("../../tlv/TlvObject.js").FieldType<number>;
+        heatSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+        coolSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+    }>;
+    /**
+     * Input to the Thermostat setWeeklySchedule command
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+     */
+    const TlvSetWeeklyScheduleRequest: import("../../tlv/TlvObject.js").ObjectSchema<{
+        numberOfTransitionsForSequence: import("../../tlv/TlvObject.js").FieldType<number>;
+        dayOfWeekForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+            sunday: BitFlag;
+            monday: BitFlag;
+            tuesday: BitFlag;
+            wednesday: BitFlag;
+            thursday: BitFlag;
+            friday: BitFlag;
+            saturday: BitFlag;
+            away: BitFlag;
+        }>>;
+        modeForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+            heatSetpointPresent: BitFlag;
+            coolSetpointPresent: BitFlag;
+        }>>;
+        transitions: import("../../tlv/TlvObject.js").FieldType<import("../../tlv/TlvObject.js").TypeFromFields<{
+            /**
+             * This field represents the start time of the schedule transition during the associated day. The time will be
+             * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
+             * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
+             *
+             * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.9.5.1
+             */
+            transitionTime: import("../../tlv/TlvObject.js").FieldType<number>;
+            heatSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+            coolSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+        }>[]>;
+    }>;
+    /**
+     * Input to the Thermostat getWeeklySchedule command
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+     */
+    const TlvGetWeeklyScheduleRequest: import("../../tlv/TlvObject.js").ObjectSchema<{
+        daysToReturn: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+            sunday: BitFlag;
+            monday: BitFlag;
+            tuesday: BitFlag;
+            wednesday: BitFlag;
+            thursday: BitFlag;
+            friday: BitFlag;
+            saturday: BitFlag;
+            away: BitFlag;
+        }>>;
+        modeToReturn: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+            heatSetpointPresent: BitFlag;
+            coolSetpointPresent: BitFlag;
+        }>>;
+    }>;
+    /**
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+     */
+    const TlvGetWeeklyScheduleResponse: import("../../tlv/TlvObject.js").ObjectSchema<{
+        numberOfTransitionsForSequence: import("../../tlv/TlvObject.js").FieldType<number>;
+        dayOfWeekForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+            sunday: BitFlag;
+            monday: BitFlag;
+            tuesday: BitFlag;
+            wednesday: BitFlag;
+            thursday: BitFlag;
+            friday: BitFlag;
+            saturday: BitFlag;
+            away: BitFlag;
+        }>>;
+        modeForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+            heatSetpointPresent: BitFlag;
+            coolSetpointPresent: BitFlag;
+        }>>;
+        transitions: import("../../tlv/TlvObject.js").FieldType<import("../../tlv/TlvObject.js").TypeFromFields<{
+            /**
+             * This field represents the start time of the schedule transition during the associated day. The time will be
+             * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
+             * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
+             *
+             * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.9.5.1
+             */
+            transitionTime: import("../../tlv/TlvObject.js").FieldType<number>;
+            heatSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+            coolSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+        }>[]>;
+    }>;
+    /**
+     * These are optional features supported by ThermostatCluster.
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.3.1
+     */
+    enum Feature {
+        /**
+         * Heating
+         *
+         * Thermostat is capable of managing a heating device
+         */
+        Heating = "Heating",
+        /**
+         * Cooling
+         *
+         * Thermostat is capable of managing a cooling device
+         */
+        Cooling = "Cooling",
+        /**
+         * Occupancy
+         *
+         * Supports Occupied and Unoccupied setpoints
+         */
+        Occupancy = "Occupancy",
+        /**
+         * ScheduleConfiguration
+         *
+         * Supports remote configuration of a weekly schedule of setpoint transitions
+         */
+        ScheduleConfiguration = "ScheduleConfiguration",
+        /**
+         * Setback
+         *
+         * Supports configurable setback (or span)
+         */
+        Setback = "Setback",
+        /**
+         * AutoMode
+         *
+         * Supports a System Mode of Auto
+         */
+        AutoMode = "AutoMode",
+        /**
+         * LocalTemperatureNotExposed
+         *
+         * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+         */
+        LocalTemperatureNotExposed = "LocalTemperatureNotExposed"
+    }
+    /**
+     * These elements and properties are present in all Thermostat clusters.
+     */
+    const Base: BaseClusterComponent<{
+        /**
+         * Heating
+         *
+         * Thermostat is capable of managing a heating device
+         */
+        heating: BitFlag;
+        /**
+         * Cooling
+         *
+         * Thermostat is capable of managing a cooling device
+         */
+        cooling: BitFlag;
+        /**
+         * Occupancy
+         *
+         * Supports Occupied and Unoccupied setpoints
+         */
+        occupancy: BitFlag;
+        /**
+         * ScheduleConfiguration
+         *
+         * Supports remote configuration of a weekly schedule of setpoint transitions
+         */
+        scheduleConfiguration: BitFlag;
+        /**
+         * Setback
+         *
+         * Supports configurable setback (or span)
+         */
+        setback: BitFlag;
+        /**
+         * AutoMode
+         *
+         * Supports a System Mode of Auto
+         */
+        autoMode: BitFlag;
+        /**
+         * LocalTemperatureNotExposed
+         *
+         * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+         */
+        localTemperatureNotExposed: BitFlag;
+    }, {
+        /**
+         * This attribute indicates the current LocalTemperature value, when available. The value may be local, or
+         * remote, depending on the value of the RemoteSensing attribute when supported.
+         *
+         *   • If the LTNE feature is not supported:
+         *
+         *     ◦ If the temperature measurement is invalid or currently unavailable, the attribute shall report
+         *       null.
+         *
+         *     ◦ If the temperature measurement is valid, the attribute shall report that value.
+         *
+         *   • Otherwise, if the LTNE feature is supported, there is no feedback externally available for the
+         *     LocalTemperature value. In that case, the LocalTemperature attribute shall always report null.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.2
+         */
+        localTemperature: Attribute<number | null, any>;
+        /**
+         * This attribute represents the outdoor temperature, as measured locally or remotely (over the network).
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.3
+         */
+        outdoorTemperature: OptionalAttribute<number | null, any>;
+        /**
+         * This attribute indicates when the local temperature, outdoor temperature and occupancy are being sensed
+         * by remote networked sensors, rather than internal sensors.
+         *
+         * A bit set to 1 indicates remote sensing of the relevant value.
+         *
+         * Table 72. RemoteSensing Attribute Bit Values
+         *
+         * If the LTNE feature is present in the server, the LocalTemperature RemoteSensing bit value shall always
+         * report a value of 0.
+         *
+         * If the LocalTemperature RemoteSensing bit is written with a value of 1 when the LTNE feature is present,
+         * the write shall fail and the server shall report a CONSTRAINT_ERROR.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.22
+         */
+        remoteSensing: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+            /**
+             * When set, LocalTemperature Value is derived from a remote node
+             */
+            localTemperature: BitFlag;
+            /**
+             * When set, OutdoorTemperature is derived from a remote node
+             */
+            outdoorTemperature: BitFlag;
+            /**
+             * When set, Occupancy is derived from a remote node
+             */
+            occupancy: BitFlag;
+        }>, any>;
+        /**
+         * This attribute specifies the overall operating environment of the thermostat, and thus the possible
+         * system modes that the thermostat can operate in. It shall be set to one of the following values.
+         *
+         * Table 73. ControlSequenceOfOperation Values
+         *
+         * NOTE
+         *
+         * CoolingAndHeating
+         *
+         * A thermostat indicating it supports CoolingAndHeating (or CoolingAndHeatingWithReheat) SHOULD be able to
+         * request heating or cooling on demand and will usually support the Auto SystemMode.
+         *
+         * Systems which support cooling or heating, requiring external intervention to change modes or where the
+         * whole building must be in the same mode, SHOULD report CoolingOnly or HeatingOnly based on the current
+         * capability.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.23
+         */
+        controlSequenceOfOperation: WritableAttribute<ControlSequenceOfOperation, any>;
+        /**
+         * This attribute specifies the current operating mode of the thermostat, It shall be set to one of the
+         * following values, as limited by the ControlSequenceOfOperation Attribute.
+         *
+         * NOTE It is not mandatory to support all values.
+         *
+         * Table 75. Interpretation of Heat, Cool and Auto SystemMode Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.24
+         */
+        systemMode: WritableAttribute<SystemMode, any>;
+        /**
+         * This attribute specifies whether each of the alarms listed below is enabled. When the bit number
+         * corresponding to the alarm code is set to 1, the alarm is enabled, else it is disabled. Bits not
+         * corresponding to a code in the table are reserved.
+         *
+         * When the Alarms cluster is implemented on a device, and one of the alarm conditions included in this
+         * table occurs, an alarm notification is generated, with the alarm code field set as listed in the table.
+         *
+         * Table 76. Alarm Codes
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.25
+         */
+        alarmMask: OptionalAttribute<TypeFromPartialBitSchema<{
+            initializationFailure: BitFlag;
+            hardwareFailure: BitFlag;
+            selfCalibrationFailure: BitFlag;
+        }>, any>;
+        /**
+         * This attribute specifies the temperature hold status on the thermostat. If hold status is on, the
+         * thermostat SHOULD maintain the temperature set point for the current mode until a system mode change. If
+         * hold status is off, the thermostat SHOULD follow the setpoint transitions specified by its internal
+         * scheduling program. If the thermostat supports setpoint hold for a specific duration, it SHOULD also
+         * implement the TemperatureSetpointHoldDuration attribute.
+         *
+         * Table 78. TemperatureSetpointHold Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.30
+         */
+        temperatureSetpointHold: OptionalWritableAttribute<TemperatureSetpointHold, any>;
+        /**
+         * This attribute sets the period in minutes for which a setpoint hold is active. Thermostats that support
+         * hold for a specified duration SHOULD implement this attribute. The null value indicates the field is
+         * unused. All other values are reserved.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.31
+         */
+        temperatureSetpointHoldDuration: OptionalWritableAttribute<number | null, any>;
+        /**
+         * This attribute determines the operational state of the thermostat’s programming. The thermostat shall
+         * modify its programming operation when this attribute is modified by a client and update this attribute
+         * when its programming operation is modified locally by a user. The thermostat may support more than one
+         * active ThermostatProgrammingOperationMode. For example, the thermostat may operate simultaneously in
+         * Schedule Programming Mode and Recovery Mode.
+         *
+         * Thermostats which contain a schedule may use this attribute to control how that schedule is used, even
+         * if they do not support the Schedule Configuration feature.
+         *
+         * Table 79. ThermostatProgrammingOperationMode Attribute Values
+         *
+         * When ScheduleActive is not set, the setpoint is altered only by manual up/down changes at the thermostat
+         * or remotely, not by internal schedule programming.
+         *
+         * NOTE Modifying the ScheduleActive bit does not clear or delete previous weekly schedule programming
+         * configurations.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.32
+         */
+        thermostatProgrammingOperationMode: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+            /**
+             * Schedule programming mode. This enables any programmed weekly schedule configurations.
+             */
+            scheduleActive: BitFlag;
+            /**
+             * Auto/recovery mode
+             */
+            autoRecovery: BitFlag;
+            /**
+             * Economy/EnergyStar mode
+             */
+            economy: BitFlag;
+        }>, any>;
+        /**
+         * This attribute represents the current relay state of the heat, cool, and fan relays.
+         *
+         * Table 80. HVAC Relay State Values
+         *
+         * Unimplemented outputs shall be treated as if they were Off.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.33
+         */
+        thermostatRunningState: OptionalAttribute<TypeFromPartialBitSchema<{
+            /**
+             * Heat State On
+             */
+            heat: BitFlag;
+            /**
+             * Cool State On
+             */
+            cool: BitFlag;
+            /**
+             * Fan State On
+             */
+            fan: BitFlag;
+            /**
+             * Heat 2nd Stage State On
+             */
+            heatStage2: BitFlag;
+            /**
+             * Cool 2nd Stage State On
+             */
+            coolStage2: BitFlag;
+            /**
+             * Fan 2nd Stage State On
+             */
+            fanStage2: BitFlag;
+            /**
+             * Fan 3rd Stage Stage On
+             */
+            fanStage3: BitFlag;
+        }>, any>;
+        /**
+         * This attribute specifies the source of the current active OccupiedCoolingSetpoint or
+         * OccupiedHeatingSetpoint (i.e., who or what determined the current setpoint).
+         *
+         * This attribute enables service providers to determine whether changes to setpoints were initiated due to
+         * occupant comfort, scheduled programming or some other source (e.g., electric utility or other service
+         * provider). Because automation services may initiate frequent setpoint changes, this attribute clearly
+         * differentiates the source of setpoint changes made at the thermostat.
+         *
+         * Table 81. SetpointChangeSource Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.34
+         */
+        setpointChangeSource: OptionalAttribute<SetpointChangeSource, any>;
+        /**
+         * This attribute specifies the delta between the current active OccupiedCoolingSetpoint or
+         * OccupiedHeatingSetpoint and the previous active setpoint. This attribute is meant to accompany the
+         * SetpointChangeSource attribute; devices implementing SetpointChangeAmount SHOULD also implement
+         * SetpointChangeSource.
+         *
+         * The null value indicates that the previous setpoint was unknown.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.35
+         */
+        setpointChangeAmount: OptionalAttribute<number | null, any>;
+        /**
+         * This attribute specifies the time in UTC at which the SetpointChangeSourceAmount attribute change was
+         * recorded.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.36
+         */
+        setpointChangeSourceTimestamp: OptionalAttribute<number, any>;
+        /**
+         * This attribute specifies the delta between the LocalTemperature Value and the OccupiedHeatingSetpoint or
+         * UnoccupiedHeatingSetpoint attributes at which the Thermostat server will operate in emergency heat mode.
+         *
+         * If the difference between LocalTemperature Value and Un/OccupiedHeatingSetpoint is greater than or equal
+         * to the EmergencyHeatDelta and the Thermostat server’s SystemMode attribute is in a heating-related mode,
+         * then the Thermostat server shall immediately switch to the SystemMode attribute value that provides the
+         * highest stage of heating (e.g., emergency heat) and continue operating in that running state until the
+         * OccupiedHeatingSetpoint value is reached. For example:
+         *
+         *   • LocalTemperature = 10.0°C
+         *
+         *   • OccupiedHeatingSetpoint = 16.0°C
+         *
+         *   • EmergencyHeatDelta = 2.0°C
+         *
+         * ⇒ OccupiedHeatingSetpoint - LocalTemperature ≥? EmergencyHeatDelta
+         *
+         * ⇒ 16°C - 10°C ≥? 2°C
+         *
+         * ⇒ TRUE >>> Thermostat server changes its SystemMode to operate in 2nd stage or emergency heat mode
+         *
+         * The purpose of this attribute is to provide Thermostat clients the ability to configure rapid heating
+         * when a setpoint is of a specified amount greater than the measured temperature. This allows the heated
+         * space to be quickly heated to the desired level set by the user.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.43
+         */
+        emergencyHeatDelta: OptionalWritableAttribute<number, any>;
+        /**
+         * This attribute indicates the type of Mini Split ACType of Mini Split AC is defined depending on how
+         * Cooling and Heating condition is achieved by Mini Split AC.
+         *
+         * Table 82. ACType Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.44
+         */
+        acType: OptionalWritableAttribute<AcType, any>;
+        /**
+         * This attribute indicates capacity of Mini Split AC in terms of the format defined by the
+         * ACCapacityFormat attribute
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.45
+         */
+        acCapacity: OptionalWritableAttribute<number, any>;
+        /**
+         * This attribute indicates type of refrigerant used within the Mini Split AC.
+         *
+         * Table 83. ACRefrigerantType Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.46
+         */
+        acRefrigerantType: OptionalWritableAttribute<AcRefrigerantType, any>;
+        /**
+         * This attribute indicates type of Compressor used within the Mini Split AC.
+         *
+         * Table 84. ACCompressorType Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.47
+         */
+        acCompressorType: OptionalWritableAttribute<AcCompressorType, any>;
+        /**
+         * This attribute indicates the type of errors encountered within the Mini Split AC. Error values are
+         * reported with four bytes values. Each bit within the four bytes indicates the unique error.
+         *
+         * Table 85. ACErrorCode Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.48
+         */
+        acErrorCode: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+            /**
+             * Compressor Failure or Refrigerant Leakage
+             */
+            compressorFail: BitFlag;
+            /**
+             * Room Temperature Sensor Failure
+             */
+            roomSensorFail: BitFlag;
+            /**
+             * Outdoor Temperature Sensor Failure
+             */
+            outdoorSensorFail: BitFlag;
+            /**
+             * Indoor Coil Temperature Sensor Failure
+             */
+            coilSensorFail: BitFlag;
+            /**
+             * Fan Failure
+             */
+            fanFail: BitFlag;
+        }>, any>;
+        /**
+         * This attribute indicates the position of Louver on the AC.
+         *
+         * Table 86. ACLouverPosition Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.49
+         */
+        acLouverPosition: OptionalWritableAttribute<AcLouverPosition, any>;
+        /**
+         * This attribute represents the temperature of the AC coil, as measured locally or remotely (over the
+         * network).
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.50
+         */
+        acCoilTemperature: OptionalAttribute<number | null, any>;
+        /**
+         * This attribute specifies the format for the ACCapacity attribute.
+         *
+         * Table 87. ACCapacity Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.51
+         */
+        acCapacityFormat: OptionalWritableAttribute<AcCapacityFormat, any>;
+    }, {
+        /**
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+         */
+        setpointRaiseLower: Command<import("../../tlv/TlvObject.js").TypeFromFields<{
+            mode: import("../../tlv/TlvObject.js").FieldType<SetpointAdjustMode>;
+            amount: import("../../tlv/TlvObject.js").FieldType<number>;
+        }>, void, any>;
+        /**
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+         */
+        getRelayStatusLog: OptionalCommand<void, void, any>;
+    }, import("../../cluster/Cluster.js").Events>;
+    /**
+     * A ThermostatCluster supports these elements if it supports feature Occupancy.
+     */
+    const OccupancyComponent: ClusterComponent<{
+        /**
+         * This attribute specifies whether the heated/cooled space is occupied or not, as measured locally or
+         * remotely (over the network). If bit 0 = 1, the space is occupied, else it is unoccupied. All other bits
+         * are reserved.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.4
+         */
+        occupancy: Attribute<TypeFromPartialBitSchema<{
+            occupied: BitFlag;
+        }>, any>;
+    }, import("../../cluster/Cluster.js").Commands, import("../../cluster/Cluster.js").Events>;
+    /**
+     * A ThermostatCluster supports these elements if it supports feature Heating.
+     */
+    const HeatingComponent: ClusterComponent<{
+        /**
+         * This attribute specifies the absolute minimum level that the heating setpoint may be set to. This is a
+         * limitation imposed by the manufacturer.
+         *
+         * Refer to Setpoint Limits for constraints
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.5
+         */
+        absMinHeatSetpointLimit: OptionalFixedAttribute<number, any>;
+        /**
+         * This attribute specifies the absolute maximum level that the heating setpoint may be set to. This is a
+         * limitation imposed by the manufacturer.
+         *
+         * Refer to Setpoint Limits for constraints
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.6
+         */
+        absMaxHeatSetpointLimit: OptionalFixedAttribute<number, any>;
+        /**
+         * This attribute specifies the level of heating demanded by the PI loop in percent. This value is 0 when
+         * the thermostat is in “off” or “cooling” mode.
+         *
+         * This attribute is reported regularly and may be used to control a heating device.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.10
+         */
+        piHeatingDemand: OptionalAttribute<number, any>;
+        /**
+         * This attribute specifies the heating mode setpoint when the room is occupied.
+         *
+         * Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute such that these
+         * constraints are violated, a response with the status code CONSTRAINT_ERROR shall be returned.
+         *
+         * If the occupancy status of the room is unknown, this attribute shall be used as the heating mode
+         * setpoint.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.14
+         */
+        occupiedHeatingSetpoint: WritableAttribute<number, any>;
+        /**
+         * This attribute specifies the minimum level that the heating setpoint may be set to.
+         *
+         * This attribute, and the following three attributes, allow the user to define setpoint limits more
+         * constrictive than the manufacturer imposed ones. Limiting users (e.g., in a commercial building) to such
+         * setpoint limits can help conserve power.
+         *
+         * Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute to a value which
+         * conflicts with setpoint values then those setpoints shall be adjusted by the minimum amount to permit
+         * this attribute to be set to the desired value. If an attempt is made to set this attribute to a value
+         * which is not consistent with the constraints and cannot be resolved by modifying setpoints then a
+         * response with the status code CONSTRAINT_ERROR shall be returned.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.17
+         */
+        minHeatSetpointLimit: OptionalWritableAttribute<number, any>;
+        /**
+         * This attribute specifies the maximum level that the heating setpoint may be set to.
+         *
+         * Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute to a value which
+         * conflicts with setpoint values then those setpoints shall be adjusted by the minimum amount to permit
+         * this attribute to be set to the desired value. If an attempt is made to set this attribute to a value
+         * which is not consistent with the constraints and cannot be resolved by modifying setpoints then a
+         * response with the status code CONSTRAINT_ERROR shall be returned.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.18
+         */
+        maxHeatSetpointLimit: OptionalWritableAttribute<number, any>;
+    }, import("../../cluster/Cluster.js").Commands, import("../../cluster/Cluster.js").Events>;
+    /**
+     * A ThermostatCluster supports these elements if it supports feature Cooling.
+     */
+    const CoolingComponent: ClusterComponent<{
+        /**
+         * This attribute specifies the absolute minimum level that the cooling setpoint may be set to. This is a
+         * limitation imposed by the manufacturer.
+         *
+         * Refer to Setpoint Limits for constraints
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.7
+         */
+        absMinCoolSetpointLimit: OptionalFixedAttribute<number, any>;
+        /**
+         * This attribute specifies the absolute maximum level that the cooling setpoint may be set to. This is a
+         * limitation imposed by the manufacturer.
+         *
+         * Refer to Setpoint Limits for constraints
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.8
+         */
+        absMaxCoolSetpointLimit: OptionalFixedAttribute<number, any>;
+        /**
+         * This attribute specifies the level of cooling demanded by the PI (proportional integral) control loop in
+         * use by the thermostat (if any), in percent. This value is 0 when the thermostat is in “off” or “heating”
+         * mode.
+         *
+         * This attribute is reported regularly and may be used to control a cooling device.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.9
+         */
+        piCoolingDemand: OptionalAttribute<number, any>;
+        /**
+         * This attribute specifies the cooling mode setpoint when the room is occupied.
+         *
+         * Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute such that these
+         * constraints are violated, a response with the status code CONSTRAINT_ERROR shall be returned.
+         *
+         * If the occupancy status of the room is unknown, this attribute shall be used as the cooling mode
+         * setpoint.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.13
+         */
+        occupiedCoolingSetpoint: WritableAttribute<number, any>;
+        /**
+         * This attribute specifies the minimum level that the cooling setpoint may be set to.
+         *
+         * Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute to a value which
+         * conflicts with setpoint values then those setpoints shall be adjusted by the minimum amount to permit
+         * this attribute to be set to the desired value. If an attempt is made to set this attribute to a value
+         * which is not consistent with the constraints and cannot be resolved by modifying setpoints then a
+         * response with the status code CONSTRAINT_ERROR shall be returned.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.19
+         */
+        minCoolSetpointLimit: OptionalWritableAttribute<number, any>;
+        /**
+         * This attribute specifies the maximum level that the cooling setpoint may be set to.
+         *
+         * Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute to a value which
+         * conflicts with setpoint values then those setpoints shall be adjusted by the minimum amount to permit
+         * this attribute to be set to the desired value. If an attempt is made to set this attribute to a value
+         * which is not consistent with the constraints and cannot be resolved by modifying setpoints
+         *
+         * then a response with the status code CONSTRAINT_ERROR shall be returned.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.20
+         */
+        maxCoolSetpointLimit: OptionalWritableAttribute<number, any>;
+    }, import("../../cluster/Cluster.js").Commands, import("../../cluster/Cluster.js").Events>;
+    /**
+     * A ThermostatCluster supports these elements if doesn't support feature LTNE.
+     */
+    const NotLocalTemperatureNotExposedComponent: ClusterComponent<{
+        /**
+         * This attribute specifies the offset the Thermostat server shall make to the measured temperature
+         * (locally or remotely) to adjust the LocalTemperature Value prior to using, displaying or reporting it.
+         *
+         * The purpose of this attribute is to adjust the calibration of the Thermostat server per the user’s
+         * preferences (e.g., to match if there are multiple servers displaying different values for the same HVAC
+         * area) or compensate for variability amongst temperature sensors.
+         *
+         * If a Thermostat client attempts to write LocalTemperatureCalibration attribute to an unsupported value
+         * (e.g., out of the range supported by the Thermostat server), the Thermostat server shall respond with a
+         * status of SUCCESS and set the value of LocalTemperatureCalibration to the upper or lower limit reached.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.12
+         */
+        localTemperatureCalibration: OptionalWritableAttribute<number, any>;
+    }, import("../../cluster/Cluster.js").Commands, import("../../cluster/Cluster.js").Events>;
+    /**
+     * A ThermostatCluster supports these elements if it supports features Cooling and Occupancy.
+     */
+    const CoolingAndOccupancyComponent: ClusterComponent<{
+        /**
+         * This attribute specifies the cooling mode setpoint when the room is unoccupied.
+         *
+         * Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute such that these
+         * constraints are violated, a response with the status code CONSTRAINT_ERROR shall be returned.
+         *
+         * If the occupancy status of the room is unknown, this attribute shall not be used.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.15
+         */
+        unoccupiedCoolingSetpoint: WritableAttribute<number, any>;
+    }, import("../../cluster/Cluster.js").Commands, import("../../cluster/Cluster.js").Events>;
+    /**
+     * A ThermostatCluster supports these elements if it supports features Heating and Occupancy.
+     */
+    const HeatingAndOccupancyComponent: ClusterComponent<{
+        /**
+         * This attribute specifies the heating mode setpoint when the room is unoccupied.
+         *
+         * Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute such that these
+         * constraints are violated, a response with the status code CONSTRAINT_ERROR shall be returned.
+         *
+         * If the occupancy status of the room is unknown, this attribute shall not be used.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.16
+         */
+        unoccupiedHeatingSetpoint: WritableAttribute<number, any>;
+    }, import("../../cluster/Cluster.js").Commands, import("../../cluster/Cluster.js").Events>;
+    /**
+     * A ThermostatCluster supports these elements if it supports feature AutoMode.
+     */
+    const AutoModeComponent: ClusterComponent<{
+        /**
+         * On devices which support the AUTO feature, this attribute specifies the minimum difference between the
+         * Heat Setpoint and the Cool Setpoint.
+         *
+         * Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute to a value which
+         * conflicts with setpoint values then those setpoints shall be adjusted by the minimum amount to permit
+         * this attribute to be set to the desired value. If an attempt is made to set this attribute to a value
+         * which is not consistent with the constraints and cannot be resolved by modifying setpoints then a
+         * response with the status code CONSTRAINT_ERROR shall be returned.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.21
+         */
+        minSetpointDeadBand: WritableAttribute<number, any>;
+        /**
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7
+         */
+        thermostatRunningMode: OptionalAttribute<ThermostatRunningMode, any>;
+    }, import("../../cluster/Cluster.js").Commands, import("../../cluster/Cluster.js").Events>;
+    /**
+     * A ThermostatCluster supports these elements if it supports feature ScheduleConfiguration.
+     */
+    const ScheduleConfigurationComponent: ClusterComponent<{
+        /**
+         * This attribute represents the day of the week that this thermostat considers to be the start of week for
+         * weekly set point scheduling.
+         *
+         * Table 77. StartofWeek Values
+         *
+         * This attribute may be able to be used as the base to determine if the device supports weekly scheduling
+         * by reading the attribute. Successful response means that the weekly scheduling is supported.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.27
+         */
+        startOfWeek: FixedAttribute<StartOfWeek, any>;
+        /**
+         * This attribute determines how many weekly schedule transitions the thermostat is capable of handling.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.28
+         */
+        numberOfWeeklyTransitions: FixedAttribute<number, any>;
+        /**
+         * This attribute determines how many daily schedule transitions the thermostat is capable of handling.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.29
+         */
+        numberOfDailyTransitions: FixedAttribute<number, any>;
+    }, {
+        /**
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+         */
+        setWeeklySchedule: Command<import("../../tlv/TlvObject.js").TypeFromFields<{
+            numberOfTransitionsForSequence: import("../../tlv/TlvObject.js").FieldType<number>;
+            dayOfWeekForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                sunday: BitFlag;
+                monday: BitFlag;
+                tuesday: BitFlag;
+                wednesday: BitFlag;
+                thursday: BitFlag;
+                friday: BitFlag;
+                saturday: BitFlag;
+                away: BitFlag;
+            }>>;
+            modeForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                heatSetpointPresent: BitFlag;
+                coolSetpointPresent: BitFlag;
+            }>>;
+            transitions: import("../../tlv/TlvObject.js").FieldType<import("../../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field represents the start time of the schedule transition during the associated day. The time will be
+                 * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
+                 * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
+                 *
+                 * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.9.5.1
+                 */
+                transitionTime: import("../../tlv/TlvObject.js").FieldType<number>;
+                heatSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+                coolSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+            }>[]>;
+        }>, void, any>;
+        /**
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+         */
+        getWeeklySchedule: Command<import("../../tlv/TlvObject.js").TypeFromFields<{
+            daysToReturn: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                sunday: BitFlag;
+                monday: BitFlag;
+                tuesday: BitFlag;
+                wednesday: BitFlag;
+                thursday: BitFlag;
+                friday: BitFlag;
+                saturday: BitFlag;
+                away: BitFlag;
+            }>>;
+            modeToReturn: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                heatSetpointPresent: BitFlag;
+                coolSetpointPresent: BitFlag;
+            }>>;
+        }>, import("../../tlv/TlvObject.js").TypeFromFields<{
+            numberOfTransitionsForSequence: import("../../tlv/TlvObject.js").FieldType<number>;
+            dayOfWeekForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                sunday: BitFlag;
+                monday: BitFlag;
+                tuesday: BitFlag;
+                wednesday: BitFlag;
+                thursday: BitFlag;
+                friday: BitFlag;
+                saturday: BitFlag;
+                away: BitFlag;
+            }>>;
+            modeForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                heatSetpointPresent: BitFlag;
+                coolSetpointPresent: BitFlag;
+            }>>;
+            transitions: import("../../tlv/TlvObject.js").FieldType<import("../../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field represents the start time of the schedule transition during the associated day. The time will be
+                 * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
+                 * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
+                 *
+                 * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.9.5.1
+                 */
+                transitionTime: import("../../tlv/TlvObject.js").FieldType<number>;
+                heatSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+                coolSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+            }>[]>;
+        }>, any>;
+        /**
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+         */
+        clearWeeklySchedule: Command<void, void, any>;
+    }, import("../../cluster/Cluster.js").Events>;
+    /**
+     * A ThermostatCluster supports these elements if it supports feature Setback.
+     */
+    const SetbackComponent: ClusterComponent<{
+        /**
+         * This attribute specifies the amount that the Thermostat server will allow the LocalTemperature Value to
+         * float above the OccupiedCooling setpoint (i.e., OccupiedCooling + OccupiedSetback) or below the
+         * OccupiedHeating setpoint (i.e., OccupiedHeating – OccupiedSetback) before initiating a state change to
+         * bring the temperature back to the user’s desired setpoint. This attribute is sometimes also referred to
+         * as the “span.”
+         *
+         * The purpose of this attribute is to allow remote configuration of the span between the desired set
+         *
+         * point and the measured temperature to help prevent over-cycling and reduce energy bills, though this may
+         * result in lower comfort on the part of some users.
+         *
+         * The null value indicates the attribute is unused.
+         *
+         * If the Thermostat client attempts to write OccupiedSetback to a value greater than OccupiedSetbackMax,
+         * the Thermostat server shall set its OccupiedSetback value to OccupiedSetbackMax and shall send a Write
+         * Attribute Response command with a Status Code field enumeration of SUCCESS response.
+         *
+         * If the Thermostat client attempts to write OccupiedSetback to a value less than OccupiedSetbackMin, the
+         * Thermostat server shall set its OccupiedSetback value to OccupiedSetbackMin and shall send a Write
+         * Attribute Response command with a Status Code field enumeration of SUCCESS response.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.37
+         */
+        occupiedSetback: WritableAttribute<number | null, any>;
+        /**
+         * This attribute specifies the minimum value that the Thermostat server will allow the OccupiedSetback
+         * attribute to be configured by a user.
+         *
+         * The null value indicates the attribute is unused.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.38
+         */
+        occupiedSetbackMin: FixedAttribute<number | null, any>;
+        /**
+         * This attribute specifies the maximum value that the Thermostat server will allow the OccupiedSetback
+         * attribute to be configured by a user.
+         *
+         * The null value indicates the attribute is unused.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.39
+         */
+        occupiedSetbackMax: FixedAttribute<number | null, any>;
+    }, import("../../cluster/Cluster.js").Commands, import("../../cluster/Cluster.js").Events>;
+    /**
+     * A ThermostatCluster supports these elements if it supports features Setback and Occupancy.
+     */
+    const SetbackAndOccupancyComponent: ClusterComponent<{
+        /**
+         * This attribute specifies the amount that the Thermostat server will allow the LocalTemperature Value to
+         * float above the UnoccupiedCooling setpoint (i.e., UnoccupiedCooling + UnoccupiedSetback) or below the
+         * UnoccupiedHeating setpoint (i.e., UnoccupiedHeating - UnoccupiedSetback) before initiating a state
+         * change to bring the temperature back to the user’s desired setpoint. This attribute is sometimes also
+         * referred to as the “span.”
+         *
+         * The purpose of this attribute is to allow remote configuration of the span between the desired setpoint
+         * and the measured temperature to help prevent over-cycling and reduce energy bills, though this may
+         * result in lower comfort on the part of some users.
+         *
+         * The null value indicates the attribute is unused.
+         *
+         * If the Thermostat client attempts to write UnoccupiedSetback to a value greater than
+         * UnoccupiedSetbackMax, the Thermostat server shall set its UnoccupiedSetback value to
+         * UnoccupiedSetbackMax and shall send a Write Attribute Response command with a Status Code field
+         * enumeration of SUCCESS response.
+         *
+         * If the Thermostat client attempts to write UnoccupiedSetback to a value less than UnoccupiedSetbackMin,
+         * the Thermostat server shall set its UnoccupiedSetback value to UnoccupiedSetbackMin and shall send a
+         * Write Attribute Response command with a Status Code field enumeration of SUCCESS response.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.40
+         */
+        unoccupiedSetback: WritableAttribute<number | null, any>;
+        /**
+         * This attribute specifies the minimum value that the Thermostat server will allow the UnoccupiedSetback
+         * attribute to be configured by a user.
+         *
+         * The null value indicates the attribute is unused.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.41
+         */
+        unoccupiedSetbackMin: FixedAttribute<number | null, any>;
+        /**
+         * This attribute specifies the maximum value that the Thermostat server will allow the UnoccupiedSetback
+         * attribute to be configured by a user.
+         *
+         * The null value indicates the attribute is unused.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.42
+         */
+        unoccupiedSetbackMax: FixedAttribute<number | null, any>;
+    }, import("../../cluster/Cluster.js").Commands, import("../../cluster/Cluster.js").Events>;
+    /**
+     * Thermostat
+     *
+     * This cluster provides an interface to the functionality of a thermostat.
+     *
+     * ThermostatCluster supports optional features that you can enable with the ThermostatCluster.with() factory
+     * method.
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3
+     */
+    const Cluster: ExtensibleCluster<{
+        /**
+         * Heating
+         *
+         * Thermostat is capable of managing a heating device
+         */
+        heating: BitFlag;
+        /**
+         * Cooling
+         *
+         * Thermostat is capable of managing a cooling device
+         */
+        cooling: BitFlag;
+        /**
+         * Occupancy
+         *
+         * Supports Occupied and Unoccupied setpoints
+         */
+        occupancy: BitFlag;
+        /**
+         * ScheduleConfiguration
+         *
+         * Supports remote configuration of a weekly schedule of setpoint transitions
+         */
+        scheduleConfiguration: BitFlag;
+        /**
+         * Setback
+         *
+         * Supports configurable setback (or span)
+         */
+        setback: BitFlag;
+        /**
+         * AutoMode
+         *
+         * Supports a System Mode of Auto
+         */
+        autoMode: BitFlag;
+        /**
+         * LocalTemperatureNotExposed
+         *
+         * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+         */
+        localTemperatureNotExposed: BitFlag;
+    }, TypeFromPartialBitSchema<{
+        /**
+         * Heating
+         *
+         * Thermostat is capable of managing a heating device
+         */
+        heating: BitFlag;
+        /**
+         * Cooling
+         *
+         * Thermostat is capable of managing a cooling device
+         */
+        cooling: BitFlag;
+        /**
+         * Occupancy
+         *
+         * Supports Occupied and Unoccupied setpoints
+         */
+        occupancy: BitFlag;
+        /**
+         * ScheduleConfiguration
+         *
+         * Supports remote configuration of a weekly schedule of setpoint transitions
+         */
+        scheduleConfiguration: BitFlag;
+        /**
+         * Setback
+         *
+         * Supports configurable setback (or span)
+         */
+        setback: BitFlag;
+        /**
+         * AutoMode
+         *
+         * Supports a System Mode of Auto
+         */
+        autoMode: BitFlag;
+        /**
+         * LocalTemperatureNotExposed
+         *
+         * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+         */
+        localTemperatureNotExposed: BitFlag;
+    }>, import("../../util/Type.js").Merge<{
+        /**
+         * This attribute indicates the current LocalTemperature value, when available. The value may be local, or
+         * remote, depending on the value of the RemoteSensing attribute when supported.
+         *
+         *   • If the LTNE feature is not supported:
+         *
+         *     ◦ If the temperature measurement is invalid or currently unavailable, the attribute shall report
+         *       null.
+         *
+         *     ◦ If the temperature measurement is valid, the attribute shall report that value.
+         *
+         *   • Otherwise, if the LTNE feature is supported, there is no feedback externally available for the
+         *     LocalTemperature value. In that case, the LocalTemperature attribute shall always report null.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.2
+         */
+        localTemperature: Attribute<number | null, any>;
+        /**
+         * This attribute represents the outdoor temperature, as measured locally or remotely (over the network).
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.3
+         */
+        outdoorTemperature: OptionalAttribute<number | null, any>;
+        /**
+         * This attribute indicates when the local temperature, outdoor temperature and occupancy are being sensed
+         * by remote networked sensors, rather than internal sensors.
+         *
+         * A bit set to 1 indicates remote sensing of the relevant value.
+         *
+         * Table 72. RemoteSensing Attribute Bit Values
+         *
+         * If the LTNE feature is present in the server, the LocalTemperature RemoteSensing bit value shall always
+         * report a value of 0.
+         *
+         * If the LocalTemperature RemoteSensing bit is written with a value of 1 when the LTNE feature is present,
+         * the write shall fail and the server shall report a CONSTRAINT_ERROR.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.22
+         */
+        remoteSensing: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+            /**
+             * When set, LocalTemperature Value is derived from a remote node
+             */
+            localTemperature: BitFlag;
+            /**
+             * When set, OutdoorTemperature is derived from a remote node
+             */
+            outdoorTemperature: BitFlag;
+            /**
+             * When set, Occupancy is derived from a remote node
+             */
+            occupancy: BitFlag;
+        }>, any>;
+        /**
+         * This attribute specifies the overall operating environment of the thermostat, and thus the possible
+         * system modes that the thermostat can operate in. It shall be set to one of the following values.
+         *
+         * Table 73. ControlSequenceOfOperation Values
+         *
+         * NOTE
+         *
+         * CoolingAndHeating
+         *
+         * A thermostat indicating it supports CoolingAndHeating (or CoolingAndHeatingWithReheat) SHOULD be able to
+         * request heating or cooling on demand and will usually support the Auto SystemMode.
+         *
+         * Systems which support cooling or heating, requiring external intervention to change modes or where the
+         * whole building must be in the same mode, SHOULD report CoolingOnly or HeatingOnly based on the current
+         * capability.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.23
+         */
+        controlSequenceOfOperation: WritableAttribute<ControlSequenceOfOperation, any>;
+        /**
+         * This attribute specifies the current operating mode of the thermostat, It shall be set to one of the
+         * following values, as limited by the ControlSequenceOfOperation Attribute.
+         *
+         * NOTE It is not mandatory to support all values.
+         *
+         * Table 75. Interpretation of Heat, Cool and Auto SystemMode Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.24
+         */
+        systemMode: WritableAttribute<SystemMode, any>;
+        /**
+         * This attribute specifies whether each of the alarms listed below is enabled. When the bit number
+         * corresponding to the alarm code is set to 1, the alarm is enabled, else it is disabled. Bits not
+         * corresponding to a code in the table are reserved.
+         *
+         * When the Alarms cluster is implemented on a device, and one of the alarm conditions included in this
+         * table occurs, an alarm notification is generated, with the alarm code field set as listed in the table.
+         *
+         * Table 76. Alarm Codes
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.25
+         */
+        alarmMask: OptionalAttribute<TypeFromPartialBitSchema<{
+            initializationFailure: BitFlag;
+            hardwareFailure: BitFlag;
+            selfCalibrationFailure: BitFlag;
+        }>, any>;
+        /**
+         * This attribute specifies the temperature hold status on the thermostat. If hold status is on, the
+         * thermostat SHOULD maintain the temperature set point for the current mode until a system mode change. If
+         * hold status is off, the thermostat SHOULD follow the setpoint transitions specified by its internal
+         * scheduling program. If the thermostat supports setpoint hold for a specific duration, it SHOULD also
+         * implement the TemperatureSetpointHoldDuration attribute.
+         *
+         * Table 78. TemperatureSetpointHold Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.30
+         */
+        temperatureSetpointHold: OptionalWritableAttribute<TemperatureSetpointHold, any>;
+        /**
+         * This attribute sets the period in minutes for which a setpoint hold is active. Thermostats that support
+         * hold for a specified duration SHOULD implement this attribute. The null value indicates the field is
+         * unused. All other values are reserved.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.31
+         */
+        temperatureSetpointHoldDuration: OptionalWritableAttribute<number | null, any>;
+        /**
+         * This attribute determines the operational state of the thermostat’s programming. The thermostat shall
+         * modify its programming operation when this attribute is modified by a client and update this attribute
+         * when its programming operation is modified locally by a user. The thermostat may support more than one
+         * active ThermostatProgrammingOperationMode. For example, the thermostat may operate simultaneously in
+         * Schedule Programming Mode and Recovery Mode.
+         *
+         * Thermostats which contain a schedule may use this attribute to control how that schedule is used, even
+         * if they do not support the Schedule Configuration feature.
+         *
+         * Table 79. ThermostatProgrammingOperationMode Attribute Values
+         *
+         * When ScheduleActive is not set, the setpoint is altered only by manual up/down changes at the thermostat
+         * or remotely, not by internal schedule programming.
+         *
+         * NOTE Modifying the ScheduleActive bit does not clear or delete previous weekly schedule programming
+         * configurations.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.32
+         */
+        thermostatProgrammingOperationMode: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+            /**
+             * Schedule programming mode. This enables any programmed weekly schedule configurations.
+             */
+            scheduleActive: BitFlag;
+            /**
+             * Auto/recovery mode
+             */
+            autoRecovery: BitFlag;
+            /**
+             * Economy/EnergyStar mode
+             */
+            economy: BitFlag;
+        }>, any>;
+        /**
+         * This attribute represents the current relay state of the heat, cool, and fan relays.
+         *
+         * Table 80. HVAC Relay State Values
+         *
+         * Unimplemented outputs shall be treated as if they were Off.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.33
+         */
+        thermostatRunningState: OptionalAttribute<TypeFromPartialBitSchema<{
+            /**
+             * Heat State On
+             */
+            heat: BitFlag;
+            /**
+             * Cool State On
+             */
+            cool: BitFlag;
+            /**
+             * Fan State On
+             */
+            fan: BitFlag;
+            /**
+             * Heat 2nd Stage State On
+             */
+            heatStage2: BitFlag;
+            /**
+             * Cool 2nd Stage State On
+             */
+            coolStage2: BitFlag;
+            /**
+             * Fan 2nd Stage State On
+             */
+            fanStage2: BitFlag;
+            /**
+             * Fan 3rd Stage Stage On
+             */
+            fanStage3: BitFlag;
+        }>, any>;
+        /**
+         * This attribute specifies the source of the current active OccupiedCoolingSetpoint or
+         * OccupiedHeatingSetpoint (i.e., who or what determined the current setpoint).
+         *
+         * This attribute enables service providers to determine whether changes to setpoints were initiated due to
+         * occupant comfort, scheduled programming or some other source (e.g., electric utility or other service
+         * provider). Because automation services may initiate frequent setpoint changes, this attribute clearly
+         * differentiates the source of setpoint changes made at the thermostat.
+         *
+         * Table 81. SetpointChangeSource Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.34
+         */
+        setpointChangeSource: OptionalAttribute<SetpointChangeSource, any>;
+        /**
+         * This attribute specifies the delta between the current active OccupiedCoolingSetpoint or
+         * OccupiedHeatingSetpoint and the previous active setpoint. This attribute is meant to accompany the
+         * SetpointChangeSource attribute; devices implementing SetpointChangeAmount SHOULD also implement
+         * SetpointChangeSource.
+         *
+         * The null value indicates that the previous setpoint was unknown.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.35
+         */
+        setpointChangeAmount: OptionalAttribute<number | null, any>;
+        /**
+         * This attribute specifies the time in UTC at which the SetpointChangeSourceAmount attribute change was
+         * recorded.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.36
+         */
+        setpointChangeSourceTimestamp: OptionalAttribute<number, any>;
+        /**
+         * This attribute specifies the delta between the LocalTemperature Value and the OccupiedHeatingSetpoint or
+         * UnoccupiedHeatingSetpoint attributes at which the Thermostat server will operate in emergency heat mode.
+         *
+         * If the difference between LocalTemperature Value and Un/OccupiedHeatingSetpoint is greater than or equal
+         * to the EmergencyHeatDelta and the Thermostat server’s SystemMode attribute is in a heating-related mode,
+         * then the Thermostat server shall immediately switch to the SystemMode attribute value that provides the
+         * highest stage of heating (e.g., emergency heat) and continue operating in that running state until the
+         * OccupiedHeatingSetpoint value is reached. For example:
+         *
+         *   • LocalTemperature = 10.0°C
+         *
+         *   • OccupiedHeatingSetpoint = 16.0°C
+         *
+         *   • EmergencyHeatDelta = 2.0°C
+         *
+         * ⇒ OccupiedHeatingSetpoint - LocalTemperature ≥? EmergencyHeatDelta
+         *
+         * ⇒ 16°C - 10°C ≥? 2°C
+         *
+         * ⇒ TRUE >>> Thermostat server changes its SystemMode to operate in 2nd stage or emergency heat mode
+         *
+         * The purpose of this attribute is to provide Thermostat clients the ability to configure rapid heating
+         * when a setpoint is of a specified amount greater than the measured temperature. This allows the heated
+         * space to be quickly heated to the desired level set by the user.
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.43
+         */
+        emergencyHeatDelta: OptionalWritableAttribute<number, any>;
+        /**
+         * This attribute indicates the type of Mini Split ACType of Mini Split AC is defined depending on how
+         * Cooling and Heating condition is achieved by Mini Split AC.
+         *
+         * Table 82. ACType Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.44
+         */
+        acType: OptionalWritableAttribute<AcType, any>;
+        /**
+         * This attribute indicates capacity of Mini Split AC in terms of the format defined by the
+         * ACCapacityFormat attribute
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.45
+         */
+        acCapacity: OptionalWritableAttribute<number, any>;
+        /**
+         * This attribute indicates type of refrigerant used within the Mini Split AC.
+         *
+         * Table 83. ACRefrigerantType Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.46
+         */
+        acRefrigerantType: OptionalWritableAttribute<AcRefrigerantType, any>;
+        /**
+         * This attribute indicates type of Compressor used within the Mini Split AC.
+         *
+         * Table 84. ACCompressorType Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.47
+         */
+        acCompressorType: OptionalWritableAttribute<AcCompressorType, any>;
+        /**
+         * This attribute indicates the type of errors encountered within the Mini Split AC. Error values are
+         * reported with four bytes values. Each bit within the four bytes indicates the unique error.
+         *
+         * Table 85. ACErrorCode Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.48
+         */
+        acErrorCode: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+            /**
+             * Compressor Failure or Refrigerant Leakage
+             */
+            compressorFail: BitFlag;
+            /**
+             * Room Temperature Sensor Failure
+             */
+            roomSensorFail: BitFlag;
+            /**
+             * Outdoor Temperature Sensor Failure
+             */
+            outdoorSensorFail: BitFlag;
+            /**
+             * Indoor Coil Temperature Sensor Failure
+             */
+            coilSensorFail: BitFlag;
+            /**
+             * Fan Failure
+             */
+            fanFail: BitFlag;
+        }>, any>;
+        /**
+         * This attribute indicates the position of Louver on the AC.
+         *
+         * Table 86. ACLouverPosition Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.49
+         */
+        acLouverPosition: OptionalWritableAttribute<AcLouverPosition, any>;
+        /**
+         * This attribute represents the temperature of the AC coil, as measured locally or remotely (over the
+         * network).
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.50
+         */
+        acCoilTemperature: OptionalAttribute<number | null, any>;
+        /**
+         * This attribute specifies the format for the ACCapacity attribute.
+         *
+         * Table 87. ACCapacity Values
+         *
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.51
+         */
+        acCapacityFormat: OptionalWritableAttribute<AcCapacityFormat, any>;
+    }, import("../../cluster/Cluster.js").GlobalAttributes<{
+        /**
+         * Heating
+         *
+         * Thermostat is capable of managing a heating device
+         */
+        heating: BitFlag;
+        /**
+         * Cooling
+         *
+         * Thermostat is capable of managing a cooling device
+         */
+        cooling: BitFlag;
+        /**
+         * Occupancy
+         *
+         * Supports Occupied and Unoccupied setpoints
+         */
+        occupancy: BitFlag;
+        /**
+         * ScheduleConfiguration
+         *
+         * Supports remote configuration of a weekly schedule of setpoint transitions
+         */
+        scheduleConfiguration: BitFlag;
+        /**
+         * Setback
+         *
+         * Supports configurable setback (or span)
+         */
+        setback: BitFlag;
+        /**
+         * AutoMode
+         *
+         * Supports a System Mode of Auto
+         */
+        autoMode: BitFlag;
+        /**
+         * LocalTemperatureNotExposed
+         *
+         * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+         */
+        localTemperatureNotExposed: BitFlag;
+    }>>, {
+        /**
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+         */
+        setpointRaiseLower: Command<import("../../tlv/TlvObject.js").TypeFromFields<{
+            mode: import("../../tlv/TlvObject.js").FieldType<SetpointAdjustMode>;
+            amount: import("../../tlv/TlvObject.js").FieldType<number>;
+        }>, void, any>;
+        /**
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+         */
+        getRelayStatusLog: OptionalCommand<void, void, any>;
+    }, import("../../cluster/Cluster.js").Events, <T extends ("Heating" | "Cooling" | "Occupancy" | "ScheduleConfiguration" | "Setback" | "AutoMode" | "LocalTemperatureNotExposed")[]>(...features_0: T) => Extension<BitFlags<{
+        /**
+         * Heating
+         *
+         * Thermostat is capable of managing a heating device
+         */
+        heating: BitFlag;
+        /**
+         * Cooling
+         *
+         * Thermostat is capable of managing a cooling device
+         */
+        cooling: BitFlag;
+        /**
+         * Occupancy
+         *
+         * Supports Occupied and Unoccupied setpoints
+         */
+        occupancy: BitFlag;
+        /**
+         * ScheduleConfiguration
+         *
+         * Supports remote configuration of a weekly schedule of setpoint transitions
+         */
+        scheduleConfiguration: BitFlag;
+        /**
+         * Setback
+         *
+         * Supports configurable setback (or span)
+         */
+        setback: BitFlag;
+        /**
+         * AutoMode
+         *
+         * Supports a System Mode of Auto
+         */
+        autoMode: BitFlag;
+        /**
+         * LocalTemperatureNotExposed
+         *
+         * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+         */
+        localTemperatureNotExposed: BitFlag;
+    }, T>>>;
+    type Extension<SF extends TypeFromPartialBitSchema<typeof Base.features>> = ClusterForBaseCluster<typeof Base, SF> & {
+        supportedFeatures: SF;
+    } & (SF extends {
+        occupancy: true;
+    } ? typeof OccupancyComponent : {}) & (SF extends {
+        heating: true;
+    } ? typeof HeatingComponent : {}) & (SF extends {
+        cooling: true;
+    } ? typeof CoolingComponent : {}) & (SF extends {
+        localTemperatureNotExposed: false;
+    } ? typeof NotLocalTemperatureNotExposedComponent : {}) & (SF extends {
+        cooling: true;
+        occupancy: true;
+    } ? typeof CoolingAndOccupancyComponent : {}) & (SF extends {
+        heating: true;
+        occupancy: true;
+    } ? typeof HeatingAndOccupancyComponent : {}) & (SF extends {
+        autoMode: true;
+    } ? typeof AutoModeComponent : {}) & (SF extends {
+        scheduleConfiguration: true;
+    } ? typeof ScheduleConfigurationComponent : {}) & (SF extends {
+        setback: true;
+    } ? typeof SetbackComponent : {}) & (SF extends {
+        setback: true;
+        occupancy: true;
+    } ? typeof SetbackAndOccupancyComponent : {}) & (SF extends {
+        autoMode: true;
+        heating: false;
+    } ? never : {}) & (SF extends {
+        autoMode: true;
+        cooling: false;
+    } ? never : {}) & (SF extends {
+        heating: false;
+        cooling: false;
+    } ? never : {});
+    /**
+     * This cluster supports all Thermostat 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.
+     */
+    const Complete: CreateCluster<{
+        /**
+         * Heating
+         *
+         * Thermostat is capable of managing a heating device
+         */
+        heating: BitFlag;
+        /**
+         * Cooling
+         *
+         * Thermostat is capable of managing a cooling device
+         */
+        cooling: BitFlag;
+        /**
+         * Occupancy
+         *
+         * Supports Occupied and Unoccupied setpoints
+         */
+        occupancy: BitFlag;
+        /**
+         * ScheduleConfiguration
+         *
+         * Supports remote configuration of a weekly schedule of setpoint transitions
+         */
+        scheduleConfiguration: BitFlag;
+        /**
+         * Setback
+         *
+         * Supports configurable setback (or span)
+         */
+        setback: BitFlag;
+        /**
+         * AutoMode
+         *
+         * Supports a System Mode of Auto
+         */
+        autoMode: BitFlag;
+        /**
+         * LocalTemperatureNotExposed
+         *
+         * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+         */
+        localTemperatureNotExposed: BitFlag;
+    }, TypeFromPartialBitSchema<{
+        /**
+         * Heating
+         *
+         * Thermostat is capable of managing a heating device
+         */
+        heating: BitFlag;
+        /**
+         * Cooling
+         *
+         * Thermostat is capable of managing a cooling device
+         */
+        cooling: BitFlag;
+        /**
+         * Occupancy
+         *
+         * Supports Occupied and Unoccupied setpoints
+         */
+        occupancy: BitFlag;
+        /**
+         * ScheduleConfiguration
+         *
+         * Supports remote configuration of a weekly schedule of setpoint transitions
+         */
+        scheduleConfiguration: BitFlag;
+        /**
+         * Setback
+         *
+         * Supports configurable setback (or span)
+         */
+        setback: BitFlag;
+        /**
+         * AutoMode
+         *
+         * Supports a System Mode of Auto
+         */
+        autoMode: BitFlag;
+        /**
+         * LocalTemperatureNotExposed
+         *
+         * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+         */
+        localTemperatureNotExposed: BitFlag;
+    }>, import("../../util/Type.js").Merge<{
+        occupancy: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, Attribute<TypeFromPartialBitSchema<{
+            occupied: BitFlag;
+        }>, any>>;
+        absMinHeatSetpointLimit: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, OptionalFixedAttribute<number, any>>;
+        absMaxHeatSetpointLimit: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, OptionalFixedAttribute<number, any>>;
+        absMinCoolSetpointLimit: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, OptionalFixedAttribute<number, any>>;
+        absMaxCoolSetpointLimit: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, OptionalFixedAttribute<number, any>>;
+        piCoolingDemand: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, OptionalAttribute<number, any>>;
+        piHeatingDemand: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, OptionalAttribute<number, any>>;
+        localTemperatureCalibration: AsConditional<any, OptionalWritableAttribute<number, any>>;
+        occupiedCoolingSetpoint: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, WritableAttribute<number, any>>;
+        occupiedHeatingSetpoint: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, WritableAttribute<number, any>>;
+        unoccupiedCoolingSetpoint: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, WritableAttribute<number, any>>;
+        unoccupiedHeatingSetpoint: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, WritableAttribute<number, any>>;
+        minHeatSetpointLimit: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, OptionalWritableAttribute<number, any>>;
+        maxHeatSetpointLimit: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, OptionalWritableAttribute<number, any>>;
+        minCoolSetpointLimit: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, OptionalWritableAttribute<number, any>>;
+        maxCoolSetpointLimit: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, OptionalWritableAttribute<number, any>>;
+        minSetpointDeadBand: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, WritableAttribute<number, any>>;
+        thermostatRunningMode: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, OptionalAttribute<ThermostatRunningMode, any>>;
+        startOfWeek: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, FixedAttribute<StartOfWeek, any>>;
+        numberOfWeeklyTransitions: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, FixedAttribute<number, any>>;
+        numberOfDailyTransitions: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, FixedAttribute<number, any>>;
+        occupiedSetback: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, WritableAttribute<number | null, any>>;
+        occupiedSetbackMin: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, FixedAttribute<number | null, any>>;
+        occupiedSetbackMax: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, FixedAttribute<number | null, any>>;
+        unoccupiedSetback: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, WritableAttribute<number | null, any>>;
+        unoccupiedSetbackMin: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, FixedAttribute<number | null, any>>;
+        unoccupiedSetbackMax: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, FixedAttribute<number | null, any>>;
+        localTemperature: Attribute<number | null, any>;
+        outdoorTemperature: OptionalAttribute<number | null, any>;
+        remoteSensing: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+            /**
+             * When set, LocalTemperature Value is derived from a remote node
+             */
+            localTemperature: BitFlag;
+            /**
+             * When set, OutdoorTemperature is derived from a remote node
+             */
+            outdoorTemperature: BitFlag;
+            /**
+             * When set, Occupancy is derived from a remote node
+             */
+            occupancy: BitFlag;
+        }>, any>;
+        controlSequenceOfOperation: WritableAttribute<ControlSequenceOfOperation, any>;
+        systemMode: WritableAttribute<SystemMode, any>;
+        alarmMask: OptionalAttribute<TypeFromPartialBitSchema<{
+            initializationFailure: BitFlag;
+            hardwareFailure: BitFlag;
+            selfCalibrationFailure: BitFlag;
+        }>, any>;
+        temperatureSetpointHold: OptionalWritableAttribute<TemperatureSetpointHold, any>;
+        temperatureSetpointHoldDuration: OptionalWritableAttribute<number | null, any>;
+        thermostatProgrammingOperationMode: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+            /**
+             * Schedule programming mode. This enables any programmed weekly schedule configurations.
+             */
+            scheduleActive: BitFlag;
+            /**
+             * Auto/recovery mode
+             */
+            autoRecovery: BitFlag;
+            /**
+             * Economy/EnergyStar mode
+             */
+            economy: BitFlag;
+        }>, any>;
+        thermostatRunningState: OptionalAttribute<TypeFromPartialBitSchema<{
+            /**
+             * Heat State On
+             */
+            heat: BitFlag;
+            /**
+             * Cool State On
+             */
+            cool: BitFlag;
+            /**
+             * Fan State On
+             */
+            fan: BitFlag;
+            /**
+             * Heat 2nd Stage State On
+             */
+            heatStage2: BitFlag;
+            /**
+             * Cool 2nd Stage State On
+             */
+            coolStage2: BitFlag;
+            /**
+             * Fan 2nd Stage State On
+             */
+            fanStage2: BitFlag;
+            /**
+             * Fan 3rd Stage Stage On
+             */
+            fanStage3: BitFlag;
+        }>, any>;
+        setpointChangeSource: OptionalAttribute<SetpointChangeSource, any>;
+        setpointChangeAmount: OptionalAttribute<number | null, any>;
+        setpointChangeSourceTimestamp: OptionalAttribute<number, any>;
+        emergencyHeatDelta: OptionalWritableAttribute<number, any>;
+        acType: OptionalWritableAttribute<AcType, any>;
+        acCapacity: OptionalWritableAttribute<number, any>;
+        acRefrigerantType: OptionalWritableAttribute<AcRefrigerantType, any>;
+        acCompressorType: OptionalWritableAttribute<AcCompressorType, any>;
+        acErrorCode: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+            /**
+             * Compressor Failure or Refrigerant Leakage
+             */
+            compressorFail: BitFlag;
+            /**
+             * Room Temperature Sensor Failure
+             */
+            roomSensorFail: BitFlag;
+            /**
+             * Outdoor Temperature Sensor Failure
+             */
+            outdoorSensorFail: BitFlag;
+            /**
+             * Indoor Coil Temperature Sensor Failure
+             */
+            coilSensorFail: BitFlag;
+            /**
+             * Fan Failure
+             */
+            fanFail: BitFlag;
+        }>, any>;
+        acLouverPosition: OptionalWritableAttribute<AcLouverPosition, any>;
+        acCoilTemperature: OptionalAttribute<number | null, any>;
+        acCapacityFormat: OptionalWritableAttribute<AcCapacityFormat, any>;
+        clusterRevision: Attribute<number, never>;
+        featureMap: Attribute<TypeFromPartialBitSchema<{
+            /**
+             * Heating
+             *
+             * Thermostat is capable of managing a heating device
+             */
+            heating: BitFlag;
+            /**
+             * Cooling
+             *
+             * Thermostat is capable of managing a cooling device
+             */
+            cooling: BitFlag;
+            /**
+             * Occupancy
+             *
+             * Supports Occupied and Unoccupied setpoints
+             */
+            occupancy: BitFlag;
+            /**
+             * ScheduleConfiguration
+             *
+             * Supports remote configuration of a weekly schedule of setpoint transitions
+             */
+            scheduleConfiguration: BitFlag;
+            /**
+             * Setback
+             *
+             * Supports configurable setback (or span)
+             */
+            setback: BitFlag;
+            /**
+             * AutoMode
+             *
+             * Supports a System Mode of Auto
+             */
+            autoMode: BitFlag;
+            /**
+             * LocalTemperatureNotExposed
+             *
+             * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+             */
+            localTemperatureNotExposed: BitFlag;
+        }>, never>;
+        attributeList: Attribute<import("../../datatype/AttributeId.js").AttributeId[], never>;
+        eventList: Attribute<import("../../datatype/EventId.js").EventId[], never>;
+        acceptedCommandList: Attribute<import("../../datatype/CommandId.js").CommandId[], never>;
+        generatedCommandList: Attribute<import("../../datatype/CommandId.js").CommandId[], never>;
+    }, import("../../cluster/Cluster.js").GlobalAttributes<{
+        /**
+         * Heating
+         *
+         * Thermostat is capable of managing a heating device
+         */
+        heating: BitFlag;
+        /**
+         * Cooling
+         *
+         * Thermostat is capable of managing a cooling device
+         */
+        cooling: BitFlag;
+        /**
+         * Occupancy
+         *
+         * Supports Occupied and Unoccupied setpoints
+         */
+        occupancy: BitFlag;
+        /**
+         * ScheduleConfiguration
+         *
+         * Supports remote configuration of a weekly schedule of setpoint transitions
+         */
+        scheduleConfiguration: BitFlag;
+        /**
+         * Setback
+         *
+         * Supports configurable setback (or span)
+         */
+        setback: BitFlag;
+        /**
+         * AutoMode
+         *
+         * Supports a System Mode of Auto
+         */
+        autoMode: BitFlag;
+        /**
+         * LocalTemperatureNotExposed
+         *
+         * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+         */
+        localTemperatureNotExposed: BitFlag;
+    }>>, {
+        setWeeklySchedule: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, Command<import("../../tlv/TlvObject.js").TypeFromFields<{
+            numberOfTransitionsForSequence: import("../../tlv/TlvObject.js").FieldType<number>;
+            dayOfWeekForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                sunday: BitFlag;
+                monday: BitFlag;
+                tuesday: BitFlag;
+                wednesday: BitFlag;
+                thursday: BitFlag;
+                friday: BitFlag;
+                saturday: BitFlag;
+                away: BitFlag;
+            }>>;
+            modeForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                heatSetpointPresent: BitFlag;
+                coolSetpointPresent: BitFlag;
+            }>>;
+            transitions: import("../../tlv/TlvObject.js").FieldType<import("../../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field represents the start time of the schedule transition during the associated day. The time will be
+                 * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
+                 * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
+                 *
+                 * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.9.5.1
+                 */
+                transitionTime: import("../../tlv/TlvObject.js").FieldType<number>;
+                heatSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+                coolSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+            }>[]>;
+        }>, void, any>>;
+        getWeeklySchedule: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, Command<import("../../tlv/TlvObject.js").TypeFromFields<{
+            daysToReturn: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                sunday: BitFlag;
+                monday: BitFlag;
+                tuesday: BitFlag;
+                wednesday: BitFlag;
+                thursday: BitFlag;
+                friday: BitFlag;
+                saturday: BitFlag;
+                away: BitFlag;
+            }>>;
+            modeToReturn: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                heatSetpointPresent: BitFlag;
+                coolSetpointPresent: BitFlag;
+            }>>;
+        }>, import("../../tlv/TlvObject.js").TypeFromFields<{
+            numberOfTransitionsForSequence: import("../../tlv/TlvObject.js").FieldType<number>;
+            dayOfWeekForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                sunday: BitFlag;
+                monday: BitFlag;
+                tuesday: BitFlag;
+                wednesday: BitFlag;
+                thursday: BitFlag;
+                friday: BitFlag;
+                saturday: BitFlag;
+                away: BitFlag;
+            }>>;
+            modeForSequence: import("../../tlv/TlvObject.js").FieldType<TypeFromPartialBitSchema<{
+                heatSetpointPresent: BitFlag;
+                coolSetpointPresent: BitFlag;
+            }>>;
+            transitions: import("../../tlv/TlvObject.js").FieldType<import("../../tlv/TlvObject.js").TypeFromFields<{
+                /**
+                 * This field represents the start time of the schedule transition during the associated day. The time will be
+                 * represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be
+                 * represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.
+                 *
+                 * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.9.5.1
+                 */
+                transitionTime: import("../../tlv/TlvObject.js").FieldType<number>;
+                heatSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+                coolSetpoint: import("../../tlv/TlvObject.js").FieldType<number | null>;
+            }>[]>;
+        }>, any>>;
+        clearWeeklySchedule: AsConditional<import("../../schema/BitmapSchema.js").BitSchema, Command<void, void, any>>;
+        /**
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+         */
+        setpointRaiseLower: Command<import("../../tlv/TlvObject.js").TypeFromFields<{
+            mode: import("../../tlv/TlvObject.js").FieldType<SetpointAdjustMode>;
+            amount: import("../../tlv/TlvObject.js").FieldType<number>;
+        }>, void, any>;
+        /**
+         * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+         */
+        getRelayStatusLog: OptionalCommand<void, void, any>;
+    }, {}>;
+}
+export type ThermostatCluster = typeof Thermostat.Cluster;
+export declare const ThermostatCluster: ExtensibleCluster<{
+    /**
+     * Heating
+     *
+     * Thermostat is capable of managing a heating device
+     */
+    heating: BitFlag;
+    /**
+     * Cooling
+     *
+     * Thermostat is capable of managing a cooling device
+     */
+    cooling: BitFlag;
+    /**
+     * Occupancy
+     *
+     * Supports Occupied and Unoccupied setpoints
+     */
+    occupancy: BitFlag;
+    /**
+     * ScheduleConfiguration
+     *
+     * Supports remote configuration of a weekly schedule of setpoint transitions
+     */
+    scheduleConfiguration: BitFlag;
+    /**
+     * Setback
+     *
+     * Supports configurable setback (or span)
+     */
+    setback: BitFlag;
+    /**
+     * AutoMode
+     *
+     * Supports a System Mode of Auto
+     */
+    autoMode: BitFlag;
+    /**
+     * LocalTemperatureNotExposed
+     *
+     * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+     */
+    localTemperatureNotExposed: BitFlag;
+}, TypeFromPartialBitSchema<{
+    /**
+     * Heating
+     *
+     * Thermostat is capable of managing a heating device
+     */
+    heating: BitFlag;
+    /**
+     * Cooling
+     *
+     * Thermostat is capable of managing a cooling device
+     */
+    cooling: BitFlag;
+    /**
+     * Occupancy
+     *
+     * Supports Occupied and Unoccupied setpoints
+     */
+    occupancy: BitFlag;
+    /**
+     * ScheduleConfiguration
+     *
+     * Supports remote configuration of a weekly schedule of setpoint transitions
+     */
+    scheduleConfiguration: BitFlag;
+    /**
+     * Setback
+     *
+     * Supports configurable setback (or span)
+     */
+    setback: BitFlag;
+    /**
+     * AutoMode
+     *
+     * Supports a System Mode of Auto
+     */
+    autoMode: BitFlag;
+    /**
+     * LocalTemperatureNotExposed
+     *
+     * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+     */
+    localTemperatureNotExposed: BitFlag;
+}>, import("../../util/Type.js").Merge<{
+    /**
+     * This attribute indicates the current LocalTemperature value, when available. The value may be local, or
+     * remote, depending on the value of the RemoteSensing attribute when supported.
+     *
+     *   • If the LTNE feature is not supported:
+     *
+     *     ◦ If the temperature measurement is invalid or currently unavailable, the attribute shall report
+     *       null.
+     *
+     *     ◦ If the temperature measurement is valid, the attribute shall report that value.
+     *
+     *   • Otherwise, if the LTNE feature is supported, there is no feedback externally available for the
+     *     LocalTemperature value. In that case, the LocalTemperature attribute shall always report null.
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.2
+     */
+    localTemperature: Attribute<number | null, any>;
+    /**
+     * This attribute represents the outdoor temperature, as measured locally or remotely (over the network).
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.3
+     */
+    outdoorTemperature: OptionalAttribute<number | null, any>;
+    /**
+     * This attribute indicates when the local temperature, outdoor temperature and occupancy are being sensed
+     * by remote networked sensors, rather than internal sensors.
+     *
+     * A bit set to 1 indicates remote sensing of the relevant value.
+     *
+     * Table 72. RemoteSensing Attribute Bit Values
+     *
+     * If the LTNE feature is present in the server, the LocalTemperature RemoteSensing bit value shall always
+     * report a value of 0.
+     *
+     * If the LocalTemperature RemoteSensing bit is written with a value of 1 when the LTNE feature is present,
+     * the write shall fail and the server shall report a CONSTRAINT_ERROR.
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.22
+     */
+    remoteSensing: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+        /**
+         * When set, LocalTemperature Value is derived from a remote node
+         */
+        localTemperature: BitFlag;
+        /**
+         * When set, OutdoorTemperature is derived from a remote node
+         */
+        outdoorTemperature: BitFlag;
+        /**
+         * When set, Occupancy is derived from a remote node
+         */
+        occupancy: BitFlag;
+    }>, any>;
+    /**
+     * This attribute specifies the overall operating environment of the thermostat, and thus the possible
+     * system modes that the thermostat can operate in. It shall be set to one of the following values.
+     *
+     * Table 73. ControlSequenceOfOperation Values
+     *
+     * NOTE
+     *
+     * CoolingAndHeating
+     *
+     * A thermostat indicating it supports CoolingAndHeating (or CoolingAndHeatingWithReheat) SHOULD be able to
+     * request heating or cooling on demand and will usually support the Auto SystemMode.
+     *
+     * Systems which support cooling or heating, requiring external intervention to change modes or where the
+     * whole building must be in the same mode, SHOULD report CoolingOnly or HeatingOnly based on the current
+     * capability.
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.23
+     */
+    controlSequenceOfOperation: WritableAttribute<Thermostat.ControlSequenceOfOperation, any>;
+    /**
+     * This attribute specifies the current operating mode of the thermostat, It shall be set to one of the
+     * following values, as limited by the ControlSequenceOfOperation Attribute.
+     *
+     * NOTE It is not mandatory to support all values.
+     *
+     * Table 75. Interpretation of Heat, Cool and Auto SystemMode Values
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.24
+     */
+    systemMode: WritableAttribute<Thermostat.SystemMode, any>;
+    /**
+     * This attribute specifies whether each of the alarms listed below is enabled. When the bit number
+     * corresponding to the alarm code is set to 1, the alarm is enabled, else it is disabled. Bits not
+     * corresponding to a code in the table are reserved.
+     *
+     * When the Alarms cluster is implemented on a device, and one of the alarm conditions included in this
+     * table occurs, an alarm notification is generated, with the alarm code field set as listed in the table.
+     *
+     * Table 76. Alarm Codes
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.25
+     */
+    alarmMask: OptionalAttribute<TypeFromPartialBitSchema<{
+        initializationFailure: BitFlag;
+        hardwareFailure: BitFlag;
+        selfCalibrationFailure: BitFlag;
+    }>, any>;
+    /**
+     * This attribute specifies the temperature hold status on the thermostat. If hold status is on, the
+     * thermostat SHOULD maintain the temperature set point for the current mode until a system mode change. If
+     * hold status is off, the thermostat SHOULD follow the setpoint transitions specified by its internal
+     * scheduling program. If the thermostat supports setpoint hold for a specific duration, it SHOULD also
+     * implement the TemperatureSetpointHoldDuration attribute.
+     *
+     * Table 78. TemperatureSetpointHold Values
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.30
+     */
+    temperatureSetpointHold: OptionalWritableAttribute<Thermostat.TemperatureSetpointHold, any>;
+    /**
+     * This attribute sets the period in minutes for which a setpoint hold is active. Thermostats that support
+     * hold for a specified duration SHOULD implement this attribute. The null value indicates the field is
+     * unused. All other values are reserved.
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.31
+     */
+    temperatureSetpointHoldDuration: OptionalWritableAttribute<number | null, any>;
+    /**
+     * This attribute determines the operational state of the thermostat’s programming. The thermostat shall
+     * modify its programming operation when this attribute is modified by a client and update this attribute
+     * when its programming operation is modified locally by a user. The thermostat may support more than one
+     * active ThermostatProgrammingOperationMode. For example, the thermostat may operate simultaneously in
+     * Schedule Programming Mode and Recovery Mode.
+     *
+     * Thermostats which contain a schedule may use this attribute to control how that schedule is used, even
+     * if they do not support the Schedule Configuration feature.
+     *
+     * Table 79. ThermostatProgrammingOperationMode Attribute Values
+     *
+     * When ScheduleActive is not set, the setpoint is altered only by manual up/down changes at the thermostat
+     * or remotely, not by internal schedule programming.
+     *
+     * NOTE Modifying the ScheduleActive bit does not clear or delete previous weekly schedule programming
+     * configurations.
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.32
+     */
+    thermostatProgrammingOperationMode: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+        /**
+         * Schedule programming mode. This enables any programmed weekly schedule configurations.
+         */
+        scheduleActive: BitFlag;
+        /**
+         * Auto/recovery mode
+         */
+        autoRecovery: BitFlag;
+        /**
+         * Economy/EnergyStar mode
+         */
+        economy: BitFlag;
+    }>, any>;
+    /**
+     * This attribute represents the current relay state of the heat, cool, and fan relays.
+     *
+     * Table 80. HVAC Relay State Values
+     *
+     * Unimplemented outputs shall be treated as if they were Off.
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.33
+     */
+    thermostatRunningState: OptionalAttribute<TypeFromPartialBitSchema<{
+        /**
+         * Heat State On
+         */
+        heat: BitFlag;
+        /**
+         * Cool State On
+         */
+        cool: BitFlag;
+        /**
+         * Fan State On
+         */
+        fan: BitFlag;
+        /**
+         * Heat 2nd Stage State On
+         */
+        heatStage2: BitFlag;
+        /**
+         * Cool 2nd Stage State On
+         */
+        coolStage2: BitFlag;
+        /**
+         * Fan 2nd Stage State On
+         */
+        fanStage2: BitFlag;
+        /**
+         * Fan 3rd Stage Stage On
+         */
+        fanStage3: BitFlag;
+    }>, any>;
+    /**
+     * This attribute specifies the source of the current active OccupiedCoolingSetpoint or
+     * OccupiedHeatingSetpoint (i.e., who or what determined the current setpoint).
+     *
+     * This attribute enables service providers to determine whether changes to setpoints were initiated due to
+     * occupant comfort, scheduled programming or some other source (e.g., electric utility or other service
+     * provider). Because automation services may initiate frequent setpoint changes, this attribute clearly
+     * differentiates the source of setpoint changes made at the thermostat.
+     *
+     * Table 81. SetpointChangeSource Values
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.34
+     */
+    setpointChangeSource: OptionalAttribute<Thermostat.SetpointChangeSource, any>;
+    /**
+     * This attribute specifies the delta between the current active OccupiedCoolingSetpoint or
+     * OccupiedHeatingSetpoint and the previous active setpoint. This attribute is meant to accompany the
+     * SetpointChangeSource attribute; devices implementing SetpointChangeAmount SHOULD also implement
+     * SetpointChangeSource.
+     *
+     * The null value indicates that the previous setpoint was unknown.
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.35
+     */
+    setpointChangeAmount: OptionalAttribute<number | null, any>;
+    /**
+     * This attribute specifies the time in UTC at which the SetpointChangeSourceAmount attribute change was
+     * recorded.
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.36
+     */
+    setpointChangeSourceTimestamp: OptionalAttribute<number, any>;
+    /**
+     * This attribute specifies the delta between the LocalTemperature Value and the OccupiedHeatingSetpoint or
+     * UnoccupiedHeatingSetpoint attributes at which the Thermostat server will operate in emergency heat mode.
+     *
+     * If the difference between LocalTemperature Value and Un/OccupiedHeatingSetpoint is greater than or equal
+     * to the EmergencyHeatDelta and the Thermostat server’s SystemMode attribute is in a heating-related mode,
+     * then the Thermostat server shall immediately switch to the SystemMode attribute value that provides the
+     * highest stage of heating (e.g., emergency heat) and continue operating in that running state until the
+     * OccupiedHeatingSetpoint value is reached. For example:
+     *
+     *   • LocalTemperature = 10.0°C
+     *
+     *   • OccupiedHeatingSetpoint = 16.0°C
+     *
+     *   • EmergencyHeatDelta = 2.0°C
+     *
+     * ⇒ OccupiedHeatingSetpoint - LocalTemperature ≥? EmergencyHeatDelta
+     *
+     * ⇒ 16°C - 10°C ≥? 2°C
+     *
+     * ⇒ TRUE >>> Thermostat server changes its SystemMode to operate in 2nd stage or emergency heat mode
+     *
+     * The purpose of this attribute is to provide Thermostat clients the ability to configure rapid heating
+     * when a setpoint is of a specified amount greater than the measured temperature. This allows the heated
+     * space to be quickly heated to the desired level set by the user.
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.43
+     */
+    emergencyHeatDelta: OptionalWritableAttribute<number, any>;
+    /**
+     * This attribute indicates the type of Mini Split ACType of Mini Split AC is defined depending on how
+     * Cooling and Heating condition is achieved by Mini Split AC.
+     *
+     * Table 82. ACType Values
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.44
+     */
+    acType: OptionalWritableAttribute<Thermostat.AcType, any>;
+    /**
+     * This attribute indicates capacity of Mini Split AC in terms of the format defined by the
+     * ACCapacityFormat attribute
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.45
+     */
+    acCapacity: OptionalWritableAttribute<number, any>;
+    /**
+     * This attribute indicates type of refrigerant used within the Mini Split AC.
+     *
+     * Table 83. ACRefrigerantType Values
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.46
+     */
+    acRefrigerantType: OptionalWritableAttribute<Thermostat.AcRefrigerantType, any>;
+    /**
+     * This attribute indicates type of Compressor used within the Mini Split AC.
+     *
+     * Table 84. ACCompressorType Values
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.47
+     */
+    acCompressorType: OptionalWritableAttribute<Thermostat.AcCompressorType, any>;
+    /**
+     * This attribute indicates the type of errors encountered within the Mini Split AC. Error values are
+     * reported with four bytes values. Each bit within the four bytes indicates the unique error.
+     *
+     * Table 85. ACErrorCode Values
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.48
+     */
+    acErrorCode: OptionalWritableAttribute<TypeFromPartialBitSchema<{
+        /**
+         * Compressor Failure or Refrigerant Leakage
+         */
+        compressorFail: BitFlag;
+        /**
+         * Room Temperature Sensor Failure
+         */
+        roomSensorFail: BitFlag;
+        /**
+         * Outdoor Temperature Sensor Failure
+         */
+        outdoorSensorFail: BitFlag;
+        /**
+         * Indoor Coil Temperature Sensor Failure
+         */
+        coilSensorFail: BitFlag;
+        /**
+         * Fan Failure
+         */
+        fanFail: BitFlag;
+    }>, any>;
+    /**
+     * This attribute indicates the position of Louver on the AC.
+     *
+     * Table 86. ACLouverPosition Values
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.49
+     */
+    acLouverPosition: OptionalWritableAttribute<Thermostat.AcLouverPosition, any>;
+    /**
+     * This attribute represents the temperature of the AC coil, as measured locally or remotely (over the
+     * network).
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.50
+     */
+    acCoilTemperature: OptionalAttribute<number | null, any>;
+    /**
+     * This attribute specifies the format for the ACCapacity attribute.
+     *
+     * Table 87. ACCapacity Values
+     *
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.7.51
+     */
+    acCapacityFormat: OptionalWritableAttribute<Thermostat.AcCapacityFormat, any>;
+}, import("../../cluster/Cluster.js").GlobalAttributes<{
+    /**
+     * Heating
+     *
+     * Thermostat is capable of managing a heating device
+     */
+    heating: BitFlag;
+    /**
+     * Cooling
+     *
+     * Thermostat is capable of managing a cooling device
+     */
+    cooling: BitFlag;
+    /**
+     * Occupancy
+     *
+     * Supports Occupied and Unoccupied setpoints
+     */
+    occupancy: BitFlag;
+    /**
+     * ScheduleConfiguration
+     *
+     * Supports remote configuration of a weekly schedule of setpoint transitions
+     */
+    scheduleConfiguration: BitFlag;
+    /**
+     * Setback
+     *
+     * Supports configurable setback (or span)
+     */
+    setback: BitFlag;
+    /**
+     * AutoMode
+     *
+     * Supports a System Mode of Auto
+     */
+    autoMode: BitFlag;
+    /**
+     * LocalTemperatureNotExposed
+     *
+     * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+     */
+    localTemperatureNotExposed: BitFlag;
+}>>, {
+    /**
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+     */
+    setpointRaiseLower: Command<import("../../tlv/TlvObject.js").TypeFromFields<{
+        mode: import("../../tlv/TlvObject.js").FieldType<Thermostat.SetpointAdjustMode>;
+        amount: import("../../tlv/TlvObject.js").FieldType<number>;
+    }>, void, any>;
+    /**
+     * @see {@link MatterApplicationClusterSpecificationV1_1} § 4.3.8
+     */
+    getRelayStatusLog: OptionalCommand<void, void, any>;
+}, import("../../cluster/Cluster.js").Events, <T extends ("Heating" | "Cooling" | "Occupancy" | "ScheduleConfiguration" | "Setback" | "AutoMode" | "LocalTemperatureNotExposed")[]>(...features_0: T) => Thermostat.Extension<BitFlags<{
+    /**
+     * Heating
+     *
+     * Thermostat is capable of managing a heating device
+     */
+    heating: BitFlag;
+    /**
+     * Cooling
+     *
+     * Thermostat is capable of managing a cooling device
+     */
+    cooling: BitFlag;
+    /**
+     * Occupancy
+     *
+     * Supports Occupied and Unoccupied setpoints
+     */
+    occupancy: BitFlag;
+    /**
+     * ScheduleConfiguration
+     *
+     * Supports remote configuration of a weekly schedule of setpoint transitions
+     */
+    scheduleConfiguration: BitFlag;
+    /**
+     * Setback
+     *
+     * Supports configurable setback (or span)
+     */
+    setback: BitFlag;
+    /**
+     * AutoMode
+     *
+     * Supports a System Mode of Auto
+     */
+    autoMode: BitFlag;
+    /**
+     * LocalTemperatureNotExposed
+     *
+     * Thermostat does not expose the LocalTemperature Value in the LocalTemperature attribute
+     */
+    localTemperatureNotExposed: BitFlag;
+}, T>>>;
+//# sourceMappingURL=ThermostatCluster.d.ts.map