Matter Cluster 513 — Thermostat Cluster

Cluster Identity

Revision history

Shadow Path Format

Cluster 513 values in the device shadow use this format:

endpoint_id / 513 / attribute_id

Example:

{
  "1/513/0": 1
}

Cluster 513 Features

The FeatureMap attribute (1/513/65532) is a bitmap. Each bit set means the device implements that feature and the attributes and commands that depend on it.

Example: FeatureMap = 0 means no optional feature is enabled; 2039 means every feature listed above is enabled.

Data Types

ACCapacityFormatEnum

ACCompressorTypeEnum

ACLouverPositionEnum

ACRefrigerantTypeEnum

ACTypeEnum

ControlSequenceOfOperationEnum

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.

PresetScenarioEnum

SetpointChangeSourceEnum

SetpointRaiseLowerModeEnum

StartOfWeekEnum

SystemModeEnum

TemperatureSetpointHoldEnum

ThermostatRunningModeEnum

ACErrorCodeBitmap (bitmap)

OccupancyBitmap (bitmap)

PresetTypeFeaturesBitmap (bitmap)

RelayStateBitmap (bitmap)

RemoteSensingBitmap (bitmap)

ScheduleDayOfWeekBitmap (bitmap)

ScheduleModeBitmap (bitmap)

ScheduleTypeFeaturesBitmap (bitmap)

ThermostatSuggestionNotFollowingReasonBitmap (bitmap)

PresetStruct (struct)

PresetTypeStruct (struct)

ScheduleStruct (struct)

ScheduleTransitionStruct (struct)

This struct provides a time of day and a set of days of the week for a state transition within a schedule. The thermostat must use the following order of precedence for determining a new setpoint at the time of transition: 1.

ScheduleTypeStruct (struct)

ThermostatSuggestionStruct (struct)

WeeklyScheduleTransitionStruct (struct)

This represents a single transition in a Thermostat schedule

Cluster 513 Attributes

Cluster 513 defines 61 attributes plus the global attributes. Conformance: M mandatory, O optional, a feature code means "mandatory when that feature is present", square brackets mean "optional when …".

Global attributes

Attribute Details

Attribute 0 / 0x0000 — LocalTemperature

Path example:

1/513/0

Indicates the current Calculated Local Temperature, when available. - If the LTNE feature is not supported: - If the LocalTemperatureCalibration is invalid or currently unavailable, the attribute must report null. - If the LocalTemperatureCalibration is valid, the attribute must 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 must always report null.

Example:

{
  "1/513/0": 1
}

Attribute 1 / 0x0001 — OutdoorTemperature

Path example:

1/513/1

Indicates the outdoor temperature, as measured locally or remotely (over the network).

Example:

{
  "1/513/1": 1
}

Attribute 2 / 0x0002 — Occupancy

Path example:

1/513/2

Indicates whether the heated/cooled space is occupied or not, as measured locally or remotely (over the network).

Bits (OccupancyBitmap):

Example:

{
  "1/513/2": 0
}

Attribute 3 / 0x0003 — AbsMinHeatSetpointLimit

Path example:

1/513/3

Indicates 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

Example:

{
  "1/513/3": 1
}

Attribute 4 / 0x0004 — AbsMaxHeatSetpointLimit

Path example:

1/513/4

Indicates 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

Example:

{
  "1/513/4": 1
}

Attribute 5 / 0x0005 — AbsMinCoolSetpointLimit

Path example:

1/513/5

Indicates 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

Example:

{
  "1/513/5": 1
}

Attribute 6 / 0x0006 — AbsMaxCoolSetpointLimit

Path example:

1/513/6

Indicates 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

Example:

{
  "1/513/6": 1
}

Attribute 7 / 0x0007 — PICoolingDemand

Path example:

1/513/7

No condensed specification text is available for PICoolingDemand; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/7": 0
}

Attribute 8 / 0x0008 — PIHeatingDemand

Path example:

1/513/8

No condensed specification text is available for PIHeatingDemand; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/8": 0
}

Attribute 9 / 0x0009 — HVACSystemTypeConfiguration

Path example:

1/513/9

No condensed specification text is available for HVACSystemTypeConfiguration; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/9": 0
}

Attribute 16 / 0x0010 — LocalTemperatureCalibration

Path example:

1/513/16

Indicates the offset the Thermostat server must make to the measured temperature (locally or remotely) to adjust the Calculated Local Temperature 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.

Example:

{
  "1/513/16": 0
}

