Bridges and fabric administration1872 — Ecosystem Information

Matter Cluster 1872 — Ecosystem Information

Matter Cluster 1872 (0x0750) Ecosystem Information: attributes, commands, events, data types, shadow paths and bridge payload examples.

Matter Cluster 1872 — Ecosystem Information Cluster

Matter Cluster 1872, also written as 0x0750, is the Ecosystem Information Cluster. The Ecosystem Information Cluster provides extended device information for all the logical devices represented by a Bridged Node. The Ecosystem Information Cluster presents the view of device name and location metadata for presentation by a client of the cluster to a user. This cluster is intended to support Fabric Synchronization and be present on an endpoint with the BridgedNode device type listed in the DeviceTypeList of the endpoint's Descriptor cluster.

Cluster Identity

FieldValue
Cluster ID decimal1872
Cluster ID hex0x0750
Cluster nameEcosystem Information
Cluster revision (Matter 1.6.1)1
Roleutility
ScopeEndpoint
PICS codeECOINFO
Typical endpoint0

Revision history

RevisionChange
1Initial revision

Shadow Path Format

Cluster 1872 values in the device shadow use this format:

endpoint_id / 1872 / attribute_id

Example:

{
  "0/1872/0": []
}
PartMeaning
0Endpoint ID
1872Ecosystem Information cluster
0DeviceDirectory attribute

Data Types

DeviceTypeStruct (struct)

The device type and revision define endpoint conformance to a release of a device type definition. See the Data Model specification for more information.

FieldNameTypeConformanceConstraintMeaning
0DeviceTypedevtype-idM—This indicates the device type definition.
1Revisionuint16Mmin 1This is the implemented revision of the device type definition.

EcosystemDeviceStruct (struct) — fabric-scoped

FieldNameTypeConformanceConstraintMeaning
0DeviceNamestringOmax length 64Indicates the device's name, which is provided externally if the user consents.
1DeviceNameLastEditepoch-usDeviceName—Indicates the timestamp of when the DeviceName was last modified.
2BridgedEndpointendpoint-nodescdescIndicates the endpoint this EcosystemDeviceStruct is associated with on this Bridge.
3OriginalEndpointendpoint-nodescdescIndicates the endpoint this EcosystemDeviceStruct is associated with on the original device represented by this bridge's Bridged Node.
4DeviceTypeslist of DeviceTypeStructMdescIndicates all of the DeviceTypes within the DeviceTypeList in the Descriptor Cluster associated with this EcosystemDeviceStruct entry.
5UniqueLocationIDslist of stringMmax 64 entries—
6UniqueLocationIDsLastEditepoch-usM——

EcosystemLocationStruct (struct) — fabric-scoped

FieldNameTypeConformanceConstraintMeaning
0UniqueLocationIDstringMmax length 64—
1LocationDescriptorLocationDescriptorStructM—Indicates the location (e.g. living room, driveway) and associated metadata that is provided externally if the user consents.
2LocationDescriptorLastEditepoch-usM—Indicates the timestamp of when the LocationDescriptor was last modified.

Cluster 1872 Attributes

Cluster 1872 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
00x0000DeviceDirectorylist of EcosystemDeviceStructMR (read: manage, fabric-scoped)persisted—
10x0001LocationDirectorylist of EcosystemLocationStructMR (read: manage, fabric-scoped)persisted—

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 — DeviceDirectory

Path example:

0/1872/0

This attribute contains the list of logical devices represented by a Bridged Node. Most of the time this will contain a single entry, but may grow with more complex device compositions (e.g. another bridge.) An empty list indicates that the information is not available.

PropertyValue
Typelist of EcosystemDeviceStruct
ConformanceM
AccessR (read: manage, fabric-scoped)
Qualitiespersisted

Each entry is a EcosystemDeviceStruct (see Data Types).

Example:

{
  "0/1872/0": []
}

Attribute 1 / 0x0001 — LocationDirectory

Path example:

0/1872/1

This attribute contains the list of rooms, areas and groups associated with the DeviceDirectory entries, and must NOT contain locations which are dynamically generated and removed by an ecosystem. (E.g. a location that is generated and removed based on the user being home is not permitted. However, an initially generated location name that does not quickly change is acceptable.) An empty list indicates that the information is not available. LocationDirectory entries is removed if there is no DeviceDirectory that references it.

PropertyValue
Typelist of EcosystemLocationStruct
ConformanceM
AccessR (read: manage, fabric-scoped)
Qualitiespersisted

Each entry is a EcosystemLocationStruct (see Data Types).

Example:

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

Cluster 1872 Commands

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

Cluster 1872 Events

Cluster 1872 defines no events.


SmartphoneKey Notes

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