Bluetooth: Mesh sensor

The Bluetooth mesh sensor sample demonstrates how to set up a basic mesh Sensor Server model application that provides sensor data to one Sensor Client model. Four different sensor types are used to showcase different ways for the server to publish data. In addition, the sample demonstrates usage of both single-channel sensor types and sensor series types.

Note

This sample must be paired with the Bluetooth: Mesh sensor observer sample to show any functionality. The mesh sensor provides the sensor data used by the observer.

Overview

This sample is split into the following source files:

• A main.c file to handle initialization.

• One additional file for handling Bluetooth mesh models, model_handler.c.

The following Bluetooth mesh sensor types are used in this sample:

• bt_mesh_sensor_present_dev_op_temp - Published by the server according to its publishing period (see Configuring models).

• bt_mesh_sensor_rel_runtime_in_a_dev_op_temp_range - Periodically requested by the client.

• bt_mesh_sensor_presence_detected - Published when a button is pressed on the server.

• bt_mesh_sensor_time_since_presence_detected - Periodically requested by the client and published by the server according to its publishing period (see Configuring models).

Moreover, the on-chip TEMP_NRF5 temperature sensor is used.

Provisioning

The provisioning is handled by the Bluetooth mesh provisioning handler for Nordic DKs. Use nRF Mesh mobile app for provisioning and configuring of models supported by the sample.

Models

The following table shows the Bluetooth mesh sensor composition data for this sample:

Element 1
Config Server
Health Server
Sensor Server

The models are used for the following purposes:

• Config Server allows configurator devices to configure the node remotely.

• Health Server provides attention callbacks that are used during provisioning to call your attention to the device. These callbacks trigger blinking of the LEDs.

• Sensor Server provides sensor data to one or more mesh sensor observers.

The model handling is implemented in src/model_handler.c, which uses the TEMP_NRF5 temperature sensor, and the DK Button and LEDs library to detect button presses.

Requirements

The sample supports the following development kits:

Hardware platforms	PCA	Board name	Build target
nRF52 DK	PCA10040	nrf52dk_nrf52832	nrf52dk_nrf52832
nRF52840 DK	PCA10056	nrf52840dk_nrf52840	nrf52840dk_nrf52840

The sample also requires a smartphone with Nordic Semiconductor’s nRF Mesh mobile app installed in one of the following versions:

• nRF Mesh mobile app for Android

• nRF Mesh mobile app for iOS

Additionally, the sample requires the Bluetooth: Mesh sensor observer sample application. The application needs to be programmed on a separate device, and configured according to the sensor observer sample’s testing guide.

User interface

Buttons:

Can be used to input the OOB authentication value during provisioning. All buttons have the same functionality during the provisioning procedure.

Button 1:

Simulate presence detected (after the provisioning procedure is finished).

Building and running

This sample can be found under samples/bluetooth/mesh/sensor_server in the nRF Connect SDK folder structure.

See Building and programming a sample application for information about how to build and program the application.

Testing

Note

The Bluetooth mesh sensor sample cannot demonstrate any functionality on its own, and needs a device with the Bluetooth: Mesh sensor observer sample running in the same mesh network. Before testing the sensor sample, go through the sensor observer sample’s testing guide with a different kit.

After programming the sample to your development kit, you can test it by using a smartphone with Nordic Semiconductor’s nRF Mesh app installed. Testing consists of provisioning the device, and configuring it for communication with the mesh models.

Provisioning the device

The provisioning assigns an address range to the device, and adds it to the mesh network. Complete the following steps in the nRF Mesh app:

1. Tap Add node to start scanning for unprovisioned mesh devices.

2. Select the Mesh Sensor device to connect to it.

3. Tap Identify, and then Provision, to provision the device.

4. When prompted, select an OOB method and follow the instructions in the app.

Once the provisioning is complete, the app returns to the Network screen.

Configuring models

See Configuring mesh models using the nRF Mesh mobile app for details on how to configure the mesh models with the nRF Mesh mobile app.

Configure the Sensor Server model on the Mesh Sensor node:

• Bind the model to Application Key 1.

• Set the publication parameters:

  • Destination/publish address: Select an existing group or create a new one, but make sure that the Sensor Client subscribes to the same group.

  • Retransmit count: Set the count to zero (Disabled), to avoid duplicate logging in the Sensor Client’s UART terminal.

• Set the subscription parameters: Select an existing group or create a new one, but make sure that the Sensor Client publishes to the same group.

The Sensor Server model is now configured and able to send data to the Sensor Client.

Note

To enable Sensor Server configuration by a Sensor Client, an application key must be bound to the Sensor Setup Server. This functionality must also be programmed in the Sensor Client device.

Dependencies

This sample uses the following nRF Connect SDK libraries:

• Sensor Server

• Bluetooth mesh provisioning handler for Nordic DKs

• DK Button and LEDs

In addition, it uses the following Zephyr libraries:

• include/drivers/hwinfo.h

• Kernel Services:

  • include/kernel.h

• Bluetooth:

  • include/bluetooth/bluetooth.h

• Bluetooth Mesh Profile:

  • include/bluetooth/mesh.h