-
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
[BUG] onnetwork commissioning doesn't add network to networks list #24684
Comments
If a device is placed on the network through non-Matter means, then either the network should not appear in the networks list, or whatever did the placing on the network should explicitly add the network there. The first of those is argued for by this part of the spec:
but the spec does have provisions for the Ethernet version of the network commissioning cluster to automatically populate the list with the one entry.... So really, this needs to be raised as a spec issue to clarify behavior. |
To my reading that spec paragraph simply talks about the fact that the list order reflects configuration precedence and doesn't change by itself (e.g. when the primary network is unavailable and the device falls back to the secondary network). |
closing issue, onnetwork devices should not have network commissioning cluster |
Reproduction steps
Connect wifi device to the same wifi network as the commissioner beforehand
Commission the device using onnetwork pairing
./chip-tool pairing onnetwork 1 20202021
Read the networks list, it should show 0 entries
./chip-tool networkcommissioning read networks 1 0
AddOrUpdateWiFiNetwork
is not calledCommitConfiguration
storing an emptymStagingNetwork
and the wifi is not persisted in kvs for Ameba platformIs this an expected behaviour? Should platform code implement adding the network or should it be the controller's job? If it is controller's job, how would the wifi password be known to the controller?
Bug prevalence
always
GitHub hash of the SDK that was being used
bdefbcb
Platform
ameba, other
Platform Version(s)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: