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.

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

[Fabric-Admin] Update the Fabric Sync guide to explain the confusion #35638

Merged
merged 3 commits into from
Sep 18, 2024
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
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
5 changes: 5 additions & 0 deletions docs/guides/fabric_synchronization_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -118,6 +118,11 @@ of Ecosystem 1 has successfully paired with Ecosystem 2 on Endpoint 2:
>>> A new device is added on Endpoint 2.
```

Note: We only need to add the local bridge to the ecosystem to trigger the
Fabric Sync Setup process. In the example above, the Fabric Sync Setup process
yufengwangca marked this conversation as resolved.
Show resolved Hide resolved
is initiated by the command 'add-bridge' from Ecosystem 1. Adding the local
bridge on the other side is optional.

### Pair Light Example to Ecosystem 2

Since Fabric-Bridge also functions as a Matter server, running it alongside the
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ constexpr char kInteractiveModeHistoryFileName[] = "chip_tool_history";
constexpr char kInteractiveModeStopCommand[] = "quit()";

#if defined(PW_RPC_ENABLED)
constexpr uint16_t kRetryIntervalS = 5;
constexpr uint16_t kRetryIntervalS = 3;
#endif

// File pointer for the log file
Expand Down
Loading