Cannot connect to nrf52840 running any matter examples using chip-device-ctl (BLE or IP)

RE: Cannot connect to nrf52840 running any matter examples using chip-device-ctl (BLE or IP)

gautam_joshi — Mon, 15 May 2023 06:31:15 GMT

hello i get the same error, my matter controller is Ubuntu 20.04 and i am using nrf52840 as a matter device and i get timeout error when i try to commissioning.

RE: Cannot connect to nrf52840 running any matter examples using chip-device-ctl (BLE or IP)

Sigurd Hellesvik — Thu, 28 Oct 2021 11:57:56 GMT

Hi,

I am sorry for the late answer. I have not found any solution to this yet.

Are you able to test the CHIPTool with a laptop running Ubuntu, and see if that works?

Regards,
Sigurd Hellesvik

RE: Cannot connect to nrf52840 running any matter examples using chip-device-ctl (BLE or IP)

kodyholman — Fri, 22 Oct 2021 01:05:31 GMT

pi-bluetooth was already installed.

I did setup the HCI USB on a spare nrf52840_dongle and got the same error:

ubuntu@matter:~/scripts$ chip-device-ctrl --bluetooth-adapter hci1
[1634862699.177933][116982:116982] CHIP:CTL: SyncSetKeyValue on ExampleOpCredsCAKey
[1634862699.178260][116982:116982] CHIP:CTL: SyncSetKeyValue on ExampleOpCredsICAKey
[1634862699.183935][116982:116982] CHIP:IN: UDP::Init bind&listen port=5541
[1634862699.184097][116982:116982] CHIP:IN: UDP::Init bind&listen port=5541
[1634862699.184204][116982:116982] CHIP:IN: TransportMgr initialized
[1634862699.184229][116982:116982] CHIP:DIS: Init fabric pairing table with server storage
[1634862699.184277][116982:116982] CHIP:IN: local node id is 0x000000000001B669
[1634862699.188401][116982:116982] CHIP:DL: Avahi client registered
[1634862699.190061][116982:116982] CHIP:ZCL: Using ZAP configuration...
[1634862699.190173][116982:116982] CHIP:ZCL: deactivate report event
[1634862699.190220][116982:116982] CHIP:CTL: Getting operational keys
[1634862699.190581][116982:116982] CHIP:CTL: Getting root certificate for the controller from the issuer
[1634862699.191661][116982:116982] CHIP:CTL: Generating operational certificate for the controller
[1634862699.192678][116982:116982] CHIP:CTL: Getting intermediate CA certificate from the issuer
[1634862699.192992][116982:116982] CHIP:CTL: GetIntermediateCACertificate returned ../../src/controller/ExampleOperationalCredentialsIssuer.cpp:129: No Error
[1634862699.193340][116982:116982] CHIP:CTL: SyncSetKeyValue on Fabric0
[1634862699.193382][116982:116982] CHIP:CTL: Generating credentials
[1634862699.193828][116982:116982] CHIP:CTL: Loaded credentials successfully
[1634862699.207480][116982:116989] CHIP:DL: Platform main loop started.
Chip Device Controller Shell
Bluetooth adapter set to hci1

