ad2fd44d7a
Moves mesh feature configuration to a separate module, deprecating the bt_mesh_cfg_srv structure. The initial values for the features should now be enabled through KConfig, where new config entries have been added for each feature. This removes the upward dependency on the config server from the core stack, and makes the config server a pure frontend for the configuration states, as all spec mandated behavior around the feature states is now encapsulated. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
24 lines
852 B
ReStructuredText
24 lines
852 B
ReStructuredText
.. _bluetooth_mesh_cfg:
|
|
|
|
Runtime configuration
|
|
#####################
|
|
|
|
The Bluetooth Mesh 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
|
|
Config Client can communicate with to change the node configuration. In some
|
|
cases, the mesh node can't rely on the Config 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
|
|
:project: Zephyr
|
|
:members:
|