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

doc: chip_tool_guide: fix the order of arguments in pairing code command #28494

Merged
merged 1 commit into from
Aug 3, 2023
Merged

doc: chip_tool_guide: fix the order of arguments in pairing code command #28494

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions docs/guides/chip_tool_guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -980,23 +980,23 @@ Complete the following steps:
fabric by using the following command pattern:

```
$ ./chip-tool pairing code <payload> <node_id> --commissioner-name <commissioner_name>
$ ./chip-tool pairing code <node_id> <payload> --commissioner-name <commissioner_name>
```

In this command:

- _<payload\>_ is the the QR code payload or a manual pairing code generated
by the first commissioner instance when opened commissioning window
- _<node_id\>_ is the user-defined ID of the node being commissioned. It
doesn't need to be the same ID, as for the first fabric.
- _<payload\>_ is the the QR code payload or a manual pairing code generated
by the first commissioner instance when opened commissioning window
- _<commissioner_name\>_ is the name of the second fabric. Valid values are
"alpha", "beta", "gamma", and integers greater than or equal to 4. The
default if not specified is "alpha".

**Example of command:**

```
$ ./chip-tool pairing code 36281602573 1 --commissioner-name beta
$ ./chip-tool pairing code 1 36281602573 --commissioner-name beta
```

#### Step 5: Test reception of commands
Expand Down