btc_ble_mesh_rpr_client_prov_comp_cb() function

Send an Access Layer message.

Send a model publication message. Before calling this function, the user needs to ensure that the model publication message (bt_mesh_model_pub .msg) contains a valid message to be sent. Note that this API is only to be used for non-period publishing. For periodic publishing the app only needs to make sure that bt_mesh_model_pub .msg contains a valid message whenever the bt_mesh_model_pub .update callback is called.

Get the element that a model belongs to.

Get whether the model is in the primary element of the device.

Check if the msg received by client model is a publish msg or not

Get whether the model is in the primary element of the device.

When an Element receives a Health Fault Get, or a Health Fault Test, or a Health Fault Test Unacknowledged, or a Health Fault Clear, or a Health Fault Clear Unacknowledged message that is not successfully processed (i.e. the Company ID field that does not identify any Health Fault state present in the node), it shall ignore the message. The Health Fault state is identified by Company ID and may be present in the node for more than one Company ID.

Check if model is extended by another model.

Immediately store the model's user data in persistent storage.

Let a model extend another. Mesh models may be extended to reuse their functionality, forming a more complex model. A Mesh model may extend any number of models, in any element. The extensions may also be nested, ie a model that extends another may itself be extended. A set of models that extend each other form a model extension list. All models in an extension list share one subscription list per element. The access layer will utilize the combined subscription list of all models in an extension list and element, giving the models extended subscription list capacity.