Matter Cluster 144 — Electrical Power Measurement Cluster

Cluster Identity

Revision history

Shadow Path Format

Cluster 144 values in the device shadow use this format:

endpoint_id / 144 / attribute_id

Example:

{
  "1/144/0": 1
}

Cluster 144 Features

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

MeasurementTypeEnum

PowerModeEnum

HarmonicMeasurementStruct (struct)

MeasurementAccuracyRangeStruct (struct)

MeasurementAccuracyStruct (struct)

MeasurementRangeStruct (struct)

This struct indicates the maximum and minimum values of a given measurement type during a measurement period, along with the observation times of these values.

Cluster 144 Attributes

Cluster 144 defines 19 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 — PowerMode

Path example:

1/144/0

This indicates the current mode of the server. For some servers, such as an EV, this may change depending on the mode of charging or discharging.

Values (PowerModeEnum):

Example:

{
  "1/144/0": 1
}

Attribute 1 / 0x0001 — NumberOfMeasurementTypes

Path example:

1/144/1

This indicates the maximum number of measurement types the server is capable of reporting.

Example:

{
  "1/144/1": 1
}

Attribute 2 / 0x0002 — Accuracy

Path example:

1/144/2

This indicates a list of accuracy specifications for the measurement types supported by the server. There is an entry for ActivePower, as well as any other measurement types implemented by this server.

Each entry is a MeasurementAccuracyStruct (see Data Types).

Example:

{
  "1/144/2": []
}

Attribute 3 / 0x0003 — Ranges

Path example:

1/144/3

This indicates a list of measured ranges for different measurement types. Each measurement type has at most one entry in this list, representing the range of measurements in the most recent measurement period. The reporting interval of this attribute is manufacturer dependent. The server may choose to omit publication of deltas considered not meaningful.

Each entry is a MeasurementRangeStruct (see Data Types).

Example:

{
  "1/144/3": []
}

Attribute 4 / 0x0004 — Voltage

Path example:

1/144/4

This indicates the most recent Voltage reading in millivolts (mV). The reporting interval of this attribute is manufacturer dependent. The server may choose to omit publication of deltas considered not meaningful. The server must NOT mark this attribute ready for report if the last time this was done was more recently than 1 second ago.

Example:

{
  "1/144/4": 1
}

Attribute 5 / 0x0005 — ActiveCurrent

Path example:

1/144/5

This indicates the most recent ActiveCurrent reading in milliamps (mA). A positive value represents current flowing into the server, while a negative value represents current flowing out of the server. The reporting interval of this attribute is manufacturer dependent. The server may choose to omit publication of deltas considered not meaningful.

Example:

{
  "1/144/5": 1
}

Attribute 6 / 0x0006 — ReactiveCurrent

Path example:

1/144/6

This indicates the most recent ReactiveCurrent reading in milliamps (mA). A positive value represents current flowing into the server, while a negative value represents current flowing out of the server. The reporting interval of this attribute is manufacturer dependent. The server may choose to omit publication of deltas considered not meaningful.

Example:

{
  "1/144/6": 1
}

Attribute 7 / 0x0007 — ApparentCurrent

Path example:

1/144/7

This indicates the most recent ApparentCurrent (square root sum of the squares of active and reactive currents) reading in milliamps (mA). A positive value represents current flowing into the server, while a negative value represents current flowing out of the server. The reporting interval of this attribute is manufacturer dependent. The server may choose to omit publication of deltas considered not meaningful.

Example:

{
  "1/144/7": 1
}

Attribute 8 / 0x0008 — ActivePower

Path example:

1/144/8

This indicates the most recent ActivePower reading in milliwatts (mW). If the power cannot be measured, a value of null is returned. A positive value represents power imported, while a negative value represents power exported. The reporting interval of this attribute is manufacturer dependent.

Example:

{
  "1/144/8": 1
}

Attribute 9 / 0x0009 — ReactivePower

Path example:

1/144/9

This indicates the most recent ReactivePower reading in millivolt-amps reactive (mVAR). A positive value represents power imported, while a negative value represents power exported. The reporting interval of this attribute is manufacturer dependent. The server may choose to omit publication of deltas considered not meaningful.

Example:

{
  "1/144/9": 1
}

Attribute 10 / 0x000A — ApparentPower

Path example:

1/144/10

This indicates the most recent ApparentPower reading in millivolt-amps (mVA). A positive value represents power imported, while a negative value represents power exported. The reporting interval of this attribute is manufacturer dependent. The server may choose to omit publication of deltas considered not meaningful.

Example:

{
  "1/144/10": 1
}

Attribute 11 / 0x000B — RMSVoltage

Path example:

1/144/11

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

Example:

{
  "1/144/11": 1
}

Attribute 12 / 0x000C — RMSCurrent

Path example:

1/144/12

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

Example:

{
  "1/144/12": 1
}

Attribute 13 / 0x000D — RMSPower

Path example:

1/144/13

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

Example:

{
  "1/144/13": 1
}

Attribute 14 / 0x000E — Frequency

Path example:

1/144/14

This indicates the most recent Frequency reading in millihertz (mHz). The reporting interval of this attribute is manufacturer dependent. The server may choose to omit publication of deltas considered not meaningful. The server must NOT mark this attribute ready for report if the last time this was done was more recently than 1 second ago.

Example:

{
  "1/144/14": 0
}

Attribute 15 / 0x000F — HarmonicCurrents

Path example:

1/144/15

This indicates a list of HarmonicMeasurementStruct values, with each HarmonicMeasurementStruct representing the harmonic current reading for the harmonic order specified by Order. The reporting interval of this attribute is manufacturer dependent. The server may choose to omit publication of deltas considered not meaningful. The server must NOT mark this attribute ready for report if the last time this was done was more recently than 1 second ago.

Each entry is a HarmonicMeasurementStruct (see Data Types).

Example:

{
  "1/144/15": []
}

Attribute 16 / 0x0010 — HarmonicPhases

Path example:

1/144/16

This indicates a list of HarmonicMeasurementStruct values, with each HarmonicMeasurementStruct representing the most recent phase of the harmonic current reading for the harmonic order specified by Order. The reporting interval of this attribute is manufacturer dependent. The server may choose to omit publication of deltas considered not meaningful. The server must NOT mark this attribute ready for report if the last time this was done was more recently than 1 second ago.

Each entry is a HarmonicMeasurementStruct (see Data Types).

Example:

{
  "1/144/16": []
}

Attribute 17 / 0x0011 — PowerFactor

Path example:

1/144/17

This indicates the Power Factor ratio in +/- 1/100ths of a percent. The reporting interval of this attribute is manufacturer dependent. The server may choose to omit publication of deltas considered not meaningful. The server must NOT mark this attribute ready for report if the last time this was done was more recently than 1 second ago.

Example:

{
  "1/144/17": 1
}

Attribute 18 / 0x0012 — NeutralCurrent

Path example:

1/144/18

This indicates the most recent NeutralCurrent reading in milliamps (mA). Typically this is a derived value, taking the magnitude of the vector sum of phase currents. If the neutral current cannot be measured or derived, a value of null is returned. A positive value represents an imbalance between the phase currents when power is imported.

Example:

{
  "1/144/18": 1
}

Cluster 144 Commands

Cluster 144 defines no commands. It is read (and, for writable attributes, written) through attribute access only.

Cluster 144 Events

Event 0 — MeasurementPeriodRanges

If supported, this event is generated at the end of a measurement period. The start and end times for measurement periods is determined by the server, and may represent overlapping periods.

SmartphoneKey Notes

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