-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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.
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
[controller] Add IP rendezvous feature to CHIP Device controller #4050
Conversation
@@ -530,10 +536,35 @@ void nl_Chip_DeviceController_SetLogFilter(uint8_t category) | |||
CHIP_ERROR nl_Chip_DeviceController_Connect(chip::DeviceController::ChipDeviceController * devCtrl, BLE_CONNECTION_OBJECT connObj, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unrelated question: why do we have a 'nl' prefix here? I am generally used to nl meaning 'nest labs' and then we can replace with just 'chip_DeviceController_connect' and similar and omit the nl prefix.
@andy31415 @rwalker-apple PTAL |
Size increase report for "esp32-example-build" from d2645f9
Full report output
|
Size increase report for "nrfconnect-example-build" from d2645f9
Full report output
|
Problem
Basic IP rendezvous is supported on device side, however, when using chip-tool pairing softap:
It does not work.
Summary of Changes
chip-tool pairing softap work
connect -ip
command to python bindingTesting
Tested w/ rpi running ubuntu 20.10 desktop.
After this PR, chip-device-ctrl can establish pase sessions, however, no traffic will use it, I will submit another pr for adding cluster support to chip device controller python binding. There are some special checks for BLE rendezvous, and they should be removed in the future after network provisioning cluster is ready.
Fixes #4038