Matter Cluster 121 — Water Tank Level Monitoring Cluster

Cluster Identity

Revision history

Shadow Path Format

Cluster 121 values in the device shadow use this format:

endpoint_id / 121 / attribute_id

Example:

{
  "1/121/2": 0
}

Cluster 121 Features

The FeatureMap attribute (1/121/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.

Data Types

ChangeIndicationEnum

DegradationDirectionEnum

ProductIdentifierTypeEnum

ReplacementProductStruct (struct)

Cluster 121 Attributes

Cluster 121 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 — Condition

Path example:

1/121/0

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

Example:

{
  "1/121/0": 1
}

Attribute 1 / 0x0001 — DegradationDirection

Path example:

1/121/1

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

Values (DegradationDirectionEnum):

Example:

{
  "1/121/1": 0
}

Attribute 2 / 0x0002 — ChangeIndication

Path example:

1/121/2

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

Values (ChangeIndicationEnum):

Example:

{
  "1/121/2": 0
}

Attribute 3 / 0x0003 — InPlaceIndicator

Path example:

1/121/3

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

Example:

{
  "1/121/3": true
}

Attribute 4 / 0x0004 — LastChangedTime

Path example:

1/121/4

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

Example:

{
  "1/121/4": 0
}

Attribute 5 / 0x0005 — ReplacementProductList

Path example:

1/121/5

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

Each entry is a ReplacementProductStruct (see Data Types).

Example:

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

Cluster 121 Commands

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

AcceptedCommandList

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

endpoint_id / 121 / 65529

{
  "1/121/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": 121,
    "command_name": "ResetCondition",
    "payload": {},
    "timed_request_timeout_ms": 1000
  }
}

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

Purpose

ResetCondition is a client-to-server command of the Water Tank Level Monitoring cluster.

Command Identity

Payload Fields

This command has no payload fields.

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 121,
    "command_name": "ResetCondition",
    "payload": {}
  }
}

Cluster 121 Events

Cluster 121 defines no events.

SmartphoneKey Notes

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