You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Home Assistant Matter Hub publishes Home Assistant entities as Matter devices, so Apple Home, Google Home, Alexa and any other Matter controller can see and control them. Needs only a long-lived access token.
Uses the RiDDiX fork, not t0bst4r. The original project reached end of maintenance in January 2026 and explicitly points at RiDDiX/home-assistant-matter-hub (1.1k ★, active, v2.0.52).
Careful with the install path: the fork's docs still contain the upstream line npm install -g home-assistant-matter-hub — that npm name belongs to t0bst4r and is stale. The fork ships only a Docker image and HA add-ons, so this script builds from source instead.
Stack:NODE_VERSION="24" NODE_MODULE="pnpm@^10" setup_nodejs, tarball + pnpm install --frozen-lockfile + pnpm build, then node /opt/matter-hub/apps/home-assistant-matter-hub/dist/backend/cli.js start --storage-location=/opt/matter-hub_data. Web UI on :8482.
Config:/opt/matter-hub.env with HAMH_HOME_ASSISTANT_URL and HAMH_HOME_ASSISTANT_ACCESS_TOKEN (both must be filled in before it works).
Note: Matter needs working IPv6 and mDNS on the same L2 segment. APs/switches that filter or rate-limit multicast are the usual cause of devices going "No Response" — flagged in the JSON notes.
Note:/opt/matter-hub_data holds the fabric credentials; deleting it unpairs every controller.
Set HAMH_HOME_ASSISTANT_URL and HAMH_HOME_ASSISTANT_ACCESS_TOKEN in /opt/matter-hub.env, then run 'systemctl restart matter-hub'. Create the long-lived access token in Home Assistant under your user profile, Security tab.
Matter relies on IPv6 and mDNS. The container needs working IPv6 and must be on the same L2 network as your Matter controllers. Access points and switches that filter or rate-limit multicast are the most common cause of devices going 'No Response' after a while - check for IGMP snooping, mDNS/Bonjour filtering and AP isolation.
Bridge data and fabric credentials are stored in /opt/matter-hub_data. Deleting that directory unpairs every controller and requires re-commissioning.
This is the community fork by RiDDiX. The original t0bst4r/home-assistant-matter-hub ended maintenance in January 2026 and receives no further fixes.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Activity
github-actions commentedon Aug 3, 2026
The Matter-Hub script is ready for testing:
Set HAMH_HOME_ASSISTANT_URL and HAMH_HOME_ASSISTANT_ACCESS_TOKEN in /opt/matter-hub.env, then run 'systemctl restart matter-hub'. Create the long-lived access token in Home Assistant under your user profile, Security tab.
Matter relies on IPv6 and mDNS. The container needs working IPv6 and must be on the same L2 network as your Matter controllers. Access points and switches that filter or rate-limit multicast are the most common cause of devices going 'No Response' after a while - check for IGMP snooping, mDNS/Bonjour filtering and AP isolation.
Bridge data and fabric credentials are stored in /opt/matter-hub_data. Deleting that directory unpairs every controller and requires re-commissioning.
This is the community fork by RiDDiX. The original t0bst4r/home-assistant-matter-hub ended maintenance in January 2026 and receives no further fixes.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Discord testing thread: https://discord.com/channels/1302816934508630047/1533802717909352550
github-actions commentedon Sep 7, 2026
A PR has been created for matter-hub: community-scripts/ProxmoxVE#17093
MickLesk commentedon Sep 7, 2026
Merged with #17093 in ProxmoxVE