matterbridge 3.0.1-dev-20250501-4f463f9 → 3.0.1-dev-20250502-6d36575

package/CHANGELOG.md

@@ -13,17 +13,21 @@ If you like this project and find it useful, please consider giving it a star on
 If you want to run Matterbridge in Home Assistant please use the official add-on https://github.com/Luligu/matterbridge-home-assistant-addon that also has Ingress and side panel.
 It is also available the official Matterbridge Home Assistant plugin https://github.com/Luligu/matterbridge-hass.
 
-## New plugin matterbridge-webhooks
+## [3.0.1] - 2025-05-??
 
-A new plugin has been added: https://github.com/Luligu/matterbridge-webhooks
+### Added
 
-It allows you to expose any webhooks to Matter.
+- [docker]: The builder for the **docker** image with tag **latest** will run each day at 00:00 UTC. Inside the image matterbridge and all plugins with the latest release (as published on npm) are already loaded. You can just pull the new image and matterbridge with all plugins will be the latest.
+- [docker]: The builder for the **docker** image with tag **dev** will run each day at 00:00 UTC. Inside the image matterbridge and all plugins with the dev release (as pushed on GitHub) are already loaded. You can just pull the new image and matterbridge with all plugins will be the latest dev (it is possible that the devs are outdated by published latests).
+- [npm]: The dev of matterbridge is published with tag **dev** on **npm** each day at 00:00 UTC if there is a new commit. It is possible that the dev is outdated by published latest.
+- [frontend]: Added closeSnackbarMessage() to remove the notification with timeout = 0.
+- [frontend]: Moved plugin actions from express to web socket.
 
-Features:
+### Changed
 
-- The webhooks parameters can easily be entered in the frontend.
-- It is possible to choose the method: GET or POST.
-- The webhook can be tested directly in the frontend.
+- [docker]: Updated the [Docker configurations](README-DOCKER.md).
+
+## [3.0.0] - 2025-04-29
 
 ## Breaking changes
 
@@ -38,8 +42,6 @@ Modified clusters:
 
 - OccupancySensing cluster.
 
-## [3.0.0] - 2025-04-29
-
 ### Added
 
 - [addEndpoint]: Added an error handler with deep stack on aggregatorNode.add() and serverNode.add() calls.
@@ -56,7 +58,6 @@ Modified clusters:
 - [parameter]: Added getIntArrayParameter and getStringArrayParameter.
 - [frontend]: Added the view menu to load the logs directly in the browser.
 - [docker]: Optimized the dockerfiles and reduced the image size by 30%.
-- [docker]: The builder for the docker image with tag latest will run each day at 00:00 UTC. Inside the image all plugins with the latest release (as published on npm) are already loaded. You can just pull the new image and matterbridge with all plugins will be the latest.
 
 ### Changed
 

package/README-DOCKER.md

@@ -16,7 +16,11 @@
 
 ## Run matterbridge with docker and docker compose
 
-The Matterbridge Docker image, which includes a manifest list for the linux/amd64, linux/arm64 and linux/arm/v7 architectures, is published on Docker Hub.
+The Matterbridge Docker image, which includes a manifest list for the linux/amd64, linux/arm64 and linux/arm/v7 architectures, is published on **Docker Hub**.
+
+The image (tag **latest**) includes matterbridge and all plugins with the latest release (as published on npm). You can just pull the new image and matterbridge with all plugins will be the latest release published on npm.
+
+The image (tag **dev**) includes matterbridge and all plugins with the dev release (as pushed on GitHub). You can just pull the new image and matterbridge with all plugins will be the latest release pushed on GitHub. It is possible that the devs are outdated by published latests.
 
 It is based on node:22-bookworm-slim and integrates the health check.
 
@@ -30,9 +34,12 @@ With docker run
 
 The health check still runs in the background, but:
 The container doesn’t restart automatically if it becomes unhealthy.
-You must manually check the health status:
 
+You can manually check the health status:
+
+```bash
 docker exec -it matterbridge curl -v http://localhost:8283/health
+```
 
 ### First create the Matterbridge directories
 
@@ -40,9 +47,9 @@ This will create the required directories in your home directory if they don't e
 
 ```bash
 cd ~
-mkdir -p ./Matterbridge
-mkdir -p ./.matterbridge
-sudo chown -R $USER:$USER ./Matterbridge ./.matterbridge
+mkdir -p ~/Matterbridge
+mkdir -p ~/.matterbridge
+sudo chown -R $USER:$USER ~/Matterbridge ~/.matterbridge
 ```
 
 You may need to adapt the script to your setup.
@@ -64,13 +71,11 @@ The container must have full access to the host network (needed for mdns).
 
 ```bash
 sudo docker run --name matterbridge \
-  -v /home/<USER>/Matterbridge:/root/Matterbridge \
-  -v /home/<USER>/.matterbridge:/root/.matterbridge \
+  -v ~/Matterbridge:/root/Matterbridge \
+  -v ~/.matterbridge:/root/.matterbridge \
   --network host --restart always -d luligu/matterbridge:latest
 ```
 
-Replace USER with your user name (i.e. ubuntu or pi).
-
 You may need to adapt the script to your setup.
 
 ### Run with docker compose
@@ -85,13 +90,11 @@ services:
     network_mode: host                                        # Ensures the Matter mdns works
     restart: always                                           # Ensures the container always restarts automatically
     volumes:
-      - "/home/<USER>/Matterbridge:/root/Matterbridge"        # Mounts the Matterbridge plugin directory
-      - "/home/<USER>/.matterbridge:/root/.matterbridge"      # Mounts the Matterbridge storage directory
+      - "${HOME}/Matterbridge:/root/Matterbridge"             # Mounts the Matterbridge plugin directory
+      - "${HOME}/.matterbridge:/root/.matterbridge"           # Mounts the Matterbridge storage directory
 ```
 
-Replace USER with your user name (i.e. ubuntu or pi: "/home/ubuntu/Matterbridge:/root/Matterbridge").
-
-copy it in the home directory or edit the existing one to add the matterbridge service.
+Copy it in the home directory or edit the existing one to add the matterbridge service.
 
 Then start docker compose with:
 
@@ -99,6 +102,12 @@ Then start docker compose with:
 docker compose up -d
 ```
 
+or start only the matterbridge container with:
+
+```bash
+docker compose up -d matterbridge
+```
+
 ### Stop with docker compose
 
 ```bash
@@ -107,8 +116,11 @@ docker compose down
 
 ### Update with docker compose
 
+This will pull the new matterbridge image and restart the matterbridge container.
+
 ```bash
-docker compose pull
+docker compose pull matterbridge
+docker compose up -d --no-deps matterbridge
 ```
 
 ### Inspect the container