Readonly
absReadonly
absReadonly
absReadonly
absReadonly
acIndicates capacity of Mini Split AC in terms of the format defined by the ACCapacityFormat attribute
Readonly
acIndicates the format for the ACCapacity attribute.
Readonly
acIndicates the temperature of the AC coil, as measured locally or remotely (over the network).
Readonly
acIndicates the type of compressor used within the Mini Split AC.
Readonly
acIndicates the type of errors encountered within the Mini Split AC.
Readonly
acIndicates the position of Louver on the AC.
Readonly
acIndicates type of refrigerant used within the Mini Split AC.
Readonly
acIndicates the type of Mini Split ACTypeEnum of Mini Split AC is defined depending on how Cooling and Heating condition is achieved by Mini Split AC.
Readonly
controlIndicates the overall operating environment of the thermostat, and thus the possible system modes that the thermostat can operate in.
Readonly
emergencyIndicates the delta between the Calculated Local Temperature and the OccupiedHeatingSetpoint or UnoccupiedHeatingSetpoint attributes at which the Thermostat server will operate in emergency heat mode.
If the difference between the Calculated Local Temperature and OccupiedCoolingSetpoint or UnoccupiedCoolingSetpoint 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:
• Calculated Local Temperature = 10.0°C
• OccupiedHeatingSetpoint = 16.0°C
• EmergencyHeatDelta = 2.0°C
⇒ OccupiedHeatingSetpoint - Calculated Local Temperature ≥? 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.
Readonly
localIndicates the current Calculated Local Temperature, when available.
• If the LTNE feature is not supported:
◦ If the LocalTemperatureCalibration is invalid or currently unavailable, the attribute shall report
null.
◦ If the LocalTemperatureCalibration is valid, the attribute shall report that value.
• Otherwise, if the LTNE feature is supported, there is no feedback externally available for the LocalTemperatureCalibration. In that case, the LocalTemperature attribute shall always report null.
Readonly
localReadonly
maxReadonly
maxReadonly
minReadonly
minReadonly
minReadonly
numberReadonly
numberReadonly
occupancy: Attribute<TypeFromPartialBitSchema<{ Readonly
occupiedReadonly
occupiedReadonly
occupiedReadonly
occupiedReadonly
occupiedReadonly
outdoorIndicates the outdoor temperature, as measured locally or remotely (over the network).
Readonly
piReadonly
piReadonly
remoteIndicates when the local temperature, outdoor temperature and occupancy are being sensed by remote networked sensors, rather than internal sensors.
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.
Readonly
setpointIndicates 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.
Readonly
setpointIndicates 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.
Readonly
setpointIndicates the time in UTC at which the SetpointChangeAmount attribute change was recorded.
Readonly
startReadonly
systemIndicates the current operating mode of the thermostat. Its value shall be limited by the ControlSequenceOfOperation attribute.
Readonly
temperatureIndicates the temperature hold status on the thermostat. If hold status is on, the thermostat SHOULD maintain the temperature setpoint 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.
Readonly
temperatureIndicates 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.
Readonly
thermostatIndicates 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 ProgrammingOperationModeBitmap. 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 ScheduleConfiguration feature.
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.
Readonly
thermostatReadonly
thermostatIndicates the current relay state of the heat, cool, and fan relays. Unimplemented outputs shall be treated as if they were Off.
Readonly
unoccupiedReadonly
unoccupiedReadonly
unoccupiedReadonly
unoccupiedReadonly
unoccupiedReadonly
clearReadonly
getReadonly
setpointUpon receipt, the attributes for the indicated setpoint(s) shall have the amount specified in the Amount field added to them. If the resulting value is outside the limits imposed by MinCoolSetpointLimit, MaxCoolSetpointLimit, MinHeatSetpointLimit and MaxHeatSetpointLimit, the value is clamped to those limits. This is not considered an error condition.
Readonly
setReadonly
autoAutoMode
Supports a System Mode of Auto
Readonly
cooling: BitFlagCooling
Thermostat is capable of managing a cooling device
Readonly
heating: BitFlagHeating
Thermostat is capable of managing a heating device
Readonly
localLocalTemperatureNotExposed
This feature indicates that the Calculated Local Temperature used internally is unavailable to report externally, for example due to the temperature control being done by a separate subsystem which does not offer a view into the currently measured temperature, but allows setpoints to be provided.
Readonly
occupancy: BitFlagOccupancy
Supports Occupied and Unoccupied setpoints
Readonly
scheduleScheduleConfiguration
Supports remote configuration of a weekly schedule of setpoint transitions
Readonly
setback: BitFlagSetback
Supports configurable setback (or span)
Modify elements using ElementModifier.alter.
Modify elements using ElementModifier.enable.
Modify elements using ElementModifier.set.
Select features using ClusterComposer.compose.
Rest
...selection: SelectionT
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.