provision problem

RE: provision problem

Bjørn Kvaale — Mon, 08 Jul 2019 12:09:51 GMT

Check the rx_handle() function, in addition to the other functions in the switch case (i.e. network_packet_in(), net_beacon_packet_in() & config_packet_in()).

RE: provision problem

zhengrui — Tue, 02 Jul 2019 03:04:13 GMT

Sorry to reply for a long time.

I've gotten it.But for qustion(4),I don't find any call or interface in gatt_evt_handler to connect to the information about setting the publish/subscribe information & the app key in mesh network.So I don't know how to configure them.

RE: provision problem

Bjørn Kvaale — Fri, 10 May 2019 11:05:46 GMT

1) You advertise both a non-connectable (PB-ADV) & a connectable (PB-GATT) beacon. The connectable beacon also includes the mesh provisioning service UUID.

2) The device sends data via the proxy.c file using the proxy service. This can be seen by looking at the proxy light switch example device log (e.g. debugging using Segger Embedded Studio). One can see that the MESH_GATT_EVT_TYPE_TX_READY & MESH_GATT_EVT_TYPE_TX_COMPLETE events in gatt_evt_handler get called a few times.

3) The rx_handle function in proxy.c is used to handle incoming packets from the nRF Mesh mobile app (e.g. see MESH_GATT_EVT_TYPE_RX).

4) You set the publish/subscribe information & the app key via the nRF Mesh app. The same gatt_evt_handler is used to receive the incoming appkey bind & publish/subscribe address messages. Are you wondering where the appkey & the publish/subscribe messages get stored in the device itself?