Align the capitalization of the term "Bluetooth Mesh" to Bluetooth mesh" in the documentation. This is done to to match the new updated naming convention done in Bluetooth SIG. In the upcoming spec versions, it its used "Bluetooth mesh" with the lower case convention. Signed-off-by: Ingar Kulbrandstad <ingar.kulbrandstad@nordicsemi.no>
21 lines
818 B
ReStructuredText
21 lines
818 B
ReStructuredText
.. _bluetooth_mesh_cfg:
|
|
|
|
Runtime Configuration
|
|
#####################
|
|
|
|
The runtime configuration API allows applications to change their runtime
|
|
configuration directly, without going through the Configuration models.
|
|
|
|
Bluetooth mesh nodes should generally be configured by a central network
|
|
configurator device with a :ref:`bluetooth_mesh_models_cfg_cli` model. Each
|
|
mesh node instantiates a :ref:`bluetooth_mesh_models_cfg_srv` model that the
|
|
Configuration Client can communicate with to change the node configuration. In some
|
|
cases, the mesh node can't rely on the Configuration Client to detect or determine
|
|
local constraints, such as low battery power or changes in topology. For these
|
|
scenarios, this API can be used to change the configuration locally.
|
|
|
|
API reference
|
|
*************
|
|
|
|
.. doxygengroup:: bt_mesh_cfg
|