matterbridge 3.4.5-dev-20251222-5853b56 → 3.4.5-dev-20251224-e00e572

package/CHANGELOG.md

@@ -32,7 +32,8 @@ Advantages:
 
 ### Added
 
-- [DevContainer]: Refactored Dev Container setup. The Matterbridge instance can be paired on native Linux hosts or WSL 2 with Docker engine CLI integration. On Docker Desktop on Windows or macOS is not possible cause Docker Desktop runs inside a VM and not directly on the host.
+- [DevContainer]: Refactored Dev Container setup. The Matterbridge instance can now be paired on native Linux hosts or WSL 2 with Docker engine CLI integration. On Docker Desktop on Windows or macOS is not possible cause Docker Desktop runs inside a VM and not directly on the host so mDNS is not supported.
+- [DevContainer]: Since is now possible to pair from Dev Container, named volumes have been added to persist storage and plugins across rebuilds.
 
 ### Changed
 

package/README-DEV.md

@@ -52,12 +52,32 @@ To start the Dev Container, simply open the project folder in [Visual Studio Cod
 
 > **Note:** The first time you use the Dev Container, it may take a while to download all the required Docker images and set up the environment. Subsequent starts will be as fast as from the local folder.
 
-Since Dev Container doesn't run in network mode 'host', it is not possible to pair Mattebridge running inside the Dev Container.
+## Dev containers networking limitations
+
+Dev containers have networking limitations depending on the host OS and Docker setup.
+
+• Docker Desktop on Windows or macOS:
+
+- Runs inside a VM
+- Host networking mode is NOT available
+- Matterbridge and plugins can run but:
+  ❌ Pairing with Matter controllers will NOT work cause of missing mDNS support
+  ✅ Remote and local network access (cloud services, internet APIs) works normally
+  ✅ Matterbridge frontend works normally
+
+• Native Linux or WSL 2 with Docker Engine CLI integration:
+
+- Host networking IS available
+- Full local network access is supported with mDNS
+- Matterbridge and plugins work correctly, including pairing
+- Matterbridge frontend works normally
+
+## How to pair the plugin
 
-When you want to test your plugin with a paired controller, you have several options:
+When you want to test your plugin with a paired controller and you cannot use native Linux or WSL 2 with Docker Engine, you have several other options:
 
 - create a tgz (npm run npmPack) and upload it to a running instance of matterbridge.
-- publish it with tag dev and install it (matterbridge-yourplugin@dev in Install plugins) in a running instance of matterbridge.
+- publish the plugin with tag dev and install it (matterbridge-yourplugin@dev in Install plugins) in a running instance of matterbridge.
 - use a local instance of matterbridge running outside the dev container and install (../matterbridge-yourplugin in Install plugins) or add (../matterbridge-yourplugin in Install plugins) your plugin to it (easiest way). Adjust the path if matterbridge dir and your plugin dir are not in the same parent directory.
 
 ## Guidelines on imports/exports

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "matterbridge",
-  "version": "3.4.5-dev-20251222-5853b56",
+  "version": "3.4.5-dev-20251224-e00e572",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "matterbridge",
-      "version": "3.4.5-dev-20251222-5853b56",
+      "version": "3.4.5-dev-20251224-e00e572",
       "license": "Apache-2.0",
       "dependencies": {
         "@matter/main": "0.15.6",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "matterbridge",
-  "version": "3.4.5-dev-20251222-5853b56",
+  "version": "3.4.5-dev-20251224-e00e572",
   "description": "Matterbridge plugin manager for Matter",
   "author": "https://github.com/Luligu",
   "license": "Apache-2.0",