Searched full:mesh (Results 1 – 25 of 353) sorted by relevance
12345678910>>...15
| /Zephyr-Core-3.6.0/include/zephyr/bluetooth/ |
| D | mesh.h | 2 * @brief Bluetooth Mesh Profile APIs.
18 #include <zephyr/bluetooth/mesh/keys.h>
19 #include <zephyr/bluetooth/mesh/msg.h>
20 #include <zephyr/bluetooth/mesh/access.h>
21 #include <zephyr/bluetooth/mesh/main.h>
22 #include <zephyr/bluetooth/mesh/cfg.h>
23 #include <zephyr/bluetooth/mesh/cfg_srv.h>
24 #include <zephyr/bluetooth/mesh/health_srv.h>
25 #include <zephyr/bluetooth/mesh/blob_srv.h>
26 #include <zephyr/bluetooth/mesh/cfg_cli.h>
[all …]
|
| /Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/ |
| D | mesh.rst | 3 Bluetooth Mesh Profile
6 The Bluetooth Mesh profile adds secure wireless multi-hop communication for
8 `Bluetooth Mesh Protocol Specification v1.1 <https://www.bluetooth.com/specifications/specs/mesh-pr…
10 Read more about Bluetooth Mesh on the
11 `Bluetooth SIG Website <https://www.bluetooth.com/bluetooth-resources/?tags=mesh>`_.
16 mesh/core.rst
17 mesh/access.rst
18 mesh/models.rst
19 mesh/msg.rst
20 mesh/sar_cfg.rst
[all …]
|
| /Zephyr-Core-3.6.0/tests/bluetooth/mesh/basic/ |
| D | testcase.yaml | 2 bluetooth.mesh.main:
11 - mesh
12 bluetooth.mesh.dbg:
22 - mesh
23 bluetooth.mesh.friend:
33 - mesh
34 bluetooth.mesh.gatt:
44 - mesh
45 bluetooth.mesh.lpn:
55 - mesh
[all …]
|
| /Zephyr-Core-3.6.0/tests/bsim/bluetooth/mesh/ |
| D | compile.sh | 20 app=tests/bsim/bluetooth/mesh compile
21 app=tests/bsim/bluetooth/mesh conf_overlay=overlay_pst.conf compile
22 app=tests/bsim/bluetooth/mesh conf_overlay=overlay_gatt.conf compile
23 app=tests/bsim/bluetooth/mesh conf_overlay=overlay_low_lat.conf compile
24 app=tests/bsim/bluetooth/mesh conf_overlay=overlay_psa.conf compile
25 app=tests/bsim/bluetooth/mesh conf_overlay="overlay_pst.conf;overlay_psa.conf" compile
26 app=tests/bsim/bluetooth/mesh conf_overlay="overlay_gatt.conf;overlay_psa.conf" compile
27 app=tests/bsim/bluetooth/mesh conf_overlay="overlay_low_lat.conf;overlay_psa.conf" compile
28 app=tests/bsim/bluetooth/mesh conf_overlay="overlay_gatt.conf;overlay_low_lat.conf" compile
29 app=tests/bsim/bluetooth/mesh conf_overlay="overlay_pst.conf;overlay_gatt.conf" compile
[all …]
|
| D | README.rst | 1 Bluetooth Mesh BabbleSim tests
4 This directory contains a set of high level system tests for the Bluetooth Mesh
10 mesh subsystem, and each folder has a corresponding test_<subfolder>.c under the
13 There's only a single test application for all the Bluetooth Mesh BabbleSim
21 The Bluetooth Mesh tests have no extra requirements, and can be run using the
24 To only run the mesh tests, set ``SEARCH_PATH`` to point to this folder before
60 The Bluetooth Mesh BabbleSim tests mainly operate on the test framework for the
61 BabbleSim platform, but with some mesh specific additions:
66 All test scripts in the Bluetooth Mesh BabbleSim test suite follow a common
75 ``RunTest`` starts one mesh application for each selected harness, before
[all …]
|
| /Zephyr-Core-3.6.0/samples/boards/nrf/mesh/onoff_level_lighting_vnd_app/ |
| D | CMakeLists.txt | 13 src/mesh/ble_mesh.c
14 src/mesh/device_composition.c
15 src/mesh/no_transition_work_handler.c
16 src/mesh/publisher.c
17 src/mesh/state_binding.c
18 src/mesh/transition.c
23 src/mesh
|
| D | README.rst | 1 .. _bluetooth-mesh-onoff-level-lighting-vnd-sample:
3 Bluetooth: Mesh Generic OnOff, Generic Level, Lighting & Vendor Models
7 This is a application demonstrating a Bluetooth Mesh node in
48 States of Servers are bounded as per Bluetooth SIG Mesh Model Specification v1.0
62 This sample can be found under :zephyr_file:`samples/boards/nrf/mesh/onoff_level_lighting_vnd_app` …
68 :zephyr-app: samples/boards/nrf/mesh/onoff_level_lighting_vnd_app
97 the mesh configuration. As additional nodes (boards) are provisioned, it
112 This application was derived from the sample mesh skeleton at
113 :zephyr_file:`samples/bluetooth/mesh`.
|
| /Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/mesh/ |
| D | shell.rst | 3 Bluetooth Mesh Shell
6 The Bluetooth Mesh shell subsystem provides a set of Bluetooth Mesh shell commands for the
7 :ref:`shell_api` module. It allows for testing and exploring the Bluetooth Mesh API through an
10 The Bluetooth Mesh shell interface provides access to most Bluetooth Mesh features, including
16 The Bluetooth Mesh shell subsystem depends on the application to create the composition data and do
17 the mesh initialization.
22 The Bluetooth Mesh shell subsystem is most easily used through the Bluetooth Mesh shell application
24 interact with the Bluetooth Mesh shell application.
29 The Bluetooth Mesh shell subsystem adds a single ``mesh`` command, which holds a set of
30 sub-commands. Every time the device boots up, make sure to call ``mesh init`` before any of the
[all …]
|
| D | priv_beacon_srv.rst | 7 mesh specification. It is enabled with
10 The Private Beacon Server model is introduced in the Bluetooth Mesh Protocol
11 Specification version 1.1, and controls the mesh node's Private Beacon state,
14 The Private Beacons feature adds privacy to the different Bluetooth Mesh
16 mesh node from being tracked by devices outside the mesh network, and hides the
27 :c:macro:`BT_MESH_MODEL_PRIV_BEACON_SRV`. Note that if the mesh node stored
|
| D | models.rst | 3 Mesh models
9 The Bluetooth Mesh specification defines foundation models that can be
10 used by network administrators to configure and diagnose mesh nodes.
37 In addition to the foundation models defined in the Bluetooth Mesh specification, the Bluetooth Mesh
|
| D | priv_beacon_cli.rst | 7 mesh specification. It is enabled with the
10 The Private Beacon Client model is introduced in the Bluetooth Mesh Protocol
14 The Private Beacons feature adds privacy to the different Bluetooth Mesh
16 mesh node from being tracked by devices outside the mesh network, and hides the
|
| D | access.rst | 6 The access layer is the application's interface to the Bluetooth Mesh network.
10 Mesh models
13 The functionality of a mesh node is represented by models. A model implements
15 thermostat. The mesh models are grouped into *elements*. Each element is
17 model. Conventionally, each element represents a single aspect of the mesh
27 behavior in the `Bluetooth Mesh Model Specification
28 <https://www.bluetooth.com/specifications/mesh-specifications/>`_. All models
32 Mesh models have several parameters that can be configured either through
33 initialization of the mesh stack or with the
70 multiple nodes throughout the mesh network with a single message.
[all …]
|
| D | core.rst | 6 The core provides functionality for managing the general Bluetooth Mesh
15 a mesh network as a leaf node. An LPN interacts with the mesh network through
20 The radio control and polling is managed automatically by the mesh stack, but
36 numbers from elements within the mesh network to perform protection against
41 the amount of traffic in a mesh network, storing recently seen sequence numbers
75 The mesh stack uses the :ref:`Settings Subsystem <settings_api>` for storing the
118 All mesh stack bearers advertise data with the :c:macro:`BT_ID_DEFAULT` local identity.
119 The value is preset in the mesh stack implementation. When Bluetooth® Low Energy (LE)
120 and Bluetooth Mesh coexist on the same device, the application should allocate and
|
| /Zephyr-Core-3.6.0/tests/bsim/bluetooth/mesh/tests_scripts/suspend/ |
| D | suspend_resume.sh | 7 # Test that periodic publication is stopped when suspending Mesh, and that it
8 # is started again when Mesh is resumed. The test will fail under two
9 # conditions; if no publication is received while Mesh is enabled,
10 # or if a publication is received while Mesh is suspended.
15 # 2. Suspend Mesh, checking that publication stops.
16 # 3. Resume Mesh a specified time after suspension. Check that publication resumes.
|
| D | suspend_disable_resume.sh | 7 # Test that periodic publication is stopped when suspending Mesh and disabling
8 # Bluetooth, and that it is started again when Bluetooth is re-enabled and Mesh is resumed.
10 # Mesh is enabled, or if a publication is received while Mesh is suspended.
15 # 2. Suspend Mesh and disable Bluetooth, checking that publication stops.
16 # 3. Enable Bluetooth and resume Mesh a specified time after suspension.
|
| /Zephyr-Core-3.6.0/include/zephyr/bluetooth/mesh/ |
| D | sar_cfg_srv.h | 8 * @brief Bluetooth Mesh SAR Configuration Server Model APIs.
13 #include <zephyr/bluetooth/mesh.h>
14 #include <zephyr/bluetooth/mesh/sar_cfg.h>
17 * @brief Bluetooth Mesh
18 * @defgroup bt_mesh_sar_cfg_srv Bluetooth Mesh SAR Configuration Server Model
|
| D | statistic.h | 2 * @brief BLE mesh statistic APIs.
27 /** The structure that keeps statistics of mesh frames handling. */
52 /** @brief Get mesh frame handling statistic.
54 * @param st BLE mesh statistic.
58 /** @brief Reset mesh frame handling statistic.
|
| /Zephyr-Core-3.6.0/samples/bluetooth/mesh/ |
| D | README.rst | 3 Bluetooth: Mesh
9 This sample demonstrates Bluetooth Mesh functionality. It has several
10 standard mesh models, and supports provisioning over both the
16 controlling the first LED on the board over the mesh.
30 This sample can be found under :zephyr_file:`samples/bluetooth/mesh` in the
39 :zephyr-app: samples/bluetooth/mesh
51 to enable mesh support.
56 The sample can either be provisioned into an existing mesh network with an
|
| /Zephyr-Core-3.6.0/samples/boards/nrf/mesh/onoff-app/ |
| D | README.rst | 1 .. _bluetooth-mesh-onoff-sample:
3 Bluetooth: Mesh OnOff Model
9 This is a simple application demonstrating a Bluetooth Mesh multi-element node.
10 Each element has a mesh onoff client and server
16 corresponding LED and does not initiate any mesh activity.
46 This sample can be found under :zephyr_file:`samples/boards/nrf/mesh/onoff-app` in the
52 :zephyr-app: samples/boards/nrf/mesh/onoff-app
77 the mesh configuration. As additional nodes (boards) are provisioned, it
96 This application was derived from the sample mesh skeleton at
97 :zephyr_file:`samples/bluetooth/mesh`.
|
| /Zephyr-Core-3.6.0/subsys/bluetooth/mesh/shell/ |
| D | Kconfig | 1 # Bluetooth Mesh shell configuration options
7 bool "Bluetooth Mesh shell"
10 Activate shell module that provides Bluetooth Mesh commands to
27 Bluetooth Mesh shell module together with several provisioning
30 initialization of mesh.
50 This option enables support for test mesh shell commands.
57 Bluetooth Mesh shell module together with fault controlling
|
| /Zephyr-Core-3.6.0/tests/bsim/bluetooth/mesh/src/ |
| D | gatt_common.c | 22 /* mesh provisioning service */ in bt_mesh_test_parse_mesh_pb_gatt_service()
25 /* mesh provisioning service */ in bt_mesh_test_parse_mesh_pb_gatt_service()
32 /* mesh proxy service */ in bt_mesh_test_parse_mesh_proxy_service()
35 /* mesh proxy service */ in bt_mesh_test_parse_mesh_proxy_service()
|
| /Zephyr-Core-3.6.0/tests/bluetooth/mesh_shell/src/ |
| D | main.c | 14 #include <zephyr/bluetooth/mesh.h>
15 #include <zephyr/bluetooth/mesh/shell.h>
131 printk("Initializing mesh failed (err %d)\n", err); in bt_ready()
139 printk("Mesh initialized\n"); in bt_ready()
142 printk("Mesh network restored from flash\n"); in bt_ready()
162 printk("Before any Mesh commands you must run \"mesh init\"\n"); in main()
|
| /Zephyr-Core-3.6.0/subsys/bluetooth/mesh/ |
| D | access.h | 82 /** @brief Register a callback function hook for mesh model messages.
84 * Register a callback function to act as a hook for receiving mesh model layer messages
92 /** @brief Send a mesh model message.
94 * Send a mesh model layer message out into the mesh network without having instantiated
95 * the relevant mesh models.
97 * @param ctx The Bluetooth Mesh message context.
|
| /Zephyr-Core-3.6.0/samples/boards/reel_board/mesh_badge/ |
| D | README.rst | 3 Mesh Badge
9 This sample app for the reel board showcases Bluetooth Mesh
37 #. Once disconnected the board switches over to Bluetooth Mesh mode, and you
41 each other over mesh: by pressing the user button on the board the first
45 To reset a board to its initial state (disable mesh, erase the stored
|
| /Zephyr-Core-3.6.0/tests/bsim/bluetooth/mesh/tests_scripts/provision/ |
| D | pb_remote_timeout.sh | 15 # 3. 3rd device enables Mesh and starts advertising unprovisioned device beacons.
16 # 4. 3rd device disables Mesh scan while still advertising. Mesh stack remains active.
22 # 9. 3rd device enables Mesh scan again and becomes responsive.
|
12345678910>>...15
