Matter Cluster 153 — Energy EVSE Cluster

Cluster Identity

Revision history

Shadow Path Format

Cluster 153 values in the device shadow use this format:

endpoint_id / 153 / attribute_id

Example:

{
  "1/153/0": 0
}

Cluster 153 Features

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

Data Types

EnergyTransferStoppedReasonEnum

FaultStateEnum

StateEnum

SupplyStateEnum

TargetDayOfWeekBitmap (bitmap)

ChargingTargetScheduleStruct (struct)

This represents a set of user specified charging targets for an EV for a set of specified days.

ChargingTargetStruct (struct)

This represents a single user specified charging target for an EV. An EVSE or EMS system optimizer may use this information to take the Time of Use Tariff, grid carbon intensity, local generation (solar PV) into account to provide the cheapest and cleanest energy to the EV.

Cluster 153 Attributes

Cluster 153 defines 23 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 — State

Path example:

1/153/0

Indicates the current status of the EVSE. This higher-level status is partly derived from the signaling protocol as communicated between the EVSE and the vehicle through the pilot signal. The State attribute must change when the EVSE detects change of condition of the EV (plugged in or unplugged, whether the vehicle is asking for demand or not, and if it is charging or discharging). SessionEnding is not really a state but a transition.

Values (StateEnum):

Example:

{
  "1/153/0": 0
}

Attribute 1 / 0x0001 — SupplyState

Path example:

1/153/1

Indicates whether the EV is currently allowed to charge from or discharge to the EVSE.

Values (SupplyStateEnum):

Example:

{
  "1/153/1": 0
}

Attribute 2 / 0x0002 — FaultState

Path example:

1/153/2

Indicates the type of fault detected by the EVSE (internally or as detected in the pilot signal). When the SupplyState attribute is DisabledError, the FaultState attribute will be one of the values listed in FaultStateEnum, except NoError. For all values of SupplyState other than DisabledError, the FaultState attribute is NoError.

Values (FaultStateEnum):

Example:

{
  "1/153/2": 0
}

Attribute 3 / 0x0003 — ChargingEnabledUntil

Path example:

1/153/3

Indicates the time, in UTC, that the EVSE will automatically stop current flow to the EV. A null value indicates the EVSE is always enabled for charging. A value in the past or 0x0 indicates that EVSE charging is disabled. The attribute is only set via the payload of the EnableCharging command.

Example:

{
  "1/153/3": 1
}

Attribute 4 / 0x0004 — DischargingEnabledUntil

Path example:

1/153/4

Indicates the time, in UTC, that the EVSE will automatically stop current flow from the EV. A null value indicates the EVSE is always enabled for discharging. A value in the past or 0x0 indicates that EVSE discharging is disabled. The attribute is only set via the payload of the EnableDischarging command.

Example:

{
  "1/153/4": 1
}

Attribute 5 / 0x0005 — CircuitCapacity

Path example:

1/153/5

Indicates the capacity that the circuit that the EVSE is connected to can provide. It is intended to allow implementation of a self-managed network of EVSEs. It is assumed that the device will allow the setting of such values by an installer.

Example:

{
  "1/153/5": 1
}

Attribute 6 / 0x0006 — MinimumChargeCurrent

Path example:

1/153/6

Indicates the minimum current that can be delivered by the EVSE to the EV. The attribute can be set using the EnableCharging command.

Example:

{
  "1/153/6": 1
}

Attribute 7 / 0x0007 — MaximumChargeCurrent

Path example:

1/153/7

Indicates the maximum current that can be delivered by the EVSE to the EV. This represents the actual maximum current offered to the EV at any time. Note that the EV can draw less current than this value. For example, the EV may be limiting its power draw based on the operating conditions of the battery, such as temperature and state of charge.

Example:

{
  "1/153/7": 1
}

Attribute 8 / 0x0008 — MaximumDischargeCurrent

Path example:

1/153/8

Indicates the maximum current that can be received by the EVSE from the EV. This attribute can be set using the EnableDischarging command. This attribute value is the minimum of: - CircuitCapacity - Electrician's installation setting - CableAssemblyCurrentLimit (detected by the EVSE when the cable is plugged in) - MaximumDischargeCurrent field in the EnableDischarging command

