From 37f82b597cea903e5f28b3b4c575583d319bebb0 Mon Sep 17 00:00:00 2001 From: Boris Zbarsky Date: Wed, 31 Aug 2022 22:57:08 -0400 Subject: [PATCH] Fix documentation for chip-app1 commisioning. use "pairing code" to avoid problems like that. Fixes https://github.com/project-chip/connectedhomeip/issues/22312 --- docs/guides/simulated_device_linux.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/docs/guides/simulated_device_linux.md b/docs/guides/simulated_device_linux.md index 5bbd5f2b6452cf..f8fc6b6ae715ce 100644 --- a/docs/guides/simulated_device_linux.md +++ b/docs/guides/simulated_device_linux.md @@ -88,15 +88,12 @@ interact with it using chip-tool 1. Follow the instruction to build chip-tool in the [chip-tool readme](../../examples/chip-tool). -2. Run this command to initiate the pairing. +2. Run this command to commission. ``` - ./out/debug/standalone/chip-tool pairing ethernet 0x654321 20202021 3842 [IP ADDRESS of App] 5542 + ./out/debug/standalone/chip-tool pairing code MT:-24J0AFN00KA0648G00 ``` -3. Run this command to complete the commissioning. - ``` - ./out/debug/standalone/chip-tool generalcommissioning commissioning-complete 0x654321 0 - ``` -4. Most tests will start at this point and now an send cluster commands with + or whatever is listed on the "SetupQRCode:" line in the log output. +3. Most tests will start at this point and now an send cluster commands with chip-tool as follow. ```