Matter v2.2.0 unable to android commission, with "pairing failed"

Ive been trying the last few Sdk versions to evaluate the matter examples without luck. With 2.2 released yesterday I jumped on that hoping it would clear up my issue, but no dice.

22.04 ubuntu with nrf-docker with v2.2.0, programmed the rcp and the matter light bulb example
rpi 3b+ setup like the 2.2 docs say ot-br-posix @ 0895ad5
I have the android chiptool associated with the 2.2 tag

Im unable to commission ble over thread, with "pairing failed" in android chiptool

My logs on the nrf52840 dk get to here before "I: 137257 [FS]Fail-safe timer expired"

D: 110318 [DMG]Decreasing reference count for CommandHandler, remaining 1
D: 110324 [DL]OpenThread State Changed (Flags: 0x1006c100)
D: 110330 [DL] Network Name: OpenThread
D: 110333 [DL] PAN Id: 0x46A7
D: 110336 [DL] Extended PAN Id: 0x0747C2C1E3CB1D09
D: 110341 [DL] Channel: 16
D: 110344 [DL] Mesh Prefix: fdde:ad00:beef::/64
D: 110348 [DL]OpenThread State Changed (Flags: 0x1100101d)
D: 110354 [DL] Device Role: DETACHED
D: 110358 [DL] Thread Unicast Addresses:
D: 110362 [DL] fdde:ad00:beef:0:a3c1:30d8:5d26:74f3/64 valid
D: 110368 [DL] fe80::94f5:b84b:42a5:9b84/64 valid preferred
D: 112781 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 112875 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 115350 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 117858 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 117915 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)
D: 120390 [DL]Write request received for CHIPoBLE RX characteristic (ConnId 0x00)
D: 122898 [DL]Sending indication for CHIPoBLE TX characteristic (ConnId 00, len 3)
D: 122956 [DL]Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

My logs on the pi are verbose, but something that stands out, but doesnt google anywhere else is a "Failed to process Child ID Request: Security"

Dec 08 01:02:47 raspberrypi otbr-agent[27385]: 05:29:33.813 [W] Mle-----------: Failed to process Child ID Request: Security
Dec 08 01:02:47 raspberrypi otbr-agent[27385]: 05:29:33.953 [I] Mac-----------: Frame tx attempt 16/16 failed, error:NoAck, len:126, seqnum:31, type:Data, src:6ae4f275a2ab4472, dst:beada8f9f39cdb0a, sec:yes, ackreq:yes
Dec 08 01:02:47 raspberrypi otbr-agent[27385]: 05:29:33.953 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:313, chksum:62da, ecn:no, to:beada8f9f39cdb0a, sec:yes, error:NoAck, prio:net
Dec 08 01:02:47 raspberrypi otbr-agent[27385]: 05:29:33.953 [N] MeshForwarder-: src:[fe80:0:0:0:68e4:f275:a2ab:4472]:19788
Dec 08 01:02:47 raspberrypi otbr-agent[27385]: 05:29:33.953 [N] MeshForwarder-: dst:[fe80:0:0:0:bcad:a8f9:f39c:db0a]:19788
Dec 08 01:02:47 raspberrypi otbr-agent[27385]: 05:29:33.992 [I] MeshForwarder-: Received IPv6 UDP msg, len:104, chksum:bcb5, ecn:no, from:beada8f9f39cdb0a, sec:no, prio:net, rss:-69.0
Dec 08 01:02:47 raspberrypi otbr-agent[27385]: 05:29:33.992 [I] MeshForwarder-: src:[fe80:0:0:0:bcad:a8f9:f39c:db0a]:19788
Dec 08 01:02:47 raspberrypi otbr-agent[27385]: 05:29:33.992 [I] MeshForwarder-: dst:[fe80:0:0:0:68e4:f275:a2ab:4472]:19788
Dec 08 01:02:47 raspberrypi otbr-agent[27385]: 05:29:33.992 [W] Mle-----------: Failed to process UDP: Duplicated
Dec 08 01:02:47 raspberrypi otbr-agent[27385]: 05:29:34.036 [I] MeshForwarder-: Received IPv6 UDP msg, len:104, chksum:bcb5, ecn:no, from:beada8f9f39cdb0a, sec:no, prio:net, rss:-69.0


Any idea what this could be?


Thanks

Parents
  • Hi Jacob and Denver,

    Sorry for the late reply. I just set up the same environment to do tests for Matter.

    I can recreate the same issue on our company network, but using home network or mobile phone as wifi host, the Matter light sample can successfully join the thread network formed by OTBR and function well.

    It is clear that the issue is caused by some configuration or restriction from the local network. In the meantime, please try to test with a different network. I will do further investigation into it and give you feedback later.

    Best regards,

    Charlie

Reply
  • Hi Jacob and Denver,

    Sorry for the late reply. I just set up the same environment to do tests for Matter.

    I can recreate the same issue on our company network, but using home network or mobile phone as wifi host, the Matter light sample can successfully join the thread network formed by OTBR and function well.

    It is clear that the issue is caused by some configuration or restriction from the local network. In the meantime, please try to test with a different network. I will do further investigation into it and give you feedback later.

    Best regards,

    Charlie

Children
No Data
Related