matterbridge 3.0.8-dev-20250622-9a6255a → 3.0.8-dev-20250624-5abb0bb

package/CHANGELOG.md

@@ -16,7 +16,7 @@ If you like this project and find it useful, please consider giving it a star on
 
 - [DevContainer]: Added support for the **Matterbridge Dev Container** with an optimized named volume for `node_modules`.
 - [GitHub]: Added GitHub issue templates for bug reports and feature requests.
-- [Systemd]: Added a systemd service file for Matterbridge.
+- [Systemd]: Added a systemd service file for Matterbridge in the systemd directory.
 - [ESLint]: Refactored ESLint configuration for TypeScript and improved plugin integration.
 - [ESLint]: Added the plugins `eslint-plugin-promise`, `eslint-plugin-jsdoc`, and `@vitest/eslint-plugin`.
 - [Vitest]: Added Vitest for TypeScript project testing. It will replace Jest, which does not work correctly with ESM module mocks.
@@ -24,8 +24,10 @@ If you like this project and find it useful, please consider giving it a star on
 
 ### Changed
 
-- [package]: Updated dependencies and refactored scripts.
+- [package]: Updated package to Automator v. 2.0.0.
+- [package]: Updated dependencies.
 - [storage]: Bumped `node-storage-manager` to 2.0.0.
+- [logger]: Bumped `node-ansi-logger` to 3.1.1.
 
 ### Fixed
 

package/README-DEV.md

@@ -18,13 +18,13 @@
 
 The easiest way is to clone the [Matterbridge Plugin Template](https://github.com/Luligu/matterbridge-plugin-template) that has **Dev Container support for instant development environment** and all tools and extensions (like Node.js, npm, TypeScript, ESLint, Prettier, Jest and Vitest) already loaded and configured.
 
-Then change the name (keep matterbridge- at the beginning of the name), version, description, author, homepage, repository, bugs and funding in the package.json.
+After you clone it locally, change the name (keep always matterbridge- at the beginning of the name), version, description, author, homepage, repository, bugs and funding in the package.json.
 
-It is possible to add two custom properties to the package.json: **help** and **changelog** with a url that will be used in the frontend instead of the default (/blob/main/README.md and /blob/main/CHANGELOG.md).
+It is also possible to add two custom properties to the package.json: **help** and **changelog** with a url that will be used in the frontend instead of the default (/blob/main/README.md and /blob/main/CHANGELOG.md).
 
 Add your plugin logic in module.ts.
 
-The Matterbridge Plugin Template has an already configured Jest / Vitest test unit (coverage 100%) that you can expand while you add your own plugin logic.
+The Matterbridge Plugin Template has an already configured Jest / Vitest test unit (with 100% coverage) that you can expand while you add your own plugin logic.
 
 It also has a workflow configured to run on push and pull request that build, lint and test the plugin on node 20, 22 and 24 with ubuntu, macOS and windows.
 
@@ -80,13 +80,13 @@ Matterbridge exports from:
 
 - All matter.js types.
 
-### WARNING \***\*\*\*\*\***
+### \***\*\*\*\*\*** WARNING \***\*\*\*\*\***
 
 A plugin must never install or import from `@matter` or `@project-chip` directly (neither as a dependency, devDependency, nor peerDependency), as this leads to a second instance of `matter.js`, causing instability and unpredictable errors such as "The only instance is Endpoint".
 
 Additionally, when Matterbridge updates the `matter.js` version, it should be consistent across all plugins.
 
-### WARNING \***\*\*\*\*\***
+### \***\*\*\*\*\*** WARNING \***\*\*\*\*\***
 
 A plugin must never install Matterbridge (neither as a dependency, devDependency, nor peerDependency).
 
@@ -100,9 +100,25 @@ Matterbridge must be linked to the plugin in development only. At runtime the pl
 }
 ```
 
-If you don't use Dev Container from the Matterbridge Plugin Template, on the machine you use for development of your plugin, you need to clone matterbridge, built it locally and link it globally (npm link from the matterbridge package root).
+If you don't use Dev Container from the Matterbridge Plugin Template, on the host you use for the development of your plugin, you need to clone matterbridge, built it locally and link it globally (npm link from the matterbridge package root).
+
+```bash
+git clone https://github.com/Luligu/matterbridge.git
+cd matterbridge
+npm install
+npm run build
+npm link
+```
+
+If you want to develop a plugin using the dev branch of matterbridge (I suggest you do it).
 
-If you want to develop a plugin using the dev branch of matterbridge (I suggest you do it), you have to clone the dev branch of matterbridge, build it locally and link it (npm run deepCleanBuild does all necessary steps).
+```bash
+git clone -b dev https://github.com/Luligu/matterbridge.git
+cd matterbridge
+npm install
+npm run build
+npm link
+```
 
 Always keep your local instance of matterbridge up to date.
 
@@ -116,19 +132,19 @@ To install i.e. https://github.com/Luligu/matterbridge-example-accessory-platfor
 
 On windows:
 
-```
+```powershell
 cd $HOME\Matterbridge
 ```
 
 On linux or macOS:
 
