Matterbridge
Matterbridge is a Matter plugin manager that creates a single pairable device for your Matter devices, letting smart-home users add them quickly to Apple…
Platform availability
Available on 2 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
31/100 Low
- Maintained
- 0GitHub repository no longer exists
- Popular
- No data
- Easy to install
- 452 install platforms, install notes, Docker image
- Light to run
- 95512 MB minimum RAM, runs on ARM
Based on 3 of 4 factors.
Availability: platform listings confirmed today
No GitHub repository data collected yet.
Checked 54 days ago - source: GitHub (BigBearTechWorld/matterbridge)
Resources & Compatibility
Minimum requirements: 512 MB RAM. ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Create the config folders first Run the setup commands that create Matterbridge’s config, certificate, and npm folders before installing. These folders hold your settings and security files, and if they are missing or owned by the wrong user account, the app may fail to start or save changes. source
- Install and start the Node.js version Run npm install -g matterbridge --omit=dev, then run matterbridge to start the bridge (npm is the Node.js package installer). Without the install step, the matterbridge command does not exist; without starting it, the bridge is not running. source
- Enable it to start on boot If you installed it as a Linux system service (a background program managed by the computer), run sudo systemctl start matterbridge and sudo systemctl enable matterbridge (sudo gives administrator rights). This starts the bridge now and makes it start again after a reboot, so your Matter devices do not stop working when the machine restarts. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I need to create Matterbridge's config, certificate, and npm folders before installation?
Yes. Run the setup commands that create Matterbridge's config, certificate, and npm folders before installing. If those folders are missing or owned by the wrong user account, Matterbridge may fail to start or save changes.
How do I install and start the Node.js version of Matterbridge?
Run npm install -g matterbridge --omit=dev, then run matterbridge to start the bridge. Without the install step, the matterbridge command does not exist, and without starting it, the bridge is not running.
How can I make Matterbridge start automatically after a reboot?
If Matterbridge is installed as a Linux system service, run sudo systemctl start matterbridge and sudo systemctl enable matterbridge. This starts it now and makes it start again after a reboot.
What troubleshooting guidance does Matterbridge provide?
The troubleshooting documentation covers common issues, debugging methods, diagnostic tools, and strategies for identifying and resolving configuration problems.
Answers sourced from deepwiki.com, github.com, github.com, github.com
Community
- Exposing all Home Assistant devices to Matter with Matterbridge - Reddit (reddit)
- Reddit (reddit)
- Matterbridge? : r/homebridge - Reddit (reddit)
- Can anyone explain XMPP bridges and how I can use them? (reddit)
Collected 48 days ago - public community threads