matterbridge 3.4.2-dev-20251206-00998e1 → 3.4.3-dev-20251206-06686b7

package/CHANGELOG.md

@@ -28,6 +28,28 @@ Advantages:
 - individual plugin isolation in childbridge mode;
 - ability to update the plugin in childbridge mode without restarting matterbridge;
 
+## [3.4.3] - 2025-12-12
+
+### Added
+
+- [frontend]: Added homepage icon and link to https://matterbridge.io/.
+
+### Changed
+
+- [package]: Updated dependencies.
+- [frontend]: Bumped `frontend` version to v.3.3.4.
+- [package]: Changed homepage to https://matterbridge.io.
+- [frontend]: Changed help link to https://matterbridge.io/README.html.
+- [frontend]: Changed changelog link to https://matterbridge.io/CHANGELOG.html.
+- [frontend]: Changed changelog icon to HistoryOutlinedIcon.
+
+### Fixed
+
+- [matterbridge]: Plugin version is now updated even if the plugin is disabled.
+- [matterbridge]: Fixed default delay and fixed_delay to 120 seconds.
+
+<a href="https://www.buymeacoffee.com/luligugithub"><img src="https://matterbridge.io/bmc-button.svg" alt="Buy me a coffee" width="80"></a>
+
 ## [3.4.2] - 2025-12-05
 
 ### Race condition

package/README-SERVICE-LOCAL.md

@@ -18,14 +18,14 @@
 
 ## Run matterbridge as a daemon with systemctl (Linux only) with local global node_modules
 
-The advantage of this setup is that the global node_modules are private for the user and sudo is not required.
-
-This configuration uses a private separate npm cache.
+The advantage of this setup is that the global node_modules and npm cache are private for the user and sudo is not required.
 
 The service runs rootless like the current user.
 
 The storage position is compatible with the traditional setup (~/Matterbridge ~/.matterbridge ~/.mattercert).
 
+Also various scripts don't work if you choose this configuration.
+
 ### First create the Matterbridge directories and set the correct permissions
 
 This will create the required directories if they don't exist

package/README-SERVICE-OPT.md

@@ -18,9 +18,7 @@
 
 ## Run matterbridge as a daemon with systemctl (Linux only) with user matterbridge and private global node_modules
 
-The advantage of this setup is that the global node_modules are private for matterbridge and sudo is not required.
-
-This configuration uses a private separate npm cache.
+The advantage of this setup is that the global node_modules and npm cache are private for matterbridge and sudo is not required.
 
 The service runs with group and user matterbridge and the system has full protection.
 
@@ -28,7 +26,7 @@ The service runs with group and user matterbridge and the system has full protec
 
 The storage position is **not compatible** with the traditional setup (~/Matterbridge ~/.matterbridge ~/.mattercert).
 
-Also various script don't work if you choose this configuration.
+Also various scripts don't work if you choose this configuration.
 
 ### 1 - Create the matterbridge user and group
 
@@ -62,7 +60,7 @@ sudo chmod -R 755 /opt/matterbridge /opt/matterbridge/Matterbridge /opt/matterbr
 # make sure the “bin” dir exists for global executables
 sudo -u matterbridge mkdir -p /opt/matterbridge/.npm-global/bin
 # ✅ Install matterbridge in the private global node_modules using the private npm cache
-sudo -u matterbridge NPM_CONFIG_PREFIX=/opt/matterbridge/.npm-global NPM_CONFIG_CACHE=/opt/matterbridge/.npm-cache npm install matterbridge --omit=dev --verbose --global
+sudo -u matterbridge npm install matterbridge --omit=dev --verbose --global --prefix=/opt/matterbridge/.npm-global --cache=/opt/matterbridge/.npm-cache
 # ✅ 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

package/README.md

@@ -178,37 +178,31 @@ Home page
 
 ### Run matterbridge as a daemon with systemctl (Linux only)
 
-Traditional configuration
+Traditional configuration: [configuration](README-SERVICE.md)
 
