Matter commissioning fails between two nrf52840 boards

RE: Matter commissioning fails between two nrf52840 boards

AHaug — Thu, 21 Jul 2022 10:42:57 GMT

Hi again,

Back with some late input.

The issue you had with nrfutil could be caused by you having both python3.8 and python3.10. Check your PATH to make sure you're using the correct version for nrfutil (python3.10) and have that selected/remove the older modules.

With regards to the BLE connection issue on a RPi: We've spent a lot of time trying to reproduce and analyze cases reported by customers and the majority of the cases end up beeing known and reported to the manufactorer of the BLE chip on RPi. Usually it helps retrying to connect to the RPi. Unfortunately since this seems to be a 3rd party issue, I would recommend you to ask the RPi support for more information here. If we can "prove" (strongly imply) that this part of the issue is on our side, we will of course try to solve it.

I would also try using another BLE adapter.

We will continue to look into this issue, but I hope this helps for now.

Kind regards,
Andreas

RE: Matter commissioning fails between two nrf52840 boards

braden — Tue, 19 Jul 2022 17:19:43 GMT

Ok, I decided to wipe the pi and start over. Same result. However, I see that I'm using BT v5.53, when the chip-tool guide says to use v5.55+ (which requires Ubuntu 22+). So I wiped the pi again and installed Ubuntu 22 64bit ARM.

Setup was slightly painful. Mostly I followed the guides, but had to install a few extra things to get matter to build.

apt-get update
apt install python3.10-venv
apt-get install libgtk-3-dev
apt-get install python-dev-is-python3

Finally, everything was built with the requisite BT version.

$ bluetoothctl version
Version 5.64

Well, it turns out that bluetooth on the RPi just has a million and one problems. I've now encountered many more errors that sound like `failed to connect - some bluetooth error`.

It seems this hardware setup is not going to work. Time to abandon ship and build a virtual one.

RE: Matter commissioning fails between two nrf52840 boards

braden — Mon, 18 Jul 2022 18:53:20 GMT

Now, after reflashing the dongle, I am back at the previous error:

...
[1658169487.273242][2552:2555] CHIP:DL: FAIL: ConnectDevice : GDBus.Error:org.bluez.Error.Failed: Software caused connection abort (36)
[1658169487.273525][2552:2557] CHIP:DL: HandlePlatformSpecificBLEEvent 16386
[1658169487.273607][2552:2557] CHIP:CTL: Commissioning discovery over BLE failed: ../../src/platform/Linux/bluez/Helper.cpp:1775: CHIP Error 0x000000AC: Internal error
...
[1658169515.132848][2552:2552] CHIP:TOO: Run command failure: ../../examples/chip-tool/commands/pairing/PairingCommand.cpp:151: CHIP Error 0x00000003: Incorrect state

I have verified that bluetooth seems to be working tho.

$ sudo apt-get upgrade pi-bluetooth
Reading package lists... Done
Building dependency tree       
Reading state information... Done
pi-bluetooth is already the newest version (0.1.15ubuntu0~20.04.1).
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  libfwupdplugin1
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ sudo apt-get upgrade bluez
Reading package lists... Done
Building dependency tree       
Reading state information... Done
bluez is already the newest version (5.53-0ubuntu3.6).
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  libfwupdplugin1
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ sudo service bluetooth status
● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-07-18 18:25:15 UTC; 16min ago
       Docs: man:bluetoothd(8)
   Main PID: 2314 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4435)
     CGroup: /system.slice/bluetooth.service
             └─2314 /usr/lib/bluetooth/bluetoothd

Jul 18 18:25:15 ubuntu systemd[1]: Starting Bluetooth service...
Jul 18 18:25:15 ubuntu bluetoothd[2314]: Bluetooth daemon 5.53
Jul 18 18:25:15 ubuntu systemd[1]: Started Bluetooth service.
Jul 18 18:25:15 ubuntu bluetoothd[2314]: Starting SDP server
Jul 18 18:25:15 ubuntu bluetoothd[2314]: Bluetooth management interface 1.14 initialized

