Searched full:mesh (Results 1 – 25 of 209) sorted by relevance
123456789
| /Zephyr-Core-2.7.6/tests/bluetooth/mesh/ |
| D | testcase.yaml | 2 bluetooth.mesh.main:
5 tags: bluetooth mesh
6 bluetooth.mesh.dbg:
10 tags: bluetooth mesh
11 bluetooth.mesh.friend:
15 tags: bluetooth mesh
16 bluetooth.mesh.gatt:
20 tags: bluetooth mesh
21 bluetooth.mesh.lpn:
25 tags: bluetooth mesh
[all …]
|
| /Zephyr-Core-2.7.6/doc/reference/bluetooth/ |
| D | mesh.rst | 3 Bluetooth Mesh Profile
6 The Bluetooth mesh profile adds secure wireless multi-hop communication for
8 `Bluetooth Mesh Profile Specification v1.0.1 <https://www.bluetooth.com/specifications/mesh-specifi…
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/provisioning.rst
[all …]
|
| /Zephyr-Core-2.7.6/include/bluetooth/ |
| D | mesh.h | 2 * @brief Bluetooth mesh Profile APIs.
17 #include <bluetooth/mesh/msg.h>
18 #include <bluetooth/mesh/access.h>
19 #include <bluetooth/mesh/main.h>
20 #include <bluetooth/mesh/cfg.h>
21 #include <bluetooth/mesh/cfg_srv.h>
22 #include <bluetooth/mesh/health_srv.h>
23 #include <bluetooth/mesh/cfg_cli.h>
24 #include <bluetooth/mesh/health_cli.h>
25 #include <bluetooth/mesh/proxy.h>
[all …]
|
| /Zephyr-Core-2.7.6/doc/reference/bluetooth/mesh/ |
| D | shell.rst | 3 Bluetooth Mesh Shell
6 The Bluetooth mesh shell subsystem provides a set of Bluetooth mesh shell commands for the :ref:`sh…
7 It allows for testing and exploring the Bluetooth mesh API through an interactive interface, withou…
9 The Bluetooth mesh shell interface provides access to most Bluetooth mesh features, including provi…
14 The Bluetooth mesh shell subsystem depends on the :ref:`bluetooth_mesh_models_cfg_cli` and :ref:`bl…
19 The Bluetooth mesh shell subsystem is most easily used through the Bluetooth mesh shell application…
20 See :ref:`shell_api` for information on how to connect and interact with the Bluetooth mesh shell a…
25 …mesh shell subsystem adds a single ``mesh`` command, which holds a set of sub-commands. Every time…
27 uart:~$ mesh init
32 The mesh node must be provisioned to become part of the network. This is only necessary the first t…
[all …]
|
| 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
13 a mesh network as a leaf node. An LPN interacts with the mesh network through
18 The radio control and polling is managed automatically by the mesh stack, but
28 numbers from elements within the mesh network to perform protection against
33 the amount of traffic in a mesh network, storing recently seen sequence numbers
|
| D | cfg.rst | 9 Bluetooth mesh nodes should generally be configured by a central network
11 mesh node instantiates a :ref:`bluetooth_mesh_models_cfg_srv` model that the
13 cases, the mesh node can't rely on the Configuration Client to detect or determine
|
| D | provisioning.rst | 6 Provisioning is the process of adding devices to a mesh network. It requires
10 adding new nodes to the mesh network.
15 The Provisioning module in the Zephyr Bluetooth mesh stack supports both the
22 All Bluetooth mesh nodes must be provisioned before they can participate in a
23 Bluetooth mesh network. The Provisioning API provides all the functionality
24 necessary for a device to become a provisioned mesh node.
93 provide public and private keys to the mesh stack. The unprovisioned device
100 mechanism. In this case, a new key pair will be generated by the mesh stack
166 by the mesh stack, and the provisioning :c:member:`bt_mesh_prov.complete`
176 a set of vulnerabilities in the Bluetooth mesh provisioning protocol that showcased
[all …]
|
| D | cfg_srv.rst | 6 The Configuration Server model is a foundation model defined by the Bluetooth mesh
8 mesh node. It does not have an API of its own, but relies on a
17 The Configuration Server model is mandatory on all Bluetooth mesh nodes, and
|
| D | health_srv.rst | 8 faults in the mesh node and map the mesh nodes to their physical location.
22 Fault values ``0x01`` to ``0x7f`` are reserved for the Bluetooth mesh
58 Fault values defined by the Bluetooth mesh specification.
|
| /Zephyr-Core-2.7.6/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
25 src/mesh
|
| D | sample.yaml | 2 name: Bluetooth Mesh
4 sample.bluetooth.mesh.onoff_level_lighting_vnd:
8 sample.bluetooth.mesh.onoff_level_lighting_vnd.mcumgr:
|
| 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-2.7.6/tests/bluetooth/bsim_bt/bsim_test_mesh/ |
| 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-2.7.6/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
50 The sample can either be provisioned into an existing mesh network with an
|
| D | sample.yaml | 2 name: Bluetooth Mesh
4 sample.bluetooth.mesh:
|
| /Zephyr-Core-2.7.6/subsys/bluetooth/mesh/ |
| D | access.h | 57 /** @brief Register a callback function hook for mesh model messages.
59 * Register a callback function to act as a hook for recieving mesh model layer messages
67 /** @brief Send a mesh model message.
69 * Send a mesh model layer message out into the mesh network without having instantiated
70 * the relevant mesh models.
72 * @param ctx The Bluetooth mesh message context.
|
| D | Kconfig | 1 # Bluetooth mesh configuration options
7 bool "Bluetooth mesh support"
14 This option enables Bluetooth mesh support. The specific
29 Enable this option to allow the device to be provisioned into a mesh network.
70 bool "Mesh Configuration Database [EXPERIMENTAL]"
128 This option enables support for the Mesh GATT Proxy Service,
129 i.e. the ability to act as a proxy between a Mesh GATT Client
130 and a Mesh network.
176 instantiate Bluetooth mesh models.
182 mesh networking is initialized.
[all …]
|
| /Zephyr-Core-2.7.6/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`.
|
| D | sample.yaml | 2 name: Bluetooth Mesh
4 sample.bluetooth.mesh.onoff:
|
| /Zephyr-Core-2.7.6/doc/reference/networking/ |
| D | thread.rst | 12 Thread is a low-power mesh networking technology, designed specifically for home
15 a Thread mesh network to the internet with a Thread Border Router.
17 The Thread specification provides a high level of network security. Mesh networks
19 and all communications within the mesh are encrypted. More information about
29 A Thread Border Router is required to connect mesh network to the internet.
|
| /Zephyr-Core-2.7.6/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
|
| D | sample.yaml | 2 description: reel board mesh badge sample
3 name: mesh badge
|
| /Zephyr-Core-2.7.6/tests/bluetooth/bsim_bt/bsim_test_mesh/src/ |
| D | test_scanner.c | 8 #include "mesh/net.h"
9 #include "mesh/adv.h"
10 #include "mesh/mesh.h"
11 #include "mesh/foundation.h"
109 /** Test sending message with not supported ad type for mesh.
111 * First message send message with an ad data type not supported by mesh, and
171 /** Test receiving message with invalid ad type or packet length for mesh. */
|
| /Zephyr-Core-2.7.6/include/bluetooth/mesh/ |
| D | access.h | 15 #include <bluetooth/mesh/msg.h>
68 /** Helper to define a mesh element within an array.
86 /** Abstraction that describes a Mesh Element */
110 /* Models from the Mesh Model Specification */
287 * @return Mesh transmit value that can be used e.g. for the default
320 * @return Mesh transmit value that can be used e.g. for the default
433 /** @brief Callback called when the mesh is started.
436 * after all mesh data has been loaded from persistent storage.
438 * When this callback fires, the mesh model may start its behavior,
449 * Called on every model instance during mesh initialization.
[all …]
|
123456789
