[TC-ICDM-3.2]UI-python - DUT(lit-icd-app) Fails to Communicate with Test Harness After Reboot at Step 2c

Description:
In test case TC-ICDM-3.2, the DUT (lit-icd-app) fails to communicate with the Test Harness (TH) after rebooting at test step 2c. The test script does not handle the scenario where the DUT needs additional time to re-establish communication with the TH.

Steps to Reproduce:
From the Test-Harness user interface loaded the ICD management PICS file to select the test cases.
Selected the TC-ICDM-3.2 UI-Python test case to executed.
Executed the below mentioned command to put DUT into a commissionable state, ./lit-icd-app
Click the Start button on Test-Harness user interface.

Expected Behavior:
The DUT should successfully re-establish communication with the TH after rebooting at test step 2c and continue the test sequence.

Actual Behavior:
The DUT does not communicate with the TH after the reboot, and the test case fails at step 2c.

PFA Python script execution log :
TC-ICDM-3.2.log
TC-ICDM-3.2 DUT log.txt

Validated the test case using verification steps, it's worked as expected

TC-ICDM-3.2 DUT.txt
TC-ICDM-3.2 TH.txt

Additional Information:
Device: lit-icd-app (DUT)
Test Harness (TH):

Version: v2.11-beta3+fall2024
Sha: f52d40a

NOTE :
manual verification works, the issue appears to be solely script-related. Addressing the script’s handling of post-reboot communication should resolve the test failures.

Start by locating the UI-Python implementation of TC-ICDM-3.2 and reviewing the attached Python execution and DUT/TH logs around step 2c. Reproduce with ./lit-icd-app and compare the script path with the manual verification logs. Done means the script handles post-reboot communication and TC-ICDM-3.2 completes.