$ sudo bluetoothctl
Agent registered
[CHG] Controller E4:5F:01:AE:C9:43 Pairable: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller E4:5F:01:AE:C9:43 Discovering: yes
[CHG] Device 5E:6B:F7:31:0B:02 RSSI: -70
[CHG] Device 5E:6B:F7:31:0B:02 ManufacturerData Key: 0x004c
[CHG] Device 5E:6B:F7:31:0B:02 ManufacturerData Value:
  0c 0e 00 4f 41 30 66 b4 80 6e 23 67 52 ec 3e 4d  ...OA0f..n#gR.>M
  10 06 4e 1d 64 e3 97 28                          ..N.d..(        
[NEW] Device 50:01:00:00:01:2E Flash-012E
[CHG] Device 7D:8C:74:DF:19:3D RSSI: -58
[CHG] Device 7D:8C:74:DF:19:3D TxPower: 12
[CHG] Device 7D:8C:74:DF:19:3D ManufacturerData Key: 0x004c
[CHG] Device 7D:8C:74:DF:19:3D ManufacturerData Value:
  10 06 5b 1d 8c de fe a8                          ..[.....

As well, otbr seems fine.

$ sudo service otbr-agent status
● otbr-agent.service - OpenThread Border Router Agent
     Loaded: loaded (/lib/systemd/system/otbr-agent.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-07-18 18:20:09 UTC; 21min ago
    Process: 2099 ExecStartPre=/usr/sbin/service mdns start (code=exited, status=0/SUCCESS)
   Main PID: 2106 (otbr-agent)
      Tasks: 1 (limit: 4435)
     CGroup: /system.slice/otbr-agent.service
             └─2106 /usr/sbin/otbr-agent -I wpan0 -B wlan0 spinel+hdlc+uart:///dev/ttyACM0 trel://wlan0

Jul 18 18:41:18 ubuntu otbr-agent[2106]: 00:21:09.494 [I] MeshForwarder-:     src:[fe80:0:0:0:b023:fc87:27d8:74ca]:19788
Jul 18 18:41:18 ubuntu otbr-agent[2106]: 00:21:09.495 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jul 18 18:41:24 ubuntu otbr-agent[2106]: 00:21:15.418 [I] Mle-----------: Send Advertisement (ff02:0:0:0:0:0:0:1)
Jul 18 18:41:24 ubuntu otbr-agent[2106]: 00:21:15.424 [I] MeshForwarder-: Sent IPv6 UDP msg, len:90, chksum:9805, ecn:no, to:0xffff, sec:no, prio:net
Jul 18 18:41:24 ubuntu otbr-agent[2106]: 00:21:15.424 [I] MeshForwarder-:     src:[fe80:0:0:0:b023:fc87:27d8:74ca]:19788
Jul 18 18:41:24 ubuntu otbr-agent[2106]: 00:21:15.424 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788
Jul 18 18:41:39 ubuntu otbr-agent[2106]: 00:21:30.559 [I] Mle-----------: Send Announce on channel 26
Jul 18 18:41:39 ubuntu otbr-agent[2106]: 00:21:30.566 [I] MeshForwarder-: Sent IPv6 UDP msg, len:83, chksum:eb65, ecn:no, to:0xffff, sec:yes, prio:net
Jul 18 18:41:39 ubuntu otbr-agent[2106]: 00:21:30.566 [I] MeshForwarder-:     src:[fe80:0:0:0:b023:fc87:27d8:74ca]:19788
Jul 18 18:41:39 ubuntu otbr-agent[2106]: 00:21:30.566 [I] MeshForwarder-:     dst:[ff02:0:0:0:0:0:0:1]:19788

RE: Matter commissioning fails between two nrf52840 boards

braden — Mon, 18 Jul 2022 18:12:37 GMT

I'm trying this again today, seeing similar results.

To mix things up, I thought I'd build and flash the board on my pi instead of my pc. Following this guide, I failed at step 6 with

~/ot-nrf528xx$ pip install -U nrfutil
Collecting nrfutil
  Using cached nrfutil-6.1.6.tar.gz (844 kB)
Requirement already satisfied, skipping upgrade: click in /usr/lib/python3/dist-packages (from nrfutil) (7.0)
Collecting crcmod
  Using cached crcmod-1.7.tar.gz (89 kB)
Collecting ecdsa
  Using cached ecdsa-0.18.0-py2.py3-none-any.whl (142 kB)
Collecting intelhex
  Using cached intelhex-2.3.0-py2.py3-none-any.whl (50 kB)
Collecting libusb1==1.9.3
  Using cached libusb1-1.9.3-py3-none-any.whl (60 kB)
ERROR: Could not find a version that satisfies the requirement pc_ble_driver_py>=0.16.4 (from nrfutil) (from versions: 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.6.1, 0.6.2, 0.8.0, 0.8.1, 0.9.0, 0.9.1, 0.10.0, 0.11.0, 0.11.1, 0.11.2, 0.11.3, 0.11.4)
ERROR: No matching distribution found for pc_ble_driver_py>=0.16.4 (from nrfutil)

I saw somesone suggest uninstalling and reinstalling pc-ble-driver-py, so I

~/ot-nrf528xx$ pip uninstall pc-ble-driver-py
WARNING: Skipping pc-ble-driver-py as it is not installed.

Interesting. Anyway...

~/ot-nrf528xx$ pip install pc-ble-driver-py
Collecting pc-ble-driver-py
  Downloading pc_ble_driver_py-0.11.4.tar.gz (8.0 MB)
     |████████████████████████████████| 8.0 MB 72 kB/s 
Processing /home/ubuntu/.cache/pip/wheels/8e/70/28/3d6ccd6e315f65f245da085482a2e1c7d14b90b30f239e2cf4/future-0.18.2-py3-none-any.whl
Collecting wrapt
  Downloading wrapt-1.14.1-cp38-cp38-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (81 kB)
     |████████████████████████████████| 81 kB 1.9 MB/s 
Building wheels for collected packages: pc-ble-driver-py
  Building wheel for pc-ble-driver-py (setup.py) ... done
  Created wheel for pc-ble-driver-py: filename=pc_ble_driver_py-0.11.4-py3-none-any.whl size=8095775 sha256=456d8f95a3b916b5c2028789e97d6fc99055f08b2e04a482c0e2128265c5eabc
  Stored in directory: /home/ubuntu/.cache/pip/wheels/39/f5/9a/55f39f0f091a0f6c315e332ec1c909c52e2819bc2972c2494a
Successfully built pc-ble-driver-py
Installing collected packages: future, wrapt, pc-ble-driver-py
Successfully installed future-0.18.2 pc-ble-driver-py-0.11.4 wrapt-1.14.1

With the ble driver installed, time to install nrfUtil

~/ot-nrf528xx$ python3 -m pip install -U nrfutil
Defaulting to user installation because normal site-packages is not writeable
Collecting nrfutil
  Using cached nrfutil-6.1.6.tar.gz (844 kB)
  Preparing metadata (setup.py) ... done
Requirement already satisfied: click in /usr/lib/python3/dist-packages (from nrfutil) (7.0)
Collecting crcmod
  Using cached crcmod-1.7.tar.gz (89 kB)
  Preparing metadata (setup.py) ... done
Collecting ecdsa
  Using cached ecdsa-0.18.0-py2.py3-none-any.whl (142 kB)
Collecting intelhex
  Using cached intelhex-2.3.0-py2.py3-none-any.whl (50 kB)
Collecting libusb1==1.9.3
  Using cached libusb1-1.9.3-py3-none-any.whl (60 kB)
Collecting nrfutil
  Downloading nrfutil-6.1.5.tar.gz (844 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 844.9/844.9 kB 5.1 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
  Downloading nrfutil-6.1.4.tar.gz (844 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 844.8/844.8 kB 5.5 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
  Using cached nrfutil-6.1.3.tar.gz (844 kB)
  Preparing metadata (setup.py) ... done
  Downloading nrfutil-6.1.2.tar.gz (844 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 844.1/844.1 kB 5.0 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
Collecting libusb1
  Downloading libusb1-3.0.0-py3-none-any.whl (62 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.1/62.1 kB 2.0 MB/s eta 0:00:00
Collecting nrfutil
  Downloading nrfutil-6.1.1.tar.gz (841 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 841.8/841.8 kB 6.1 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
  Downloading nrfutil-6.1.0.tar.gz (842 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 842.7/842.7 kB 6.1 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
  Downloading nrfutil-6.0.1.tar.gz (843 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 843.9/843.9 kB 5.6 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
  Downloading nrfutil-5.2.0.tar.gz (850 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 850.7/850.7 kB 6.1 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
Collecting behave~=1.0
  Downloading behave-1.2.6-py2.py3-none-any.whl (136 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 136.8/136.8 kB 2.8 MB/s eta 0:00:00
Collecting ecdsa~=0.13.0
  Downloading ecdsa-0.13.3-py2.py3-none-any.whl (52 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 52.1/52.1 kB 2.0 MB/s eta 0:00:00
Collecting enum34~=1.0
  Downloading enum34-1.1.10-py3-none-any.whl (11 kB)
Requirement already satisfied: pc_ble_driver_py~=0.11.4 in /home/ubuntu/.local/lib/python3.8/site-packages (from nrfutil) (0.11.4)
Collecting piccata~=1.0
  Downloading piccata-1.0.1.tar.gz (16 kB)
  Preparing metadata (setup.py) ... done
Collecting protobuf~=3.6
  Downloading protobuf-3.20.1-cp38-cp38-manylinux2014_aarch64.whl (918 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 918.1/918.1 kB 5.6 MB/s eta 0:00:00
Requirement already satisfied: pyserial~=3.0 in /usr/lib/python3/dist-packages (from nrfutil) (3.4)
Collecting pyspinel==1.0.0a3
  Downloading pyspinel-1.0.0a3.tar.gz (49 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 49.3/49.3 kB 2.2 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
Collecting pyyaml~=4.2b1
  Downloading PyYAML-4.2b4.tar.gz (262 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 262.6/262.6 kB 5.7 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
Requirement already satisfied: six~=1.9 in /usr/lib/python3/dist-packages (from nrfutil) (1.14.0)
Collecting tqdm~=4.25
  Downloading tqdm-4.64.0-py2.py3-none-any.whl (78 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 78.4/78.4 kB 1.6 MB/s eta 0:00:00
Collecting ipaddress
  Downloading ipaddress-1.0.23-py2.py3-none-any.whl (18 kB)
Collecting parse-type>=0.4.2
  Downloading parse_type-0.6.0-py2.py3-none-any.whl (32 kB)
Collecting parse>=1.8.2
  Downloading parse-1.19.0.tar.gz (30 kB)
  Preparing metadata (setup.py) ... done
Requirement already satisfied: future in /home/ubuntu/.local/lib/python3.8/site-packages (from pc_ble_driver_py~=0.11.4->nrfutil) (0.18.2)
Requirement already satisfied: wrapt in /home/ubuntu/.local/lib/python3.8/site-packages (from pc_ble_driver_py~=0.11.4->nrfutil) (1.14.1)
Building wheels for collected packages: nrfutil, pyspinel, crcmod, piccata, pyyaml, parse
  Building wheel for nrfutil (setup.py) ... done
  Created wheel for nrfutil: filename=nrfutil-5.2.0-py3-none-any.whl size=911037 sha256=16df52e67645a9a45bdddb62de631e3e7261814ef1c3ff9858c849840e25b199
  Stored in directory: /home/ubuntu/.cache/pip/wheels/c1/af/f7/f240c7018b692e93fa9abef5a4dba5bd2a5a00c59e56865210
  Building wheel for pyspinel (setup.py) ... done
  Created wheel for pyspinel: filename=pyspinel-1.0.0a3-py3-none-any.whl size=55513 sha256=5f3504731139bd762e4af3406f3fa5ac12b1a142ff0d322a6f9316f70e1c0f91
  Stored in directory: /home/ubuntu/.cache/pip/wheels/ec/98/96/276b3f2eec4cc409698d0fe171051e1cbe8d883e5ba15756b3
  Building wheel for crcmod (setup.py) ... done
  Created wheel for crcmod: filename=crcmod-1.7-cp38-cp38-linux_aarch64.whl size=35610 sha256=b06b8c9832201c8cd27796e402495f92935c53fffd7bce583deac0f3eb38d972
  Stored in directory: /home/ubuntu/.cache/pip/wheels/ca/5a/02/f3acf982a026f3319fb3e798a8dca2d48fafee7761788562e9
  Building wheel for piccata (setup.py) ... done
  Created wheel for piccata: filename=piccata-1.0.1-py3-none-any.whl size=20727 sha256=842092972829e731740502813c50ea1eee5a55efa5ff80c8ee3dc70eae5d8804
  Stored in directory: /home/ubuntu/.cache/pip/wheels/a4/68/01/a92750aef1de0fe3b435d16aa508ae116bffb2b1ef6eb0dc77
  Building wheel for pyyaml (setup.py) ... done
  Created wheel for pyyaml: filename=PyYAML-4.2b4-cp38-cp38-linux_aarch64.whl size=43031 sha256=cda77494b76d6bc019a009233779b049349a18186dc46e43b21e83e1f5395089
  Stored in directory: /home/ubuntu/.cache/pip/wheels/3f/db/67/c44d262205f8f6105abf4c0aff6045a176d94e1011e85dde88
  Building wheel for parse (setup.py) ... done
  Created wheel for parse: filename=parse-1.19.0-py3-none-any.whl size=24580 sha256=cd8e0315b7a280e4bd6fd7758ab8e001852397cf70d712495edc09ac6b8d286b
  Stored in directory: /home/ubuntu/.cache/pip/wheels/e5/33/1f/68392720485b3ecf125a69e700baaab7624616deedea2fa6e2
Successfully built nrfutil pyspinel crcmod piccata pyyaml parse
Installing collected packages: parse, libusb1, ipaddress, intelhex, enum34, ecdsa, crcmod, tqdm, pyyaml, pyspinel, protobuf, piccata, parse-type, behave, nrfutil
Successfully installed behave-1.2.6 crcmod-1.7 ecdsa-0.13.3 enum34-1.1.10 intelhex-2.3.0 ipaddress-1.0.23 libusb1-1.9.3 nrfutil-5.2.0 parse-1.19.0 parse-type-0.6.0 piccata-1.0.1 protobuf-3.20.1 pyspinel-1.0.0a3 pyyaml-4.2b4 tqdm-4.64.0

Great! Now I can use nrfUtil to build this thing.

~/ot-nrf528xx$ nrfutil pkg generate --hw-version 52 --sd-req=0x00 \
>     --application build/bin/ot-rcp.hex \
>     --application-version 1 build/bin/ot-rcp.zip

|===============================================================|
|##      ##    ###    ########  ##    ## #### ##    ##  ######  |
|##  ##  ##   ## ##   ##     ## ###   ##  ##  ###   ## ##    ## |
|##  ##  ##  ##   ##  ##     ## ####  ##  ##  ####  ## ##       |
|##  ##  ## ##     ## ########  ## ## ##  ##  ## ## ## ##   ####|
|##  ##  ## ######### ##   ##   ##  ####  ##  ##  #### ##    ## |
|##  ##  ## ##     ## ##    ##  ##   ###  ##  ##   ### ##    ## |
| ###  ###  ##     ## ##     ## ##    ## #### ##    ##  ######  |
|===============================================================|
|You are not providing a signature key, which means the DFU     |
|files will not be signed, and are vulnerable to tampering.     |
|This is only compatible with a signature-less bootloader and is|
|not suitable for production environments.                      |
|===============================================================|

Traceback (most recent call last):
  File "/home/ubuntu/.local/bin/nrfutil", line 8, in <module>
    sys.exit(cli())
  File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/home/ubuntu/.local/lib/python3.8/site-packages/nordicsemi/__main__.py", line 867, in generate
    package.generate_package(zipfile_path)
  File "/home/ubuntu/.local/lib/python3.8/site-packages/nordicsemi/dfu/package.py", line 403, in generate_package
    for key, firmware_data in self.firmwares_data.iteritems():
AttributeError: 'dict' object has no attribute 'iteritems'

It would seem someone expects python2, and someone else has python3.

python2 and python3 are installed on the pi. Not sure how to get this command to work.

Looking at the failure logs I'm getting from pairing attempts, the very last line intrigues me.

[1658163090.255000][25638:25638] CHIP:TOO: Run command failure: ../../src/controller/AutoCommissioner.cpp:204: CHIP Error 0x0000002F: Invalid argument

I see a similar message at the bottom of this guide (green box), but in my case, the dongle is indeed /dev/ttyACM0. I replugged it anyway, but there was no change.

RE: Matter commissioning fails between two nrf52840 boards

AHaug — Mon, 18 Jul 2022 08:33:02 GMT

Hi again,

I have not been able to recreate your issue yet, but based on

FAIL: ConnectDevice : GDBus.Error:org.bluez.Error.Failed: Software caused connection abort (36)

we believe there could be an issue with the RPi Bluetooth adapter. Some workarounds does involve trying to connect multiple time, but we do not believe that to be sufficient in all cases. Usually it is worth making sure that rpi-bluetooth and bluez apt packages are up to date. In some cases restarting the BLE adapter and/or bluez helps (you can do the latter with sudo systemctl restart bluetooth . If nothing helps, you can use an external BLE adapter. For example, you can program Zephyr's HCI USB sample onto a nRF52840 DK/Dongle and use it as a BLE adapter (https://docs.zephyrproject.org/2.7.0/samples/bluetooth/hci_usb/README.html).

Let me know if this fixes your issue or not and I will report that feedback back to the Matter developers

Kind regards,
Andreas

RE: Matter commissioning fails between two nrf52840 boards

AHaug — Thu, 14 Jul 2022 13:12:48 GMT

Hi,

I have picked up your case and will try to to see if I can recreate the issue. I will hopefully come back with an answer within two working days (friday/monday). In the meanwhile, please let me know if you manage to resolve the issue yourself

Kind regards,
Andreas