-
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] Network commissioning support on Controller #4622
[controller] Network commissioning support on Controller #4622
Conversation
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.
@erjiaqing thank you for doing this! LGTM 👍
Few questions - more about specification..:
- How controller obtains Thread Operational Credentials (is it out of the spec, and we should use MeshCop connection to Thread Border Router)?
- How Controller will know if the device operates on WiFi or Thread? Or the user will always need to know that and configure it manually?
src/app/encoder.cpp
Outdated
.Put8(kSeqNum) | ||
.Put8(ZCL_ADD_THREAD_NETWORK_COMMAND_ID) | ||
.Put(static_cast<uint8_t>(operationalDatasetStrLen)) | ||
.Put(reinterpret_cast<char *>(operationalDataset)) |
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.
Just a question.. Why we send Operational Dataset in a form of a string and not in the binary form of Operational Dataset TLV?
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.
@vivien-apple I think we need BYTE_STRING type support in encoder and dispatcher. (item 1 in #4503 )
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.
Right. String are not a first class citizen of the encoder at the moment. I need to have a look at them at some point, since I think I have seen some bugs even for regular strings...
</description>connectedhomeip/src/app/zap-templates/zcl/provisioning.xml Lines 61 to 71 in f1b7b31
This comment was generated by todo based on a
|
</description>connectedhomeip/src/app/zap-templates/zcl/provisioning.xml Lines 67 to 77 in f1b7b31
This comment was generated by todo based on a
|
</description>connectedhomeip/src/app/zap-templates/zcl/provisioning.xml Lines 73 to 83 in f1b7b31
This comment was generated by todo based on a
|
f277155
to
8c124a3
Compare
examples/all-clusters-app/all-clusters-common/all-clusters-app.zap
Outdated
Show resolved
Hide resolved
examples/all-clusters-app/all-clusters-common/all-clusters-app.zap
Outdated
Show resolved
Hide resolved
@vivien-apple All comment resolved, PTAL. |
Size increase report for "nrfconnect-example-build" from e76ed54
Full report output
|
Size increase report for "esp32-example-build" from e76ed54
Full report output
|
@woody-apple PTAL |
…ject-chip#4622)" This reverts commit 1a78a5f.
Problem
Add network provisioning cluster define for provisioning use, also adds support on controller side.
Support on end device side will be a seperate PR later.
This PR also fixs support for ByteString in encoder for interaction model.
Summary of Changes
See above.
Fixes #3945