CHIP lighting demo, Commissioning starts, app dies, 52840dk seems to be in child state, but app does not control light on/off.

RE: CHIP lighting demo, Commissioning starts, app dies, 52840dk seems to be in child state, but app does not control light on/off.

riedlse — Thu, 11 Feb 2021 16:37:59 GMT

Much better news, had a thread in the open thread forum on otbr and my setup, Jon suggested adding radvd for ipv6 routing. Not sure if that was part of the fix.

https://groups.google.com/u/2/g/openthread-users/c/Yne0KQUGumA

One thing that didn't work was commissioning when I setup the otbr using ot-ctl, it did work when I used the web guide to form the network.

When the android chip tool went to the light control screen, it initially could not connect. I then tried pinging the board after I did an "ot ipaddr" from the rpi and it worked, then I noticed the the IP address on the chip tool only had 1 : where the IP address had a :0:0: , when I modified the address to the same as it showed and I pinged

IT WORKED (well once, I was able to turn on the light, debug below)

so far no luck getting it working again, but I will continue to debug later, need to go skiing now.

I would call this solved with the proper border router config.

I: 749031[BLE] Received rendezvous message from lu

D: 749035[BLE] Received spake2p msg3

D: 749041[IN] New pairing for device lu, key 0!!

I: 749046[SVR] Received a new connection.

I: 749050[SVR] Device completed SPAKE2+ handshake

