Control Matter door lock from the remote side

[h.vig]

Hi,

I am a new beginner when it comes to Thread and Matter. I am trying to run Matter on nrf52840. I flashed the door lock example, commissioned the device using BLE and got it to work. But I do not understand how the remote side works.

Can I control this door lock using a "key" example over Thread? Is it possible to control this device only using the Matter controller? The current pre-built version of the android app from Nordic does not have the door key functionality, as I understand. Will it be possible to test this example?

The instructions in here are not clear. https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.7.0/nrf/samples/matter/lock/README.html#

Any help is appreciated. Thanks

[Sigurd Hellesvik]

Hi

A matter device can in general be controlled in two different ways:

1. Using a matter controller.
Matter controllers are connected over WiFi, and can be either an Android or Linux device. See Matter Tools for more on this.

2. Using another Matter device
This is done over the Thread network using ZCL commands, the same way the Light Bulb and Light Switch samples does.
We do not as of now have a Matter device to control the door lock sample.

The current pre-built version of the android app from Nordic does not have the door key functionality, as I understand. Will it be possible to test this example?

You should be able to use the same view as "Light On/Off" for the door lock sample.

This is not very intuitive. Matter is a new project, and the CHIP controller applications are still under some development. 
Hopefully, they will improve as the Matter project progresses.

Also, we will do a development webinar on Matter devices 14. October, if you want to learn more on the subject.

Did this answer your questions?

Regards,
Sigurd Hellesvik

[h.vig]

Hi, Thanks for the response.

Its my lack of experience with Zigbee and ZCL that is the big culprit here. I will be there for the Oct 14 webinar. But I would like some more answers now.

So I got my device commissioned using the mobile app. It is a CHILD in the Thread network connected to a OTBR. I connected my phone to the same network as the OTBR. As I understand from your answer, I use the same view as "Light ON/OFF" and try to control the door lock. But I do not know how to look for the Fabric Id in this available log. Looking at my logs, I think my fabric Id is 112233 (0x1B669) and Node Id is 9. But when I try to retrieve the IP address of the device, it fails and I am not able to continue.

https://github.com/project-chip/connectedhomeip/blob/master/docs/guides/nrfconnect_android_commissioning.md

1. How do I get the Fabric Id and Node Id? Any information on how to control the door lock (after commissioning) would be great.

2. I know that in Thread the devices will need to pair (establish a DTLS connection). Will that be handled automatically by the app (lock client) and the lock server? Is the PSK shared during the commissioning stages?

I totally understand that the mobile app is still a PoC but I believe that the documentation could have been better especially for people who do not have experience with Zigbee.

Thanks in advance for the help

