JavaScript/TypeScript based Matter Implementation

What is Matter?

Matter is a new secure, reliable and local standard protocol for smart/IoT devices launched at the end of 2022 by the Connectivity Standards Alliance.

To learn more about Matter visit https://csa-iot.org/all-solutions/matter/

What is matter.js?

matter.js is a TypeScript/JavaScript implementation of the complete Matter protocol.

Our main goal is to create a robust and compliant library that enables the seamless implementation of Matter-compatible devices, bridges, controllers, and a shell application. This effort is dedicated to improving Matter's accessibility for testers, smart home enthusiasts, and developers of OS-based IoT products. Fostering a second implementation of the Matter standard, aligned with the same specifications, not only expands the ecosystem but also contributes to the validation and increased robustness of the standard itself.

matter.js consists of a set of pure JavaScript base packages without any native dependencies, implementing the Matter protocol and required interfaces in JavaScript, along with extensive typings for The Matter standard and the matter.js APIs. Further packages with Node.js based native dependencies utilize the base package to implement platform-specific parts using Node.js for networking and other necessary native features or add BLE support. Node.js example scripts implement example CLI scripts for devices, bridges or controllers. A Matter Shell allow to interact with Matter devices as controller via a CLI interface.

To use matter.js in your own non-Node.js based projects you need to implement the platform specific parts. See Using matter.js in unsupported JavaScript environments for more details. If you do this please contact us to add your platform to the list of supported platforms.

matter.js employs code generation to ensure a comprehensive model of all Matter Clusters and (soon) device types. This includes typing and documentation, readily available within developers' IDEs, facilitating easy accessibility and adherence to conformance information during coding. This approach allows for easy addition of new clusters and device types, ensuring synchronization with the Matter standard.

How is matter.js used?

matter.js serves various purposes and is employed for:

• Building (commercial) Matter devices and bridges:
  Use JavaScript/TypeScript to create Matter devices or bridges for OS-based IoT products. The extensive typing information and documentation facilitate the easy implementation of required functionality while ensuring synchronization with the Matter specification. If you plan to certify a device based on matter.js please see note below.

• Building Matter controllers:
  Develop Matter controllers with JavaScript/TypeScript for OS-based IoT products. Post-commissioning (including BLE support), controllers can access all data from devices and control them. The API supports development with known typings of all clusters when endpoints and device types are known during development. It also allows generic programmatic access to all clusters and attributes. Typing information of custom clusters can be added to the controller or accessed generically with generic data parsing support. If you plan to build/certify a controller based on matter.js please see note below.

• Rapid prototyping for test and development:
  Enable rapid development of device or controller prototypes for testing and development purposes. JavaScript's nature and the convenient matter.js API make it easy to create prototypes. Testing different feature combinations or endpoint structures can be done quickly using JavaScript testing frameworks.

• Ad-hoc testing of Matter devices using the matter.js shell:
  Employ the Matter Shell application as a controller to interact with Matter devices via a CLI interface. Ideal for manual testing and development purposes.

Explore the versatile capabilities of matter.js and adapt it to your specific use cases!

A note on certification

If you plan to officially certify a device, bridge or controller based on matter.js please contact us via E-Mail or Discord to get the latest information of the certification status of matter.js, supported and not yet supported features and consulting on the certification process.

matter.js successfully passed certification already. There are still thinks to consider and to discuss when you plan to certify.

How to use matter.js

Creat a new project based on matter.js

We provide templates for various matter.js use cases. You can bootstrap a new project in Node.js using npm init:

npm init @matter
Copy

For details on available templates and other options:

npm init @matter help
Copy

Add matter.js to an existing project

To use matter.js you import @matter/main as dependency in your project. This package re-exports functionality from other packages, so it is not necessary to have multiple dependencies. If you need BLE support you can use @matter/nodejs-ble as additional dependency.

npm install @matter/main --save
Copy

If your project is not based on Node.js you need to implement the platform specific parts. See Using matter.js in unsupported JavaScript environments for more details.

Run the examples

The templates we use when you bootstrap a new application are available as examples you can run directly. You can install then in Node.js as follows:

npm install @matter/examples
Copy

Please refer to the Examples readme on how to use the examples: @matter/examples

Extending and contributing to matter.js

We welcome contributions! If you have Node.js installed, prepare your development envirnment as follows:

git clone https://github.com/project-chip/matter.js
cd matter.js
npm install
Copy

This will install all dependencies and create symlinks between the packages, so that it can be used locally. It also builds all packages.

On Windows in order to successfully build all the packages (tested on Windows 11 Pro) make sure that to have installed Node.js 18+, the windows-build-tools and node-gyp version 10. On Non-Windows platforms and having Python 3.12+ installed please also make sure to use npm 10.2.3+.

