[CERT-TEST-FAILURE] Inconsistent Group Cluster Behavior in Light-switch-app (Nordic): FeatureMap Read Succeeds but JoinGroup Returns Unsupported Cluster

[Ashwinigrl]

Feature Area

Other

Test Case

TC-BIND-2.3

Reproduction steps

Description:

While validating the TC-BIND-2.3 test case with the Groupcast feature on the Light-switch-app (Nordic platform), inconsistent behavior is observed for the Group cast cluster.

The JoinGroup command returns Unsupported Cluster.
However, the FeatureMap attribute read returns a successful (expected) response.

Expected Behavior:
If the Group cluster is not implemented in the sample app, all related interactions (both commands and attribute reads) should return Unsupported Cluster consistently.

Actual Behavior:

FeatureMap read → Successful response
JoinGroup command → Unsupported Cluster

This indicates partial or inconsistent implementation of the Group cluster.

1. Press the button 1 in nordic board nrf54L15-DK() to put DUT into a commissionable state.
2. Once DUT reach the commissionable state sent below mentioned command on TH.

./chip-tool pairing ble-thread 74 hex:<Hex data set> 20202021 3840

3. TH1 reads the DUT Groupcast featuremap attribute.

./chip-tool groupcast read feature-map 74 0

Verify that, TH1(Chip-tool) receives the featuremap attribute and Sender feature (bit 1) is set.

[1775123734.705] [13085:13087] [TOO] Endpoint: 0 Cluster: 0x0000_0065 Attribute 0x0000_FFFC DataVersion: 987778989
[1775123734.705] [13085:13087] [TOO] FeatureMap: 2(Example value)

4. TH1 sends Groupcast JoinGroup command with the following fields * GroupID = 1 * Endpoints = [EP1] — endpoint of the OnOff server on TH2 * KeySetID = 0x01a1 * Key = randomly generated key (Key1) to TH2 endpoint 0.

./chip-tool groupcast join-group 0x1 "[1]" 0x01a1 2 0 --Key hex:b0b1b2b3b4b5b6b7b8b9babbbcbdbebf --UseAuxiliaryACL 1

On TH1(Chip-tool), Verify the success response for JoinGroup

[1775808027.533] [4052:4054] [DMG] CommandPathIB =
[1775808027.533] [4052:4054] [DMG] {
[1775808027.533] [4052:4054] [DMG] EndpointId = 0x0,
[1775808027.533] [4052:4054] [DMG] ClusterId = 0x65,
[1775808027.533] [4052:4054] [DMG] CommandId = 0x0,
[1775808027.534] [4052:4054] [DMG] },
[1775808027.534] [4052:4054] [DMG]
[1775808027.534] [4052:4054] [DMG] StatusIB =
[1775808027.534] [4052:4054] [DMG] {
[1775808027.534] [4052:4054] [DMG] status = 0xc3 (UNSUPPORTED_CLUSTER),
[1775808027.534] [4052:4054] [DMG] },
[1775808027.534] [4052:4054] [DMG]
[1775808027.534] [4052:4054] [DMG] },
[1775808027.534] [4052:4054] [DMG]
[1775808027.534] [4052:4054] [DMG] },
[1775808027.534] [4052:4054] [DMG]
[1775808027.534] [4052:4054] [DMG] ],
[1775808027.535] [4052:4054] [DMG]
[1775808027.535] [4052:4054] [DMG] InteractionModelRevision = 12
[1775808027.535] [4052:4054] [DMG] },
[1775808027.535] [4052:4054] [DMG] Received Command Response Status for Endpoint=0 Cluster=0x0000_0065 Command=0x0000_0000 Status=0xc3
[1775808027.535] [4052:4054] [TOO] Error: IM Error 0x000005C3: General error: 0xc3 (UNSUPPORTED_CLUSTER)

Bug prevalence

Whenever I do this

GitHub hash of the SDK that was being used

cdb458b

Platform

raspi, nrf

Anything else?

Reference logs:

TC_BIND_2_3 (DUT).txt

TC_BIND_2_3 (CHIP-TOOL).txt

Sample app used to run this test:
Light switch app

[Ashwinigrl]

@jmartinez-silabs could you please take a look at this issue?