Remove leftover rendezvous bypass bits.

.github/workflows/examples-linux-standalone.yaml

@@ -90,8 +90,7 @@ jobs:
             - name: Build example Standalone All Clusters Server
               timeout-minutes: 5
               run: |
-                  scripts/examples/gn_build_example.sh examples/all-clusters-app/linux out/all_clusters_debug \
-                    chip_bypass_rendezvous=true
+                  scripts/examples/gn_build_example.sh examples/all-clusters-app/linux out/all_clusters_debug
                   .environment/pigweed-venv/bin/python3 scripts/tools/memory/gh_sizes.py \
                     linux debug all-clusters-app \
                     out/all_clusters_debug/chip-all-clusters-app \

config/ameba/args.gni

@@ -29,7 +29,6 @@ chip_build_tests = false
 chip_inet_config_enable_tcp_endpoint = true
 chip_inet_config_enable_udp_endpoint = true
 
-chip_bypass_rendezvous = false
 chip_config_network_layer_ble = true
 
 custom_toolchain = "//third_party/connectedhomeip/config/ameba/toolchain:ameba"

config/mbed/CMakeLists.txt

@@ -275,7 +275,6 @@ chip_gn_arg_bool  ("chip_build_tests"                     CONFIG_CHIP_BUILD_TEST
 chip_gn_arg_bool  ("chip_monolithic_tests"                CONFIG_CHIP_BUILD_TESTS)
 chip_gn_arg_bool  ("chip_build_libshell"                  CONFIG_CHIP_LIB_SHELL)
 chip_gn_arg_bool  ("chip_with_platform_mbedtls"           CONFIG_CHIP_WITH_EXTERNAL_MBEDTLS)
-chip_gn_arg_bool  ("chip_bypass_rendezvous"               CONFIG_CHIP_BYPASS_RENDEZVOUS)
 chip_gn_arg_bool  ("chip_build_pw_rpc_lib"                CONFIG_CHIP_PW_RPC)
 chip_gn_arg_bool  ("chip_enable_data_model"               CONFIG_CHIP_DATA_MODEL)
 if (CONFIG_CHIP_PW_RPC)

examples/all-clusters-app/ameba/README.md

@@ -65,7 +65,6 @@ There are two commissioning modes supported by Ameba platform:
 
 1. In "connectedhomeip/config/ameba/args.gni"
 
-    - set `chip_bypass_rendezvous = false`
     - Set `chip_config_network_layer_ble = true`
 
 2. In "connectedhomeip/src/platform/Ameba/CHIPDevicePlatformConfig.h"
@@ -82,7 +81,6 @@ There are two commissioning modes supported by Ameba platform:
 
 1. In "connectedhomeip/config/ameba/args.gni"
 
-    - set `chip_bypass_rendezvous = false`
     - Set `chip_config_network_layer_ble = false`
 
 2. In "connectedhomeip/src/platform/Ameba/CHIPDevicePlatformConfig.h"

examples/all-clusters-app/esp32/README.md

@@ -148,18 +148,14 @@ that are currently supported include `ESP32-DevKitC` (default),
 
 ## Commissioning and cluster control
 
-Commissioning can be carried out using WiFi, BLE or Bypass.
+Commissioning can be carried out using WiFi or BLE.
 
 1.  Set the `Rendezvous Mode` for commissioning using menuconfig; the default
     Rendezvous mode is BLE.
 
          $ idf.py menuconfig
 
-Select the Rendezvous Mode via `Demo -> Rendezvous Mode`. If Rendezvous Mode is
-ByPass then set the credentials of the WiFi Network (i.e. SSID and Password from
-menuconfig).
-
-`idf.py menuconfig -> Component config -> CHIP Device Layer -> WiFi Station Options`
+Select the Rendezvous Mode via `Demo -> Rendezvous Mode`.
 
 NOTE: to avoid build error
 `undefined reference to 'chip::DevelopmentCerts::kDacPublicKey'`, set VID to

examples/all-clusters-app/esp32/main/CHIPDeviceManager.cpp

@@ -74,12 +74,6 @@ CHIP_ERROR CHIPDeviceManager::Init(CHIPDeviceManagerCallbacks * cb)
         ConnectivityMgr().SetBLEAdvertisingEnabled(false);
         ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
     }
