Matter 1.3 SVE

[hoorii-zzy]

Hello,

We want to compile the APP firmware for Matter 1.3SVE based on NCS with the Matter commit being 9f6d627e0262e1d023986291948bb4e845be803e. However, we are unsure which version of NCS to use. Can you provide a recommendation?

Yours

Jerry

[Sigurd Hellesvik]

Hi,

We do not yet support Matter 1.3.
See https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/protocols/matter/index.html.

On main, we are just integrating 1.2.

Regards,
Sigurd Hellesvik

[hoorii-zzy]

Hello,

I want to confirm one thing: if my device is a low-power device(SIT) and I want to enable ICD functionality, do I have to enable the ICD management cluster? Or is it sufficient to follow the Nordic's documentation and define CONFIG_CHIP_ENABLE_ICD_SUPPORT=y? Because I have encountered several ICDM SVE use cases that always fail.

Yours,

Jerry

[Sigurd Hellesvik]

See Enable Matter Intermittently Connected Devices support

Our Window Covering sample has ICD enabled by default.

[hoorii-zzy]

Thanks!

BTW, when I read the event-list attribute of the ICD management cluster, I always encounter the error "UNSUPPORTED_ATTRIBUTE", even though I have confirmed that I have checked it in ZAP. Could you please advise on how to resolve this problem?

Yours,

Jerry

[Sigurd Hellesvik]

hoorii-zzy said:

, when I read the event-list attribute of the ICD management cluster

Do you see this in the window management sample?

[hoorii-zzy]

Hi,

Yes, window-app example is the same error.

[Sigurd Hellesvik]

Could you post the command that you use when the error occurs?
Then I can check if this is a bug or not.

[hoorii-zzy]

Sigurd Hellesvik said:

Could you post the command that you use when the error occurs?

./chip-tool icdmanagement read event-list 1 0

[hoorii-zzy]

Hi,

What is the result of the verification? I hope you can please reply to me and provide a solution as soon as possible.

Yours,

Jerry

[Sigurd Hellesvik]

What happens if you try the following command?

./chip-tool icdmanagement read attribute-list 1 0

[hoorii-zzy]

The log is :

[1708501051.949683][11183:11185] CHIP:TOO: Endpoint: 0 Cluster: 0x0000_0046 Attribute 0x0000_FFFB DataVersion: 34489136

[1708501051.949797][11183:11185] CHIP:TOO: AttributeList: 14 entries

[1708501051.949826][11183:11185] CHIP:TOO: [1]: 0

[1708501051.949849][11183:11185] CHIP:TOO: [2]: 1

[1708501051.949872][11183:11185] CHIP:TOO: [3]: 2

[1708501051.949894][11183:11185] CHIP:TOO: [4]: 3

[1708501051.949917][11183:11185] CHIP:TOO: [5]: 4

[1708501051.949939][11183:11185] CHIP:TOO: [6]: 5

[1708501051.950030][11183:11185] CHIP:TOO: [7]: 65528

[1708501051.950053][11183:11185] CHIP:TOO: [8]: 65529

[1708501051.950075][11183:11185] CHIP:TOO: [9]: 65531

[1708501051.950098][11183:11185] CHIP:TOO: [10]: 65532

[1708501051.950121][11183:11185] CHIP:TOO: [11]: 65533

[1708501051.950360][11183:11185] CHIP:EM: <<< [E:29125i S:10702 M:258654000 (Ack:205884655)] (S) Msg TX to 1:0000000000000001 [F489] [UDP:[fe80::e65f:1ff:fe49:ae1a%wlan0]:5540] --- Type 0000:10 (SecureChannel:StandaloneAck)

[Sigurd Hellesvik]

0xfffa is missing from your list of supported attributes.

This is the reason to why event-list fails