[Bug] [TC-WNCV-5.1, 6.1, 7.1] Simulated Test Case has no WindowCovering Cluster on chip-app1 (Test Harness v2.11-beta3.1+fall2024)

[Trishia]

Describe the bug

[TC-WNCV-5.1, 6.1, 7.1] Simulated Test Case has no WindowCovering Cluster on chip-app1 (Test Harness v2.11-beta3.1+fall2024).
You should change chip-app1 to chip-all-clusters-app in this [TC-WNCV-5.1] Simulated Test Case.

On the TH Logs:

Run Test Runner is Ready
--
TH Version: v2.11-beta3.1+fall2024
TH SHA: 9c1ef58
TH SDK SHA: 17b1a38
Test Run Executing
################################################################################
Test Suite Executing: FirstAppSuite
YAML Version: 17b1a38e909e7874593bcb87c31be03a5866f1d4
Setting up SDK container
th-sdk container started with configuration: {'privileged': True, 'detach': True, 'network': 'host', 'name': 'th-sdk', 'command': 'tail -f /dev/null', 'volumes': {'/var/run/dbus/system_bus_socket': {'bind': '/var/run/dbus/system_bus_socket', 'mode': 'rw'}, PosixPath('/var/tmp'): {'bind': '/logs', 'mode': 'rw'}, PosixPath('/var/paa-root-certs'): {'bind': '/paa-root-certs', 'mode': 'ro'}, PosixPath('/var/credentials/development'): {'bind': '/credentials/development', 'mode': 'ro'}, PosixPath('/home/ubuntu/certification-tool/backend/test_collections/matter/sdk_tests/sdk_checkout/python_testing'): {'bind': '/root/python_testing', 'mode': 'rw'}, 'mapped_data_model_volume': {'bind': '/root/python_testing/data_model', 'mode': 'rw'}, PosixPath('/home/ubuntu/certification-tool/backend/test_collections/matter/sdk_tests/support/python_testing/models/rpc_client/test_harness_client.py'): {'bind': '/root/python_testing/scripts/sdk/test_harness_client.py', 'mode': 'rw'}}}
Setting up test runner
Starting chip server
New Node Id generated: 0xb984a1e00143323
Sending command to SDK container: ./chip-app1 --interactive --port 9002 --trace_file "/logs/trace_log_2024-10-18_17.12.13_0xb984a1e00143323_CHIP_WEBSOCKET_SERVER.log" --trace_decode 1

On the DUT (As a Controller) Logs:

02:12:51.586  7728-7785  DMG                      D  ReportDataMessage =
02:12:51.586  7728-7785  DMG                      D  {
02:12:51.586  7728-7785  DMG                      D  	AttributeReportIBs =
02:12:51.586  7728-7785  DMG                      D  	[
02:12:51.586  7728-7785  DMG                      D  		AttributeReportIB =
02:12:51.587  7728-7785  DMG                      D  		{
02:12:51.587  7728-7785  DMG                      D  			AttributeDataIB =
02:12:51.587  7728-7785  DMG                      D  			{
02:12:51.587  7728-7785  DMG                      D  				DataVersion = 0x3ee75da,
02:12:51.587  7728-7785  DMG                      D  				AttributePathIB =
02:12:51.587  7728-7785  DMG                      D  				{
02:12:51.587  7728-7785  DMG                      D  					Endpoint = 0x1,
02:12:51.587  7728-7785  DMG                      D  					Cluster = 0x1d,
02:12:51.587  7728-7785  DMG                      D  					Attribute = 0x0000_0001,
02:12:51.587  7728-7785  DMG                      D  				}
02:12:51.587  7728-7785  DMG                      D  					
02:12:51.587  7728-7785  DMG                      D  				Data = [
02:12:51.588  7728-7785  DMG                      D  						3 (unsigned), 4 (unsigned), 6 (unsigned), 8 (unsigned), 29 (unsigned), 40 (unsigned), 43 (unsigned), 45 (unsigned), 64 (unsigned), 65 (unsigned), 98 (unsigned), 768 (unsigned), 1030 (unsigned), 1106 (unsigned), 
02:12:51.588  7728-7785  DMG                      D  				],
02:12:51.588  7728-7785  DMG                      D  			},
02:12:51.588  7728-7785  DMG                      D  			
02:12:51.588  7728-7785  DMG                      D  		},
02:12:51.588  7728-7785  DMG                      D  		
02:12:51.588  7728-7785  DMG                      D  	],
02:12:51.588  7728-7785  DMG                      D  	
02:12:51.588  7728-7785  DMG                      D  	SuppressResponse = true, 
02:12:51.588  7728-7785  DMG                      D  	InteractionModelRevision = 11
02:12:51.588  7728-7785  DMG                      D  }
02:12:51.591  7728-7785  System.out               I  put : 1, status Success, clusterStatus None
...
02:12:51.605  7728-7785  Descriptor...onFragment  D  ServerClusterList: [Identify, Groups, OnOff, LevelControl, Descriptor, BasicInformation, LocalizationConfiguration, UnitLocalization, FixedLabel, UserLabel, ScenesManagement, ColorControl, OccupancySensing, ThreadBorderRouterManagement]

@hiltonlima
I can't test WindowCovering Client TCs any more for now.
Could you look into this issue and fix it as soon as possible?

Steps to reproduce the behavior

No response

Expected behavior

No response

Log files

No response

PICS file

No response

Screenshots

No response

Environment

• TH Version: Test Harness v2.11-beta3.1+fall2024
• OS: Ubuntu Server 24.04.1/RaspberryPi 4

Additional Information

No response

[Trishia]

[TC-WNCV-5.1, 6.1, 7.1] Simulated Test Case still has no WindowCovering Cluster in chip-app1 on TH (Version: v2.11+fall2024).

@hiltonlima When will you fix this issue?? This is urgent issue for DUT preparing Matter 1.4 Certification so you should update TH as soon as possible.

[fabiowmm]

@rquidute please take over this one.

[rquidute]

I was able to run successfully TC-WNCV-6.1 and TC-WNCV-7.1.
The TC-WNCV-5.1 I did not had the manual steps handy.

• TC-WNCV-7.1 Logs:

UI_Test_Run_2024_12_18_17_53_48.log

• TC-WNCV-6.1 Logs:
  UI_Test_Run_2024_12_18_17_52_33.log