Attribute 17 / 0x0011 — OccupiedCoolingSetpoint

Path example:

1/513/17

Indicates the cooling mode setpoint when the room is occupied. Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute to a value greater than MaxCoolSetpointLimit or less than MinCoolSetpointLimit, a response with the status code CONSTRAINT_ERROR is returned. If this attribute is set to a value that is less than (OccupiedHeatingSetpoint + MinSetpointDeadBand), the value of OccupiedHeatingSetpoint is adjusted to (OccupiedCoolingSetpoint - MinSetpointDeadBand).

Example:

{
  "1/513/17": 1
}

Attribute 18 / 0x0012 — OccupiedHeatingSetpoint

Path example:

1/513/18

Indicates the heating mode setpoint when the room is occupied. Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute to a value greater than MaxHeatSetpointLimit or less than MinHeatSetpointLimit, a response with the status code CONSTRAINT_ERROR is returned. If this attribute is set to a value that is greater than (OccupiedCoolingSetpoint - MinSetpointDeadBand), the value of OccupiedCoolingSetpoint is adjusted to (OccupiedHeatingSetpoint + MinSetpointDeadBand).

Example:

{
  "1/513/18": 1
}

Attribute 19 / 0x0013 — UnoccupiedCoolingSetpoint

Path example:

1/513/19

Indicates the cooling mode setpoint when the room is unoccupied. Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute to a value greater than MaxCoolSetpointLimit or less than MinCoolSetpointLimit, a response with the status code CONSTRAINT_ERROR is returned. If this attribute is set to a value that is less than (UnoccupiedHeatingSetpoint + MinSetpointDeadBand), the value of UnoccupiedHeatingSetpoint is adjusted to (UnoccupiedCoolingSetpoint - MinSetpointDeadBand).

Example:

{
  "1/513/19": 1
}

Attribute 20 / 0x0014 — UnoccupiedHeatingSetpoint

Path example:

1/513/20

Indicates the heating mode setpoint when the room is unoccupied. Refer to Setpoint Limits for constraints. If an attempt is made to set this attribute to a value greater than MaxHeatSetpointLimit or less than MinHeatSetpointLimit, a response with the status code CONSTRAINT_ERROR is returned. If this attribute is set to a value that is greater than (UnoccupiedCoolingSetpoint - MinSetpointDeadBand), the value of UnoccupiedCoolingSetpoint is adjusted to (UnoccupiedHeatingSetpoint + MinSetpointDeadBand).

Example:

{
  "1/513/20": 1
}

Attribute 21 / 0x0015 — MinHeatSetpointLimit

Path example:

1/513/21

Indicates 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.

Example:

{
  "1/513/21": 1
}

Attribute 22 / 0x0016 — MaxHeatSetpointLimit

Path example:

1/513/22

Indicates 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 is 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 is returned.

Example:

{
  "1/513/22": 1
}

Attribute 23 / 0x0017 — MinCoolSetpointLimit

Path example:

1/513/23

Indicates 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 is 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 is returned.

Example:

{
  "1/513/23": 1
}

Attribute 24 / 0x0018 — MaxCoolSetpointLimit

Path example:

1/513/24

Indicates 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 is 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 is returned.

Example:

{
  "1/513/24": 1
}

Attribute 25 / 0x0019 — MinSetpointDeadBand

Path example:

1/513/25

On devices which support the AUTO feature, this attribute indicates the minimum difference between the Heat Setpoint and the Cool Setpoint. Refer to Setpoint Limits for constraints. Prior to revision 8 of this cluster specification the value of this attribute was constrained to a range of 0°C to 2.5°C. For backwards compatibility, this attribute is optionally writeable.

Example:

{
  "1/513/25": 0
}

Attribute 26 / 0x001A — RemoteSensing

Path example:

1/513/26

Indicates 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 must 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 must fail and the server must report a CONSTRAINT_ERROR.

Bits (RemoteSensingBitmap):

Example:

{
  "1/513/26": 0
}

Attribute 27 / 0x001B — ControlSequenceOfOperation

Path example:

1/513/27

Indicates the overall operating environment of the thermostat, and thus the possible system modes that the thermostat can operate in. If an attempt is made to write to this attribute, the server must silently ignore the write and the value of this attribute must remain unchanged. This behavior is in place for backwards compatibility with existing thermostats.

Values (ControlSequenceOfOperationEnum):

Example:

{
  "1/513/27": 0
}

Attribute 28 / 0x001C — SystemMode

Path example:

1/513/28

Indicates the current operating mode of the thermostat. Its value is limited by the ControlSequenceOfOperation attribute.

Values (SystemModeEnum):

Example:

{
  "1/513/28": 0
}

Attribute 30 / 0x001E — ThermostatRunningMode

Path example:

1/513/30

Indicates the running mode of the thermostat. This attribute uses the same values as SystemModeEnum but can only be Off, Cool or Heat. This attribute is intended to provide additional information when the thermostat's system mode is in auto mode.

Values (ThermostatRunningModeEnum):

Example:

{
  "1/513/30": 0
}

Attribute 35 / 0x0023 — TemperatureSetpointHold

Path example:

1/513/35

Indicates 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.

Values (TemperatureSetpointHoldEnum):

Example:

{
  "1/513/35": 0
}

Attribute 36 / 0x0024 — TemperatureSetpointHoldDuration

Path example:

1/513/36

Indicates 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.

Example:

{
  "1/513/36": 1
}

Attribute 37 / 0x0025 — ThermostatProgrammingOperationMode

Path example:

1/513/37

No condensed specification text is available for ThermostatProgrammingOperationMode; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/37": 0
}

Attribute 41 / 0x0029 — ThermostatRunningState

Path example:

1/513/41

Indicates the current relay state of the heat, cool, and fan relays. Unimplemented outputs is treated as if they were Off.

Bits (RelayStateBitmap):

Example:

{
  "1/513/41": 0
}

Attribute 48 / 0x0030 — SetpointChangeSource

Path example:

1/513/48

Indicates 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.

Values (SetpointChangeSourceEnum):

Example:

{
  "1/513/48": 0
}

Attribute 49 / 0x0031 — SetpointChangeAmount

Path example:

1/513/49

Indicates 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.

Example:

{
  "1/513/49": 1
}

Attribute 50 / 0x0032 — SetpointChangeSourceTimestamp

Path example:

1/513/50

Indicates the time in UTC at which the SetpointChangeAmount attribute change was recorded.

Example:

{
  "1/513/50": 0
}

Attribute 52 / 0x0034 — OccupiedSetback

Path example:

1/513/52

No condensed specification text is available for OccupiedSetback; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/52": 0
}

Attribute 53 / 0x0035 — OccupiedSetbackMin

Path example:

1/513/53

No condensed specification text is available for OccupiedSetbackMin; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/53": 0
}

Attribute 54 / 0x0036 — OccupiedSetbackMax

Path example:

1/513/54

No condensed specification text is available for OccupiedSetbackMax; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/54": 0
}

Attribute 55 / 0x0037 — UnoccupiedSetback

Path example:

1/513/55

No condensed specification text is available for UnoccupiedSetback; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/55": 0
}

Attribute 56 / 0x0038 — UnoccupiedSetbackMin

Path example:

1/513/56

No condensed specification text is available for UnoccupiedSetbackMin; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/56": 0
}

Attribute 57 / 0x0039 — UnoccupiedSetbackMax

Path example:

1/513/57

No condensed specification text is available for UnoccupiedSetbackMax; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/57": 0
}

Attribute 58 / 0x003A — EmergencyHeatDelta

Path example:

1/513/58

Indicates 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 must 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.

Example:

{
  "1/513/58": 0
}

Attribute 64 / 0x0040 — ACType

Path example:

1/513/64

No condensed specification text is available for ACType; use the type, conformance and constraint below together with the cluster description above.

Values (ACTypeEnum):

Example:

{
  "1/513/64": 1
}

Attribute 65 / 0x0041 — ACCapacity

Path example:

1/513/65

No condensed specification text is available for ACCapacity; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/65": 1
}

Attribute 66 / 0x0042 — ACRefrigerantType

Path example:

1/513/66

No condensed specification text is available for ACRefrigerantType; use the type, conformance and constraint below together with the cluster description above.

Values (ACRefrigerantTypeEnum):

Example:

{
  "1/513/66": 1
}

Attribute 67 / 0x0043 — ACCompressorType

Path example:

1/513/67

No condensed specification text is available for ACCompressorType; use the type, conformance and constraint below together with the cluster description above.

Values (ACCompressorTypeEnum):

Example:

{
  "1/513/67": 1
}

Attribute 68 / 0x0044 — ACErrorCode

Path example:

1/513/68

No condensed specification text is available for ACErrorCode; use the type, conformance and constraint below together with the cluster description above.

Bits (ACErrorCodeBitmap):

Example:

{
  "1/513/68": 0
}

Attribute 69 / 0x0045 — ACLouverPosition