-    else
-    {
-        // If rendezvous is bypassed, enable SoftAP so that the device can still
-        // be communicated with via its SoftAP as needed.
-        ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
-    }
 
     // Register a function to receive events from the CHIP device layer.  Note that calls to
     // this function will happen on the CHIP event loop thread, not the app_main thread.

examples/all-clusters-app/esp32/main/Kconfig.projbuild

@@ -51,8 +51,6 @@ menu "Demo"
       help
           Specifies the Rendezvous mode of the peripheral.
 
-      config RENDEZVOUS_MODE_BYPASS
-          bool "Bypass"
       config RENDEZVOUS_MODE_SOFTAP
           bool "Soft-AP"
       config RENDEZVOUS_MODE_BLE
@@ -87,7 +85,6 @@ menu "Demo"
     config RENDEZVOUS_MODE
        int
        range 0 8
-       default 0 if RENDEZVOUS_MODE_BYPASS
        default 1 if RENDEZVOUS_MODE_SOFTAP
        default 2 if RENDEZVOUS_MODE_BLE
        default 4 if RENDEZVOUS_MODE_ON_NETWORK

examples/all-clusters-app/mbed/config.in

@@ -1,7 +1,6 @@
 CONFIG_CHIP_BUILD_TESTS=n
 CONFIG_CHIP_WITH_EXTERNAL_MBEDTLS=y
 CONFIG_CHIP_PROJECT_CONFIG=main/include/CHIPProjectConfig.h
-CONFIG_CHIP_BYPASS_RENDEZVOUS=n
 CONFIG_MBED_BSD_SOCKET_TRACE=n
 CONFIG_CHIP_OTA_REQUESTOR=y
 CONFIG_CHIP_DATA_MODEL=y

examples/bridge-app/esp32/README.md

@@ -155,18 +155,14 @@ make sure the IDF_PATH has been exported(See the manual setup steps above).
 
 ## Commissioning and cluster control
 
-Commissioning can be carried out using WiFi, BLE or Bypass.
+Commissioning can be carried out using WiFi or BLE.
 
 1.  Set the `Rendezvous Mode` for commissioning using menuconfig; the default
     Rendezvous mode is BLE.
 
          $ idf.py menuconfig
 
-Select the Rendezvous Mode via `Demo -> Rendezvous Mode`. If Rendezvous Mode is
-Bypass then set the credentials of the WiFi Network (i.e. SSID and Password from
-menuconfig).
-
-`idf.py menuconfig -> Component config -> CHIP Device Layer -> WiFi Station Options`
+Select the Rendezvous Mode via `Demo -> Rendezvous Mode`.
 
 2.  Now flash the device with the same command as before. (Use the right `/dev`
     device)

examples/bridge-app/esp32/main/CHIPDeviceManager.cpp

@@ -69,12 +69,6 @@ CHIP_ERROR CHIPDeviceManager::Init(CHIPDeviceManagerCallbacks * cb)
         ConnectivityMgr().SetBLEAdvertisingEnabled(false);
         ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
     }
-    else
-    {
-        // If rendezvous is bypassed, enable SoftAP so that the device can still
-        // be communicated with via its SoftAP as needed.
-        ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
-    }
 
     // Register a function to receive events from the CHIP device layer.  Note that calls to
     // this function will happen on the CHIP event loop thread, not the app_main thread.

examples/bridge-app/esp32/main/Kconfig.projbuild

@@ -6,8 +6,6 @@ menu "Demo"
       help
           Specifies the Rendezvous mode of the peripheral.
 
-      config RENDEZVOUS_MODE_BYPASS
-          bool "Bypass"
       config RENDEZVOUS_MODE_WIFI
           bool "Wi-Fi"
       config RENDEZVOUS_MODE_BLE