Example:

{
  "1/153/8": 1
}

Attribute 9 / 0x0009 — UserMaximumChargeCurrent

Path example:

1/153/9

Indicates a maximum current that can set by the consumer (e.g. via an app) as a preference to further reduce the charging rate. This may be desirable if the home owner has a solar PV or battery storage system which may only be able to deliver a limited amount of power. The consumer can manually control how much they allow the EV to take. This attribute value is limited by the EVSE to be in the range of: where MinimumChargeCurrent and MaximumChargeCurrent are the values received in the EnableCharging command.

Example:

{
  "1/153/9": 1
}

Attribute 10 / 0x000A — RandomizationDelayWindow

Path example:

1/153/10

Indicates the size of a random window over which the EVSE will randomize the start of a charging session. This value is in seconds. This is a feature that is mandated in some markets (such as UK) where the EVSE should by default randomize its start time within the randomization window. By default in the UK this should be 600s.

Example:

{
  "1/153/10": 1
}

Attribute 35 / 0x0023 — NextChargeStartTime

Path example:

1/153/35

Indicates the time, in UTC, when the EVSE plans to start the next scheduled charge based on the charging preferences. A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is enabled.

Example:

{
  "1/153/35": 0
}

Attribute 36 / 0x0024 — NextChargeTargetTime

Path example:

1/153/36

Indicates the time, in UTC, when the EVSE should complete the next scheduled charge based on the charging preferences. A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is enabled.

Example:

{
  "1/153/36": 0
}

Attribute 37 / 0x0025 — NextChargeRequiredEnergy

Path example:

1/153/37

Indicates the amount of energy that the EVSE is going to attempt to add to the vehicle in the next charging target. A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is enabled, or that the next ChargingTargetStruct is using the TargetSoC value to charge the vehicle.

Example:

{
  "1/153/37": 1
}

Attribute 38 / 0x0026 — NextChargeTargetSoC

Path example:

1/153/38

Indicates the target SoC the EVSE is going to attempt to reach when the vehicle is next charged. A null value indicates that there is no scheduled charging (for example, the EVSE Mode is set to use Manual mode tag), or that the vehicle is not plugged in with the SupplyState indicating that charging is enabled, or that the next ChargingTargetStruct is using the AddedEnergy value to charge the vehicle. If the SOC feature is not supported, only the values null and 100% are supported.

Example:

{
  "1/153/38": 1
}

Attribute 39 / 0x0027 — ApproximateEVEfficiency

Path example:

1/153/39

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

Example:

{
  "1/153/39": 1
}

Attribute 48 / 0x0030 — StateOfCharge

Path example:

1/153/48

Indicates the state of charge of the EV battery in steps of 1%. The values are in the 0-100%. This attribute is only available on EVSEs which can read the state of charge from the vehicle and that support the SOC feature. If the StateOfCharge cannot be read from the vehicle it is returned with a null value.

Example:

{
  "1/153/48": 1
}

Attribute 49 / 0x0031 — BatteryCapacity

Path example:

1/153/49

Indicates the capacity of the EV battery in mWh. This value is always positive.

Example:

{
  "1/153/49": 1
}

Attribute 50 / 0x0032 — VehicleID

Path example:

1/153/50

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

Example:

{
  "1/153/50": "example"
}

Attribute 64 / 0x0040 — SessionID

Path example:

1/153/64

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

Example:

{
  "1/153/64": 1
}

Attribute 65 / 0x0041 — SessionDuration

Path example:

1/153/65

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

Example:

{
  "1/153/65": 1
}

Attribute 66 / 0x0042 — SessionEnergyCharged

Path example:

1/153/66

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

Example:

{
  "1/153/66": 1
}

Attribute 67 / 0x0043 — SessionEnergyDischarged

Path example:

1/153/67

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

Example:

{
  "1/153/67": 1
}

Cluster 153 Commands

Cluster 153 has 7 client-to-server commands and 1 response.

AcceptedCommandList

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

