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

[riedlse]

Tried running android app in debug mode, but I could not see any data on the crash.

tried resetting the board a few time and re commissioning.

followed the guide to set up the DK board, AP (used a dongle instead of DK, but seems to be operational) and the android commissioning app.

uart:~$ ot ipaddr

fd11:22:0:0:9b0c:d235:7ee8:629c

fd58:94c1:25c8:62db:0:ff:fe00:a804

fd58:94c1:25c8:62db:97f9:1f55:2419:2566

fe80:0:0:0:98d0:439c:d01:8621

Done

uart:~$ ot state

child

Done

uart:~$ 

[riedlse]

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