Hi @shubhamdp ,
ESP-Matter Version: 1.4.2
ESP-IDF Version: 5.4.1
Test Harness Version: v2.13+summer2025
Endpoint Hierarchy:
Endpoint 0 - Root Node
Endpoint 1 - Aggregator Endpoint
Endpoint 2 (dynamic ep) - Color Temperature Light Endpoint
Endpoint 3 (dynamic ep) - Extended Color Light Endpoint
Issue 1: MoveColorTemperature command sent with unsupported MoveMode value
While executing TC-CC-10.1 on a dynamic endpoint (Endpoint 2), I observed that during Step 2f, the Test Harness sends a MoveColorTemperature command with MoveMode = 2.
According to the Color Control cluster specification, the supported MoveMode values for MoveColorTemperature are:
Value 2 appears to be reserved/invalid for this command.
As a result, the DUT responds with an Invalid Command error.
The relevant section in the test script appears to be:
self.step("2f")
if self.pics_guard(self.check_pics("CC.S.F04")):
await self.TH1.SendCommand(
self.dut_node_id,
self.matter_test_config.endpoint,
cluster.Commands.MoveColorTemperature(...)
)
await asyncio.sleep(10)
- The same test step passes when executed against Endpoint 3.
- The failure is only observed on Endpoint 2 (dynamic endpoint).
Please find attached the test logs for EP2: TC-CC-10.1.log
- Is this a known issue in TH v2.13+summer2025?
- Should the DUT accept MoveMode=2, or should the test script be updated?
Issue 2: AddScene / RecallScene extension field handling
In the same test case, I observed failures during the AddScene and RecallScene related steps.
When the Scene Extension Field contains Color Control attributes that are not supported by the application, the test reports status code 133.
The attribute list being used in the test script is as follows:
kCCAttributeValueIDs = [0x0001, 0x0003, 0x0004, 0x0007, 0x4000, 0x4001, 0x4002, 0x4003, 0x4004]
If I remove the unsupported attributes from the extension field, the test passes successfully on Endpoint 3.
How should unsupported attributes in the Scene Extension Field be handled according to the specification?
Hi @shubhamdp ,
ESP-Matter Version: 1.4.2
ESP-IDF Version: 5.4.1
Test Harness Version: v2.13+summer2025
Endpoint Hierarchy:
Endpoint 0 - Root Node
Endpoint 1 - Aggregator Endpoint
Endpoint 2 (dynamic ep) - Color Temperature Light Endpoint
Endpoint 3 (dynamic ep) - Extended Color Light Endpoint
Issue 1: MoveColorTemperature command sent with unsupported MoveMode value
While executing TC-CC-10.1 on a dynamic endpoint (Endpoint 2), I observed that during Step 2f, the Test Harness sends a MoveColorTemperature command with MoveMode = 2.
According to the Color Control cluster specification, the supported MoveMode values for MoveColorTemperature are:
Value 2 appears to be reserved/invalid for this command.
As a result, the DUT responds with an Invalid Command error.
The relevant section in the test script appears to be:
Please find attached the test logs for EP2: TC-CC-10.1.log
Issue 2: AddScene / RecallScene extension field handling
In the same test case, I observed failures during the AddScene and RecallScene related steps.
When the Scene Extension Field contains Color Control attributes that are not supported by the application, the test reports status code 133.
The attribute list being used in the test script is as follows:
kCCAttributeValueIDs = [0x0001, 0x0003, 0x0004, 0x0007, 0x4000, 0x4001, 0x4002, 0x4003, 0x4004]If I remove the unsupported attributes from the extension field, the test passes successfully on Endpoint 3.
How should unsupported attributes in the Scene Extension Field be handled according to the specification?