Home
last modified time | relevance | path

Searched refs:composition (Results 1 – 8 of 8) sorted by relevance

/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Drpr_srv.rst30 …composition data of a device gets changed after device firmware update (see :ref:`firmware effect …
Ddfu.rst157 | composition data | (Optional) | (app-specific-key, composition data). |
206 composition data of the new firmware doesn't change.
208 This effect is chosen when the composition data changes and the device doesn't support the remote
209 provisioning. The new composition data takes place only after re-provisioning.
211 This effect is chosen when the composition data changes and the device supports the remote
212 provisioning. In this case, the device stays provisioned and the new composition data takes place
215 This effect is chosen if the composition data in the new firmware changes, the device doesn't
216 support the remote provisioning, and the new composition data takes effect after applying the
Daccess.rst23 The node's element and model structure is specified in the node composition
44 The full opcode list must be passed to the model structure in the composition
183 is mandatory for all mesh devices. It contains the element and model composition,
194 relations can be stored in the composition on a device, and this number should reflect the
Dshell.rst16 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
[all …]
/Zephyr-latest/boards/raspberrypi/rpi_pico2/
Drpi_pico2_rp2350a_m33.dts11 * This file provides composition of the device tree:
/Zephyr-latest/samples/bluetooth/mesh_provisioner/
DREADME.rst29 the composition data, and binding all its models to the application key.
/Zephyr-latest/subsys/bluetooth/mesh/shell/
DKconfig59 to the device composition data. Use BT_MESH_SHELL_HEALTH_PUB_DEFINE to
/Zephyr-latest/doc/project/
Dproject_roles.rst235 composition (ensure, for example, that team members are