D: 751490[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 751497[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 3)

D: 751580[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 754055[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 756563[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 3)

D: 756620[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 756845[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 756935[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 756942[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 3)

D: 757024[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 757033[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 757115[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 757122[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 3)

D: 757204[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 757213[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 757295[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 757302[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 3)

D: 757384[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 757393[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

I: 757401[BLE] Received rendezvous message for lu

I: 757406[BLE] Received rendezvous message from lu

I: 757410[NP] Received kThreadAssociationRequest

I: 757423[SVR] Device was assigned network credentials

I: 757428[DIS] CHIP minimal mDNS started advertising.

I: 757433[SVR] Device completed Rendezvous process

D: 757438[DL] In DriveBLEState

D: 757443[DL] OpenThread State Changed (Flags: 0x0106d01d)

D: 757448[DL] Device Role: DETACHED

D: 757451[DL] Network Name: OpenThread

D: 757455[DL] PAN Id: 0x1234

D: 757458[DL] Extended PAN Id: 0x1111111122222222

D: 757463[DL] Channel: 15

D: 757465[DL] Mesh Prefix: fdde:ad00:beef::/64

D: 757470[DL] Thread Unicast Addresses:

D: 757474[DL] fdde:ad00:beef:0:40ef:1293:1957:8148/64 valid preferred

D: 757481[DL] fe80::2893:9cf8:7a52:3cb7/64 valid preferred

D: 760067[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 3)

D: 760074[DL] OpenThread State Changed (Flags: 0x001132b7)

D: 760080[DL] Device Role: CHILD

D: 760083[DL] Network Name: OpenThreadDemo

D: 760087[DL] PAN Id: 0x1234

D: 760090[DL] Extended PAN Id: 0x1111111122222222

D: 760095[DL] Channel: 15

D: 760097[DL] Mesh Prefix: fd4b:2693:d337:c9f5::/64

D: 760102[DL] Partition Id: 0x6A373B69

D: 760106[DL] Thread Unicast Addresses:

D: 760110[DL] fd11:22::5dd7:5f9c:a3f9:7e6d/64 valid preferred

D: 760116[DL] fd4b:2693:d337:c9f5:0:ff:fe00:f001/64 valid preferred rloc

D: 760123[DL] fd4b:2693:d337:c9f5:40ef:1293:1957:8148/64 valid preferred

D: 760130[DL] fe80::2893:9cf8:7a52:3cb7/64 valid preferred

I: 760136[NP] Sending IP Address. Delegate 0x20005b34

D: 760142[IN] Secure message was encrypted: Msg ID 0

I: 760146[IN] Sending msg from lu to lu

I: 760150[IN] Sending secure msg on connection specific transport

I: 760156[IN] Secure msg send status 0

D: 760159[DL] OpenThread State Changed (Flags: 0x00000001)

D: 760165[DL] Thread Unicast Addresses:

D: 760168[DL] fd11:22::5dd7:5f9c:a3f9:7e6d/64 valid preferred

D: 760175[DL] fd4b:2693:d337:c9f5:0:ff:fe00:f001/64 valid preferred rloc

D: 760182[DL] fd4b:2693:d337:c9f5:40ef:1293:1957:8148/64 valid preferred

D: 760189[DL] fe80::2893:9cf8:7a52:3cb7/64 valid preferred

I: 760195[NP] Sending IP Address. Delegate 0x20005b34

D: 760201[IN] Secure message was encrypted: Msg ID 1

I: 760205[IN] Sending msg from lu to lu

I: 760209[IN] Sending secure msg on connection specific transport

I: 760215[IN] Secure msg send status 0

D: 760400[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 760408[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 20)

D: 760493[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 760501[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 760508[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 20)

D: 760580[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 760588[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 20)

D: 760673[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 760681[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 760688[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 20)

D: 760760[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 760768[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 11)

D: 760853[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 760861[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 760868[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 20)

D: 760940[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 760948[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 20)

D: 761032[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

I: 762020[DL] BLE GAP connection terminated (reason 0x13)

I: 762025[SVR] OnRendezvousError: Ble Error 6012 (0x0000177C): Remote device closed BLE connection

I: 762034[DL] Current number of connections: 0/1

D: 762038[DL] In DriveBLEState

I: 762046[DL] CHIPoBLE advertising started

I: 768761[SVR] Packet received from UDP:fd11:22:33:0:c0b5:1fd6:1ffb:c5df:58175: zu bytes

I: 768769[ZCL] APS frame processing success!

I: 768773[ZCL] RX len 25, ep a0, clus 0x618a

I: 768777[ZCL] FC 21 seq 5f cmd c2 payload[

I: 768781[ZCL] 0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX0hX

I: 768788[ZCL] ]

I: 768790[ZCL] Drop cluster 0x618a command 0xc2

I: 768794[ZCL] due to invalid endpoint:

I: 768798[ZCL] 0xa0

I: 768800[ZCL] Data model processing failure!

uart:~$ ot ipaddr

fd11:22:0:0:5dd7:5f9c:a3f9:7e6d

fd4b:2693:d337:c9f5:0:ff:fe00:f001

fd4b:2693:d337:c9f5:40ef:1293:1957:8148

fe80:0:0:0:2893:9cf8:7a52:3cb7

Done

uart:~$ ot state

child

Done

uart:~$ D: 1662050[DL] SetAdvertisingEnabled(false)

I: 1662054[DL] CHIPoBLE advertising disabled because of timeout expired

D: 1662060[DL] In DriveBLEState

I: 1662064[DL] CHIPoBLE advertising stopped

I: 2084489[SVR] Packet received from UDP:fd11:22:33:0:c0b5:1fd6:1ffb:c5df:58175: zu bytes

I: 2084497[ZCL] APS frame processing success!

I: 2084501[ZCL] RX len 3, ep 1, clus 0x 6

I: 2084504[ZCL] FC 1 seq 1 cmd 1 payload[

I: 2084508[ZCL] NULL

I: 2084510[ZCL] ]

I: 2084512[ZCL] On/Off set value: 1 1

I: 2084515[ZCL] Toggle on/off from 0 to 1

I: 2084519[ZCL] sched report event in 0 ms

I: 2084523[ZCL] Cluster callback: 6

I: Turn On Action has been initiated

I: Turn On Action has been completed

I: 2084533[ZCL] sched report event in 0 ms

I: 2084537[ZCL] Cluster callback: 8

I: 2084540[ZCL] Value: 0, length 1

I: Level Action has been initiated

I: Setting brightness level to 0

I: Level Action has been completed

D: 2084552[ZCL] Measured APS frame size 11

D: 2084556[ZCL] Successfully encoded 11 bytes

D: 2084560[IN] Secure message was encrypted: Msg ID 2

I: 2084565[IN] Sending msg from lu to lu

I: 2084569[IN] Sending secure msg on generic transport

I: 2084574[IN] Secure msg send status 0

I: 2084578[ZCL] T 0:TX (0x6e47a) Ucast 0x00x7ada8

I: 2084582[ZCL] TX buffer: [

I: 2084585[ZCL] 0hX0hX0hX0hX0hX

I: 2084588[ZCL] ]

I: 2084589[ZCL] Data model processing success!

I: 2084594[ZCL] Event: move from 0

I: 2084597[ZCL] to 255

I: 2084599[ZCL] (diff +1)

I: 2084601[ZCL] sched report event in 0 ms

I: 2084605[ZCL] Cluster callback: 8

I: 2084608[ZCL] Value: 255, length 1

I: Level Action has been initiated

I: Setting brightness level to 255

I: Level Action has been completed

RE: CHIP lighting demo, Commissioning starts, app dies, 52840dk seems to be in child state, but app does not control light on/off.

kkasperczyk — Thu, 11 Feb 2021 11:24:18 GMT

If it comes to the attached files, there is an information that you may download applications.zip containing .hex files for lock-app, ot rcp and .apk for the Android CHIP Tool and the link is located on the bottom of a page. Here you have a direct link to .zip: /cfs-file/__key/communityserver-discussions-components-files/4/applications.zip

[quote userid="38401" url="~/f/nordic-q-a/71270/chip-lighting-demo-commissioning-starts-app-dies-52840dk-seems-to-be-in-child-state-but-app-does-not-control-light-on-off/293866#293866"]But I think something is still not quite there in routing? dnsmasq, tayga and bind9 (and all the other otbr processes seem to be there)[/quote]

I know that configuring whole OTBR from scratch might be painful and there are many possible things to make mistake, so that's why in the blog post there is recommendation to use docker version, where all of this things are already done. I strongly recommend you to try using solution suggested by us, so attached applications and OTBR docker, cause it should allow you to make everything work easily and then try to make some experiments.

[quote userid="38401" url="~/f/nordic-q-a/71270/chip-lighting-demo-commissioning-starts-app-dies-52840dk-seems-to-be-in-child-state-but-app-does-not-control-light-on-off/293866#293866"]tried docker version, but that doesn't give you the AP, so went back [/quote]

I'm not quite sure what you mean here. OTBR docker purpose is not to provide WiFi AP, but only to run OTBR script on the connected RCP device with some predefined configuration. In the "Forming Thread network" section you can see generally two types of activities:

Forming Thread network with fd11:22:: prefix, by running OTBR docker on the RCP device, making configuration in the browser and etc.
Adding network 2001:db8:1::/64 to the docker and configuring routing for it. This is because, we are using then this network to create WiFi AP for the smartphone, so we need to give docker access to this network and tell it to route packets from that IP range to the Thread network addresses from range fd11:22:: (described in the point 11).

Having OTBR working, then you should try to make steps from the "Configuring WiFi hotspot" section. If for some reason it will not work for you, it is good to try detect what went wrong, so:

See if any errors appeared in the console, if yes, please try to provide them.
After completing steps 1-9, verify if you can find created hotspot on your smartphone.
Try to connect to the hotspot and verify if your smartphone got IPv6 address (notice if message similar to the: "Unable to retrieve IP address" appeared). You can also go on your smartphone to the WiFi settings -> Additional settings -> IP address and see if you can find there IPv6 address starting at 2001:db8:

[quote userid="38401" url="~/f/nordic-q-a/71270/chip-lighting-demo-commissioning-starts-app-dies-52840dk-seems-to-be-in-child-state-but-app-does-not-control-light-on-off/293866#293866"]Scroll to bottom, I tried using button 3 to connect to the network, seems to connect but gets errors as well.[/quote]

Looking at your logs everything seems to be fine. First part, when you were starting Thread using mobile commissioner went absolutely fine, please ignore the following error:

I: 30737[SVR] OnRendezvousError: Ble Error 6012 (0x0000177C): Remote device closed BLE connection

That is matter of small bug, which was fixed in the next versions and it means that your BLE connection was closed, because commissioning was finished and it is normal disconnection operation. At this point I think that whole commissioning works fine and if you see "Network unreachable" error on smartphone, that means that it is not able to send packets to the target, because of one of two things:

You did not provide it WiFi AP, so it tries to send packets to some other currently connected network.
You provided WiFi AP, but you don't have properly configured routing, so packets are send to your PC, but then they are not routed to the Thread network.

I suggest you to try run OTBR and WiFi AP following the steps from the "Forming Thread network" and "Configuring WiFi hotspot" sections. If doing it you will encounter some problems, please try to verify the reason following the mentioned hints.

RE: CHIP lighting demo, Commissioning starts, app dies, 52840dk seems to be in child state, but app does not control light on/off.

riedlse — Wed, 10 Feb 2021 20:40:36 GMT

Oh, I followed the build instruction and built the app and android app from scratch. I didn't notice the .hex files?

RE: CHIP lighting demo, Commissioning starts, app dies, 52840dk seems to be in child state, but app does not control light on/off.

riedlse — Wed, 10 Feb 2021 20:36:16 GMT

Yes, I am definitely using the light demo (I think the lock demo is essentially the same as the light demo)

OK, getting long here, definitely some issues with the border router, still not 100% certain it is setup correctly, but I do get farther. tried docker version, but that doesn't give you the AP, so went back and found stretch lite and reloaded. wifi setup didn't work (again and manually went through the setup) But I think something is still not quite there in routing? dnsmasq, tayga and bind9 (and all the other otbr processes seem to be there)

the device seems to be provisioned correctly per the thread below, an to state says it's a child, but I am back to the led short flash that says it is unprovisioned? Although it is clearly on the network? Although the topology on the OTBR does not show it.

uart:~$ ot state

child

Done

uart:~$ ot ipaddr

fd11:22:0:0:f113:838d:7249:27e2

fd2b:2ba5:d5b:b65f:0:ff:fe00:2801

fd2b:2ba5:d5b:b65f:2cc8:eacc:3c66:15e5

fe80:0:0:0:f02c:3c0:e45c:b68f

Done

uart:~$ ot ping fd2b:2ba5:d5b:b65f:4ade:bb00:8852:eee1

Done

16 bytes from fd2b:2ba5:d5b:b65f:4ade:bb00:8852:eee1: icmp_seq=1 hlim=64 time=27ms

uart:~$

The chiptool gets a

chip.devicecontroller.ChipDeviceControllerException: OS Error 2101 Network is unreachable

Scroll to bottom, I tried using button 3 to connect to the network, seems to connect but gets errors as well.

I: 26608[BLE] Received rendezvous message for lu

I: 26612[BLE] Received rendezvous message from lu

I: 26617[NP] Received kThreadAssociationRequest

I: 26635[SVR] Device was assigned network credentials

I: 26640[DIS] CHIP minimal mDNS started advertising.

I: 26645[SVR] Device completed Rendezvous process

D: 26650[DL] In DriveBLEState

D: 26654[DL] OpenThread State Changed (Flags: 0x0106d01d)

D: 26659[DL] Device Role: DETACHED

D: 26663[DL] Network Name: OpenThread

D: 26666[DL] PAN Id: 0x1234

D: 26669[DL] Extended PAN Id: 0x1111111122222222

D: 26674[DL] Channel: 15

D: 26676[DL] Mesh Prefix: fdde:ad00:beef::/64

D: 26681[DL] Thread Unicast Addresses:

D: 26685[DL] fdde:ad00:beef:0:2cc8:eacc:3c66:15e5/64 valid preferred

D: 26691[DL] fe80::f02c:3c0:e45c:b68f/64 valid preferred

D: 29081[DL] OpenThread State Changed (Flags: 0x001132b7)

D: 29086[DL] Device Role: CHILD

D: 29089[DL] Network Name: OpenThreadDemo

D: 29093[DL] PAN Id: 0x1234

D: 29096[DL] Extended PAN Id: 0x1111111122222222

D: 29101[DL] Channel: 15

D: 29103[DL] Mesh Prefix: fd2b:2ba5:d5b:b65f::/64

D: 29108[DL] Partition Id: 0x7C04DEE2

D: 29112[DL] Thread Unicast Addresses:

D: 29115[DL] fd11:22::f113:838d:7249:27e2/64 valid preferred

D: 29122[DL] fd2b:2ba5:d5b:b65f:0:ff:fe00:2801/64 valid preferred rloc

D: 29129[DL] fd2b:2ba5:d5b:b65f:2cc8:eacc:3c66:15e5/64 valid preferred

D: 29136[DL] fe80::f02c:3c0:e45c:b68f/64 valid preferred

I: 29141[NP] Sending IP Address. Delegate 0x20005b34

D: 29147[IN] Secure message was encrypted: Msg ID 0

I: 29151[IN] Sending msg from lu to lu

I: 29155[IN] Sending secure msg on connection specific transport

D: 29161[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 20)

I: 29168[IN] Secure msg send status 0

D: 29171[DL] OpenThread State Changed (Flags: 0x00000001)

D: 29177[DL] Thread Unicast Addresses:

D: 29180[DL] fd11:22::f113:838d:7249:27e2/64 valid preferred

D: 29186[DL] fd2b:2ba5:d5b:b65f:0:ff:fe00:2801/64 valid preferred rloc

D: 29193[DL] fd2b:2ba5:d5b:b65f:2cc8:eacc:3c66:15e5/64 valid preferred

D: 29200[DL] fe80::f02c:3c0:e45c:b68f/64 valid preferred

I: 29206[NP] Sending IP Address. Delegate 0x20005b34

D: 29212[IN] Secure message was encrypted: Msg ID 1

I: 29216[IN] Sending msg from lu to lu

I: 29220[IN] Sending secure msg on connection specific transport

I: 29226[IN] Secure msg send status 0

D: 29234[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 29292[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 29300[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 20)

D: 29385[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 29393[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 29400[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 20)

D: 29472[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 29480[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 20)

D: 29565[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 29573[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 29580[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 12)

D: 29652[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 29660[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 20)

D: 29744[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

I: 30732[DL] BLE GAP connection terminated (reason 0x13)

I: 30737[SVR] OnRendezvousError: Ble Error 6012 (0x0000177C): Remote device closed BLE connection

I: 30746[DL] Current number of connections: 0/1

D: 30750[DL] In DriveBLEState

I: 30758[DL] CHIPoBLE advertising started

>>>>> When reset then hit button 3

I: 502[DL] OpenThread started: OK

I: 505[DL] Setting OpenThread device type to MINIMAL END DEVICE

I: 511[ZCL] deactivate report event

I: 515[ZCL] Cluster callback: 6

I: 517[ZCL] Cluster callback: 8

I: 520[ZCL] Value: 255, length 1

I: 523[ZCL] sched report event in 65343477 ms

D: 528[IN] TransportMgr initialized

I: 531[IN] local node id is lu

D: 534[BLE] Waiting for PBKDF param request

I: 538[SVR] Server Listening...

I: 541[DL] Device Configuration:

I: 544[DL] Serial Number: (not set)

I: 547[DL] Vendor Id: 9050 (0x235A)

I: 550[DL] Product Id: 65279 (0xFEFF)

I: 554[DL] Product Revision: 1

I: 557[DL] Setup Pin Code: 12345678

I: 560[DL] Setup Discriminator: 3840 (0xF00)

I: 565[DL] Manufacturing Date: (not set)

I: 569[SVR] SetupQRCode: [CH:I34DV*-00 0C9SS0]

I: 573[SVR] Copy/paste the below URL in a browser to see the QR Code:

I: 579[SVR] dhrishi.github.io/.../qrcode.html

D: 588[DL] CHIP task running

D: 590[DL] In DriveBLEState

I: Device is not commissioned to a Thread network. Starting with the default configuration.

I: 6982[DL] CHIPoBLE advertising disabled because device is fully provisioned

D: 6989[DL] In DriveBLEState

I: 6992[SVR] nfc_t2t_emulation_stop failed: -35

E: Stopping NFC Tag emulation failed

D: 6999[DL] OpenThread State Changed (Flags: 0x0106d01d)

D: 7004[DL] Device Role: DETACHED

D: 7008[DL] Network Name: OpenThread

D: 7011[DL] PAN Id: 0x1234

D: 7014[DL] Extended PAN Id: 0x1111111122222222

D: 7019[DL] Channel: 15

D: 7021[DL] Mesh Prefix: fd11:1111:1122::/64

D: 7025[DL] Thread Unicast Addresses:

D: 7029[DL] fd11:1111:1122:0:eb54:5c65:358a:55b/64 valid preferred

D: 7036[DL] fe80::e07f:da9f:829a:124/64 valid preferred

D: 9223[DL] OpenThread State Changed (Flags: 0x001132b7)

D: 9228[DL] Device Role: CHILD

D: 9231[DL] Network Name: OpenThreadDemo

D: 9235[DL] PAN Id: 0x1234

D: 9238[DL] Extended PAN Id: 0x1111111122222222

D: 9242[DL] Channel: 15

D: 9245[DL] Mesh Prefix: fd2b:2ba5:d5b:b65f::/64

D: 9249[DL] Partition Id: 0x7C04DEE2

D: 9253[DL] Thread Unicast Addresses:

D: 9257[DL] fd11:22::474d:13cf:321:d9c6/64 valid preferred

D: 9263[DL] fd2b:2ba5:d5b:b65f:0:ff:fe00:2803/64 valid preferred rloc

D: 9270[DL] fd2b:2ba5:d5b:b65f:eb54:5c65:358a:55b/64 valid preferred

D: 9276[DL] fe80::e07f:da9f:829a:124/64 valid preferred

I: 9282[NP] Sending IP Address. Delegate 0x20005b34

E: 9287[NP] Failed in sending IP address. error Error 4003 (0x00000FA3)

D: 9294[DL] OpenThread State Changed (Flags: 0x00000001)

D: 9299[DL] Thread Unicast Addresses:

D: 9302[DL] fd11:22::474d:13cf:321:d9c6/64 valid preferred

D: 9308[DL] fd2b:2ba5:d5b:b65f:0:ff:fe00:2803/64 valid preferred rloc

D: 9315[DL] fd2b:2ba5:d5b:b65f:eb54:5c65:358a:55b/64 valid preferred

D: 9322[DL] fe80::e07f:da9f:829a:124/64 valid preferred

I: 9328[NP] Sending IP Address. Delegate 0x20005b34

E: 9332[NP] Failed in sending IP address. error Error 4003 (0x00000FA3)

ot state

child

Done

uart:~$

RE: CHIP lighting demo, Commissioning starts, app dies, 52840dk seems to be in child state, but app does not control light on/off.

kkasperczyk — Wed, 10 Feb 2021 08:31:30 GMT

Hi riedlse, thanks for reporting an issue. WiFi AP is necessary in order to provide the mobile app Internet access within the known network and be able to route packets from that network to the Thread device through the border router. So generally we can divide this test process on the two stages:

Commissioning (so called Rendezvous) - For that one you need existing Thread network (so running border router, which is Thread network leader), not configured CHIP device and smartphone running CHIP Tool mobile app. After scanning device's QR code the devices are starting exchanging information over BLE like encryption and session keys and etc. After that device has all information necessary to communicate using CHIP stack, but still is not attached to any network (Thread in that case). After that you see on the mobile app window asking to enter Thread network credentials, you press "Save network" button and CHIP device should receive it, configure Thread and join the border router's Thread network as a CHILD. All the communication is done using BLE, so for that part you don't need WiFi AP (however it's good to have it configured before, as described in the guide).
Controlling - For that one you need WiFi AP, border router and configured routing on PC, as smartphone sends IPv6 packets using WiFi and is not able to reach device inside the Thread network directly. Packets are going to the PC wlan port, routed to the border router and then sent to the CHIP device.

The important thing is to detect on which stage is your test failing. Please note that CHIP is project in early development, so after reset CHIP device is not able to communicate with the smartphone even it was paired successfully before. Also pairing device multiple times, after it changes state to CHILD will not work either. If something is going wrong, it is good idea to do the device factory reset (pressing button nr 1 for over 6 seconds), check if Thread is disabled and start pairing from the beginning.

To help me solve your problem, I would like to ask you to answer few questions:

Do you use output .hex and .apk files attached to the blog post or you tried to build apps on your own? I'm asking because you wrote that problem is with CHIP lighting demo, while attached application is lock-app, so I would like to just clarify it.
Can you find in the device logs messages similar to the following:

I: 135225[IN] New pairing for device lu, key 0!!
I: 135230[SVR] Received a new connection.
I: 135234[SVR] Device completed SPAKE2+ handshake

It should appear just before displaying Thread network configuration window on the mobile app and it proves that rendezvous session was completed successfully.

Do you see on the CHIP device logs after pressing on the mobile app "Save network" button that it changed state to CHILD? I'm a bit confused, because you attached logs showing that after exchanging CHIPoBLE TX/RX characteristics connection is broken, so operation failed, but you also wrote that it goes to the CHILD state, so I'm not sure how did you achieve it? Was there a further log saying that it changed state to CHILD or you had device in the CHILD state after previous session and you tried to pair it once again? In case you did - it will not work, so you could try factory reset the device to disable Thread and pair it once again.

When making any further tests, please try to capture and provide as much logs from the nrf52840DK as you can - it will definitely help to find the problem.

In my opinion you have some problems with completing commissioning stage successfully and routing doesn't have much to do with it, as all information are exchanged over BLE. But if it comes to the possible further routing issues, you can also try to investigate it. After having device in the CHILD state you may try to get its ip address, by typing `ot ipaddr`, as you did before, and ping it from your PC terminal. If you manage to do that, it will mean that routing is working fine. Pinging border router from the CHIP device will not check it, as they are inside of the same Thread network with the parent-child relation, so they should be able to communicate even without any routing settings.

RE: CHIP lighting demo, Commissioning starts, app dies, 52840dk seems to be in child state, but app does not control light on/off.

riedlse — Thu, 04 Feb 2021 22:07:51 GMT

So, further along, but still not quite there. It looks like I didn't understand that you needed to do all of the AP wifi setup on the border router (and the doc is missing some info about starting Dnsmasq and targa... but I think I got passed all of that. So I'm connected, the ombre shows the child in the map now. I can ping the border router. However seems something is still not working as after I hit the "Save Network", nothing happens (well it looks like the child gets setup correctly, but the screen on the chip tool never advances)

May still be some routing or Dnsmasq errors, but still at a bit of a loss....

on the child device I get

D: 305441[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 307949[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 3)

D: 308050[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 310572[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 313080[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 3)

D: 313182[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 315655[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 318164[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 3)

D: 318265[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

D: 320965[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

D: 323472[DL] Sending indication for CHIPoBLE TX characteristic (ConnId 0, len 3)

D: 323575[DL] Indication for CHIPoBLE TX characteristic done (ConnId 0x00, result 0x00)

E: 338479[BLE] ack recv timeout, closing ep 0x20006c40

I: 338484[SVR] OnRendezvousError: Ble Error 6024 (0x00001788): Message fragment acknowledgement timed out

I: 338493[BLE] Releasing end point's BLE connection back to application.

D: 403448[DL] Write request received for CHIPoBLE RX characteristic (ConnId 0x00)

I: 403456[BLE] Releasing end point's BLE connection back to application.

E: 403462[BLE] HandleChipConnectionReceived failed, err = 6018

E: 403468[BLE] failed handle new chip BLE connection, status = 6018

D: 418478[DL] ConnId: 0x00, New CCCD value: 0x0000

E: 418483[BLE] no endpoint for unsub recvd

I: 419603[DL] BLE GAP connection terminated (reason 0x13)

I: 419608[DL] Current number of connections: 0/1

D: 419612[DL] In DriveBLEState

I: 419619[DL] CHIPoBLE advertising started

RE: CHIP lighting demo, Commissioning starts, app dies, 52840dk seems to be in child state, but app does not control light on/off.

riedlse — Wed, 03 Feb 2021 18:35:21 GMT

Device says it's a child and has an IP address, but LED1 is still a short flash, so something not fully setup yet?

managed to grab the android studio debug log

D/CTL: Sending Thread credentials for channel 15, PAN ID 1234...
D/NP: Sending Thread Credentials
D/IN: Secure message was encrypted: Msg ID 0
Sending msg from 112233 to 12344321
Sending secure msg on connection specific transport
D/CTL: Received SendCharacteristic
Calling Java SendCharacteristic
D/IN: Secure msg send status 0
D/chip.BluetoothManager: ChipLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
D/CTL: Received SendCharacteristic
Calling Java SendCharacteristic
D/chip.BluetoothManager: ChipLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
D/chip.BluetoothManager: ChipLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
D/CTL: Received SendCharacteristic
Calling Java SendCharacteristic
D/chip.BluetoothManager: ChipLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
D/CTL: Received SendCharacteristic
Calling Java SendCharacteristic
D/chip.BluetoothManager: ChipLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
D/chip.BluetoothManager: ChipLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
D/CTL: Received SendCharacteristic
Calling Java SendCharacteristic
D/chip.BluetoothManager: ChipLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
D/CTL: Received SendCharacteristic
Calling Java SendCharacteristic
D/chip.BluetoothManager: ChipLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
D/chip.BluetoothManager: ChipLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
D/CTL: Received SendCharacteristic
Calling Java SendCharacteristic
D/chip.BluetoothManager: ChipLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
D/CTL: Received SendCharacteristic
Calling Java SendCharacteristic
D/chip.BluetoothManager: ChipLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
D/chip.BluetoothManager: ChipLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
D/chip.BluetoothManager: ChipLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
D/CTL: Received SendCharacteristic
Calling Java SendCharacteristic
D/chip.BluetoothManager: ChipLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
D/chip.BluetoothManager: ChipLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
D/chip.BluetoothManager: ChipLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
D/CTL: Received SendCharacteristic
D/CTL: Calling Java SendCharacteristic
D/chip.BluetoothManager: ChipLight.onCharacteristicWrite: 18ee2ef5-263d-4559-959f-4f9c429f9d11 -> 0
D/chip.BluetoothManager: ChipLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
D/chip.BluetoothManager: ChipLight.onCharacteristicChanged: 18ee2ef5-263d-4559-959f-4f9c429f9d12
D/CTL: Received SendCharacteristic
Calling Java SendCharacteristic
D/NP: Received kIPAddressAssigned
D/CTL: Remote device was assigned an ip address
I/DeviceProvisioningFragment: Pairing status update: 2
W/e.chip.chiptoo: 0xebadde09 skipped times: 0
A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x2000000a9 in tid 2024 (Binder:30144_3), pid 30144 (e.chip.chiptool)
D/Toast: show: focusDisplayId = 0, isFocusInDesktop = false mCustomDisplayId=-1
V/Toast: SHOW: android.widget.Toast$TN@f177170
Disconnected from the target VM, address: 'localhost:56965', transport: 'socket'