Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

Mesh disconnect

Hi, i have a problem with nrf mesh.
nRF5_SDK_17.0.2_d674dde

nrf5_SDK_for_Mesh_v5.0.0_src

nRF52-DK(PCA10400)

Android 6 and 10.

Bluetooth 4,1 4,2 5.0.


I use example light_switch and nrf Connect. When i use notify in Mesh Provisioning Service happened disconnect after ~60-120s. It happens on many smartphone.  I checked packets the wireshark and nrfSniffer on nRF52-DK(PCA10400). Remote user terminated connection (0x13) error occurs.

This is how I check. because our android app keeps getting disconnected in the same way

.7080.errormesh.pcapng

Parents Reply Children
  • There are no problems with this application. I do not understand the problem in the nrf connect with a notify. The notify is the same in both apps, so what's the problem?

  • Hi,

    This seems be expected behaviour. The Mesh Provisioning Service is expecting to be used for provisioning the node. Enabling notifications triggers the initiation of the provisioning link, which then starts a link timeout. This is reset each time a provisioning PDU is sent over the link, otherwise times out after NRF_MESH_PROV_LINK_TIMEOUT_MIN_US. When this times out, the connection is disconnected from the device side, assuming the provisioning process has stalled. So this is all by design, and should pose no problems for the intended and supported use case of the Mesh Provisioning Service, namely provisioning the node.

Related