[3.5.6] - 2026-02-27
Dev Breaking Changes
- [rootNode]: The serialNumber and uniqueId for accessory plugins in childbridge mode, and for devices with mode = server, are now taken from the device. These values are persisted in storage and cannot be changed later.
- [devContainer]: Add the guide to pair Matterbridge with Dev Container
- [devContainer]: Add the new dev container setup.
- [devContainer]: Add the new reflector dev container setup.
Dev News
- [binding]: Add for test only MatterbridgeBindingServer.
- [docker]: Add luligu/matterbridge:chip-test image (400MB): it is based on Ubuntu LTS, Node.Js 24 LTS and includes connectedhomeip repository with chip-tool, chip-cert and all packages requierd to run yaml and phyton tests. The matterbridge instance inside the container is already paired for yaml and python test. In the container, the chip environment and phyton environment are already active. Just open a shell inside the container with bash and run the yaml or phyton tests. Matterbridge frontend is bound on port 8283. No volumes or port mapping needed.
- [styleguide]: Add STYLEGUIDE.md.
- [contributing]: Add CONTRIBUTING.md.
Added
- [nvm]: Add detection for Nvm (not for production with systemd service).
- [nvm]: Clarify in systemd guides that Nvm cannot be used for production.
Changed
- [package]: Update dependencies.
- [package]: Bump packages to
automatorv.3.1.0. - [package]: Bump
eslintto v.10.0.2. - [package]: Bump
typescript-eslintto v.8.56.1. - [package]: Replace
eslint-plugin-importwitheslint-plugin-simple-import-sort. - [package]: Bump
matter.jsto v.0.16.10. Thanks matter.js team.
Fixed
- [advertise]: Remove no more used timeout of 15 minutes.