General and node management45 — Unit Localization

Matter Cluster 45 — Unit Localization

Matter Cluster 45 (0x002D) Unit Localization: attributes, commands, events, data types, shadow paths and bridge payload examples.

Matter Cluster 45 — Unit Localization Cluster

Matter Cluster 45, also written as 0x002D, is the Unit Localization Cluster. Nodes should be expected to be deployed to any and all regions of the world. These global regions may have differing preferences for the units in which values are conveyed in communication to a user. As such, Nodes that visually or audibly convey measurable values to the user need a mechanism by which they can be configured to use a user’s preferred unit.

Cluster Identity

FieldValue
Cluster ID decimal45
Cluster ID hex0x002D
Cluster nameUnit Localization
Cluster revision (Matter 1.6.1)2
Roleutility
ScopeNode
PICS codeLUNIT
Typical endpoint0

Revision history

RevisionChange
1Initial revision
2Added SupportedTemperatureUnits attribute

Shadow Path Format

Cluster 45 values in the device shadow use this format:

endpoint_id / 45 / attribute_id

Example:

{
  "0/45/0": 0
}
PartMeaning
0Endpoint ID
45Unit Localization cluster
0TemperatureUnit attribute

Cluster 45 Features

The FeatureMap attribute (0/45/65532) is a bitmap. Each bit set means the device implements that feature and the attributes and commands that depend on it.

BitCodeFeatureConformanceMeaning
0TEMPTemperatureUnitOThe Node can be configured to use different units of temperature when conveying values to a user

Example: FeatureMap = 0 means no optional feature is enabled; 1 means every feature listed above is enabled.


Data Types

TempUnitEnum

ValueNameConformanceMeaning
0FahrenheitOTemperature conveyed in Fahrenheit
1CelsiusOTemperature conveyed in Celsius
2KelvinOTemperature conveyed in Kelvin

Cluster 45 Attributes

Cluster 45 defines 2 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 …".

IDHexAttributeTypeConformanceAccessQualitiesDefault
00x0000TemperatureUnitTempUnitEnumTEMPR/W (read: view, write: manage)persisted—
10x0001SupportedTemperatureUnitslist of TempUnitEnumTEMPR (read: view)——

Global attributes

IDHexAttributeMeaning
655280xFFF8GeneratedCommandListResponse command IDs this server generates.
655290xFFF9AcceptedCommandListCommand IDs this server accepts.
655310xFFFBAttributeListAttribute IDs implemented.
655320xFFFCFeatureMapImplemented optional features (see above).
655330xFFFDClusterRevisionCluster revision implemented; 2 for a Matter 1.6.1 device.

Attribute Details

Attribute 0 / 0x0000 — TemperatureUnit

Path example:

0/45/0

Indicates the unit for the Node to use only when conveying temperature in communication to the user, for example such as via a user interface on the device. If provided, this value must take priority over any unit implied through the ActiveLocale Attribute. An attempt to write to this attribute with a value not included in the SupportedTemperatureUnits attribute list must result in a CONSTRAINT_ERROR.

PropertyValue
TypeTempUnitEnum
ConformanceTEMP
AccessR/W (read: view, write: manage)
Qualitiespersisted

Values (TempUnitEnum):

ValueNameMeaning
0FahrenheitTemperature conveyed in Fahrenheit
1CelsiusTemperature conveyed in Celsius
2KelvinTemperature conveyed in Kelvin

Example:

{
  "0/45/0": 0
}

Attribute 1 / 0x0001 — SupportedTemperatureUnits

Path example:

0/45/1

Indicates a list of units supported by the Node to be used when writing the TemperatureUnit attribute of this cluster. Each entry in the list is unique.

PropertyValue
Typelist of TempUnitEnum
ConformanceTEMP
AccessR (read: view)
Constraint2 to 3 entries

Example:

{
  "0/45/1": []
}

Cluster 45 Commands

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

Cluster 45 Events

Cluster 45 defines no events.


SmartphoneKey Notes

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