Commission the device onto the first fabric with chip-tool pairing ble-wifi or ble-thread, assigning a local node ID
From the first fabric's administrator, open an Enhanced Commissioning Window on the device: chip-tool pairing open-commissioning-window <node_id> 1 <timeout_seconds> <iteration> <discriminator>; record the printed manual pairing code
Switch chip-tool to the second fabric context using the --commissioner-name beta flag (or a separate storage path) so the second admin has its own fabric credentials
Commission the device onto the second fabric using the pairing code obtained in step 2: chip-tool --commissioner-name beta pairing code <new_node_id> <pairing_code>
Verify both fabrics are present on the device by reading the Operational Credentials cluster: chip-tool --commissioner-name alpha operationalcredentials nocs read 0 0
Remove a fabric when no longer needed with chip-tool operationalcredentials remove-fabric <fabric_index> <node_id> <endpoint>
Known gotchas
The commissioning window has a finite timeout; the second admin must complete pairing before it expires or the window must be re-opened
Each fabric consumes a fabric table slot on the device; consumer devices typically support a small number of fabrics (the spec requires at least 5 but devices may support more or fewer)
Using --commissioner-name with chip-tool uses separate in-memory state; ensure the correct commissioner name is specified consistently for all subsequent commands targeting that fabric
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