Path example:

1/513/69

No condensed specification text is available for ACLouverPosition; use the type, conformance and constraint below together with the cluster description above.

Values (ACLouverPositionEnum):

Example:

{
  "1/513/69": 1
}

Attribute 70 / 0x0046 — ACCoilTemperature

Path example:

1/513/70

No condensed specification text is available for ACCoilTemperature; use the type, conformance and constraint below together with the cluster description above.

Example:

{
  "1/513/70": 1
}

Attribute 71 / 0x0047 — ACCapacityFormat

Path example:

1/513/71

No condensed specification text is available for ACCapacityFormat; use the type, conformance and constraint below together with the cluster description above.

Values (ACCapacityFormatEnum):

Example:

{
  "1/513/71": 0
}

Attribute 72 / 0x0048 — PresetTypes

Path example:

1/513/72

Indicates the supported PresetScenarioEnum values, limits on how many presets can be created for each PresetScenarioEnum, and whether or not a thermostat can transition automatically to a given scenario. The list contains at least one entry. The list must NOT be larger than the number of supported PresetScenarioEnum values (maximum 7). The list must NOT contain any PresetTypeStruct entries with duplicate PresetScenarioEnum values.

Each entry is a PresetTypeStruct (see Data Types).

Example:

{
  "1/513/72": []
}

Attribute 73 / 0x0049 — ScheduleTypes

Path example:

1/513/73

Indicates the supported SystemMode values for Schedules, limits on how many schedules can be created for each SystemMode value, and whether or not a given SystemMode value supports transitions to Presets, target setpoints, or both. The list contains at least one entry. The list must NOT be larger than the number of supported schedule SystemMode values (maximum 3, since the data type only allows Auto, Heat and Cool). The list must NOT contain any ScheduleTypeStruct entries with duplicate SystemModeEnum values.

Each entry is a ScheduleTypeStruct (see Data Types).

Example:

{
  "1/513/73": []
}

Attribute 74 / 0x004A — NumberOfPresets

Path example:

1/513/74

Indicates the maximum number of entries supported by the Presets attribute.

Example:

{
  "1/513/74": 1
}

Attribute 75 / 0x004B — NumberOfSchedules

Path example:

1/513/75

Indicates the maximum number of entries supported by the Schedules attribute.

Example:

{
  "1/513/75": 1
}

Attribute 76 / 0x004C — NumberOfScheduleTransitions

Path example:

1/513/76

Indicates the maximum number of transitions per Schedules attribute entry.

Example:

{
  "1/513/76": 1
}

Attribute 77 / 0x004D — NumberOfScheduleTransitionPerDay

Path example:

1/513/77

Indicates the maximum number of transitions per day of the week supported by each Schedules attribute entry. If this value is null, there is no limit on the number of transitions per day.

Example:

{
  "1/513/77": 1
}

Attribute 78 / 0x004E — ActivePresetHandle

Path example:

1/513/78

Indicates the PresetHandle of the active preset. If this attribute is null, then there is no active preset.

Example:

{
  "1/513/78": "AQID"
}

Attribute 79 / 0x004F — ActiveScheduleHandle

Path example:

1/513/79

Indicates the ScheduleHandle of the active schedule. A null value in this attribute indicates that there is no active schedule.

Example:

{
  "1/513/79": "AQID"
}

Attribute 80 / 0x0050 — Presets

Path example:

1/513/80

This attribute contains the current list of configured presets. On receipt of a write request: 1. If the PresetHandle field is null, the PresetStruct is treated as an added preset, and the device must create a new unique value for the PresetHandle field. 1. If the BuiltIn field is true, a response with the status code CONSTRAINT_ERROR is returned. 2.

Each entry is a PresetStruct (see Data Types).

Example:

{
  "1/513/80": []
}

Attribute 81 / 0x0051 — Schedules

Path example:

1/513/81

This attribute contains a list of ScheduleStructs. On receipt of a write request: 1. For all schedules in the write request: 1. If the ScheduleHandle field is null, the ScheduleStruct is treated as an added schedule, and the device must create a new unique value for the ScheduleHandle field. 1.

Each entry is a ScheduleStruct (see Data Types).

Example:

{
  "1/513/81": []
}

Attribute 82 / 0x0052 — SetpointHoldExpiryTimestamp

Path example:

1/513/82

