Matter Cluster 86 — Temperature Control Cluster

Cluster Identity

Revision history

Shadow Path Format

Cluster 86 values in the device shadow use this format:

endpoint_id / 86 / attribute_id

Example:

{
  "1/86/0": 1
}

Cluster 86 Features

The FeatureMap attribute (1/86/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; 7 means every feature listed above is enabled.

Cluster 86 Attributes

Cluster 86 defines 6 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 — TemperatureSetpoint

Path example:

1/86/0

Indicates the desired Temperature Setpoint on the device.

Example:

{
  "1/86/0": 1
}

Attribute 1 / 0x0001 — MinTemperature

Path example:

1/86/1

Indicates the minimum temperature to which the TemperatureSetpoint attribute may be set.

Example:

{
  "1/86/1": 1
}

Attribute 2 / 0x0002 — MaxTemperature

Path example:

1/86/2

Indicates the maximum temperature to which the TemperatureSetpoint attribute may be set. If the Step attribute is supported, this attribute is such that MaxTemperature = MinTemperature + (Step * n), where n is an integer and n $>$ 0. If the Step attribute is not supported, this attribute is such that MaxTemperature $>$ MinTemperature.

Example:

{
  "1/86/2": 1
}

Attribute 3 / 0x0003 — Step

Path example:

1/86/3

Indicates the discrete value by which the TemperatureSetpoint attribute can be changed via the SetTemperature command. For example, if the value of MinTemperature is 25.00C (2500) and the Step value is 0.50C (50), valid values of the TargetTemperature field of the SetTemperature command would be 25.50C (2550), 26.00C (2600), 26.50C (2650), etc.

Example:

{
  "1/86/3": 1
}

Attribute 4 / 0x0004 — SelectedTemperatureLevel

Path example:

1/86/4

Indicates the currently selected temperature level setting of the server. This attribute is the positional index of the list item in the SupportedTemperatureLevels list that represents the currently selected temperature level setting of the server.

Example:

{
  "1/86/4": 100
}

Attribute 5 / 0x0005 — SupportedTemperatureLevels

Path example:

1/86/5

Indicates the list of supported temperature level settings that may be selected via the TargetTemperatureLevel field in the SetTemperature command. Each string is readable text that describes each temperature level setting in a way that can be easily understood by humans. For example, a washing machine can have temperature levels like "Cold", "Warm", and "Hot". Each string is specified by the manufacturer.

Example:

{
  "1/86/5": []
}

Cluster 86 Commands

Cluster 86 has 1 client-to-server command and 0 responses.

AcceptedCommandList

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

endpoint_id / 86 / 65529

{
  "1/86/65529": [
    0
  ]
}

Bridge Command Payload Format

The bridge accepts Matter commands in this structure:

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

For Cluster 86, always use "cluster_id": 86. 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: SetTemperature

Purpose

This command is used to set the temperature setpoint.

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 86,
    "command_name": "SetTemperature",
    "payload": {
      "targetTemperature": 1,
      "targetTemperatureLevel": 100
    }
  }
}

Cluster 86 Events

Cluster 86 defines no events.

SmartphoneKey Notes

• Cluster 86 is not currently exposed by SmartphoneKey devices. This page documents the Matter 1.6.1 specification so that future devices can be interpreted without changes to the backend.
• Shadow paths follow endpoint/86/attribute; attribute values that the device reports as unreadable are written as n/a.
• Attribute IDs, command IDs and enum values on this page come from the CSA Matter 1.6.1 data model; descriptions are condensed from the specification text.