Matter Cluster 95 — Microwave Oven Control Cluster

Cluster Identity

Revision history

Shadow Path Format

Cluster 95 values in the device shadow use this format:

endpoint_id / 95 / attribute_id

Example:

{
  "1/95/0": 0
}

Cluster 95 Features

The FeatureMap attribute (1/95/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 95 Attributes

Cluster 95 defines 9 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 — CookTime

Path example:

1/95/0

Indicates the total cook time associated with the operation of the device. This attribute must remain unchanged during the operation of the oven unless the value is changed via a command or out-of-band action.

Example:

{
  "1/95/0": 0
}

Attribute 1 / 0x0001 — MaxCookTime

Path example:

1/95/1

Indicates the maximum value to which the CookTime attribute can be set.

Example:

{
  "1/95/1": 0
}

Attribute 2 / 0x0002 — PowerSetting

Path example:

1/95/2

Indicates the power level associated with the operation of the device. If the MinPower, MaxPower, and PowerStep attributes are not supported: - The minimum value of this attribute is 10, - The maximum value of this attribute is 100, - The value is in even multiples of 10, - The default value is 100. If the MinPower, MaxPower, and PowerStep attributes are supported: - The value of this attribute is between MinPower and MaxPower inclusive. - The value of this attribute is such that (PowerSetting - MinPower) % PowerStep == 0

Example:

{
  "1/95/2": 1
}

Attribute 3 / 0x0003 — MinPower

Path example:

1/95/3

Indicates the minimum value to which the PowerSetting attribute that can be set on the server.

Example:

{
  "1/95/3": 1
}

Attribute 4 / 0x0004 — MaxPower

Path example:

1/95/4

Indicates the maximum value to which the PowerSetting attribute that can be set on the server.

Example:

{
  "1/95/4": 1
}

Attribute 5 / 0x0005 — PowerStep

Path example:

1/95/5

Indicates the increment of power that can be set on the server. The value of this attribute is between 1 and MaxPower inclusive. The value of this attribute is such that (MaxPower - MinPower) % PowerStep == 0 For example, if MinPower is 1, MaxPower is 10, and PowerSetting can be set to any integer between MinPower and MaxPower, PowerStep would be set to 1.

Example:

{
  "1/95/5": 1
}

Attribute 6 / 0x0006 — SupportedWatts

Path example:

1/95/6

Indicates the list of power levels (in W) supported by the server.

Example:

{
  "1/95/6": []
}

Attribute 7 / 0x0007 — SelectedWattIndex

Path example:

1/95/7

Indicates the index into the list of SupportedWatts of the currently selected power setting. The index is a valid index into the SupportedWatts list.

Example:

{
  "1/95/7": 1
}

Attribute 8 / 0x0008 — WattRating

Path example:

1/95/8

Indicates the rating, in Watts, of the microwave power of the oven. Supporting this attribute can assist clients in suggesting cooking settings for various foods and beverages.

Example:

{
  "1/95/8": 1
}

Cluster 95 Commands

Cluster 95 has 2 client-to-server commands and 0 responses.

AcceptedCommandList

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

endpoint_id / 95 / 65529

{
  "1/95/65529": [
    0,
    1
  ]
}

Bridge Command Payload Format

The bridge accepts Matter commands in this structure:

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

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

Purpose

This command is used to set the cooking parameters associated with the operation of the device. This command supports the following fields:

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 95,
    "command_name": "SetCookingParameters",
    "payload": {
      "cookMode": 1,
      "cookTime": 0
    }
  }
}

Command: AddMoreTime

Purpose

This command is used to add more time to the CookTime attribute of the server. This command supports these fields:

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 95,
    "command_name": "AddMoreTime",
    "payload": {
      "timeToAdd": 0
    }
  }
}

Cluster 95 Events

Cluster 95 defines no events.

SmartphoneKey Notes

• Cluster 95 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/95/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.