1.. _bluetooth_mesh_models_op_agg_cli:
2
3Opcodes Aggregator Client
4#########################
5
6The Opcodes Aggregator Client model is a foundation model defined by the Bluetooth Mesh
7specification. It is an optional model, enabled with the :kconfig:option:`CONFIG_BT_MESH_OP_AGG_CLI`
8option.
9
10The Opcodes Aggregator Client model is introduced in the Bluetooth Mesh Protocol Specification
11version 1.1, and is used to support the functionality of dispatching a sequence of access layer
12messages to nodes supporting the :ref:`bluetooth_mesh_models_op_agg_srv` model.
13
14The Opcodes Aggregator Client model communicates with an Opcodes Aggregator Server model using the
15device key of the target node or the application keys configured by the Configuration Client.
16
17If present, the Opcodes Aggregator Client model must only be instantiated on the primary element.
18
19The Opcodes Aggregator Client model is implicitly bound to the device key on initialization. It
20should be bound to the same application keys as the client models that are used to produce the
21sequence of messages.
22
23To be able to aggregate a message from a client model, it should support an asynchronous API, for
24example through callbacks.
25
26API reference
27*************
28
29.. doxygengroup:: bt_mesh_op_agg_cli
30