Lines Matching refs:commands

6 The Bluetooth Mesh shell subsystem provides a set of Bluetooth Mesh shell commands for the
30 sub-commands. Every time the device boots up, make sure to call ``mesh init`` before any of the
31 other Bluetooth Mesh shell commands can be called::
55 general configuration commands:
69 :ref:`bluetooth_mesh_shell_cfg_cli` commands.
106 	local unicast address before issuing any configuration commands.
118 The Bluetooth Mesh shell commands are parsed with a variety of formats:
142 The Bluetooth Mesh shell implements a large set of commands. Some of the commands accept parameters,
147 The Bluetooth Mesh shell commands are divided into the following groups:
154 	Some commands depend on specific features being enabled in the compile time configuration of
156 	mesh shell commands can be shown in the shell by calling ``mesh`` without any arguments.
175 The target commands enables the user to monitor and set the target destination address, network
176 index and application index for the shell. These parameters are used by several commands, like
511 an example of how you can set up a device to start using the Configuration Client commands:
518 * Configure the local node as desired with the Configuration Client commands.
524 * Configure the node as desired with the Configuration Client commands.
947 using the Health Client commands. To choose a specific Health Client instance the user can utilize
948 the commands ``mesh models health instance set`` and ``mesh models health instance get-all``.
1128 	BLOB Transfer Client model commands.
1164 	BLOB Transfer Server model commands.
1209 	the slot in other commands. To update the image slot, remove it using the
1323 	Firmware Update Client model commands.
1368 	Firmware Update Server model commands.
1383 The Firmware Distribution Server model commands can be added to the mesh shell by enabling the
1384 :kconfig:option:`CONFIG_BT_MESH_DFD_SRV` configuration option. The shell commands for this model
1386 commands, a Firmware Distribution Server must be instantiated by the application.
1481 	other Firmware Distribution Server model commands.
1496 The DFU metadata shell commands allow generating metadata that can be used by a Target node to
1497 check the firmware before accepting it. The commands are enabled through the
1679 	aggregating messages and sets the destination address for next shell commands to
1778 	other Remote Provisioning Client model commands.