matterbridge 3.9.3 → 3.9.4-dev-20260706-08fe8ef

package/CHANGELOG.md

@@ -58,6 +58,33 @@ These classes will run as threads in the next releases:
 - all plugins in bridge mode;
 - each plugin in childbridge mode;
 
+## [3.9.4] - Dev branch
+
+### Added
+
+- [matterbridge]: Add running statistics and improper shutdown detection.
+- [matter]: Add Matter 1.6.0 specs and the [Matter 1.6.0 changes from 1.5.1](Matter-1.6.0.md) document.
+
+### Changed
+
+- [matterbridge]: Bump `matterbridge` version to v.3.9.4.
+- [matterbridge]: Update dependencies.
+- [matterbridge]: Bump `@types/node` to v.26.1.0.
+- [matterbridge]: Bump `@typescript/native-preview` to v.7.0.0-dev.20260703.1.
+- [matterbridge]: Bump `oxfmt` to v.0.57.0.
+- [matterbridge]: Bump `oxlint` to v.1.72.0.
+- [matterbridge]: Bump `oxlint-tsgolint` to v.0.24.0.
+- [package]: Apply style to all files.
+- [service]: Update service configuration example `systemd/matterbridge.service`.
+- [service]: Update service configuration guides.
+- [matterbridge]: Bump `@matter/main` to v.0.17.4.
+- [matter]: Update the data model script to support Matter 1.6.0 generation.
+
+- [frontend]: Bump `frontend` version to v.3.5.2.
+- [frontend]: Update dependencies.
+
+<a href="https://www.buymeacoffee.com/luligugithub"><img src="https://matterbridge.io/assets/bmc-button.svg" alt="Buy me a coffee" width="80"></a>
+
 ## [3.9.3] - 2026-07-03
 
 ### Warning

package/README-SERVICE-LOCAL.md

@@ -59,10 +59,12 @@ chmod -R 755 ~/Matterbridge ~/.matterbridge ~/.mattercert ~/.npm-global ~/.npm-c
 npm install matterbridge --omit=dev --verbose --global --prefix=~/.npm-global --cache=~/.npm-cache
 # ✅ Create a link to matterbridge bin
 sudo ln -sf /home/$USER/.npm-global/bin/matterbridge /usr/local/bin/matterbridge
-# ✅ Create a link to mb_mdns bin
-sudo ln -sf /home/$USER/.npm-global/bin/mb_mdns /usr/local/bin/mb_mdns
-# ✅ Create a link to mb_coap bin
-sudo ln -sf /home/$USER/.npm-global/bin/mb_coap /usr/local/bin/mb_coap
+# ✅ Create a link to mb-health bin
+sudo ln -sf /home/$USER/.npm-global/bin/mb-health /usr/local/bin/mb-health
+# ✅ Create a link to mb-mdns bin
+sudo ln -sf /home/$USER/.npm-global/bin/mb-mdns /usr/local/bin/mb-mdns
+# ✅ Create a link to mb-coap bin
+sudo ln -sf /home/$USER/.npm-global/bin/mb-coap /usr/local/bin/mb-coap
 # ✅ Clear bash command cache as a precaution
 hash -r
 # ✅ Check which matterbridge
@@ -84,8 +86,8 @@ Add the following to this file, **replacing 5 times (!) USER with your user name
 ```text
 [Unit]
 Description=matterbridge
-After=network.target
-Wants=network.target
+After=network-online.target
+Wants=network-online.target
 StartLimitIntervalSec=60
 StartLimitBurst=5
 
@@ -95,9 +97,13 @@ Environment="NPM_CONFIG_PREFIX=/home/<USER>/.npm-global"
 Environment="NPM_CONFIG_CACHE=/home/<USER>/.npm-cache"
 ExecStart=matterbridge --service --nosudo
 WorkingDirectory=/home/<USER>/Matterbridge
-StandardOutput=inherit
-StandardError=inherit
+# Logs go to the journal (should be persistent). Read with: journalctl -u matterbridge -n 1000 -f --output cat
+StandardOutput=journal
+StandardError=journal
+SyslogIdentifier=matterbridge
 Restart=always
+RestartSec=5
+TimeoutStopSec=60
 User=<USER>
 Group=<USER>
 
@@ -127,18 +133,16 @@ One possible fix, add this line to the existing [Service] section:
 Environment="NODE_OPTIONS=--dns-result-order=ipv4first"
 ```
 
-If you use the frontend with **-ssl** --frontend 443 and get an error message: "Port 443 requires elevated privileges",
-add this:
+If you use the frontend with --ssl --frontend 443 and get an error message: "Port 443 requires elevated privileges",
+add this line to the existing [Service] section:
 
 ```text
-[Service]
 AmbientCapabilities=CAP_NET_BIND_SERVICE
 ```
 
