In the Bluetooth Mesh solution, models are used to define the functionality of nodes. Each model represents a set of states and behaviors and defines messages that are used to interact with the model states.

One example of a model is the Configuration Model, which is a mandatory model in all mesh devices. This model represents the configuration of a node (in the form of various states) and provides messages to set or retrieve configuration parameters (behavior).

In addition to the foundation models defined in the Mesh Model Specification, the nRF5 SDK for Mesh provides unique models for performing functionalities on the nodes in a mesh network.

You can also create your own models. For details, see Creating new models.

Models in the nRF5 SDK for Mesh

See the following list for the complete overview of models implemented in the nRF5 SDK for Mesh.

Note: Links under names indicate models with documentation pages.

Generic models
- Default Transition time model
  - Source files: <InstallFolder>/models/model_spec/generic_dtt
  - API reference
- OnOff model
  - Source files: <InstallFolder>/models/model_spec/generic_onoff
  - API reference
- Level model
  - Source files: <InstallFolder>/models/model_spec/generic_level
  - API reference
- Power OnOff model
  - Source files: <InstallFolder>/models/model_spec/generic_ponoff
  - API reference
Foundation models
- Health model
  - Source files: <InstallFolder>/models/foundation/health
  - API reference
- Configuration model
  - Source files: <InstallFolder>/models/foundation/config
  - API reference
Vendor models
- Simple OnOff model
  - Source files: <InstallFolder>/models/vendor/simple_on_off
  - API reference
- RSSI monitor models (RSSI model and RSSI util model)
  - Source files: <InstallFolder>/models/vendor/rssi_monitor
  - API reference
Experimental models
- PB-remote model
  - Source files: <InstallFolder>/models/experimental/pb_remote
  - API reference

For the complete overview of available Mesh Model APIs, see Mesh Models in the API Reference section.