-```
+```bash
 cd ~/Matterbridge
 ```
 
 then clone the plugin
 
-```
+```bash
 git clone https://github.com/Luligu/matterbridge-example-accessory-platform
 cd matterbridge-example-accessory-platform
 npm install
@@ -138,7 +154,7 @@ npm run build
 
 then add the plugin to Matterbridge
 
-```
+```bash
 matterbridge -add .
 ```
 

package/README.md

@@ -15,25 +15,25 @@
 
 Matterbridge is a Matter plugin manager.
 
-It allows you to have all your Matter devices up and running in a couple of minutes without
-having to deal with the pairing process of each single device.
+It allows you to have all your Matter devices up and running in a couple of minutes without having to deal with the pairing process for each individual device.
 
-The developer just focuses on the device development extending the provided classes.
+Developers can focus solely on device development by extending the provided classes.
 
-Just pair Matterbridge once, and it will load all your registered plugins.
+Simply pair Matterbridge once, and it will load all your registered plugins.
 
-This project aims to allow the porting of homebridge plugins to matterbridge plugins without recoding everything ([Development](README-DEV.md)).
+This project aims to enable porting Homebridge plugins to Matterbridge plugins without having to recode everything ([Development](README-DEV.md)).
 
-It creates a device to pair in any ecosystem like Apple Home, Google Home, Amazon Alexa, Home Assistant or
-any other ecosystem supporting Matter.
+The easiest way to start create a new plugin is to clone the [Matterbridge Plugin Template](https://github.com/Luligu/matterbridge-plugin-template) which has **Dev Container support for instant development environment** and all tools and extensions (like Node.js, npm, TypeScript, ESLint, Prettier, Jest and Vitest) already loaded and configured.
+
+Matterbridge creates a device that can be paired with any ecosystem, such as Apple Home, Google Home, Amazon Alexa, Home Assistant, or any other platform supporting Matter.
 
 You don't need a hub or a dedicated new machine.
 
-No complex setup just copy paste the installation scripts.
+No complex setup: just copy paste the installation scripts.
 
-Matterbridge is light weight and run also on slow Linux machine with 512MB of memory.
+Matterbridge is lightweight and also runs on slow Linux machines with as little as 512MB of memory.
 
-It runs perfectly on macOS and Windows too.
+It also runs perfectly on macOS and Windows.
 
 If you like this project and find it useful, please consider giving it a star on GitHub at https://github.com/Luligu/matterbridge and sponsoring it.
 
@@ -45,7 +45,7 @@ If you like this project and find it useful, please consider giving it a star on
 
 The project is build on top of https://github.com/project-chip/matter.js.
 
-A special thank to Apollon77 for his incredible work.
+A special thanks to Apollon77 for his incredible work.
 
 ## Discord
 

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "matterbridge",
-  "version": "3.0.8-dev-20250622-9a6255a",
+  "version": "3.0.8-dev-20250624-5abb0bb",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "matterbridge",
-      "version": "3.0.8-dev-20250622-9a6255a",
+      "version": "3.0.8-dev-20250624-5abb0bb",
       "license": "Apache-2.0",
       "dependencies": {
         "@matter/main": "0.14.0",
@@ -14,7 +14,7 @@
         "express": "5.1.0",
         "glob": "11.0.3",
         "multer": "2.0.1",
-        "node-ansi-logger": "3.0.1",
+        "node-ansi-logger": "3.1.1",
         "node-persist-manager": "2.0.0",
         "ws": "8.18.2"
       },
@@ -1349,12 +1349,13 @@
       }
     },
     "node_modules/node-ansi-logger": {
-      "version": "3.0.1",
-      "resolved": "https://registry.npmjs.org/node-ansi-logger/-/node-ansi-logger-3.0.1.tgz",
-      "integrity": "sha512-Nx7nkO6Sby8Eti1UFFdff3gImEC35izuvf+aRFh3mrDZ8hgXM/cZdflkpDMnDdxnabYl91LVi4RhB/dm5Yk9iA==",
-      "license": "MIT",
+      "version": "3.1.1",
+      "resolved": "https://registry.npmjs.org/node-ansi-logger/-/node-ansi-logger-3.1.1.tgz",
+      "integrity": "sha512-tFeCSxwiRg5XaNda5nC27alzraZP76nLtUk1JDZqb9byhW4WYaSGL7/lmxFHEI16gypQDMEYljuF+wcG+cPPHw==",
+      "hasShrinkwrap": true,
+      "license": "Apache-2.0",
       "engines": {
-        "node": ">=18.0.0"
+        "node": ">=18.0.0 <19.0.0 || >=20.0.0 <21.0.0 || >=22.0.0 <23.0.0 || >=24.0.0 <25.0.0"
       },
       "funding": {
         "type": "buymeacoffee",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "matterbridge",
-  "version": "3.0.8-dev-20250622-9a6255a",
+  "version": "3.0.8-dev-20250624-5abb0bb",
   "description": "Matterbridge plugin manager for Matter",
   "author": "https://github.com/Luligu",
   "license": "Apache-2.0",
@@ -103,7 +103,7 @@
     "express": "5.1.0",
     "glob": "11.0.3",
     "multer": "2.0.1",
-    "node-ansi-logger": "3.0.1",
+    "node-ansi-logger": "3.1.1",
     "node-persist-manager": "2.0.0",
     "ws": "8.18.2"
   }