-[Service configurations](README-SERVICE.md)
+or with local global node_modules and npm cache (no sudo required): [configuration](README-SERVICE-LOCAL.md)
 
-or with local global node_modules (no sudo required)
-
-[Service configurations with local global node_modules](README-SERVICE-LOCAL.md)
-
-or with user matterbridge and with private global node_modules (no sudo required)
-
-[Service configurations with user matterbridge and private global node_modules](README-SERVICE-OPT.md)
+or with user matterbridge and with private global node_modules and npm cache (no sudo required): [configuration](README-SERVICE-OPT.md)
 
 ### Run matterbridge as a system service with launchctl (macOS only)
 
-[Launchctl configurations](README-MACOS-PLIST.md)
+[Launchctl configuration](README-MACOS-PLIST.md)
 
 ### Run matterbridge with docker and docker compose
 
-[Docker configurations](README-DOCKER.md)
+[Docker configuration](README-DOCKER.md)
 
 ### Run matterbridge with podman
 
-[Podman configurations](README-PODMAN.md)
+[Podman configuration](README-PODMAN.md)
 
 ### Run matterbridge with nginx
 
-[Nginx configurations](README-NGINX.md)
+[Nginx configuration](README-NGINX.md)
 
 ### Run matterbridge as an home assistant add-on with the official add-on
 
-[Home assistant add-on configurations](https://github.com/Luligu/matterbridge-home-assistant-addon)
+[Home assistant add-on configuration](https://github.com/Luligu/matterbridge-home-assistant-addon)
 
 ### Other Home Assistant Community Add-ons
 

package/dist/cli.js

@@ -165,6 +165,8 @@ function help() {
       --service:               enable the service mode (used in the linux systemctl configuration file and macOS launchctl plist)
       --docker:                enable the docker mode (used in the docker image)
       --homedir:               override the home directory (default the os homedir)
+      --delay [seconds]:       set a delay in seconds before starting Matterbridge in the first 5 minutes from a reboot (default 120)
+      --fixed_delay [seconds]: set a fixed delay in seconds before starting Matterbridge (default 120)
   `);
     process.exit(0);
 }

package/dist/matterbridge.js

@@ -485,12 +485,12 @@ export class Matterbridge extends EventEmitter {
                     plugin.enabled = false;
                     continue;
                 }
-                if ((await this.plugins.parse(plugin)) === null) {
-                    this.log.error(`Error parsing plugin ${plg}${plugin.name}${er}. The plugin is disabled.`);
-                    plugin.error = true;
-                    plugin.enabled = false;
-                    continue;
-                }
+            }
+            if ((await this.plugins.parse(plugin)) === null) {
+                this.log.error(`Error parsing plugin ${plg}${plugin.name}${er}. The plugin is disabled.`);
+                plugin.error = true;
+                plugin.enabled = false;
+                continue;
             }
             this.log.debug(`Creating node storage context for plugin  ${plg}${plugin.name}${db}`);
             plugin.nodeContext = await this.nodeStorage.createStorage(plugin.name);
@@ -653,13 +653,13 @@ export class Matterbridge extends EventEmitter {
         }
         if (hasParameter('delay') && os.uptime() <= 60 * 5) {
             const { wait } = await import('./utils/wait.js');
-            const delay = getIntParameter('delay') || 2000;
+            const delay = getIntParameter('delay') || 120;
             this.log.warn('Delay switch found with system uptime less then 5 minutes. Waiting for ' + delay + ' seconds before starting matterbridge...');
             await wait(delay * 1000, 'Race condition delay', true);
         }
         if (hasParameter('fixed_delay')) {
             const { wait } = await import('./utils/wait.js');
-            const delay = getIntParameter('fixed_delay') || 2000;
+            const delay = getIntParameter('fixed_delay') || 120;
             this.log.warn('Fixed delay switch found. Waiting for ' + delay + ' seconds before starting matterbridge...');
             await wait(delay * 1000, 'Fixed race condition delay', true);
         }