Skip to content
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] [NetworkCommissioning] LastNetworkStatus not set every place it needs to be #32021

Closed
tcarmelveilleux opened this issue Feb 8, 2024 · 0 comments · Fixed by #32156
Closed
Assignees
Labels
bug Something isn't working commissioning Involves placing devices on the network, initial setup NetworkCommissioning issues spec Mismatch between spec and implementation utility-cluster Work for Utility Clusters
Milestone

Comments

@tcarmelveilleux
Copy link
Contributor

  • In NetworkCommissioning cluster, SetLastNetworkStatusValue is not set on failure to Scan.
  • Spec says:

[[ref_LastNetworkingStatus]]
=== LastNetworkingStatus Attribute
This attribute SHALL indicate the status of the last attempt either scan or connect to an operational network, using this interface, whether by invocation of the <<ref_ConnectNetwork,ConnectNetwork>> command or by autonomous connection after loss of connectivity or during initial establishment. If no such attempt was made, or no network configurations exist in the <<ref_Networks,Networks>> attribute, then this attribute SHALL be set to null.

This attribute is present to assist with error recovery during Network commissioning and to assist in non-concurrent networking commissioning flows.

  • Affects 1.0 through 1.3 up to fix.
  • Likely was not caught because of insufficient error coverage in cert test cases.
@tcarmelveilleux tcarmelveilleux added bug Something isn't working spec Mismatch between spec and implementation utility-cluster Work for Utility Clusters commissioning Involves placing devices on the network, initial setup labels Feb 8, 2024
@tcarmelveilleux tcarmelveilleux added this to the 1.3 SVE milestone Feb 8, 2024
@tcarmelveilleux tcarmelveilleux self-assigned this Feb 8, 2024
tcarmelveilleux added a commit to tcarmelveilleux/connectedhomeip that referenced this issue Feb 15, 2024
This PR addresses several NetworkCommissioning issues
which are all inter-related:

- Attributes are never reported on change.
- ScanNetworks used to modify attributes that should not be modified
- LastNetworkStatus was not set where required
- Thread network scanning did not report error on SSID field provided
- All ConstraintErrors actually were reported as InvalidCommand
- Lacking results of directed scanning did not report NetworkNotFound

- Fixes project-chip#32024
- Fixes project-chip#32022
- Fixes project-chip#32021
- Fixes project-chip#32019
- Fixes project-chip#32018
- Fixes project-chip#31870

Testing done:
- TC-CNET-4.4 pass on ESP32 and Linux
- Commissioning works on ESP32 and Linux
- Manual testing of all attribute changes validated with chip-repl
  - Automated test beyond TC-CNET-4.4 coming as a follow-up
@mergify mergify bot closed this as completed in #32156 Feb 16, 2024
@mergify mergify bot closed this as completed in a04f478 Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working commissioning Involves placing devices on the network, initial setup NetworkCommissioning issues spec Mismatch between spec and implementation utility-cluster Work for Utility Clusters
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant