1.. _bluetooth_mesh_sar_cfg_cli:
2
3SAR Configuration Client
4########################
5
6The SAR Configuration Client model is a foundation model defined by the Bluetooth mesh
7specification. It is an optional model, enabled with the
8:kconfig:option:`CONFIG_BT_MESH_SAR_CFG_CLI` configuration option.
9
10The SAR Configuration Client model is introduced in the Bluetooth Mesh Protocol Specification
11version 1.1, and it supports the configuration of the lower transport layer behavior of a node that
12supports the :ref:`bluetooth_mesh_sar_cfg_srv` model.
13
14The model can send messages to query or change the states supported by the SAR Configuration Server
15(SAR Transmitter and SAR Receiver) using SAR Configuration messages.
16
17The SAR Transmitter procedure is used to determine and configure the SAR Transmitter state of a SAR
18Configuration Server. Function calls :c:func:`bt_mesh_sar_cfg_cli_transmitter_get` and
19:c:func:`bt_mesh_sar_cfg_cli_transmitter_set` are used to get and set the SAR Transmitter state
20of the Target node respectively.
21
22The SAR Receiver procedure is used to determine and configure the SAR Receiver state of a SAR
23Configuration Server.  Function calls :c:func:`bt_mesh_sar_cfg_cli_receiver_get` and
24:c:func:`bt_mesh_sar_cfg_cli_receiver_set` are used to get and set the SAR Receiver state of the
25Target node respectively.
26
27For more information about the two states, see :ref:`bt_mesh_sar_cfg_states`.
28
29An element can send any SAR Configuration Client message at any time to query or change the states
30supported by the SAR Configuration Server model of a peer node.  The SAR Configuration Client model
31only accepts messages encrypted with the device key of the node supporting the SAR Configuration
32Server model.
33
34If present, the SAR Configuration Client model must only be instantiated on the primary element.
35
36API reference
37*************
38
39.. doxygengroup:: bt_mesh_sar_cfg_cli
40   :project: Zephyr
41   :members:
42