1.. _bluetooth_mesh_models_rpr_srv:
2
3Remote Provisioning Server
4##########################
5
6The Remote Provisioning Server model is a foundation model defined by the Bluetooth
7mesh specification. It is enabled with the
8:kconfig:option:`CONFIG_BT_MESH_RPR_SRV` option.
9
10The Remote Provisioning Server model is introduced in the Bluetooth Mesh Protocol
11Specification version 1.1, and is used to support the functionality of remotely
12provisioning devices into a mesh network.
13
14The Remote Provisioning Server does not have an API of its own, but relies on a
15:ref:`bluetooth_mesh_models_rpr_cli` to control it. The Remote Provisioning Server
16model only accepts messages encrypted with the node's device key.
17
18If present, the Remote Provisioning Server model must be instantiated on the primary element.
19
20Note that after refreshing the device key, node address or Composition Data through a Node
21Provisioning Protocol Interface (NPPI) procedure, the :c:member:`bt_mesh_prov.reprovisioned`
22callback is triggered. See section :ref:`bluetooth_mesh_models_rpr_cli` for further details.
23
24Limitations
25-----------
26
27The following limitations apply to Remote Provisioning Server model:
28
29* Provisioning of unprovisioned device using PB-GATT is not supported.
30* All Node Provisioning Protocol Interface (NPPI) procedures are supported. However, if the composition data of a device gets changed after device firmware update (see :ref:`firmware effect <bluetooth_mesh_dfu_firmware_effect>`), it is not possible for the device to remain provisioned. The device should be unprovisioned if its composition data is expected to change.
31
32
33API reference
34*************
35
36.. doxygengroup:: bt_mesh_rpr_srv
37