• State Verified Answer
  • Replies 8 replies
  • Subscribers 74 subscribers
  • Views 1400 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 308086
Options

NRF Connect SDK of Matter Alexa commissioning problem

mg Jeong 
Hello,
I modified and tested the Mater sample of ncs v2.3.0. (bulb sample)

I'm currently connecting home hubs from various manufacturers to Mater, and I'm having issues with the harmful Amazon Alexa commissioning.
It seems that one operation does not become kCommissioningComplete until PairingAttach.
In addition to the Nordic board, the ESP32 board makes Alexa commissioning no problem.

The board used is the nrf7002DK board and works with Matter via WiFI.
Below is the corresponding log.
please confirm. thank you.


 34626 [EM]>>> [E:15491r M:148191060] (S) Msg RX from 1:FFFFFFFB00000000 [2D8B] --- Type 0001:08 (IM:InvokeCommandRequest)
E: # CLUST-CALLBACK: UNKNOWN CLUSTER:0x00000030 ATTR:0x00000000 VAL:14
I: 34645 [EM]<<< [E:15491r M:211231927] (S) Msg TX to 1:FFFFFFFB00000000 [2D8B] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 34656 [IN](S) Sending msg 211231927 on secure session with LSID: 41202
I: 34717 [EM]>>> [E:15492r M:148191061] (S) Msg RX from 1:FFFFFFFB00000000 [2D8B] --- Type 0001:08 (IM:InvokeCommandRequest)
I: BLE DATA : 4
I: BLE DATA : 4
I: BLE DATA : 4
I: BLE DATA : 4
I: BLE DATA : 4
I: BLE DATA : 4
I: BLE DATA : 4
I: 38496 [DL]Wi-Fi scan done (0)
I: 40089 [DL]Connection to iot.dev.desk5 requested
E: 40094 [DL]Long dispatch time: 1598 ms, for event type 3
I: BLE DATA : 4
I: BLE DATA : 4
I: BLE DATA : 4
I: BLE DATA : 4
I: BLE DATA : 4
I: BLE DATA : 4
I: BLE DATA : 4
I: BLE DATA : 4
I: MBO: Disable MBO/OCE due to misbehaving AP not having enabled PMF
I: wlan0: SME: Trying to authenticate with 58:86:94:b6:10:c2 (SSID='iot.dev.desk5' freq=5180 MHz)
I: wlan0: Trying to associate with 58:86:94:b6:10:c2 (SSID='iot.dev.desk5' freq=5180 MHz)
I: wlan0: Associated with 58:86:94:b6:10:c2
I: MBO: Disable MBO/OCE due to misbehaving AP not having enabled PMF
I: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
I: wlan0: WPA: Key negotiation completed with 58:86:94:b6:10:c2 [PTK=CCMP GTK=CCMP]
I: wlan0: CTRL-EVENT-CONNECTED - Connection to 58:86:94:b6:10:c2 completed [id=0 id_str=]
I: 44028 [DL]Connected to WiFi network
E: # CLUST-CALLBACK: UNKNOWN CLUSTER:0x00000030 ATTR:0x00000000 VAL:16
I: 44039 [EM]<<< [E:15492r M:211231928] (S) Msg TX to 1:FFFFFFFB00000000 [2D8B] --- Type 0001:09 (IM:InvokeCommandResponse)
I: 44049 [IN](S) Sending msg 211231928 on secure session with LSID: 41202
I: 44056 [DIS]Advertise operational node D3867B9B8CEE2D8B-014DB4CABE723530
D: 44071 [DIS]Responding with _matter._tcp.local
D: 44075 [DIS]Responding with D3867B9B8CEE2D8B-014DB4CABE723530._matter._tcp.local
D: 44082 [DIS]Responding with D3867B9B8CEE2D8B-014DB4CABE723530._matter._tcp.local
D: 44090 [DIS]Responding with F4CE360021D6.local
D: 44094 [DIS]Responding with F4CE360021D6.local
D: 44098 [DIS]Responding with _ID3867B9B8CEE2D8B._sub._matter._tcp.local
I: 44105 [DIS]mDNS service published: _matter._tcp
I: 44109 [SVR]Operational advertising enabled
I: 44118 [SWU]Stopping the watchdog timer
I: 44122 [SWU]Starting the periodic query timer, timeout: 86400 seconds
I: # USER-EVENT: PAIRING ATTACH
I: # UART-SEND: MSG [118]: *ICT*PAIRING

