matterbridge 3.4.3-dev-20251208-0c8a552 → 3.4.3-dev-20251209-bdbfc70
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +19 -5
- package/frontend/build/assets/index.js +4 -4
- package/npm-shrinkwrap.json +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -499,15 +499,27 @@ Then, from the dots menu in the frontend, download the `matterbridge.log` and `m
|
|
|
499
499
|
|
|
500
500
|
Don't forget to unselect the debug mode when is no more needed. The network traffic and cpu usage is very high in debug mode.
|
|
501
501
|
|
|
502
|
-
##
|
|
502
|
+
## How to pair a second controller
|
|
503
503
|
|
|
504
|
-
|
|
504
|
+
There are two ways to pair a second controller:
|
|
505
|
+
|
|
506
|
+
- from the first controller find the `share` or `turn on pairing mode` method and get a new (QR)code and use it to pair the second controller;
|
|
507
|
+
|
|
508
|
+
- from Matterbridge frontend click `Turn on pairing mode` in the `Paired fabrics` panel and proceed like for the first controller.
|
|
509
|
+
|
|
510
|
+
|
|
511
|
+
|
|
512
|
+
Be patient cause the procedure can fail sometimes.
|
|
513
|
+
|
|
514
|
+
## How to avoid race condition on start / restart
|
|
515
|
+
|
|
516
|
+
We have a race condition when, after a blackout or with docker compose or with other systems that start more then one process, Matterbridge always starts before other required system or network components.
|
|
505
517
|
|
|
506
518
|
Race condition can cause missing configuration or missed devices on the controller side. All Matterbridge official plugins already wait for system and network components to be ready so there is no need of delay.
|
|
507
519
|
|
|
508
520
|
To solve the race condition on blackout, use the --delay parameter. There is no delay on normal restart cause the delay is applied only in the first 5 minutes from system reboot.
|
|
509
521
|
|
|
510
|
-
To solve the race condition on docker compose, use the --fixed_delay parameter. The start will always be delayed.
|
|
522
|
+
To solve the race condition on docker compose, use the --fixed_delay parameter. The start will always be delayed so use it only if strictly necessary.
|
|
511
523
|
|
|
512
524
|
# Known general issues
|
|
513
525
|
|
|
@@ -548,7 +560,7 @@ So far is the only controller supporting all Matter 1.2, 1.3 and 1.4 device type
|
|
|
548
560
|
## Home Assistant issues
|
|
549
561
|
|
|
550
562
|
- If HA doesn't show all devices, reload the Matter Server Integration or reboot HA
|
|
551
|
-
- Home Assistant doesn't seem to always react when a device is removed from the bridge: they remain in HA unavailable forever
|
|
563
|
+
- Home Assistant doesn't seem to always react when a device is removed from the bridge: they remain in HA unavailable forever. A full Home Assistant restart solves the problem.
|
|
552
564
|
- Use Apple Home when you have to choose the controller type even if you pair Matterbridge directly with HA.
|
|
553
565
|
|
|
554
566
|
## Google Home
|
|
@@ -596,7 +608,9 @@ We believe in a welcoming and respectful community for all. Please make sure to
|
|
|
596
608
|
## Support
|
|
597
609
|
|
|
598
610
|
If you find this project helpful and you wish to support the ongoing development, you can do so by buying me a coffee.
|
|
599
|
-
|
|
611
|
+
|
|
612
|
+
On my side I sponsor the packages that I use in this project and single developers. It would be nice to have sponsors too.
|
|
613
|
+
|
|
600
614
|
Click on the badge below to get started:
|
|
601
615
|
|
|
602
616
|
<a href="https://www.buymeacoffee.com/luligugithub">
|