Lines Matching full:node
53 This option determines for how long the local node advertises
54 using Node Identity. The given value is in seconds. The
63 node supports.
119 based on what kind of features the local node shoule have. E.g.
134 In order to fulfil the above requirement, even if the node might
136 how many hours the node has been in the state. This doesn't
139 ways that the node will be used and what kind of power source it
145 duration that the node has been in the current state gets
176 models the local node supports, i.e. what's the largest
177 message payload that the node needs to be able to send.
196 Support for acting as a Mesh Relay Node.
201 Enable this option to be able to act as a Low Power Node.
208 is that the node may miss out on messages intended for it
210 node.
218 node.
223 Time in seconds from the last received message, that the node
235 The contribution of the RSSI measured by the Friend node used
249 the Friend node can store in its Friend Queue. As an example,
255 The ReceiveDelay is the time between the Low Power node
257 allows the Friend node time to prepare the response. The value
264 consecutive requests sent by the Low Power node. If no
265 requests are received by the Friend node before the
294 Enable this option to be able to act as a Friend Node.
299 Receive Window in milliseconds supported by the Friend node.
311 Friend node for a Low Power node.
489 100th increment. If the node sends messages very frequently a
490 higher value makes more sense, whereas if the node sends
501 persistent storage after a change occurs. If the node receives
505 if the node operates a security sensitive use case, and there's
508 writing to storage exposes the node to potential message
514 This value defines BLE Mesh device/node name.
515 value: '"nimble-mesh-node"'