Lines Matching refs:composition
16 The Bluetooth Mesh shell subsystem depends on the application to create the composition data and do
71 A good first step is to read out the node's own composition data::
75 This prints a list of the composition data of the node, including a list of its model IDs.
112 opcode handler list to the composition data in ``subsys/bluetooth/mesh/shell.c``, and print the
498 enabled, and as long as the Configuration Client model is present in the model composition of the
517 * Monitor the composition data of the local node (``mesh models cfg get-comp``).
523 * Monitor the composition data of the target device (``mesh models cfg get-comp``).
552 Read a composition data page. The full composition data page will be printed. If the target
555 * ``Page``: The composition data page to request. Defaults to 0 if omitted.
942 as long as one or more Health Client model(s) is present in the model composition of the
946 By default, the module will choose the first Health Client instance in the model composition when
1503 Clear the stored composition data to be used for the Target node.
1554 …* ``Hash``: Hash of the composition data generated using ``mesh models dfu metadata comp-hash-get`…