endpoint_id / 153 / 65529

{
  "1/153/65529": [
    1,
    2,
    3,
    4,
    5,
    6,
    7
  ]
}

Bridge Command Payload Format

The bridge accepts Matter commands in this structure:

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

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

Purpose

The GetTargetsResponse is sent in response to the GetTargets Command.

Command Identity

Response Fields

Command: Disable

Purpose

Allows a client to disable the EVSE from charging and discharging.

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": 153,
    "command_name": "Disable",
    "payload": {},
    "timed_request_timeout_ms": 1000
  }
}

This is a timed command: the bridge must send it inside a timed interaction, so timed_request_timeout_ms is required.

Command: EnableCharging

Purpose

This command allows a client to enable the EVSE to charge an EV, and to provide or update the maximum and minimum charge current.

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 153,
    "command_name": "EnableCharging",
    "payload": {
      "chargingEnabledUntil": 1,
      "minimumChargeCurrent": 1,
      "maximumChargeCurrent": 1
    },
    "timed_request_timeout_ms": 1000
  }
}

This is a timed command: the bridge must send it inside a timed interaction, so timed_request_timeout_ms is required.

Command: EnableDischarging

Purpose

On receipt, this must allow a client to enable the discharge of an EV, and to provide or update the maximum discharge current.

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 153,
    "command_name": "EnableDischarging",
    "payload": {
      "dischargingEnabledUntil": 1,
      "maximumDischargeCurrent": 1
    },
    "timed_request_timeout_ms": 1000
  }
}

This is a timed command: the bridge must send it inside a timed interaction, so timed_request_timeout_ms is required.

Command: StartDiagnostics

Purpose

Allows a client to put the EVSE into a self-diagnostics mode.

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": 153,
    "command_name": "StartDiagnostics",
    "payload": {},
    "timed_request_timeout_ms": 1000
  }
}

This is a timed command: the bridge must send it inside a timed interaction, so timed_request_timeout_ms is required.

Command: SetTargets

Purpose

Allows a client to set the user specified charging targets.

Command Identity

Payload Fields

Bridge Command Example

{
  "message_id": "1",
  "command": "device_command",
  "args": {
    "endpoint_id": 1,
    "cluster_id": 153,
    "command_name": "SetTargets",
    "payload": {
      "chargingTargetSchedules": []
    },
    "timed_request_timeout_ms": 1000
  }
}

This is a timed command: the bridge must send it inside a timed interaction, so timed_request_timeout_ms is required.

Command: GetTargets

Purpose

Allows a client to retrieve the current set of charging targets.

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": 153,
    "command_name": "GetTargets",
    "payload": {},
    "timed_request_timeout_ms": 1000
  }
}

This is a timed command: the bridge must send it inside a timed interaction, so timed_request_timeout_ms is required.

The device answers with GetTargetsResponse (see below).

Command: ClearTargets

Purpose

Allows a client to clear all stored charging targets.

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": 153,
    "command_name": "ClearTargets",
    "payload": {},
    "timed_request_timeout_ms": 1000
  }
}

This is a timed command: the bridge must send it inside a timed interaction, so timed_request_timeout_ms is required.

Cluster 153 Events

Event 0 — EVConnected

Event 1 — EVNotDetected

Event 2 — EnergyTransferStarted

This event is generated whenever the EV starts charging or discharging, except when an EV has switched between charging and discharging under the control of the PowerAdjustment feature of the Device Energy Management cluster of the associated Device Energy Management device.

Event 3 — EnergyTransferStopped

This event is generated whenever the EV stops charging or discharging, except when an EV has switched between charging and discharging under the control of the PowerAdjustment feature of the Device Energy Management cluster of the associated Device Energy Management device.

Event 4 — Fault

If the EVSE detects a fault it must generate a Fault Event. The SupplyState attribute is set to DisabledError and the type of fault detected by the EVSE is stored in the FaultState attribute. This event is generated when the FaultState changes from any error state. i.e. if it changes from NoError to any other state and if the error then clears, this would generate 2 events.

Event 5 — RFID

SmartphoneKey Notes

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