I: nRF5 802154 radio initialized
I: 8 Sectors of 4096 bytes
I: alloc wra: 7, fa0
I: data wra: 7, b04
*** Booting Zephyr OS build v2.6.99-ncs1  ***
I: Init CHIP stack
I: SoftDevice Controller build revision: 
I: 3f 47 70 8e 81 95 4e 86 |?Gp...N.
I: 9d d3 a2 95 88 f6 30 0a |......0.
I: 7f 53 49 fd             |.SI.    
I: Starting CHIP task
I: Init Thread stack
I: 159 [DL]OpenThread started: OK
I: 163 [DL]Setting OpenThread device type to MINIMAL END DEVICE
I: 169 [ZCL]Using ZAP configuration...
I: 176 [ZCL]deactivate report event
I: 179 [ZCL]OpCreds: Initiating OpCreds cluster by writing fabrics list from fabric table.
D: 187 [DIS]Set the fabric pairing table delegate
I: 191 [ZCL]OpCreds: Call to writeFabricsIntoFabricsListAttribute
I: 197 [ZCL]OpCreds: Stored 0 fabrics in fabrics list attribute.
I: 203 [ZCL]Unknown cluster ID: 40
I: 206 [ZCL]Unknown cluster ID: 40
I: 210 [ZCL]Unknown cluster ID: 40
I: 213 [ZCL]Unknown cluster ID: 40
I: 216 [ZCL]Unknown cluster ID: 40
I: 220 [ZCL]Unknown cluster ID: 40
I: 223 [ZCL]Unknown cluster ID: 40
I: 226 [ZCL]Unknown cluster ID: 40
D: 230 [DIS]Init fabric pairing table with server storage
D: 235 [IN]UDP::Init bind&listen port=5540
D: 239 [IN]TransportMgr initialized
I: 243 [IN]local node id is 0x0000000000BC5C01
I: 248 [DIS]Start dns-sd server
I: 252 [IN]CASE Server enabling CASE session setups
I: 257 [SVR]Server Listening...
I: 260 [DL]Device Configuration:
I: 264 [DL]  Serial Number: TEST_SN
I: 267 [DL]  Vendor Id: 9050 (0x235A)
I: 270 [DL]  Product Id: 20043 (0x4E4B)
I: 275 [DL]  Product Revision: 1
I: 279 [DL]  Setup Pin Code: 20202021
I: 283 [DL]  Setup Discriminator: 3840 (0xF00)
I: 288 [DL]  Manufacturing Date: (not set)
I: 292 [DL]  Device Type: 65535 (0xFFFF)
I: 298 [SVR]SetupQRCode: [MT:W0GU2OTB00KA0648G00]
I: 302 [SVR]Copy/paste the below URL in a browser to see the QR Code:
I: 308 [SVR]https://dhrishi.github.io/connectedhomeip/qrcode.html?data=MT%3AW0GU2OTB00KA0648G00
I: 319 [SVR]Manual pairing code: [34970112332]
D: 324 [DL]CHIP task running
D: 327 [DL]In DriveBLEState