@@ -21,7 +19,6 @@ menu "Demo"
     config RENDEZVOUS_MODE
        int
        range 0 8
-       default 0 if RENDEZVOUS_MODE_BYPASS
        default 1 if RENDEZVOUS_MODE_WIFI
        default 2 if RENDEZVOUS_MODE_BLE
        default 4 if RENDEZVOUS_MODE_THREAD

examples/lighting-app/ameba/README.md

@@ -63,7 +63,6 @@ There are two commissioning modes supported by Ameba platform:
 
 1. In "connectedhomeip/config/ameba/args.gni"
 
-    - set `chip_bypass_rendezvous = false`
     - Set `chip_config_network_layer_ble = true`
 
 2. In "connectedhomeip/src/platform/Ameba/CHIPDevicePlatformConfig.h"
@@ -79,7 +78,6 @@ There are two commissioning modes supported by Ameba platform:
 
 1. In "connectedhomeip/config/ameba/args.gni"
 
-    - set `chip_bypass_rendezvous = false`
     - Set `chip_config_network_layer_ble = false`
 
 2. In "connectedhomeip/src/platform/Ameba/CHIPDevicePlatformConfig.h"

examples/lighting-app/cyw30739/src/main.cpp

@@ -156,15 +156,7 @@ void EventHandler(const ChipDeviceEvent * event, intptr_t arg)
     }
 }
 
-void HandleThreadStateChangeEvent(const ChipDeviceEvent * event)
-{
-#if CHIP_BYPASS_RENDEZVOUS
-    if (event->ThreadStateChange.NetDataChanged && !ConnectivityMgr().IsThreadProvisioned())
-    {
-        ThreadStackMgr().JoinerStart();
-    }
-#endif /* CHIP_BYPASS_RENDEZVOUS */
-}
+void HandleThreadStateChangeEvent(const ChipDeviceEvent * event) {}
 
 void LightManagerCallback(LightingManager::Actor_t actor, LightingManager::Action_t action, uint8_t level)
 {

examples/lighting-app/esp32/main/CHIPDeviceManager.cpp

@@ -69,12 +69,6 @@ CHIP_ERROR CHIPDeviceManager::Init(CHIPDeviceManagerCallbacks * cb)
         ConnectivityMgr().SetBLEAdvertisingEnabled(false);
         ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
     }
-    else
-    {
-        // If rendezvous is bypassed, enable SoftAP so that the device can still
-        // be communicated with via its SoftAP as needed.
-        ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
-    }
 
     // Register a function to receive events from the CHIP device layer.  Note that calls to
     // this function will happen on the CHIP event loop thread, not the app_main thread.

examples/lighting-app/esp32/main/Kconfig.projbuild

@@ -85,8 +85,6 @@ menu "Demo"
       help
           Specifies the Rendezvous mode of the peripheral.
 
-      config RENDEZVOUS_MODE_BYPASS
-          bool "Bypass"
       config RENDEZVOUS_MODE_WIFI
           bool "Wi-Fi"
       config RENDEZVOUS_MODE_BLE
@@ -100,7 +98,6 @@ menu "Demo"
     config RENDEZVOUS_MODE
        int
        range 0 8
-       default 0 if RENDEZVOUS_MODE_BYPASS
        default 1 if RENDEZVOUS_MODE_WIFI
        default 2 if RENDEZVOUS_MODE_BLE
        default 4 if RENDEZVOUS_MODE_THREAD

examples/lighting-app/mbed/config.in

@@ -1,7 +1,6 @@
 CONFIG_CHIP_BUILD_TESTS=n
 CONFIG_CHIP_WITH_EXTERNAL_MBEDTLS=y
 CONFIG_CHIP_PROJECT_CONFIG=main/include/CHIPProjectConfig.h
-CONFIG_CHIP_BYPASS_RENDEZVOUS=n
 CONFIG_MBED_BSD_SOCKET_TRACE=n
 CONFIG_CHIP_PW_RPC=y
 CONFIG_CHIP_OTA_REQUESTOR=y

examples/lighting-app/nrfconnect/main/AppTask.cpp

