RE: nRF Mesh Client URI

Joakim Jakobsen — Tue, 29 Jan 2019 12:18:10 GMT

Hello.

If you take a look at the Release Notes for nRF5 SDK for Mesh, one of the changes is that we have implemented the URI Hash usage in this version of the SDK.
All examples will now advertise the URI Hash in the unprovisioned device beacon, and the static provisioner example uses this URI hash during the provisioning process.

If you take a look at the Light Switch Client, in the main.c at line 251;

mesh_provisionee_start_params_t prov_start_params =
{
    .p_static_data    = static_auth_data,
    .prov_complete_cb = provisioning_complete_cb,
    .prov_device_identification_start_cb = device_identification_start_cb,
    .prov_device_identification_stop_cb = NULL,
    .prov_abort_cb = provisioning_aborted_cb,
    .p_device_uri = EX_URI_LS_CLIENT
};

The device URI, EX_URI_LS_CLIENT is assigned.

The Uniform Resource Identifiers for the examples can found in example_common.h
Quote;
* @note Replace the example URI strings with the desired URIs for the end products. The URI strings
* should be coded as specified in the Bluetooth Core Specification Supplement v6, section 1.18.

Best regards,
Joakim