[CERT-TEST-FAILURE] TC-HSTAT-2.4 fails at Step 15 with InvalidCommand (0x85) for DisallowContinuous TestEventTrigger

Author: AshwinigrlCreated Sep 18, 2026Updated Sep 18, 2026
Labelsbugcert blockerneeds triage

Feature Area

Other

Test Case

TC-HSTAT-2.4

Reproduction steps

While validating TC-HSTAT-2.4 on the 1.7 TE2 TH, the test case fails at Step 15 when sending the TestEventTrigger command to the General Diagnostics Cluster.

The test attempts to send the following TestEventTrigger for the DisallowContinuous event:

EventTrigger = 0x0205000000000000

The DUT responds with InvalidCommand (0x85) instead of SUCCESS (0x00).

Failed Test Step

Step 15: TH sends TestEventTrigger command to General Diagnostics Cluster on Endpoint 0 with EnableKey field set to PIXIT.HSTAT.TEST_EVENT_TRIGGER_KEY and EventTrigger field set to PIXIT.HSTAT.TEST_EVENT_TRIGGER for DisallowContinuous event. Expected: DUT responds with status SUCCESS (0x00).

Observed Result

The DUT returns: Cluster = General Diagnostics (0x0033) Command = TestEventTrigger (0x0000) Status = 0x85 (InvalidCommand)

Relevant log:

Received Command Response Status for Endpoint=0 Cluster=0x0000_0033 Command=0x0000_0000 Status=0x85

matter.interaction_model.InteractionModelError: InteractionModelError: InvalidCommand (0x85)

The failure occurs while executing:

disallow_continuous_event() -> send_test_event_triggers(eventTrigger=0x0205000000000000)

The Matter test framework subsequently reports:

Details=Sending TestEventTrigger resulted in Unexpected error. Are they enabled in DUT? Command returned - 133 Relevant Log [MatterTest] Received Command Response Status for Endpoint=0 Cluster=0x0000_0033 Command=0x0000_0000 Status=0x85

InteractionModelError: InvalidCommand (0x85)

mobly.signals.TestFailure: Details=Sending TestEventTrigger resulted in Unexpected error. Are they enabled in DUT? Command returned - 133

Expected Result

The DUT should accept the TestEventTrigger command with: EventTrigger = 0x0205000000000000 and respond with: SUCCESS (0x00)

Reproduction steps: Command used to launch the DUT ./chip-all-clusters-app --camera-test-videosrc --camera-test-audiosrc --app-pipe /tmp/pavst_2_13_fifo Command used to run the python script: python3 TC_HSTAT_2_4.py --commissioning-method on-network --discriminator 3840 --passcode 20202021 --storage-path admin_storage.json --endpoint 1 --PICS

Bug prevalence

Whenever I do this

GitHub hash of the SDK that was being used

99a81bd32986c5292b0b1c9245c8e247c2ad717d

Platform

raspi

Anything else?

Python script References:

Reference failure logs: TC_HSTAT_2_4 (2).log

Source: project-chip/connectedhomeip