You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TH should be able to connect DUT using 1st ACCESSPOINT with connected status as TRUE when the fail-safe is disarmed after connecting to 2nd ACCESSPOINT.
Reproduction steps
Paired TH ( CHIP_TOOL ) and DUT ( ALL-CLUSTERS-APP) through ble-wifi
Survensa
changed the title
[TC-CNET-4.11] TH is not able to connect back to 1st access point after fail-safe is disarmed from 2nd access point
[CERT-TEST-FAILURE]-TC-CNET- 4.11 - Test failed
Jul 10, 2023
This may not make it to Sep1 due to seemingly more complex changes.
It is odd that the network list says "not connected" yet we are communicating via chip-tool (presumably over ip).
Feature Area
Other
Test Case
TC-CNET-4.11
Summary
TH should be able to connect DUT using 1st ACCESSPOINT with connected status as TRUE when the fail-safe is disarmed after connecting to 2nd ACCESSPOINT.
Reproduction steps
Paired TH ( CHIP_TOOL ) and DUT ( ALL-CLUSTERS-APP) through ble-wifi
Armed the fail-safe :
./chip-tool generalcommissioning arm-fail-safe 900 1 1 0
Checked the 1st connected ACCESSPOINT :
./chip-tool networkcommissioning read networks 1 0
Removed the network :
./chip-tool networkcommissioning remove-network hex:47524C50726976617465 1 0 --Breadcrumb 1
Added 2nd ACCESSPOINT network :
./chip-tool networkcommissioning add-or-update-wi-fi-network Sbee_Moto Sunsuraj 1 0 --Breadcrumb 1
Connected 2nd network and checked the network status :
./chip-tool networkcommissioning connect-network hex:536265655F4D6F746F 1 0 --Breadcrumb 2
and./chip-tool networkcommissioning read networks 1 0
Now Disarmed the fail-safe :
./chip-tool generalcommissioning arm-fail-safe 0 0 1 0
Checked whether the network is reverted to 1st ACCESS POINT :
./chip-tool networkcommissioning read networks 1 0
Actual Outcome :
Expected Outcome:
Bug prevalence
Whenever I do this
GitHub hash of the SDK that was being used
bfa0580
Platform
raspi
Platform Version(s)
RPI-4, 8GB-RAM variant
Log :
TC_CNET_4_11_CNTRL.txt
TC_CNET_4_11_DUT.txt
The text was updated successfully, but these errors were encountered: