We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
chip-tool uses the same node id every time, which can cause problems due to multiple entities being commissioned with the same node id
Randomize node ids in chip-tool during pairing.
The text was updated successfully, but these errors were encountered:
I guess right now the node id is not stored anywhere, just hardcoded....
I guess we could store it in the persistent storage, and reset for the pairing commands? @vivien-apple
Sorry, something went wrong.
Have chip-tool generate a random remote node id every time it pairs.
8364d6a
This way multiple things we pair don't step on each other's toes as far as mdns advertisements go. Fixes project-chip#8439
Have chip-tool generate a random remote node id every time it pairs. (#…
1571f74
…8450) This way multiple things we pair don't step on each other's toes as far as mdns advertisements go. Fixes #8439
Have chip-tool generate a random remote node id every time it pairs. (p…
dd59744
…roject-chip#8450) This way multiple things we pair don't step on each other's toes as far as mdns advertisements go. Fixes project-chip#8439
bzbarsky-apple
Successfully merging a pull request may close this issue.
Problem
chip-tool uses the same node id every time, which can cause problems due to multiple entities being commissioned with the same node id
Proposed Solution
Randomize node ids in chip-tool during pairing.
The text was updated successfully, but these errors were encountered: