matterbridge 3.3.7-dev-20251108-f254812 → 3.3.7-dev-20251109-a306ab9

package/CHANGELOG.md

@@ -28,7 +28,7 @@ Advantages:
 - individual plugin isolation in childbridge mode;
 - ability to update the plugin in childbridge mode without restarting matterbridge;
 
-## [3.3.7] - 2025-11-07
+## [3.3.7] - 2025-11-08
 
 ### Breaking Changes
 
@@ -37,7 +37,7 @@ Advantages:
 ### Added
 
 - [matterbridge]: Added a first check for plugin existence (docker pull or Hass add-on rebuild) and reinstall it before parsing the plugin. The error messages have been removed.
-- [service]: Added [configuration](README-SERVICE-OPT.md) to run matterbridge as a daemon with systemctl (Linux only) and with private global node_modules (user matterbridge and no sudo required).
+- [service]: Added [configuration](README-SERVICE-OPT.md) to run matterbridge as a daemon with systemctl (Linux only), private global node_modules, user/group matterbridge and no sudo required.
 
 ### Changed
 

package/README-SERVICE-OPT.md

@@ -20,14 +20,16 @@
 
 The advantage of this setup is that the global node_modules are private for matterbridge and sudo is not required.
 
-The service runs with user matterbridge and the system has full protection.
+The service runs with group and user matterbridge and the system has full protection.
 
 The storage position is **not compatible** with the traditional setup (~/Matterbridge ~/.matterbridge ~/.mattercert).
 
 ### 1 - Create the matterbridge user and group
 
 ```bash
+# ✅ Create the matterbridge group
 sudo groupadd --system matterbridge 2>/dev/null || true
+# ✅ Create the matterbridge user
 sudo useradd  --system \
   --home-dir /opt/matterbridge \
   --shell /usr/sbin/nologin \
@@ -42,10 +44,10 @@ This will create the required directories if they don't exist
 ```bash
 cd ~
 # ✅ Safe precaution if matterbridge was already running with the traditional setup
-sudo systemctl stop matterbridge
-# ✅ We need to uninstall from the global node_modules
-sudo npm uninstall matterbridge -g
-# ✅ Creates all needed dirs
+sudo systemctl stop matterbridge 2>/dev/null || true
+# ✅ Safe precaution we need to uninstall from the global node_modules
+sudo npm uninstall matterbridge -g 2>/dev/null || true
+# ✅ Creates all required directories
 sudo mkdir -p /opt/matterbridge /opt/matterbridge/Matterbridge /opt/matterbridge/.matterbridge /opt/matterbridge/.mattercert /opt/matterbridge/.npm-global
 # ✅ Ensures ownership
 sudo chown -R matterbridge:matterbridge /opt/matterbridge /opt/matterbridge/Matterbridge /opt/matterbridge/.matterbridge /opt/matterbridge/.mattercert /opt/matterbridge/.npm-global
@@ -55,7 +57,7 @@ sudo chmod -R 755 /opt/matterbridge /opt/matterbridge/Matterbridge /opt/matterbr
 sudo -u matterbridge mkdir -p /opt/matterbridge/.npm-global/bin
 # ✅ Install matterbridge in the private global node_modules
 sudo -u matterbridge NPM_CONFIG_PREFIX=/opt/matterbridge/.npm-global npm install matterbridge --omit=dev --verbose --global
-# ✅ Create a link to matterbridge bin
+# ✅ Create a link to matterbridge bins
 sudo ln -sf /opt/matterbridge/.npm-global/bin/matterbridge /usr/bin/matterbridge
 sudo ln -sf /opt/matterbridge/.npm-global/bin/mb_mdns /usr/bin/mb_mdns
 sudo ln -sf /opt/matterbridge/.npm-global/bin/mb_coap /usr/bin/mb_coap
@@ -69,7 +71,21 @@ matterbridge --version
 
 The storage position is **not compatible** with the traditional setup (~/Matterbridge ~/.matterbridge ~/.mattercert).
 
-You may want to copy the contents to the new directories.
+If you are migrating from the traditional service setup, before removing the old diretories, you may want to copy the contents of ~/Matterbridge ~/.matterbridge ~/.mattercert to the new directories /opt/matterbridge/Matterbridge /opt/matterbridge/.matterbridge /opt/matterbridge/.mattercert.
+
+Copy the old diretories content
+
+```bash
+sudo cp -a ~/Matterbridge/. /opt/matterbridge/Matterbridge/
+sudo cp -a ~/.matterbridge/. /opt/matterbridge/.matterbridge/
+sudo cp -a ~/.mattercert/. /opt/matterbridge/.mattercert/
+```
+
+Remove the old diretories
+
+```bash
+sudo rm -rf ~/Matterbridge ~/.matterbridge ~/.mattercert ~/.npm-global
+```
 
 ### 3 - Create a systemctl configuration file for Matterbridge
 

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "matterbridge",
-  "version": "3.3.7-dev-20251108-f254812",
+  "version": "3.3.7-dev-20251109-a306ab9",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "matterbridge",
-      "version": "3.3.7-dev-20251108-f254812",
+      "version": "3.3.7-dev-20251109-a306ab9",
       "license": "Apache-2.0",
       "dependencies": {
         "@matter/main": "0.15.6",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "matterbridge",
-  "version": "3.3.7-dev-20251108-f254812",
+  "version": "3.3.7-dev-20251109-a306ab9",
   "description": "Matterbridge plugin manager for Matter",
   "author": "https://github.com/Luligu",
   "license": "Apache-2.0",