@@ -401,11 +401,6 @@ void AppTask::StartThreadHandler(AppEvent * aEvent)
     if (aEvent->ButtonEvent.PinNo != THREAD_START_BUTTON)
         return;
 
-    if (chip::Server::GetInstance().AddTestCommissioning() != CHIP_NO_ERROR)
-    {
-        LOG_ERR("Failed to add test pairing");
-    }
-
     if (!chip::DeviceLayer::ConnectivityMgr().IsThreadProvisioned())
     {
         StartDefaultThreadNetwork();

examples/lighting-app/telink/src/AppTask.cpp

@@ -105,13 +105,6 @@ CHIP_ERROR AppTask::Init()
     ConfigurationMgr().LogDeviceConfig();
     PrintOnboardingCodes(chip::RendezvousInformationFlags(chip::RendezvousInformationFlag::kBLE));
 
-    ret = chip::Server::GetInstance().AddTestCommissioning();
-    if (ret != CHIP_NO_ERROR)
-    {
-        LOG_ERR("Failed to add test pairing");
-        return ret;
-    }
-
     return CHIP_NO_ERROR;
 }
 

examples/lock-app/cc13x2x7_26x2x7/args.gni

@@ -34,7 +34,6 @@ chip_enable_ota_requestor = true
 
 # BLE options
 chip_config_network_layer_ble = true
-chip_bypass_rendezvous = false
 
 # Disable lock tracking, since our FreeRTOS configuration does not set
 # INCLUDE_xSemaphoreGetMutexHolder

examples/lock-app/cyw30739/src/main.cpp

@@ -170,15 +170,7 @@ void EventHandler(const ChipDeviceEvent * event, intptr_t arg)
     }
 }
 
-void HandleThreadStateChangeEvent(const ChipDeviceEvent * event)
-{
-#if CHIP_BYPASS_RENDEZVOUS
-    if (event->ThreadStateChange.NetDataChanged && !ConnectivityMgr().IsThreadProvisioned())
-    {
-        ThreadStackMgr().JoinerStart();
-    }
-#endif /* CHIP_BYPASS_RENDEZVOUS */
-}
+void HandleThreadStateChangeEvent(const ChipDeviceEvent * event) {}
 
 void ActionInitiated(BoltLockManager::Action_t aAction, int32_t aActor)
 {

examples/lock-app/esp32/README.md

@@ -97,18 +97,14 @@ make sure the IDF_PATH has been exported(See the manual setup steps above).
 
 ## Commissioning and cluster control
 
-Commissioning can be carried out using WiFi, BLE or Bypass.
+Commissioning can be carried out using WiFi or BLE.
 
 1.  Set the `Rendezvous Mode` for commissioning using menuconfig; the default
     Rendezvous mode is BLE.
 
          $ idf.py menuconfig
 
-Select the Rendezvous Mode via `Demo -> Rendezvous Mode`. If Rendezvous Mode is
-Bypass then set the credentials of the WiFi Network (i.e. SSID and Password from
-menuconfig).
-
-`idf.py menuconfig -> Component config -> CHIP Device Layer -> WiFi Station Options`
+Select the Rendezvous Mode via `Demo -> Rendezvous Mode`.
 
 2.  Now flash the device with the same command as before. (Use the right `/dev`
     device)

examples/lock-app/esp32/main/CHIPDeviceManager.cpp

@@ -69,12 +69,6 @@ CHIP_ERROR CHIPDeviceManager::Init(CHIPDeviceManagerCallbacks * cb)
         ConnectivityMgr().SetBLEAdvertisingEnabled(false);
         ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
     }
-    else
-    {
-        // If rendezvous is bypassed, enable SoftAP so that the device can still
-        // be communicated with via its SoftAP as needed.
-        ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
-    }
 
     // Register a function to receive events from the CHIP device layer.  Note that calls to
     // this function will happen on the CHIP event loop thread, not the app_main thread.

examples/lock-app/esp32/main/Kconfig.projbuild

