Matter Cluster 157 — Energy EVSE Mode Cluster

Cluster Identity

Revision history

Shadow Path Format

Cluster 157 values in the device shadow use this format:

endpoint_id / 157 / attribute_id

Example:

{
  "1/157/0": 0
}

Cluster 157 Features

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

Data Types

ModeTag

ModeOptionStruct (struct)

This is a struct representing a possible mode of the server.

ModeTagStruct (struct)

A Mode Tag is meant to be interpreted by the client for the purpose the cluster serves.

Cluster 157 Attributes

Cluster 157 defines 4 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 — SupportedModes

Path example:

1/157/0

At least one entry in the SupportedModes attribute includes the Manual mode tag in the ModeTags field list. Modes with entries in the SupportedModes attribute which contain multiple mode tags permitting charging or discharging under different conditions must permit the charging or discharging to occur if any of the conditions are satisfied. Modes must NOT have both the Manual tag and the TimeOfUse or SolarCharging tags defined in the SupportedModes attribute.

Example:

{
  "1/157/0": 0
}

Attribute 1 / 0x0001 — CurrentMode

Path example:

1/157/1

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

Example:

{
  "1/157/1": 0
}

Attribute 2 / 0x0002 — StartUpMode

Path example:

1/157/2

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

Example:

{
  "1/157/2": 0
}

Attribute 3 / 0x0003 — OnMode

Path example:

1/157/3

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

Example:

{
  "1/157/3": 0
}

Cluster 157 Commands

Cluster 157 has 1 client-to-server command and 1 response.

AcceptedCommandList

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

endpoint_id / 157 / 65529

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

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

Purpose

This command is used to change device modes. On receipt of this command the device must respond with a ChangeToModeResponse command.

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 157,
    "command_name": "ChangeToMode",
    "payload": {
      "newMode": 1
    }
  }
}

The device answers with ChangeToModeResponse (see below).

Command: ChangeToModeResponse

Purpose

This command is sent by the device on receipt of the ChangeToMode command.

Command Identity

Response Fields

Cluster 157 Events

Cluster 157 defines no events.

SmartphoneKey Notes

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