If there is a known time when the TemperatureSetpointHold is cleared, this attribute contains the timestamp in UTC indicating when that will happen. If there is no such known time, this attribute is null. If the TemperatureSetpointHold is set to SetpointHoldOn and the TemperatureSetpointHoldDuration is set to null, this attribute is set to null indicating there is a hold on the Thermostat without a duration. If the TemperatureSetpointHold is set to SetpointHoldOff, this attribute is set to null indicating there is no hold on the Thermostat.

Example:

{
  "1/513/82": 0
}

Attribute 83 / 0x0053 — MaxThermostatSuggestions

Path example:

1/513/83

Indicates the maximum number of entries supported by the ThermostatSuggestions attribute.

Example:

{
  "1/513/83": 5
}

Attribute 84 / 0x0054 — ThermostatSuggestions

Path example:

1/513/84

Indicates an unordered set of thermostat suggestions. The suggested value is a PresetHandle that must match the PresetHandle of one of the entries in the Presets attribute. The Thermostat may use this information to ensure user comfort while also prioritizing other factors (e.g. energy savings, cost, and so on). Entries with effective times in the future may be used for pre-cool or pre-heat decisions. 3.7, "Re-evaluation of Current Thermostat Suggestion" for what to do if this attribute's value changes.

Each entry is a ThermostatSuggestionStruct (see Data Types).

Example:

{
  "1/513/84": []
}

Attribute 85 / 0x0055 — CurrentThermostatSuggestion

Path example:

1/513/85

Indicates an entry in the entries, which identifies the current thermostat suggestion. A value of null indicates that there is no current thermostat suggestion. When this attribute's value changes to a null value, the server may decide to set the ActivePresetHandle attribute to a value of its choice, based on schedules, occupancy sensors, etc. When the server is "following the suggestion" that means that the server must ensure that the value of the ActivePresetHandle attribute matches the value of this attribute.

Value is a ThermostatSuggestionStruct struct (see Data Types).

Example:

{
  "1/513/85": {
    "uniqueID": 1,
    "presetHandle": "AQID",
    "effectiveTime": 0,
    "expirationTime": 0
  }
}

Attribute 86 / 0x0056 — ThermostatSuggestionNotFollowingReason

Path example:

1/513/86

Indicates the reasons the Thermostat is unable to follow suggestions. When the server is unable to follow the suggestion, it must set the appropriate bits in the value of the ThermostatSuggestionNotFollowingReason attribute to indicate the reasons due to which the suggestion is not being followed. The value of the ThermostatSuggestionNotFollowingReason attribute is 0 (all bits cleared) if there are no bits defined in ThermostatSuggestionNotFollowingReasonBitmap that represent the reasons the suggestion is not being followed. If the CurrentThermostatSuggestion attribute is null, this attribute is set to null.

Bits (ThermostatSuggestionNotFollowingReasonBitmap):

Example:

{
  "1/513/86": 0
}

Cluster 513 Commands

Cluster 513 has 5 client-to-server commands and 1 response.

AcceptedCommandList

The AcceptedCommandList attribute lists the command IDs the endpoint actually implements:

endpoint_id / 513 / 65529

{
  "1/513/65529": [
    0,
    5,
    6,
    7,
    8
  ]
}

Bridge Command Payload Format

The bridge accepts Matter commands in this structure:

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 513,
    "command_name": "SetpointRaiseLower",
    "payload": {},
    "timed_request_timeout_ms": 1000
  }
}

For Cluster 513, always use "cluster_id": 513. Payload keys are the command field names in lowerCamelCase. Octet-string fields are base64-encoded. timed_request_timeout_ms is required for timed commands and ignored otherwise.

Command: SetpointRaiseLower

Purpose

This command will raise or lower the setpoint based on the provided values.

Command Identity

Payload Fields

Mode values (SetpointRaiseLowerModeEnum): 0 = Heat, 1 = Cool, 2 = Both

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 513,
    "command_name": "SetpointRaiseLower",
    "payload": {
      "mode": 0,
      "amount": 1
    }
  }
}

Command: AddThermostatSuggestionResponse

Purpose

This command is sent in response to the AddThermostatSuggestion command.

Command Identity

Response Fields

Command: SetActiveScheduleRequest

Purpose

This command will set the active schedule to the provided schedule handle.

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 513,
    "command_name": "SetActiveScheduleRequest",
    "payload": {
      "scheduleHandle": "AQID"
    }
  }
}

Command: SetActivePresetRequest

Purpose

This command will set the active preset to the provided preset handle.

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 513,
    "command_name": "SetActivePresetRequest",
    "payload": {
      "presetHandle": "AQID"
    }
  }
}