chip-device-ctrl > ble-scan
2021-10-22 00:43:23,857 ChipBLEMgr   INFO     scanning started
2021-10-22 00:43:23,991 ChipBLEMgr   INFO     Name            = MatterLock
2021-10-22 00:43:23,991 ChipBLEMgr   INFO     ID              = 3c694ac0-ac45-3c36-ae70-2e98ce5b1921
2021-10-22 00:43:23,993 ChipBLEMgr   INFO     RSSI            = -40
2021-10-22 00:43:23,994 ChipBLEMgr   INFO     Address         = 56:66:51:E9:6A:13
2021-10-22 00:43:23,999 ChipBLEMgr   INFO     Pairing State   = 0
2021-10-22 00:43:23,999 ChipBLEMgr   INFO     Discriminator   = 3840
2021-10-22 00:43:23,999 ChipBLEMgr   INFO     Vendor Id       = 9050
2021-10-22 00:43:23,999 ChipBLEMgr   INFO     Product Id      = 20043
2021-10-22 00:43:24,002 ChipBLEMgr   INFO     Adv UUID        = 0000fff6-0000-1000-8000-00805f9b34fb
2021-10-22 00:43:24,004 ChipBLEMgr   INFO     Adv Data        = 00000f5a234b4e
2021-10-22 00:43:24,004 ChipBLEMgr   INFO     
2021-10-22 00:43:34,032 ChipBLEMgr   INFO     scanning stopped
chip-device-ctrl > connect -ble 3840 20202021 1234
Device is assigned with nodeid = 1234
[1634863527.213346][116982:116989] CHIP:SC: Assigned local session key ID 1
[1634863527.213603][116982:116989] CHIP:IN: Message appended to BLE send queue
[1634863527.213704][116982:116989] CHIP:SC: Sent PBKDF param request
[1634863527.213799][116982:116989] CHIP:CTL: SyncSetKeyValue on StartKeyID
[1634863527.214390][116982:124996] CHIP:DL: TRACE: Bluez mainloop starting Thread
[1634863527.215009][116982:116985] CHIP:DL: TRACE: Bus acquired for name C-c8f6
[1634863527.227984][116982:116989] CHIP:DL: PlatformBlueZInit init success
[1634863527.235398][116982:116985] CHIP:BLE: BLE removing known devices.
[1634863527.235475][116982:116985] CHIP:BLE: BLE initiating scan.
[1634863527.295048][116982:116985] CHIP:BLE: Device 75:E9:88:FA:FF:25 does not look like a CHIP device.
[1634863527.317154][116982:116985] CHIP:BLE: New device scanned: 56:66:51:E9:6A:13
[1634863527.317340][116982:116985] CHIP:BLE: Device discriminator match. Attempting to connect.
[1634863527.322344][116982:116985] CHIP:BLE: Scan complete notification without an active scan.
[1634863527.821962][116982:116985] CHIP:DL: ConnectDevice complete
[1634863528.936372][116982:116985] CHIP:DL: Char1 /org/bluez/hci1/dev_56_66_51_E9_6A_13/service0010
[1634863528.936428][116982:116985] CHIP:DL: Char1 /org/bluez/hci1/dev_56_66_51_E9_6A_13/service0010
[1634863528.936459][116982:116985] CHIP:DL: Char1 /org/bluez/hci1/dev_56_66_51_E9_6A_13/service0010
[1634863528.936482][116982:116985] CHIP:DL: Char1 /org/bluez/hci1/dev_56_66_51_E9_6A_13/service0010
[1634863528.936508][116982:116985] CHIP:DL: Char1 /org/bluez/hci1/dev_56_66_51_E9_6A_13/service0010
[1634863528.936530][116982:116985] CHIP:DL: Char1 /org/bluez/hci1/dev_56_66_51_E9_6A_13/service0010
[1634863528.936559][116982:116985] CHIP:DL: New BLE connection 0xffff88031fd0, device 56:66:51:E9:6A:13, path /org/bluez/hci1/dev_56_66_51_E9_6A_13
[1634863528.936700][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16385
[1634863528.936745][116982:116989] CHIP:IN: BleConnectionComplete: endPoint 0xffff9d44cfe0
[1634863529.420148][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16387
[1634863529.519892][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16388
[1634863529.519955][116982:116989] CHIP:BLE: subscribe complete, ep = 0xffff9d44cfe0
[1634863529.520094][116982:116985] CHIP:DL: Indication received, conn = 0xffff88031fd0
[1634863529.520208][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16389
[1634863529.520257][116982:116989] CHIP:BLE: peripheral chose BTP version 3; central expected between 2 and 3
[1634863529.520290][116982:116989] CHIP:BLE: using BTP fragment sizes rx 20 / tx 62.
[1634863529.520320][116982:116989] CHIP:BLE: local and remote recv window size = 3
[1634863529.520447][116982:116989] CHIP:IN: BLE EndPoint 0xffff9d44cfe0 Connection Complete
[1634863529.619795][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16387
[1634863532.120028][116982:116985] CHIP:DL: Indication received, conn = 0xffff88031fd0
[1634863532.120271][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16389
[1634863534.644350][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16387
[1634863537.149560][116982:116985] CHIP:DL: Indication received, conn = 0xffff88031fd0
[1634863537.149801][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16389
[1634863539.684322][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16387
[1634863542.189774][116982:116985] CHIP:DL: Indication received, conn = 0xffff88031fd0
[1634863542.189980][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16389
[1634863544.723886][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16387
[1634863547.229714][116982:116985] CHIP:DL: Indication received, conn = 0xffff88031fd0
[1634863547.229917][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16389
[1634863549.763765][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16387
[1634863552.268903][116982:116985] CHIP:DL: Indication received, conn = 0xffff88031fd0
[1634863552.269111][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16389
[1634863554.803808][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16387
[1634863557.213789][116982:116989] CHIP:CTL: SyncSetKeyValue on StartKeyID
Failed to establish secure session to device: 50
[1634863557.214162][116982:116989] CHIP:SC: PASESession timed out while waiting for a response from the peer. Expected message type was 33
[1634863557.214232][116982:116989] CHIP:CTL: SyncSetKeyValue on StartKeyID
CHIP Error 0x00000032: Timeout
Failed to establish secure session to device: 50
chip-device-ctrl > [1634863557.308964][116982:116985] CHIP:DL: Indication received, conn = 0xffff88031fd0
[1634863557.309165][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16389
[1634863559.843600][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16387
[1634863562.348295][116982:116985] CHIP:DL: Indication received, conn = 0xffff88031fd0
[1634863562.348474][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16389
[1634863564.883449][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16387

chip-device-ctrl > 
chip-device-ctrl > 
chip-device-ctrl > 
chip-device-ctrl > [1634863567.388285][116982:116985] CHIP:DL: Indication received, conn = 0xffff88031fd0
[1634863567.388491][116982:116989] CHIP:DL: HandlePlatformSpecificBLEEvent 16389

chip-device-ctrl > exit
dbus[116982]: arguments to dbus_connection_unref() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../../dbus/dbus-connection.c line 2823.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace

Are they configuration settings I can change on my matter examples that I can try changing??

RE: Cannot connect to nrf52840 running any matter examples using chip-device-ctl (BLE or IP)

Sigurd Hellesvik — Wed, 20 Oct 2021 12:07:18 GMT

The BLE GAP error can be found in "zephyr/include/bluetooth/hci_err.h", and 0x08 is "BT_HCI_ERR_CONN_TIMEOUT".
This seems like the same error as earlier.

It seems likely that it the BLE drivers of the Raspberry Pi which are incompatible.
To test this, could you try to install "pi-bluetooth".
If that does not work, do you have access to another nRF Developement Kit?

Regards,
Sigurd Hellesvik

RE: Cannot connect to nrf52840 running any matter examples using chip-device-ctl (BLE or IP)

kodyholman — Tue, 19 Oct 2021 14:30:41 GMT

Thank you for your reply!

I checked out connectedhomip commit 'b77bfb047374b7013dbdf688f542b9326842a39e' on the Mac (found in nrf Connect v1.7.0 documentation.) This is the error I'm seeing:

chip-device-ctrl > connect -ble 3840 20202021 12
Device is assigned with nodeid = 12
[1634651717998] [40670:423545] CHIP: [BLE] NewConnection
[1634651734783] [40670:423545] CHIP: [BLE] Connecting to device with discriminator: 3840
Failed to establish secure session to device: 50
[1634651748002] [40670:423545] CHIP: [SC] PASESession timed out while waiting for a response from the peer. Expected message type was 33
CHIP Error 0x00000032: Timeout
Failed to establish secure session to device: 50

The output from the Matter lock example on the nrf devices:

I: 249545 [DL]BLE connection established (ConnId: 0x00)
I: 249550 [DL]Current number of connections: 1/1
D: 249554 [DL]In DriveBLEState
I: 249557 [DL]CHIPoBLE advertising stopped
I: 249561 [DL]NFC Tag emulation stopped
I: 251608 [DL]BLE GAP connection terminated (reason 0x08)

I think that this line could be a good clue, I just don't know how to understand what 'reason 0x08' means.

BLE GAP connection terminated (reason 0x08)

RE: Cannot connect to nrf52840 running any matter examples using chip-device-ctl (BLE or IP)

Sigurd Hellesvik — Tue, 19 Oct 2021 12:11:46 GMT

Hi Kody

Good to hear that you were able to find to connect using LAN.

I heard back from the developers on BLE:

chip-device-ctrl.py is built for Linux. If you want to use this for MacOS, you need to build the controller from source.
If you are to build the controller from source, you need to make sure that it's built using the same revision as the Lock firmware.

When using the Linux version, try to run "systemctl restart bluetooth" and try again, does this fix the problem?
Or you could try to install "pi-bluetooth" to the pi.
If this does not work, it is possible that the bluetooth device of the Raspberry pi is not compatible.
In that case, you could try to use a nRF Developement kit as a HCI USB dongle to provide BLE.

Regards,
Sigurd Hellesvik

RE: Cannot connect to nrf52840 running any matter examples using chip-device-ctl (BLE or IP)

kodyholman — Mon, 18 Oct 2021 14:31:43 GMT

I was able to get the pre-built chip-device-ctl in the sdk-connectedhomeip 1.7.0 release running on my LAN connected Linux ubuntu machine, but now I'm getting this error when trying to connect over BLE to a matter example.

chip-device-ctrl > connect -ble 3840 20202021 1234
Device is assigned with nodeid = 1234
[1634509927.806068][10100:10107] CHIP:SC: Assigned local session key ID 3
[1634509927.806268][10100:10107] CHIP:IN: Message appended to BLE send queue
[1634509927.806322][10100:10107] CHIP:SC: Sent PBKDF param request
[1634509927.806373][10100:10107] CHIP:CTL: SyncSetKeyValue on StartKeyID
[1634509927.815883][10100:10103] CHIP:BLE: BLE removing known devices.
[1634509927.815964][10100:10103] CHIP:BLE: BLE initiating scan.
[1634509927.837577][10100:10103] CHIP:BLE: Device 72:F9:81:57:D8:2E does not look like a CHIP device.
[1634509927.852725][10100:10103] CHIP:BLE: Device 90:DD:5D:B0:BF:42 does not look like a CHIP device.
[1634509927.861191][10100:10103] CHIP:BLE: Device 24:9B:56:42:17:6B does not look like a CHIP device.
[1634509927.876551][10100:10103] CHIP:BLE: Device 7E:2B:B9:DB:37:86 does not look like a CHIP device.
[1634509927.916534][10100:10103] CHIP:BLE: Device 6B:07:2C:0F:2D:66 does not look like a CHIP device.
[1634509927.950931][10100:10103] CHIP:BLE: Device 01:22:FC:42:5C:21 does not look like a CHIP device.
[1634509927.985977][10100:10103] CHIP:BLE: Device 61:56:73:0F:92:2D does not look like a CHIP device.
[1634509927.987940][10100:10103] CHIP:BLE: Device 2B:83:A8:9D:23:28 does not look like a CHIP device.
[1634509927.996619][10100:10103] CHIP:BLE: Device 08:66:98:9E:55:DD does not look like a CHIP device.
[1634509927.999998][10100:10103] CHIP:BLE: Device 0A:FF:3B:7D:A5:C4 does not look like a CHIP device.
[1634509928.036190][10100:10103] CHIP:BLE: Device 34:F6:56:F0:A4:E6 does not look like a CHIP device.
[1634509928.039802][10100:10103] CHIP:BLE: Device 1B:58:49:6E:2C:BE does not look like a CHIP device.
[1634509928.046014][10100:10103] CHIP:BLE: Device 45:5D:D3:6F:21:D3 does not look like a CHIP device.
[1634509928.065380][10100:10103] CHIP:BLE: Device 64:B5:8B:93:A0:4F does not look like a CHIP device.
[1634509928.122756][10100:10103] CHIP:BLE: New device scanned: 4C:54:50:A6:50:19
[1634509928.122868][10100:10103] CHIP:BLE: Device discriminator match. Attempting to connect.
[1634509928.128481][10100:10103] CHIP:BLE: Scan complete notification without an active scan.
[1634509929.339148][10100:10103] CHIP:DL: FAIL: ConnectDevice : GDBus.Error:org.bluez.Error.Failed: Software caused connection abort
[1634509929.339416][10100:10107] CHIP:DL: HandlePlatformSpecificBLEEvent 16386
[1634509929.339479][10100:10107] CHIP:IN: Clearing BLE pending packets.
[1634509929.339549][10100:10107] CHIP:IN: BleConnection Error: ../../src/platform/Linux/bluez/Helper.cpp:1739: CHIP Error 0x000000AC: Internal error

RE: Cannot connect to nrf52840 running any matter examples using chip-device-ctl (BLE or IP)

Sigurd Hellesvik — Mon, 18 Oct 2021 13:25:57 GMT

Hi Kody

Thank you for the good debugging information so far!

I will ask our Matter developers about this issue, and will return with an answer by the end of Wednesday, but hopefully sooner.

Regards,
Sigurd Hellesvik