Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Fabric Synchronization Guide to avoid confusion #34420

Merged
merged 2 commits into from
Jul 23, 2024
Merged

Update Fabric Synchronization Guide to avoid confusion #34420

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d2ba8f8
Update Fabric Synchronization Guide to avoid confusion
yufengwangca Jul 19, 2024
43d188a
Address the review comments
yufengwangca Jul 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion docs/guides/fabric_synchronization_guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,9 @@ Fabric-Bridge-App example app implements the Aggregator device type with Fabric
Synchronization condition met and demonstrates the end-to-end Fabric
Synchronization feature using dynamic endpoints.

The Fabric-Admin and Fabric-Bridge-App example applications must be executed on
the same physical device and communicate with each other using RPC.

Fabric Synchronization can be triggered from either side. The initiator of the
Fabric Synchronization process, who shares their devices, takes on the
Commissioner role. The recipient of the Fabric Synchronization request, who
Expand Down Expand Up @@ -82,11 +85,17 @@ fabricsync enable-auto-sync 1
Pair the Fabric-Source bridge to Fabric-Sync with node ID 1:

```
fabricsync add-bridge 1 <fabric-sink-ip>
fabricsync add-bridge 1 <fabric-source-bridge-ip>
```

### Pair Light Example to Fabric-Source

Since Fabric-Bridge also functions as a Matter server, running it alongside the
Light Example app on the same machine would cause conflicts. Therefore, you need
to run the Matter Light Example app on a separate physical machine from the one
hosting Fabric-Admin and Fabric-Bridge. You can then commission the Matter Light
Example app using Fabric-Admin on the source side.
yufengwangca marked this conversation as resolved.
Show resolved Hide resolved

Pair the Light Example with node ID 3 using its payload number:

```
Expand Down
Loading