Build the fabric-admin and fabric-bridge-app examples from the connectedhomeip repository following the Fabric Synchronization Guide
Start fabric-admin in interactive mode: ./fabric-admin; it will present a prompt where you can issue commands without re-initializing for each call
Commission the source fabric's devices into fabric-admin so it holds their credentials and can act as their administrator
Use the sync-device command in fabric-admin to bridge a device from the source fabric onto a destination fabric, which causes fabric-bridge-app to create a virtual representation of the remote device
Verify the bridged device appears in the destination fabric's device list and that attribute reads pass through to the original device
Monitor subscription reports so that state changes on the physical device are propagated to the bridge in real time
Known gotchas
Fabric synchronization is a newer Matter feature; check that your device firmware and controller versions support the ICD (Intermittently Connected Devices) and bridging clusters required
The fabric-bridge-app creates dynamic endpoints; endpoint IDs can shift across restarts, so do not hard-code them in automation rules
This workflow requires both fabric-admin and fabric-bridge-app to run concurrently and communicate over a local socket; firewall rules or port conflicts can silently break the IPC channel
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp