General and node management44 — Time Format Localization

Matter Cluster 44 — Time Format Localization

Matter Cluster 44 (0x002C) Time Format Localization: attributes, commands, events, data types, shadow paths and bridge payload examples.

Matter Cluster 44 — Time Format Localization Cluster

Matter Cluster 44, also written as 0x002C, is the Time Format 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 how dates and times are conveyed. As such, Nodes that visually or audibly convey time information need a mechanism by which they can be configured to use a user’s preferred format.

Cluster Identity

FieldValue
Cluster ID decimal44
Cluster ID hex0x002C
Cluster nameTime Format Localization
Cluster revision (Matter 1.6.1)1
Roleutility
ScopeNode
PICS codeLTIME
Typical endpoint0

Revision history

RevisionChange
1Initial revision

Shadow Path Format

Cluster 44 values in the device shadow use this format:

endpoint_id / 44 / attribute_id

Example:

{
  "0/44/0": 0
}
PartMeaning
0Endpoint ID
44Time Format Localization cluster
0HourFormat attribute

Cluster 44 Features

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

BitCodeFeatureConformanceMeaning
0CALFMTCalendarFormatOThe Node can be configured to use different calendar formats 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

CalendarTypeEnum

ValueNameConformanceMeaning
0BuddhistODates conveyed using the Buddhist calendar
1ChineseODates conveyed using the Chinese calendar
2CopticODates conveyed using the Coptic calendar
3EthiopianODates conveyed using the Ethiopian calendar
4GregorianODates conveyed using the Gregorian calendar
5HebrewODates conveyed using the Hebrew calendar
6IndianODates conveyed using the Indian calendar
7IslamicODates conveyed using the Islamic calendar
8JapaneseODates conveyed using the Japanese calendar
9KoreanODates conveyed using the Korean calendar
10PersianODates conveyed using the Persian calendar
11TaiwaneseODates conveyed using the Taiwanese calendar
255UseActiveLocaleOcalendar implied from active locale

HourFormatEnum

ValueNameConformanceMeaning
012hrMTime conveyed with a 12-hour clock
124hrMTime conveyed with a 24-hour clock
255UseActiveLocaleMUse active locale clock

Cluster 44 Attributes

Cluster 44 defines 3 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
00x0000HourFormatHourFormatEnumMR/W (read: view, write: manage)persisted—
10x0001ActiveCalendarTypeCalendarTypeEnumCALFMTR/W (read: view, write: manage)persisted—
20x0002SupportedCalendarTypeslist of CalendarTypeEnumCALFMTR (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; 1 for a Matter 1.6.1 device.

Attribute Details

Attribute 0 / 0x0000 — HourFormat

Path example:

0/44/0

Indicates the format that the Node is currently configured to use when conveying the hour unit of time. If not UseActiveLocale, this value must take priority over any unit implied through the ActiveLocale attribute. If UseActiveLocale, any unit implied through the ActiveLocale attribute is used as the hour format, and if ActiveLocale is not present, the hour format is unknown.

PropertyValue
TypeHourFormatEnum
ConformanceM
AccessR/W (read: view, write: manage)
Qualitiespersisted

Values (HourFormatEnum):

ValueNameMeaning
012hrTime conveyed with a 12-hour clock
124hrTime conveyed with a 24-hour clock
255UseActiveLocaleUse active locale clock

Example:

{
  "0/44/0": 0
}

Attribute 1 / 0x0001 — ActiveCalendarType

Path example:

0/44/1

Indicates the calendar format that the Node is currently configured to use when conveying dates. If not UseActiveLocale, this value must take priority over any unit implied through the ActiveLocale attribute. If UseActiveLocale, any unit implied through the ActiveLocale attribute is used as the calendar type, and if ActiveLocale is not present, the calendar type is unknown.

PropertyValue
TypeCalendarTypeEnum
ConformanceCALFMT
AccessR/W (read: view, write: manage)
Qualitiespersisted

Values (CalendarTypeEnum):

ValueNameMeaning
0BuddhistDates conveyed using the Buddhist calendar
1ChineseDates conveyed using the Chinese calendar
2CopticDates conveyed using the Coptic calendar
3EthiopianDates conveyed using the Ethiopian calendar
4GregorianDates conveyed using the Gregorian calendar
5HebrewDates conveyed using the Hebrew calendar
6IndianDates conveyed using the Indian calendar
7IslamicDates conveyed using the Islamic calendar
8JapaneseDates conveyed using the Japanese calendar
9KoreanDates conveyed using the Korean calendar
10PersianDates conveyed using the Persian calendar
11TaiwaneseDates conveyed using the Taiwanese calendar
255UseActiveLocalecalendar implied from active locale

Example:

{
  "0/44/1": 0
}

Attribute 2 / 0x0002 — SupportedCalendarTypes

Path example:

0/44/2

Indicates a list of CalendarTypeEnum values that are supported by the Node. The list must NOT contain any duplicate entries. The ordering of items within the list should NOT express any meaning. The maximum length of the SupportedCalendarTypes list is equivalent to the number of enumerations within CalendarTypeEnum.

PropertyValue
Typelist of CalendarTypeEnum
ConformanceCALFMT
AccessR (read: view)
Constraintdesc

Example:

{
  "0/44/2": []
}

Cluster 44 Commands

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

Cluster 44 Events

Cluster 44 defines no events.


SmartphoneKey Notes

  • Cluster 44 is present on SmartphoneKey devices or hubs today. See Matter Bridge Clusters — Detailed Reference and Matter Device Attributes & Commands for the values the bridge actually reports.
  • Shadow paths follow endpoint/44/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.