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>
25 lines
870 B
ReStructuredText
25 lines
870 B
ReStructuredText
.. _bluetooth_mesh_models_cfg_srv:
|
|
|
|
Configuration Server
|
|
####################
|
|
|
|
Configuration Server model is a foundation model defined by the Bluetooth Mesh
|
|
specification. The Configuration Server model controls most parameters of the
|
|
mesh node. It does not have an API of its own, but relies on a
|
|
:ref:`bluetooth_mesh_models_cfg_cli` to control it.
|
|
|
|
..note::
|
|
The :c:struct:`bt_mesh_cfg_srv` structure has been deprecated. The initial
|
|
values of the Relay, Beacon, Friend, Network transmit and Relay retransmit
|
|
should be set through Kconfig, and the Heartbeat feature should be
|
|
controlled through the :ref:`bluetooth_mesh_heartbeat` API.
|
|
|
|
The Configuration Server model is mandatory on all Bluetooth Mesh nodes, and
|
|
should be instantiated in the first element.
|
|
|
|
API reference
|
|
*************
|
|
|
|
.. doxygengroup:: bt_mesh_cfg_srv
|
|
:project: Zephyr
|
|
:members:
|