uart:~$ D: 5362 [DL]SetAdvertisingEnabled(true)
D: 5366 [SC]Assigned local session key ID 0
D: 5370 [SC]Waiting for PBKDF param request
I: Enabled BLE Advertisement
D: 5377 [DL]In DriveBLEState
I: 5382 [DL]CHIPoBLE advertising started
I: 5388 [DL]NFC Tag emulation started
I: 35387 [DL]CHIPoBLE advertising mode changed to slow
D: 35392 [DL]In DriveBLEState
I: 38516 [DL]BLE connection established (ConnId: 0x00)
I: 38521 [DL]Current number of connections: 1/1
D: 38525 [DL]In DriveBLEState
I: 38528 [DL]CHIPoBLE advertising stopped
I: 38531 [DL]NFC Tag emulation stopped
D: 39447 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
I: 39453 [BLE]local and remote recv window sizes = 3
I: 39458 [BLE]selected BTP version 3
I: 39461 [BLE]using BTP fragment sizes rx 62 / tx 20.
D: 39593 [DL]ConnId: 0x00, New CCCD value: 0x0001
D: 39598 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 6)
D: 39604 [IN]BLE EndPoint 0x20008808 Connection Complete
I: 39609 [DL]CHIPoBLE connection established (ConnId: 0x00, GATT MTU: 65)
D: 39692 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 39697 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
I: 39703 [EM]Received message of type 0x20 with vendorId 0x0000 and protocolId 0x0000 on exchange 34211
D: 39712 [EM]ec id: 34211, Delegate: 0x0x20003a40
D: 39717 [SC]Received PBKDF param request
D: 39890 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 39897 [SC]Sent PBKDF param response
E: 39900 [DL]Long dispatch time: 203 ms, for event type 16388
D: 39983 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 39989 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 40081 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 40086 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 40092 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 40178 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 40184 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 40276 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 40281 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 40287 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 8)
D: 40373 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 40472 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 40478 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 40569 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 40574 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
I: 40580 [EM]Received message of type 0x22 with vendorId 0x0000 and protocolId 0x0000 on exchange 34211
D: 40589 [SC]Received spake2p msg1
D: 40657 [SC]Peer assigned session key ID 14
D: 40737 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 40743 [SC]Sent spake2p msg2
E: 40746 [DL]Long dispatch time: 171 ms, for event type 16388
D: 40813 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 40818 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 40824 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 40909 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 40915 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 41007 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 41013 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 41019 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 41104 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 41110 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 41202 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 41251 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 41257 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 41348 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 41354 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 13)
D: 41446 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 41451 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 41593 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 41599 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
I: 41605 [EM]Received message of type 0x24 with vendorId 0x0000 and protocolId 0x0000 on exchange 34211
D: 41615 [SC]Received spake2p msg3
D: 41618 [IN]New secure session created for device 0x0000000000000000, key 14!!
I: 41626 [SVR]Device completed SPAKE2+ handshake
D: 41631 [DL]SetAdvertisingEnabled(false)
I: 41635 [SVR]Persisting fabric ID 0, next available 1
I: 41657 [SVR]Stored value in server storage
I: 41845 [DIS]Fabric (0) persisted to storage. Calling OnFabricPersistedToStorage
I: 41853 [ZCL]OpCreds: Fabric 0 was persisted to storage. FabricId 00000000000000000, NodeId 00000000000000000, VendorId 0x4B2D
I: 41864 [ZCL]OpCreds: Call to writeFabricsIntoFabricsListAttribute
I: 41870 [ZCL]OpCreds: Skipping over unitialized fabric with fabricId 0x0000000000000000, nodeId 0x0000000000000000 vendorId 0x0000
I: 41882 [ZCL]OpCreds: Stored 0 fabrics in fabrics list attribute.
I: 41889 [SVR]Persisting fabric ID successfully
I: 41893 [SVR]Device completed Rendezvous process
I: 41897 [SVR]Stored value in server storage
I: 41904 [SVR]Stored value in server storage
E: 41908 [DL]Long dispatch time: 315 ms, for event type 16388
D: 41914 [DL]In DriveBLEState
D: 41916 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 41922 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 41928 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 41934 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 42031 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 42037 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 42129 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 42135 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 42226 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 42232 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 42323 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 42329 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
I: 42336 [IN]Secure transport received message destined to fabric 0, node 0x0000000000000009. Key ID 0
I: 42345 [IN]Setting nodeID 9 on fabric.
I: 42349 [IN]Setting fabricID 1B669 on fabric.
I: 42353 [IN]Since fabric was modified, persisting changes to KVS
I: 42376 [SVR]Stored value in server storage
I: 42397 [DIS]Fabric (0) persisted to storage. Calling OnFabricPersistedToStorage
I: 42405 [ZCL]OpCreds: Fabric 0 was persisted to storage. FabricId 00001B66900000000, NodeId 90000000000000000, VendorId 0x4B2D
I: 42416 [ZCL]OpCreds: Call to writeFabricsIntoFabricsListAttribute
I: 42423 [ZCL]OpCreds: Skipping over unitialized fabric with fabricId 0x000000000001B669, nodeId 0x0000000000000009 vendorId 0x0000
I: 42434 [ZCL]OpCreds: Stored 0 fabrics in fabrics list attribute.
I: 42440 [EM]Received message of type 0x08 with vendorId 0x0000 and protocolId 0x0005 on exchange 34212
D: 42450 [EM]ec id: 34212, Delegate: 0x0x20006220
D: 42454 [DMG]ICR moving to [Initialize]
D: 42458 [ZCL]Received Cluster Command: Cluster=3e Command=a1 Endpoint=0
I: 42465 [ZCL]O5 ms, for event type 16388
D: 42815 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 42821 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 42908 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 42914 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 42920 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 43006 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 43011 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 43103 [DL]NotificaI: 43606 [ZCL]OpCreds: NewCertificateSigningRequest returned 0
D: 43611 [DMG]ICR moving to [AddCommand]
D: 43616 [IN]Secure message was encrypted: Msg ID 2
I: 43620 [IN]Encrypted message 0x200249f8 from 0x0000000000000009 to 0x000000000001B669 of type 9 and protocolId 5 on exchange 34213.
I: 43632 [IN]Sending msg 0x200249f8 to 0x000000000001B669 at utc time: 43632 msec
I: 43640 [IN]Sending secure msg on generic transport
D: 43645 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
I: 43651 [IND: 44362 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 44377 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 44383 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 44407 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 44412 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 44437 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 44452 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 44458 [DL]Sending notification for CHIPnnId 00, len 20)
I: 45153 [IN]Secure msg send status No Error
D: 45157 [DMG]ICR moving to [   Sending]
D: 45161 [DMG]ICR moving to [Uninitiali]
E: 45165 [DL]Long dispatch time: 231 ms, for event type 16388
D: 45172 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 45187 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 45193 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 45217 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 45222 [DL]Sending notificatiD: 47843 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 47887 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 50392 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 52899 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 52928 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 55463 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 57968 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 57997 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 60518 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 63024 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 63053 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 65573 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 68079 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 68123 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 70658 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 73164 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 73194 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 75698 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 78204 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 78234 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 80738 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 83245 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 83274 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 85793 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 88299 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 88328 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 90849 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 93355 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 93385 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 95904 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 98410 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 98440 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 98560 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 98590 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 98596 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
I: 98602 [IN]Secure transport received message destined to fabric 0, node 0x0000000000000009. Key ID 0
I: 98613 [EM]Received message of type 0x08 with vendorId 0x0000 and protocolId 0x0005 on exchange 34215
D: 98622 [EM]ec id: 34215, Delegate: 0x0x20006220
D: 98627 [DMG]ICR moving to [Initialize]
D: 98631 [ZCL]Received Cluster Command: Cluster=31 Command=6 Endpoint=0
D: 98637 [ZCL]AddThreadNetwork: 0
D: 98640 [DMG]ICR moving to [AddCommand]
D: 98645 [IN]Secure message was encrypted: Msg ID 4
I: 98650 [IN]Encrypted message 0x200249f8 from 0x0000000000000009 to 0x000000000001B669 of type 9 and protocolId 5 on exchange 34215.
I: 98662 [IN]Sending msg 0x200249f8 to 0x000000000001B669 at utc time: 98661 msec
I: 98669 [IN]Sending secure msg on generic transport
I: 98674 [IN]Secure msg send status No Error
D: 98678 [DMG]ICR moving to [   Sending]
D: 98682 [DMG]ICR moving to [Uninitiali]
D: 98685 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 98691 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 98739 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 98745 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 98751 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 98784 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 98789 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 98814 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 98820 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 98825 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 98859 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 98864 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 8)
D: 98889 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 98895 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 98935 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 98941 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 3)
D: 98964 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 98979 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
I: 98986 [IN]Secure transport received message destined to fabric 0, node 0x0000000000000009. Key ID 0
I: 98995 [EM]Received message of type 0x08 with vendorId 0x0000 and protocolId 0x0005 on exchange 34216
D: 99005 [EM]ec id: 34216, Delegate: 0x0x20006220
D: 99010 [DMG]ICR moving to [Initialize]
D: 99013 [ZCL]Received Cluster Command: Cluster=31 Command=c Endpoint=0
E: 99034 [DIS]Fabric ID not known. Using a default
I: 99039 [DIS]Found admin pairing for admin 0, node 0x0000000000000009
D: 99045 [DIS]Using Thread extended MAC for hostname.
I: 99050 [DIS]Advertise operational node 000000014A77CBB3-0000000000000009
I: 99058 [DL]advertising srp service: 000000014A77CBB3-0000000000000009._matter._tcp
E: 99065 [DIS]Operational advertising enabled
D: 99070 [DMG]ICR moving to [AddCommand]
D: 99074 [IN]Secure message was encrypted: Msg ID 5
I: 99079 [IN]Encrypted message 0x200249f8 from 0x0000000000000009 to 0x000000000001B669 of type 9 and protocolId 5 on exchange 34216.
I: 99091 [IN]Sending msg 0x200249f8 to 0x000000000001B669 at utc time: 99091 msec
I: 99098 [IN]Sending secure msg on generic transport
D: 99103 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
I: 99110 [IN]Secure msg send status No Error
D: 99114 [DMG]ICR moving to [   Sending]
D: 99118 [DMG]ICR moving to [Uninitiali]
E: 99121 [DL]Long dispatch time: 141 ms, for event type 16388
D: 99127 [DL]OpenThread State Changed (Flags: 0x1006c100)
D: 99133 [DL]   Network Name: OpenThread
D: 99136 [DL]   PAN Id: 0x7B23
D: 99139 [DL]   Extended PAN Id: 0xE08F1281728D9C9F
D: 99145 [DL]   Channel: 11
D: 99147 [DL]   Mesh Prefix: fdde:ad00:beef::/64
D: 99152 [DL]In DriveBLEState
D: 99155 [DL]OpenThread State Changed (Flags: 0x1100101d)
D: 99160 [DL]   Device Role: DETACHED
D: 99164 [DL]   Thread Unicast Addresses:
D: 99167 [DL]        fdde:ad00:beef:0:bb9f:fdb8:1c0b:89c5/64 valid
D: 99174 [DL]        fe80::540e:89c8:7820:20e4/64 valid preferred
D: 99180 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 99186 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 99192 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 99219 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 99225 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 99249 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 99264 [DL]Write request received for CHIPoBLE RX (ConnId 0x00)
D: 99270 [DL]Sending notification for CHIPoBLE TX (ConnId 00, len 20)
D: 99294 [DL]Notification for CHIPoBLE TX done (ConnId 0x00)
D: 99302 [DL]Sending notifI: 100404 [DL]BLE GAP connection terminated (reason 0x13)
D: 100410 [IN]Clearing BLE pending packets.
I: 100414 [DL]Current number of connections: 0/1
D: 100418 [DL]In DriveBLEState
D: 106706 [DL]OpenThread State Changed (Flags: 0x301132b7)
D: 106712 [DL]   Device Role: CHILD
D: 106715 [DL]   Network Name: THREAD
D: 106718 [DL]   PAN Id: 0x7B23
D: 106721 [DL]   Extended PAN Id: 0xE08F1281728D9C9F
D: 106726 [DL]   Channel: 11
D: 106729 [DL]   Mesh Prefix: fd6f:99f:9439::/64
D: 106733 [DL]   Partition Id: 0x9AC8A20A
D: 106737 [DL]   Thread Unicast Addresses:
D: 106741 [DL]        fd33:8d42:9180:0:2a64:a5e8:ea75:37dc/64 valid
D: 106747 [DL]        fd6f:99f:9439::ff:fe00:6c01/64 valid rloc
D: 106753 [DL]        fd6f:99f:9439:0:bb9f:fdb8:1c0b:89c5/64 valid
D: 106759 [DL]        fe80::540e:89c8:7820:20e4/64 valid preferred
D: 106765 [DL]OpenThread State Changed (Flags: 0x00000001)
D: 106770 [DL]   Thread Unicast Addresses:
D: 106774 [DL]        fd33:8d42:9180:0:2a64:a5e8:ea75:37dc/64 valid
D: 106780 [DL]        fd6f:99f:9439::ff:fe00:6c01/64 valid rloc
D: 106786 [DL]        fd6f:99f:9439:0:bb9f:fdb8:1c0b:89c5/64 valid
D: 106792 [DL]        fe80::540e:89c8:7820:20e4/64 valid preferred

[Sigurd Hellesvik]

Hi

h.vig said:

1. How do I get the Fabric Id and Node Id? Any information on how to control the door lock (after commissioning) would be great.

There seems to be a bug with this sample, and the developers are looking into it. I will return here when this have been resolved.

h.vig said:

2. I know that in Thread the devices will need to pair (establish a DTLS connection). Will that be handled automatically by the app (lock client) and the lock server? Is the PSK shared during the commissioning stages?

Technical details on the protocol is found in the Matter specification.
The Matter specification is currently only available for members of the Matter project.
If you want to know more on this, please contact the Matter project.

Regards,
Sigurd Hellesvik

[Sigurd Hellesvik]

Hi

Sigurd Hellesvik said:

There seems to be a bug with this sample, and the developers are looking into it. I will return here when this have been resolved.

An issue have been created for this bug.

Regards,
Sigurd Hellesvik