Help with version alignment of Matter samples in NRF Connect and Python chip device controller

Hi,

Can anyone direct me to where I can learn which versions of the various matter endpoints are compatible (i.e. matter device, matter controller and open thread border router)?

I have successfully set up a matter network with the matter lock sample on an NRF52840 DK, an OTBR using a RaspPi and NRF52840 dongle radio co-processor and a ubuntu laptop 20.04 running the python chip-device-ctrl as per the video tutorial "Developing Matter products with nRF Connect SDK". Everything works fine apart from a small issue with the service registration protocol. The versions that I have working are as follows:

- matter lock sample on NRF52840 DK built from NRF Connect v1.7.0 matter samples

- matter controller using chip-device-ctrl on laptop installed using pip install from the wheel package from Nordic's repo sdk-connectedhomeip v1.7.0

- OTBR Running 0.3.0-e149a60eb

I now want to move to a more recent version of the matter lock sample and the python controller. I am trying the following versions

- matter lock sample on NRF52840 DK built from NRF Connect v1.9.99 matter samples (main branch)

- matter controller using chip-device-ctrl on laptop installed using pip install from the wheel package from Nordic's repo sdk-connectedhomeip v1.9.0

- OTBR Running (no change) 0.3.0-e149a60eb

This new set up does not work and I while I can find the matter lock device using ble-scan, the commissioning process fails when I try to connect. Here is what I see in the logs:

Matter Controller Log

chip-device-ctrl > ble-scan
2022-03-04 17:49:33,330 ChipBLEMgr INFO scanning started
2022-03-04 17:49:33,529 ChipBLEMgr INFO Name = MatterLock
2022-03-04 17:49:33,530 ChipBLEMgr INFO ID = 3c694ac0-ac45-3c36-ae70-2e98ce5b1921
2022-03-04 17:49:33,532 ChipBLEMgr INFO RSSI = -83
2022-03-04 17:49:33,534 ChipBLEMgr INFO Address = C5:87:9A:AE:2A:2C
2022-03-04 17:49:33,544 ChipBLEMgr INFO Adv UUID = 0000fff6-0000-1000-8000-00805f9b34fb
2022-03-04 17:49:33,546 ChipBLEMgr INFO Adv Data = 00000f5a234b4e00
2022-03-04 17:49:33,547 ChipBLEMgr INFO
2022-03-04 17:49:43,518 ChipBLEMgr INFO scanning stopped
chip-device-ctrl >
chip-device-ctrl > connect -ble 3840 20202021 12345
Device is assigned with nodeid = 12345
[1646416198.711252][246867:246871] CHIP:BLE: BLE removing known devices.
[1646416198.723826][246867:246871] CHIP:BLE: BLE initiating scan.
[1646416199.459680][246867:246871] CHIP:BLE: New device scanned: C5:87:9A:AE:2A:2C
[1646416199.459773][246867:246871] CHIP:BLE: Device discriminator match. Attempting to connect.
[1646416199.464778][246867:246871] CHIP:BLE: Scan complete notification without an active scan.
[1646416201.722430][246867:246871] CHIP:DL: Bluez notify CHIPoBluez connection disconnected
[1646416201.722820][246867:246875] CHIP:IN: Failed to establish BLE connection: ../../src/platform/Linux/BLEManagerImpl.cpp:529: Ble Error 0x0000040C: Remote device closed BLE connection
[1646416201.724154][246867:246875] CHIP:BLE: no endpoint for sub complete
Failed to establish secure session to device: 50
[1646416228.679952][246867:246875] 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

Matter Lock Device Log:

23528 [SC]Assigned local session key ID 1
D: 23532 [SC]Waiting for PBKDF param request
D: 23536 [DL]CHIPoBLE advertising set to on
D: 23541 [DIS]DNS-SD StartServer modeHasValue=1 modeValue=1
D: 23546 [DL]Using Thread extended MAC for hostname.
I: 23551 [DIS]Failed to find a valid admin pairing. Node ID unknown
I: 23557 [DIS]Start dns-sd server - no current nodeId
D: 23562 [DL]Using Thread extended MAC for hostname.
I: 23567 [DIS]Advertise commission parameter vendorID=9050 productID=20043 discriminator=3840/15
E: 23576 [DIS]Failed to advertise unprovisioned commissionable node: Error CHIP:0x00000003
D: 23584 [DIS]Scheduling Discovery timeout in secs=900
E: 23589 [DIS]Failed to finalize service update: Error CHIP:0x0000001C
I: 23597 [DL]CHIPoBLE advertising started
I: 23602 [DL]NFC Tag emulation started
I: 53601 [DL]CHIPoBLE advertising mode changed to slow
I: 62302 [DL]BLE connection established (ConnId: 0x00)
I: 62307 [DL]Current number of connections: 1/1
I: 62311 [DL]CHIPoBLE advertising stopped
I: 62315 [DL]NFC Tag emulation stopped
D: 63822 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 63827 [IN]Clearing BLE pending packets.
I: 63831 [BLE]Releasing end point's BLE connection back to application.
I: 63838 [DL]Closing BLE GATT connection (ConnId 00)
E: 63843 [BLE]HandleChipConnectionReceived failed, err = 417
E: 63848 [BLE]failed handle new chip BLE connection, status = 417
E: not connected!
D: 63921 [DL]ConnId: 0x00, New CCCD value: 0x0001
E: 63925 [BLE]no endpoint for sub recvd
W: Not connected
I: 63930 [DL]CHIPoBLE connection established (ConnId: 0x00, GATT MTU: 0)
I: 63967 [DL]BLE GAP connection terminated (reason 0x16)
I: 63973 [DL]Current number of connections: 0/1
I: 63978 [DL]CHIPoBLE advertising started
I: 63983 [DL]NFC Tag emulation started
I: 93982 [DL]CHIPoBLE advertising mode changed to slow

Could anyone advise on what versions would be compatible? e.g. Should I try an earlier version of NRF connect with the controller from the wheel package in Nordic's repo sdk-connectedhomeip v1.9.0?

Many thanks

Oide

Parents
  • Hi Odie,

    I would recommend you to stick with the tagged release versions (latest would currently be v1.9.1), unless you need access to features that are not part of the release yet. The releases are thoroughly tested and should work if you use the Python controller from the same release version as the application sample. On the latest/main branch, things may occasionally break as this is where the development are done.

    Best regards,
    Jørgen

Reply
  • Hi Odie,

    I would recommend you to stick with the tagged release versions (latest would currently be v1.9.1), unless you need access to features that are not part of the release yet. The releases are thoroughly tested and should work if you use the Python controller from the same release version as the application sample. On the latest/main branch, things may occasionally break as this is where the development are done.

    Best regards,
    Jørgen

Children
No Data
Related