-If you use the **matterbridge-bthome** plugin add this:
+If you use the matterbridge-bthome plugin add this line to the existing [Service] section:
 
 ```text
-[Service]
 AmbientCapabilities=CAP_NET_BIND_SERVICE CAP_NET_RAW CAP_NET_ADMIN
 ```
 

package/README-SERVICE-OPT.md

@@ -88,10 +88,10 @@ matterbridge --version
 
 The storage position is **not compatible** with the traditional setup (~/Matterbridge ~/.matterbridge ~/.mattercert).
 
-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.
-This will save all the plugin configs and the fabrics but you need to remove all plugins and readd them cause the path will be different.
+If you are migrating from the traditional service setup, before removing the old directories, you may want to copy the contents of ~/Matterbridge ~/.matterbridge ~/.mattercert to the new directories /opt/matterbridge/Matterbridge /opt/matterbridge/.matterbridge /opt/matterbridge/.mattercert.
+This will save all the plugin configs and the fabrics, but you need to remove all plugins and add them again because the path will be different.
 
-Copy the old diretories content
+Copy the old directories content
 
 ```bash
 sudo cp -a ~/Matterbridge/. /opt/matterbridge/Matterbridge/
@@ -99,7 +99,7 @@ sudo cp -a ~/.matterbridge/. /opt/matterbridge/.matterbridge/
 sudo cp -a ~/.mattercert/. /opt/matterbridge/.mattercert/
 ```
 
-Remove the old diretories
+Remove the old directories
 
 ```bash
 sudo rm -rf ~/Matterbridge ~/.matterbridge ~/.mattercert ~/.npm-global
@@ -118,8 +118,8 @@ Add the following to this file:
 ```text
 [Unit]
 Description=matterbridge
-After=network.target
-Wants=network.target
+After=network-online.target
+Wants=network-online.target
 StartLimitIntervalSec=60
 StartLimitBurst=5
 
@@ -130,9 +130,13 @@ Environment="NPM_CONFIG_PREFIX=/opt/matterbridge/.npm-global"
 Environment="NPM_CONFIG_CACHE=/opt/matterbridge/.npm-cache"
 ExecStart=matterbridge --service --nosudo
 WorkingDirectory=/opt/matterbridge/Matterbridge
-StandardOutput=inherit
-StandardError=inherit
+# Logs go to the journal (should be persistent). Read with: journalctl -u matterbridge -n 1000 -f --output cat
+StandardOutput=journal
+StandardError=journal
+SyslogIdentifier=matterbridge
 Restart=always
+RestartSec=5
+TimeoutStopSec=60
 User=matterbridge
 Group=matterbridge
 NoNewPrivileges=true
@@ -167,18 +171,16 @@ One possible fix, add this line to the existing [Service] section:
 Environment="NODE_OPTIONS=--dns-result-order=ipv4first"
 ```
 
-If you use the frontend with **-ssl** -frontend 443 and get an error message: "Port 443 requires elevated privileges",
-add this:
+If you use the frontend with --ssl --frontend 443 and get an error message: "Port 443 requires elevated privileges",
+add this line to the existing [Service] section:
 
 ```text
-[Service]
 AmbientCapabilities=CAP_NET_BIND_SERVICE
 ```
 
-If you use the **matterbridge-bthome** plugin add this:
+If you use the matterbridge-bthome plugin add this line to the existing [Service] section:
 
 ```text
-[Service]
 AmbientCapabilities=CAP_NET_BIND_SERVICE CAP_NET_RAW CAP_NET_ADMIN
 ```
 

package/README-SERVICE.md

@@ -55,17 +55,17 @@ Create a systemctl configuration file for Matterbridge
 sudo nano /etc/systemd/system/matterbridge.service
 ```
 
-Add the following to this file, replacing 3 times (!) USER with your user name (e.g. WorkingDirectory=/home/pi/Matterbridge, User=pi and Group=pi):
+Add the following to this file, **replacing 3 times (!) USER with your user name** (e.g. WorkingDirectory=/home/pi/Matterbridge, User=pi and Group=pi):
 
 You may need to adapt the configuration to your setup:
 
-- ExecStart on some linux distribution can also be ExecStart==/usr/bin/matterbridge --service
+- On some Linux distributions, ExecStart can also be ExecStart=/usr/bin/matterbridge --service
 
 ```text
 [Unit]
 Description=matterbridge
 After=network-online.target
-Wants=network.target
+Wants=network-online.target
 StartLimitIntervalSec=60
 StartLimitBurst=5
 
@@ -73,9 +73,13 @@ StartLimitBurst=5
 Type=simple
 ExecStart=matterbridge --service
 WorkingDirectory=/home/<USER>/Matterbridge
-StandardOutput=inherit
-StandardError=inherit
+# Logs go to the journal (should be persistent). Read with: journalctl -u matterbridge -n 1000 -f --output cat
+StandardOutput=journal
+StandardError=journal
+SyslogIdentifier=matterbridge
 Restart=always
+RestartSec=5
+TimeoutStopSec=60
 User=<USER>
 Group=<USER>