@@ -26,8 +26,6 @@ menu "Demo"
       help
           Specifies the Rendezvous mode of the peripheral.
 
-      config RENDEZVOUS_MODE_BYPASS
-          bool "Bypass"
       config RENDEZVOUS_MODE_WIFI
           bool "Wi-Fi"
       config RENDEZVOUS_MODE_BLE
@@ -55,7 +53,6 @@ menu "Demo"
     config RENDEZVOUS_MODE
        int
        range 0 8
-       default 0 if RENDEZVOUS_MODE_BYPASS
        default 1 if RENDEZVOUS_MODE_WIFI
        default 2 if RENDEZVOUS_MODE_BLE
        default 4 if RENDEZVOUS_MODE_THREAD

examples/lock-app/mbed/config.in

@@ -1,7 +1,6 @@
 CONFIG_CHIP_BUILD_TESTS=n
 CONFIG_CHIP_WITH_EXTERNAL_MBEDTLS=y
 CONFIG_CHIP_PROJECT_CONFIG=main/include/CHIPProjectConfig.h
-CONFIG_CHIP_BYPASS_RENDEZVOUS=n
 CONFIG_MBED_BSD_SOCKET_TRACE=n
 CONFIG_CHIP_PW_RPC=y
 CONFIG_CHIP_OTA_REQUESTOR=n

examples/lock-app/nrfconnect/main/AppTask.cpp

@@ -377,11 +377,6 @@ void AppTask::StartThreadHandler(AppEvent * aEvent)
     if (aEvent->ButtonEvent.PinNo != THREAD_START_BUTTON)
         return;
 
-    if (chip::Server::GetInstance().AddTestCommissioning() != CHIP_NO_ERROR)
-    {
-        LOG_ERR("Failed to add test pairing");
-    }
-
     if (!ConnectivityMgr().IsThreadProvisioned())
     {
         StartDefaultThreadNetwork();

examples/ota-provider-app/esp32/main/CHIPDeviceManager.cpp

@@ -69,12 +69,6 @@ CHIP_ERROR CHIPDeviceManager::Init(CHIPDeviceManagerCallbacks * cb)
         ConnectivityMgr().SetBLEAdvertisingEnabled(false);
         ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
     }
-    else
-    {
-        // If rendezvous is bypassed, enable SoftAP so that the device can still
-        // be communicated with via its SoftAP as needed.
-        ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
-    }
 
     // Register a function to receive events from the CHIP device layer.  Note that calls to
     // this function will happen on the CHIP event loop thread, not the app_main thread.

examples/ota-provider-app/esp32/main/Kconfig.projbuild

@@ -26,8 +26,6 @@ menu "Demo"
       help
           Specifies the Rendezvous mode of the peripheral.
 
-      config RENDEZVOUS_MODE_BYPASS
-          bool "Bypass"
       config RENDEZVOUS_MODE_WIFI
           bool "Wi-Fi"
       config RENDEZVOUS_MODE_BLE
@@ -41,7 +39,6 @@ menu "Demo"
     config RENDEZVOUS_MODE
        int
        range 0 8
-       default 0 if RENDEZVOUS_MODE_BYPASS
        default 1 if RENDEZVOUS_MODE_WIFI
        default 2 if RENDEZVOUS_MODE_BLE
        default 4 if RENDEZVOUS_MODE_THREAD

examples/ota-requestor-app/esp32/main/CHIPDeviceManager.cpp

@@ -69,12 +69,6 @@ CHIP_ERROR CHIPDeviceManager::Init(CHIPDeviceManagerCallbacks * cb)
         ConnectivityMgr().SetBLEAdvertisingEnabled(false);
         ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
     }
-    else
-    {
-        // If rendezvous is bypassed, enable SoftAP so that the device can still
-        // be communicated with via its SoftAP as needed.
-        ConnectivityMgr().SetWiFiAPMode(ConnectivityManager::kWiFiAPMode_Enabled);
-    }
 
     // Register a function to receive events from the CHIP device layer.  Note that calls to
     // this function will happen on the CHIP event loop thread, not the app_main thread.