Lines Matching refs:models

8 into elements and models, which are implemented by the application.
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
20 element instantiating all the models required for a single aspect of the
25 Bluetooth SIG have defined a set of foundation models (see
26 :ref:`bluetooth_mesh_models`) and a set of models for implementing common
28 <https://www.bluetooth.com/specifications/mesh-specifications/>`_. All models
29 not specified by the Bluetooth SIG are vendor models, and must be tied to a
32 Mesh models have several parameters that can be configured either through
80 The models may send messages in two ways:
105 on every retransmission. This can, for example, be used by models that make
113 Extended models  argument
116 The Bluetooth Mesh specification allows the mesh models to extend each other.
118 extension can be used to construct complex models out of simple ones,
120 Models may extend any number of models, from any element. When one model
121 extends another in the same element, the two models will share subscription
123 two models into one, combining the number of subscriptions the models can have
124 in total. Models may extend models that extend others, creating an "extension
125 tree". All models in an extension tree share a single subscription list per
131 relationships between the models must be defined by the model implementations.
140 Mesh models may have data associated with each model instance that needs to be  argument
173 device, the models that it supports, and other features. The Composition
189 Composition Data Page 1 provides information about the relationships between models,
191 or more models. A model can extend another model by calling :c:func:`bt_mesh_model_extend`,