docs: add Matter bridge migration plan (matter-hub EOL) #27
Conversation
Spiev
commented
Jan 28, 2026
Spiev
commented
- Add migration guide: homeassistant/matter-migration.md
- Document migration from t0bst4r/home-assistant-matter-hub to Luligu/matterbridge
- Add EOL warning to README.md for Matter Hub service
- Upstream project end-of-maintenance since January 2026
- Add migration guide: homeassistant/matter-migration.md - Document migration from t0bst4r/home-assistant-matter-hub to Luligu/matterbridge - Add EOL warning to README.md for Matter Hub service - Upstream project end-of-maintenance since January 2026
There was a problem hiding this comment.
Pull request overview
This PR documents the migration path from the deprecated t0bst4r/home-assistant-matter-hub service to Luligu/matterbridge and surfaces the planned migration prominently in the main README.
Changes:
- Add a detailed German-language migration guide
homeassistant/matter-migration.mdcovering prerequisites, Docker Compose changes, Matterbridge plugin setup, pairing, rollback, and post-migration tasks. - Update the main
README.mdto flag the existing Matter Hub as upstream EOL and link to the new migration guide.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| homeassistant/matter-migration.md | Adds a step-by-step migration guide from Matter Hub to Matterbridge, including Docker configuration, HA integration via matterbridge-hass, Google Home pairing, rollback, and follow-up documentation tasks. |
| README.md | Marks the Matter Hub service as EOL and links to the Matterbridge migration guide to direct users to the new setup. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| # NEU: Matterbridge | ||
| matterbridge: | ||
| image: luligu/matterbridge:latest |
There was a problem hiding this comment.
The Docker Compose snippet configures the Matterbridge service to pull luligu/matterbridge:latest, which is a mutable image tag from a third-party registry. If the upstream image is compromised or a breaking change is pushed, your deployment could automatically pull and run untrusted code with access to your Home Assistant token and local network. To reduce supply chain risk, pin the image to a specific version or image digest and update it explicitly when you intend to upgrade.
