forked from project-chip/connectedhomeip
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'chip/master' into icd/python-wait-for-a…
…ctive-testing
- Loading branch information
Showing
299 changed files
with
20,791 additions
and
4,553 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,164 @@ | ||
| # Fabric Synchronization Guide | ||
|
|
||
| - [Fabric Synchronization Guide](#fabric-synchronization-guide) | ||
| - [Fabric Sync Example Applications](#fabric-sync-example-applications) | ||
| - [Run Fabric Sync Demo on RP4](#run-fabric-sync-demo-on-rp4) | ||
|
|
||
| ## Fabric Sync Example Applications | ||
|
|
||
| Fabric-Admin and Fabric-Bridge example applications are provided to demonstrate | ||
| Fabric Synchronization feature. You can find them in the examples. | ||
|
|
||
|  | ||
|
|
||
| Fabric-Admin example app implements the Fabric Administrator role and | ||
| communicates with the Fabric-Bridge-App on the other side, facilitating the | ||
| Fabric Synchronization process. | ||
|
|
||
| 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. | ||
|
|
||
| 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 | ||
| receives the shared devices, assumes the Commissionee role. This flexibility | ||
| enables a seamless and efficient synchronization process. | ||
|
|
||
| ### Building the Example Application | ||
|
|
||
| - Building the Fabric-Admin Application | ||
|
|
||
| [Fabric-Admin](https://github.com/project-chip/connectedhomeip/tree/master/examples/fabric-admin/README.md) | ||
|
|
||
| * Building the Fabric-Bridge Application | ||
|
|
||
| [Fabric-Bridge](https://github.com/project-chip/connectedhomeip/tree/master/examples/fabric-bridge-app/linux/README.md) | ||
|
|
||
| ## Run Fabric Sync Demo on RP4 | ||
|
|
||
| ### Setup Fabric Source | ||
|
|
||
| Connect to the Fabric Source server: | ||
|
|
||
| ``` | ||
| ssh [email protected] | ||
| ``` | ||
|
|
||
| Password: <password> | ||
|
|
||
| Run the Fabric Source script: | ||
|
|
||
| ``` | ||
| ./run_fabric_source.sh | ||
| ``` | ||
|
|
||
| ### Setup Fabric Sink | ||
|
|
||
| Connect to the Fabric Sink server: | ||
|
|
||
| ``` | ||
| ssh [email protected] | ||
| ``` | ||
|
|
||
| Password: <password> | ||
|
|
||
| Run the Fabric Sink script: | ||
|
|
||
| ``` | ||
| ./run_fabric_sink.sh | ||
| ``` | ||
|
|
||
| ### Fabric Sync Setup | ||
|
|
||
| Enable Fabric Auto Sync: | ||
|
|
||
| In Fabric-Sync console: | ||
|
|
||
| ``` | ||
| fabricsync enable-auto-sync 1 | ||
| ``` | ||
|
|
||
| Pair the Fabric-Source bridge to Fabric-Sync with node ID 1: | ||
|
|
||
| ``` | ||
| fabricsync add-bridge 1 <fabric-sink-ip> | ||
| ``` | ||
|
|
||
| ### Pair Light Example to Fabric-Source | ||
|
|
||
| Pair the Light Example with node ID 3 using its payload number: | ||
|
|
||
| ``` | ||
| pairing already-discovered 3 20202021 <ip> 5540 | ||
| ``` | ||
|
|
||
| After the Light Example is successfully paired in Fabric-Source, it will be | ||
| synced to Fabric-Sink with a new assigned node ID. | ||
|
|
||
| Toggle the Light Example: | ||
|
|
||
| From Fabric-Source: | ||
|
|
||
| ``` | ||
| onoff on <node-id> 1 | ||
| onoff off <node-id> 1 | ||
| ``` | ||
|
|
||
| From Fabric-Sink: (Use the node ID assigned) | ||
|
|
||
| ``` | ||
| onoff on x 1 | ||
| onoff off x 1 | ||
| ``` | ||
|
|
||
| ### Remove Light Example from Fabric-Source | ||
|
|
||
| Unpair the Light Example: | ||
|
|
||
| ``` | ||
| pairing unpair <node-id> | ||
| ``` | ||
|
|
||
| After the Light Example is successfully unpaired from Fabric-Source, it will | ||
| also be removed from the Fabric-Sink. | ||
|
|
||
| ### Pair Commercial Switch to Fabric-Source | ||
|
|
||
| Pair the switch using its payload number: | ||
|
|
||
| In Fabric-Source console: | ||
|
|
||
| ``` | ||
| pairing code-wifi <node-id> <ssid> <passwd> <payload> | ||
| ``` | ||
|
|
||
| After the switch is successfully paired in Fabric-Source, it will be synced to | ||
| Fabric-Sink with a new assigned node ID. | ||
|
|
||
| Toggle the switch: | ||
|
|
||
| From Fabric-Source: | ||
|
|
||
| ``` | ||
| onoff on <node-id> 1 | ||
| onoff off <node-id> 1 | ||
| ``` | ||
|
|
||
| From Fabric-Sink: (Use the node ID assigned) | ||
|
|
||
| ``` | ||
| onoff on <node-id> 1 | ||
| onoff off <node-id> 1 | ||
| ``` | ||
|
|
||
| ### Remove Switch from Fabric-Source | ||
|
|
||
| Unpair the switch: | ||
|
|
||
| ``` | ||
| pairing unpair <node-id> | ||
| ``` | ||
|
|
||
| After the switch is successfully unpaired from Fabric-Source, it will also be | ||
| removed from the Fabric-Sink. |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.