diff --git a/config/esp32/components/chip/Kconfig b/config/esp32/components/chip/Kconfig index 8991d7e97535ec..33c462e65203a9 100644 --- a/config/esp32/components/chip/Kconfig +++ b/config/esp32/components/chip/Kconfig @@ -731,7 +731,7 @@ menu "CHIP Device Layer" help The IP address and port of the server to which the device should establish a service tunnel. The supplied address must be a dot-notation IP address--not a host name. The port number is - optional; if present it should be separated from the IP address with a colon (e.g. 192.168.1.100:11097). + optional; if present it should be separated from the IP address with a colon (e.g. 192.168.1.100:5540). config LOG_PROVISIONING_HASH bool "Enable Provisioning Hash Logging" diff --git a/docs/guides/nrfconnect_examples_cli.md b/docs/guides/nrfconnect_examples_cli.md index 01cd09aed2ad9e..174aad450e2991 100644 --- a/docs/guides/nrfconnect_examples_cli.md +++ b/docs/guides/nrfconnect_examples_cli.md @@ -344,5 +344,5 @@ uart:~$ matter dns resolve Resolving ... DNS resolve for 000000014A77CBB3-0000000000BC5C01 succeeded: IP address: fd08:b65e:db8e:f9c7:8052:1a8e:4dd4:e1f3 - Port: 11097 + Port: 5540 ``` diff --git a/examples/chip-tool/README.md b/examples/chip-tool/README.md index d3a7e916a49743..d52c2a84e8f220 100644 --- a/examples/chip-tool/README.md +++ b/examples/chip-tool/README.md @@ -41,7 +41,7 @@ choose the pairing mode. The command below pair a device with the provided IP address and port of the server to talk to. - $ chip-tool pairing bypass 192.168.0.30 11097 + $ chip-tool pairing bypass 192.168.0.30 5540 #### Pair a device over BLE diff --git a/examples/lighting-app/efr32/README.md b/examples/lighting-app/efr32/README.md index 7bb2685033071a..6ade55357188df 100644 --- a/examples/lighting-app/efr32/README.md +++ b/examples/lighting-app/efr32/README.md @@ -257,7 +257,7 @@ combination with JLinkRTTClient as follows: \*\* Currently, chip-tool for Mac or Linux do not yet have the Thread provisioning feature - `chip-tool bypass 11097` + `chip-tool bypass 5540` You can provision the Chip device using Chip tool Android or iOS app or through CLI commands on your OT BR diff --git a/examples/lighting-app/telink/Readme.md b/examples/lighting-app/telink/Readme.md index 08919fbdff93ca..be923d3d05dac2 100644 --- a/examples/lighting-app/telink/Readme.md +++ b/examples/lighting-app/telink/Readme.md @@ -155,13 +155,13 @@ following states: 1. Pair with device ``` - ${CHIP_TOOL_DIR}/chip-tool pairing bypass ${IP_ADDRESS_OF_CHIP_DEVICE} 11097 + ${CHIP_TOOL_DIR}/chip-tool pairing bypass ${IP_ADDRESS_OF_CHIP_DEVICE} 5540 ``` here: - `${IP_ADDRESS_OF_CHIP_DEVICE}` is IPv6 address of CHIP device - - **11097** is standart CHIP TCP port + - **5540** is the standard CHIP TCP port 1. Switch on the light: diff --git a/examples/lock-app/efr32/README.md b/examples/lock-app/efr32/README.md index 1f0961a3f0372f..b935add4f3baae 100644 --- a/examples/lock-app/efr32/README.md +++ b/examples/lock-app/efr32/README.md @@ -246,7 +246,7 @@ combination with JLinkRTTClient as follows: \*\* Currently, chip-tool for Mac or Linux do not yet have the Thread provisioning feature - `chip-tool bypass 11097` + `chip-tool bypass 5540` You can provision the Chip device using Chip tool Android or iOS app or through CLI commands on your OT BR diff --git a/scripts/tests/test_suites.sh b/scripts/tests/test_suites.sh index 53808635a5460b..86c4ca7adb4798 100755 --- a/scripts/tests/test_suites.sh +++ b/scripts/tests/test_suites.sh @@ -122,7 +122,7 @@ for j in "${iter_array[@]}"; do # the data is there yet. background_pid="$(