@matter-server/custom-clusters
v0.5.7
Published
Custom cluster definitions for matter.js based projects
Readme
Custom Clusters
This package contains definitions for vendor-specific (custom) Matter clusters that are not part of the official Matter specification. The OHF community provides the content of these clusters on a best effort basis. There is no guarantee that the definitions are validated or approved by the respective vendors.
Overview
Custom clusters are used by device manufacturers to expose proprietary functionality. This package provides TypeScript definitions that allow the matter.js server to decode and work with these clusters.
Supported Clusters
| Cluster | ID | Vendor | Description |
|-------------------------------------|------------|----------------------------|--------------------------------------------|
| EveCluster | 0x130afc01 | Eve (0x130a/4874) | Energy monitoring, weather, motion sensors |
| InovelliCluster | 0x122ffc31 | Inovelli (0x122f/4961) | LED indicator controls |
| NeoCluster | 0x125dfc11 | Neo (0x125d/4991) | Power metering |
| HeimanCluster | 0x120bfc01 | Heiman (0x120b/4619) | Sensor states, alarms |
| ThirdRealityMeteringCluster | 0x130dfc02 | ThirdReality (0x130d/4877) | Power metering |
| DraftElectricalMeasurementCluster | 0x00000b04 | Various | Draft Matter 1.0 electrical measurement |
Adding a New Custom Cluster
Basic Structure
Create a new file in src/clusters/ (e.g., myvendor.ts):
import { attribute, cluster, uint32, single, bool, int32 } from "@matter/main/model";
@cluster(0xVENDORCLUSTERID)
export class MyVendorCluster {
@attribute(0xATTRIBUTEID1, uint32)
myAttribute?: number;
@attribute(0xATTRIBUTEID2, single)
myFloatAttribute?: number;
@attribute(0xATTRIBUTEID3, bool)
myBoolAttribute?: boolean;
}Export the Cluster
Add an export to src/clusters/index.ts:
export * from "./myvendor.js";Data Types
TypeScript supports some variants of int* and uint* types. Please choose the one that matches your use case and the maximum possible value. If not known, and the usecase might imply higher values, it is safe to use 64bit precision for both signed and unsigned types.
Available Type Imports
import {
// Integer types
int8, // Signed 8-bit integer, JavaScript datatype: `number`
int16, // Signed 16-bit integer, JavaScript datatype: `number`
int32, // Signed 32-bit integer, JavaScript datatype: `number`
int64, // Signed 64-bit integer, JavaScript datatype: `number | bigint`
uint8, // Unsigned 8-bit integer, JavaScript datatype: `number`
uint16, // Unsigned 16-bit integer, JavaScript datatype: `number`
uint32, // Unsigned 32-bit integer, JavaScript datatype: `number`
uint64, // Unsigned 64-bit integer, JavaScript datatype: `number | bigint`
// Floating point
single, // 32-bit float (float32), JavaScript datatype: `number`
double, // 64-bit float (float64), JavaScript datatype: `number`
// Other types
bool, // Boolean, JavaScript datatype: `boolean`
string, // UTF-8 string, JavaScript datatype: `string`
octstr, // Octet string (binary data), JavaScript (matter.js) datatype: `Bytes`
} from "@matter/main/model";How to provide the IDs
Please provide all Ids for clusters or attributes as lowercase Hexadecimal values.
// Good
@cluster(0x130afc01)
@attribute(0x130a0006, int32)Further Annotation options
The annotations also support the following options:
mandatory: Use this to declare an attribute as mandatory. Should mostly not be relevant. By default, all attributes are created optionalnullable: Use this to specify if the attribute is nullable which makes "null" a valid value.listOf(datatype): Use this to declare an attribute to be an array of the given datatype.
More advanced modifier or own datatype definitions can be added on request. Contact us.
Registration
Clusters defined in this package are automatically registered when the package is imported. The register.ts module handles registration with the Matter.js model system.
Building
npm run buildThis compiles the TypeScript definitions to JavaScript in the dist/ directory.
Generate cluster descriptions
Cluster description files for these custom clusters are generated by a separate package (for example, the dashboard package that contains the scripts/generate-descriptions.ts script), not from this directory.
From that package, run:
npm run generate