Connecting with the community

If you have issues please use the GitHub "Issues" of this repository. For questions or idea discussions please use the "Discussions" in this GitHub repository.

Additionally, our "Matter Integrators" Discord server is great place to discuss matter.js, the Matter protocol and how to implement Matter in various environments -- not just JavaScript/Typescript! You can join it here: https://discord.gg/ujmRNrhDuW .

Compatibility with the Matter standard

The Matter standard evolves continuously and delivers two updates per year. matter.js tries to follow the standard as closely as possible. The following list provides an overview which matter.js version is implementing which Matter standard version:

• Matter 1.0: matter.js up to 0.7.x
• Matter 1.1: matter.js 0.8.x - 0.9.x
• Matter 1.2: skipped
• Matter 1.3: matter.js 0.10.x and higher

Compatibility with popular ecosystems

Devices created with matter.js/matter-node.js have been tested with:

• Apple iOS (iPhone or iPad) and tvOS 16 (Apple TV) - "Home" app by Apple: Fully working
• Google Home Ecosystem (Android or Google Nest smart speakers/display) - "Google Home" app: Fully working
• Amazon Alexa (Amazon Echo smart speakers/displays) : Fully working
• Tuya Smart (SmartLife) app: Fully working
• Samsung SmartThings (Station or Hub v2 and later): Fully working
• LG ThinQ: Fully working, beside glitches in LG software sometimes
• Home Assistant - Matter integration: Fully working
• Aqara Hub M3: Aqara currently seem to not allow to pair test devices, so matter.js open source devices are not working with Aqara Hub M3. Please contact Aqara and request this feature.
• Yandex Smart Home: Yandex currently seem to not allow to pair test devices, so matter.js open source devices are not working with Yandex SMart Home. Please contact Yandex and request this feature.
• flic: Fully working

Matter.js based projects show up as "uncertified test devices" in the ecosystems. This is because the devices are not certified by the Connectivity Standards Alliance (CSA) and are not part of the official Matter certification program. However, the devices are fully functional and can be used in the ecosystems. The ecosystems usually inform the user about the uncertified status of the device. Please see Pairing and Usage Information for more details.

We also collected a list of tested device types on ecosystem.This is a compilation of published information by the ecosystems and own community tests.

Each ecosystem have their own specialities, see Pairing and Usage Information for more details.

When you plan to use matter.js as controller with Thread based devices please see How to use Thread based devices with matter.js Controller/Shell for more details.

We also collected some Troubleshooting information to help you with common issues.

A list ok known issues with some ecosystems can be found in KNOWN_ISSUES.md.

matter.js/matter-node.js as Controller was successfully tested with Chip example apps and several production devices (see here ).

Please report any outdated or newly discovered information on compatible ecosystems, devices, and device types or issues.

Overview of our code structure

This repository contains multiple packages (and because of this it is a monorepo). The packages are contained in the packages directory and are all published separately to NPM.

Please see the respective README files in the package directories for more information about their content.

For each package the API Documentation is updated on each official release, but can also be built locally using npm run build-doc.

Beside these packages that are published to npm there are also some packages that are not published to npm and exist as folders in the root directory:

• chip-testing: A set of scripts to allow to run the Chip-Tool-Certification tests against a matter-node.js based devices. These tests are executed on GitHub CI automatically.
• codegen: A set of scripts to generate code for the Matter code model, clusters and device types.
• model: Contains all pre-parsed information for the Matter models used to generate code for the code model, clusters and device types. It also allows to define local overrides to adjust incomplete or wrong information in the Matter models.

This repository uses the workspaces feature from npm to manage the dependencies between the packages. Because of this please only use npm install on the root of the repository. This will install all the dependencies for all the packages and also take care to create relevant symlinks between the packages.

Additionally, it uses typescript project references to allow IDE support for the dependencies. These dependencies need to be added to the tsconfig.json files if needed.

You can build and test the packages separately or all by using npm run build or npm run test on root package level. With npm run build-clean you can build all packages from scratch.

Release tags

To allow a simple use of the matter.js Monorepo based project in other projects, we publish all packages separately to NPM. There are two available release tags on NPM:

• latest: This is the default NPM tag and contains official released versions of the packages. This is the recommended tag to use in your projects. Whenever we build a new official release also the docs are updated and available in the repository.
• dev: This tag contains a nightly build of the project and is updated every night if there were changes in the repository. This is only for testing and development purposes and should not be used for real production use cases. Use e.g. npm install @matter/main@dev to install the latest nightly build of @matter/main.

Code style

matter.js relies very much on TypeScript and tries to be as type safe as possible. Please prevent using ts-ignore or other "hacks" as best as possible and try to find and fix the real typing issue if you encounter cases where you need to use them. YOu can also alwayys join discord or as in GitHub discussions if you need help.