*ICT*IPRELEASED

*ICT*ASSOCIATED:0

*ICT*IPALLOCATED:192.168.0.2 255.255.255.0 192.168.0.1 192.168.0.1


I: 44155 [DIS]Updating services using commissioning mode 0
E: 44160 [IN]SO_REUSEPORT failed: 109
I: 44169 [DIS]CHIP minimal mDNS started advertising.
I: BLE DATA : 4
I: 44212 [DIS]Advertise operational node D3867B9B8CEE2D8B-014DB4CABE723530
D: 44219 [DIS]Responding with _matter._tcp.local
D: 44224 [DIS]Responding with D3867B9B8CEE2D8B-014DB4CABE723530._matter._tcp.local
D: 44231 [DIS]Responding with D3867B9B8CEE2D8B-014DB4CABE723530._matter._tcp.local
D: 44238 [DIS]Responding with F4CE360021D6.local
D: 44243 [DIS]Responding with F4CE360021D6.local
D: 44247 [DIS]Responding with _ID3867B9B8CEE2D8B._sub._matter._tcp.local
I: 44258 [DIS]mDNS service published: _matter._tcp
I: 44264 [DIS]Advertise commission parameter vendorID=65521 productID=32773 discriminator=3840/15 cm=0
D: 44280 [DIS]Responding with _matterc._udp.local
D: 44285 [DIS]Responding with 9073414D56A40517._matterc._udp.local
D: 44290 [DIS]Responding with F4CE360021D6.local
D: 44295 [DIS]Responding with F4CE360021D6.local
D: 44299 [DIS]Responding with _V65521._sub._matterc._udp.local
D: 44305 [DIS]Responding with _S15._sub._matterc._udp.local
D: 44310 [DIS]Responding with _L3840._sub._matterc._udp.local
D: 44316 [DIS]Responding with 9073414D56A40517._matterc._udp.local
I: 44322 [DIS]CHIP minimal mDNS configured as 'Commissionable node device'; instance name: 9073414D56A40517.
I: 44349 [DIS]mDNS service published: _matterc._udp
E: 44354 [DL]Long dispatch time: 199 ms, for event type 32784
E: # CLUST-CALLBACK: UNKNOWN CLUSTER:0x0000002A ATTR:0x00000002 VAL:1
E: # CLUST-CALLBACK: UNKNOWN CLUSTER:0x0000002A ATTR:0x00000003 VAL:255
D: 44378 [IN]Clearing BLE pending packets.
I: 44382 [BLE]Releasing end point's BLE connection back to application.
I: 44388 [DL]Closing BLE GATT connection (ConnId 00)
I: 44484 [DL]BLE GAP connection terminated (reason 0x16)
I: 44489 [DL]Current number of connections: 0/1
I: BLE DATA : 4

  • 0 in reply to mg Jeong

    Hi, 

    I see that this case has fallen in between two chairs (so to speak). Apologies for the inconvenience that has caused. Could you verify if this inquiry is still something that you need an answer to or if you've resolved it yourself in the meanwhile? I'll push for a response from the Matter team if you still need an answer

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Hi,

    I haven't been able to resolve that issue yet.
If you think it is necessary for material analysis, we would appreciate it if you could leave an inquiry to the Matter team.
  • 0 in reply to mg Jeong

    Hi,

    Some feedback here from the Matter team. Following the information they were able to extract from this case they were not able to reproduce the commissioning issues you're observing with NCS v2.4.1, which is the first SDK version with WIFI production support, i.e the version of the SDK which is now recommended for WiFi. Are you able to to get everything up and running with NCS v2.4.1 instead of 2.3.0?

    Regarding the part of the case they might need more information from: It is hard to understand what specifically does not work, so if you can provide a step-by-step reproduction guide that might be helpful. 

    Could you also explain what the code modification achieves? I.e did it resolve the issue?

    Kind regards,
    Andreas

Related
Terms of service