From 1d01dea68df38be58bc2f4033e1c77470a177c5f Mon Sep 17 00:00:00 2001 From: Grzegorz Ferenc Date: Thu, 22 Jun 2023 10:20:55 +0200 Subject: [PATCH] remove tips as per Boris' comment Signed-off-by: Grzegorz Ferenc --- docs/guides/chip_tool_guide.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/docs/guides/chip_tool_guide.md b/docs/guides/chip_tool_guide.md index bda3c436ad02a9..f724b58f7bdb19 100644 --- a/docs/guides/chip_tool_guide.md +++ b/docs/guides/chip_tool_guide.md @@ -1152,10 +1152,6 @@ the following steps: >>> doorlock subscribe lock-state 5 10 1 1 ``` - > **Tip:** You can also set the `$NODE_ID` and `$ENDPOINT_ID` variables for - > the __ and __, respectively, and use them in your - > commands. - After this command is run, the CHIP Tool will check the state of the door lock every time it changes (for example, as a result of a button press or an external ecosystem action) and update it in its own records. @@ -1235,10 +1231,6 @@ the following steps: >>> doorlock subscribe-event door-lock-alarm 5 10 1 1 ``` - > **Tip:** You can also set the `$NODE_ID` and `$ENDPOINT_ID` variables for - > the __ and __, respectively, and use them in your - > commands. - After this command is run, the CHIP Tool will check the state of the door lock every time it changes (for example, as a result of a button press or an external ecosystem action) and update it in its own records.