The project contains eslint as linter and prettier as formatter. The configuration files are located in the root directory and are valid for all packages.

The following commands are available:

• npm run lint: runs eslint on all packages and outputs the results and errors
• npm run lint-fix: runs eslint on all packages and tries to fix the errors
• npm run format: runs typescript-formatter on all packages and formats the code. Files will be changed in place.
• npm run format-verify: runs typescript-formatter on all packages and checks if the code is formatted correctly. If not it will output the files that need to be formatted.

If you want to contribute to the project please make sure to check linting and formatting before creating a PR. The GitHub CI also verifies this and will fail if the code is not formatted correctly.

Building

You can use npm run build on the root level to build all packages in an incremental way. This will only build the changed files.

You can use npm run build-clean on the root level to build all packages from scratch.

Testing

You can use npm run test on the root level to run all tests for all packages.

Special testing using the Chip-Tool-Certification tests is available in the package matter-node.js-examples. Please refer to the README.md in the package for more details.

API documentation

You can use npm run build-doc on the root level to generate the API documentation for all packages in directory doc.

Current status

We are about to complete the basic certifiable feature set. Right now in the low level APIs all clusters are supported and all kind of devices can be built, but not with pre-defined cluster logic. See the Roadmap for status and next planned steps.

Using matter.js in unsupported JavaScript environments

matter.js is fully functional in Node.js. We test some portions in web browsers and offer (WIP) experimental React Native support. For other environments you will need to implement a few platform-specific abstractions:

• BigInt/UInt8Array: matter.js relies on various ES6 JavaScript language features including BigInt and UInt8Array. If your platform does not support this you need to add a polyfill.
• Network: The Network implementation needs to provide UDP server and client functionality. This is a core requirement. The Network Interface needs to be implemented which includes methods to query network interfaces of the system and to use UDP sockets.
• Crypto: Until we have a pure JavaScript implementation of the required crypto functions, a native implementation is needed. The Crypto Interface needs to be implemented which includes methods to generate random numbers, generate keys and to encrypt/decrypt data with various algorithms.
• Storage: The Storage implementation needs to provide a way to store and retrieve data, easiest in a key-value form. The Storage Interface needs to be implemented which includes methods to store and retrieve data.
• Time: We provided a time implementation compatible with any modern JS environment. You can replace our implementation by implementing he Time Interface needs to be implemented which includes methods to get the current time in milliseconds.
• BLE: If your implementation is not Ethernet based or Pre-Connected to an IP network you need to provide a BLE implementation. The BLE Interface needs to be implemented which includes methods to start and stop BLE advertising and to connect to a BLE device. Depending on if you implement a Controller or Device you need to implement the Peripheral and Broadcaster (Device) or Central and Scanner (Controller) BLE interfaces. For a device the platform you implement needs to allow to send custom "Manufacturer data" in the BLE advertising packet!
• Wi-Fi/Thread Commissioning: To implement a device that requires commissioning to join a network, you must provide a commissioning method for Wifi or thread. This must include methods to scan for networks, configure the device for a network and to connect to a network. The implementation in this case must implement WifiNetworkCommissioning and/or ThreadNetworkCommissioning clusters.
• Intl: For some internationalization features (e.g. reporting locale or calendar type) we use standard JavaScript internationalization APIs. If your platform does not support these will need to add polyfills.

The following reference implementation and code references are available as basis for own platform implementations:

• For Network, Crypto, Storage and Time functionality you can use the Node.js implementations provided by @matter/nodejs as reference.
• For BLE functionality you can use the Node.js implementations provided by @matter/nodejs-ble as reference.
• For Wi-Fi/Thread Commissioning functionality you can use the Node.js DeviceNode example script which contains a static "testing only" (but API complete for Wifi) reference.

If you implement a specific platform we would be happy about a PR with the code, so that also other community members can benefit from it.

matter.js-based projects

The following projects are available on any platform with access to Node.js 18+:

• @matter/nodejs: a Matter client / server running on node.js compatible with HA (Android / iOs support in progress)
• @matter/nodejs-shell: a Matter Shell script to allow to interact with Matter devices as controllers via a CLI interface
• node-red-matter-bridge: a Node-Red node to expose a bridge
• node-red-matter: a Node-Red node for devices and controllers (outdated)
• zigbee-matter-bridge: a Zigbee to Matter Bridge
• matterbridge: a matter.js plugin manager with 7 example plugins
  • matterbridge-zigbee2mqtt: a matterbridge production-level plugin that expose all zigbee2mqtt devices and groups to Matter
  • matterbridge-somfy-tahoma: a matterbridge production-level plugin that expose all somfy tahoma screens to Matter
  • ... and more plugins