Lines Matching refs:to
15 Enable this option to allow using random advertising interval
29 Enable this option to allow using specific duplicate scan filter
38 Allocation strategy for BLE Mesh stack, essentially provides ability to
67 Enable this option to use the default memory allocation strategy when
74 Allows to use IRAM memory region as 8bit accessible region. Every
85 Enable this option to use FreeRTOS static allocation APIs for BLE Mesh,
86 which provides the ability to use different dynamic memory (i.e. SPIRAM
95 Choose the memory to be used for FreeRTOS objects.
120 If enabled, users can use the function esp_ble_mesh_deinit() to de-initialize
159 Enable this option to allow BLE Mesh fast provisioning solution to be used.
163 into a node successfully, it can be changed to a temporary Provisioner.
168 Enable the device to be provisioned into a node. This option should be
169 enabled when an unprovisioned device is going to be provisioned into a
175 Enable the device to be a Provisioner. The option should be enabled when
176 a device is going to act as a Provisioner and provision unprovisioned
182 int "Maximum number of unprovisioned devices that can be added to device queue"
186 This option specifies how many unprovisioned devices can be added to device
187 queue for provisioning. Users can use this option to define the size of the
188 queue in the bottom layer which is used to store unprovisioned device
199 Provisioner can provision up to 6 unprovisioned devices.
201 up to 32766 unprovisioned devices, here we limit the maximum number to 100
202 just to limit the memory used by a Provisioner. The bigger the value is, the
203 more memory it will cost by a Provisioner to store the information of nodes.
249 When this option is enabled, Provisioner can call specific functions to enable
250 or disable receiving Heartbeat messages and notify them to the application layer.
260 The heartbeat filter (acceptlist or rejectlist) entries are used to store a
261 list of SRC and DST which can be used to decide if a heartbeat message will
262 be processed and notified to the application layer by Provisioner.
274 Enable this option to support BLE Mesh Provisioning functionality. For
282 Enable this option to allow the device to be provisioned over the
284 going to be used during provisioning procedure.
294 device beacon, users can use this option to change the frequency of sending
297 BLE_MESH_FAST_PROV is selected, the value is better to be 3 seconds, or less.
304 Enable this option to allow the device to be provisioned over GATT.
305 This option should be enabled if PB-GATT is going to be used during
313 Enable this option to support BLE Mesh Proxy protocol used by PB-GATT
323 ability to act as a proxy between a Mesh GATT Client and a Mesh network.
324 This option should be enabled if a node is going to be a Proxy Server.
334 this to 60 seconds and lists it as the recommended value as well.
337 node, it will start to advertise using Node Identity during the time
347 The entries of Proxy filter (whitelist or blacklist) are used to store a
348 list of addresses which can be used to decide which messages will be forwarded
349 to the Proxy Client by the Proxy Server.
357 can use the GATT bearer to send mesh messages to a node that supports the
364 Enable BLE Mesh net buffer pool tracking. This option is used to introduce another
365 variable in the bottom layer to record the usage of advertising buffers of BLE Mesh
366 devices. Recommend to enable this option as default.
390 The option allows nodes to delay a certain period of time to save proper
391 information to flash. The default value is 0, which means information
401 sequence number will be stored to flash on every 100th increment.
405 gets initialized it will add sequence number to the last stored one,
406 so that it starts off with a value that's guaranteed to be larger than
415 gets written to persistent storage after a change occurs. If the node
430 This option is created to solve the issue of failure in recovering
434 information needs to check "mesh/role" key in nvs and implements
443 If users are updating their nodes from old version to new version,
456 When Provisioner needs to store a large amount of nodes' information in the
457 flash (e.g. more than 20), this option is recommended to be enabled.
472 When selected, Provisioner can use different NVS namespaces to store
476 mesh information instance A. When the Provisioner moves to the second
480 With this option enabled, Provisioner needs to use specific functions
481 to open the corresponding NVS namespace, restore the mesh information,
515 This option specifies the maximum number of application keys to which each model
523 This option specifies the maximum number of addresses to which each model can
540 It is similar to Network message cache size, but has a different purpose.
541 The replay protection list is used to prevent a node from replay attack,
547 Provisioner can provision up to 20 nodes and each node contains two elements,
557 Enable this option will refuse to relay such messages, which could help to
561 Therefore, users need to decide whether to enable this option according to
571 is similar to Replay protection list, but has a different purpose.
572 A node is not required to cache the entire Network PDU and may cache
593 in Progress, we need to keep track of how many hours has passed
594 in the state, since the specification requires us to remain in
598 In order to fulfill the above requirement, even if the node might
599 be powered off once in a while, we need to store persistently
601 necessarily need to happen every hour (thanks to the flexible
610 stored to flash. E.g. the default value of 4 means that the
617 According to Section 3.10.5 of Mesh Specification v1.0.1.
619 equal to the last known IV index+1 and the IV Update Flag set to 0, the node may
620 update its IV without going to the IV Update in Progress state, or it may initiate
625 When the above situation is encountered, this option can be used to decide whether
626 to perform the IV index recovery procedure.
635 message at a time. And if another segmented message is going to be sent, it
637 If users are going to send multiple segmented messages at the same time, this
647 message at a time. And if another segmented message is going to be received,
649 If users are going to receive multiple segmented messages at the same time, this
657 Maximum incoming Upper Transport Access PDU length. Leave this to the default
658 value, unless you really need to optimize memory usage.
668 message payload that the node needs to be able to send.
679 Be sure to specify a sufficient number of advertising buffers
680 when setting this option to a higher value. There must be at
690 a node to support the Relay feature, and the Relay feature can still
720 Enable this option to operate as a Low Power Node. If low power consumption
722 enters the mesh network, it will try to find a Friend node and establish a
736 time after a Friend Request or Friend Poll is sent, so as to reduce more
744 for Friend nodes. If this option is disabled LPN mode needs to be manually
747 enabling this option will trigger the node starts to send Friend Request at
751 int "Time from last received message before going to LPN mode"
757 before starting to look for Friend nodes.
775 node, which is used to calculate the Friend Offer Delay.
785 Low Power node, which is used to calculate the Friend Offer Delay.
804 node time to prepare the response. The value is in units of milliseconds.
811 PollTimeout timer is used to measure time between two consecutive
816 The smaller the value, the faster the Low Power node tries to get
824 The initial value of the PollTimeout timer when Friendship is to be
835 Latency (in milliseconds) is the time it takes to enable scanning. In
837 request to enable scanning is made.
840 int "Number of groups the LPN can subscribe to"
844 Maximum number of groups to which the LPN can subscribe.
858 Enable this option to be able to act as a Friend Node.
874 Minimum number of buffers available to be stored for each local Friend Queue.
876 to store messages for each Low Power node.
885 Friend Subscription List Remove messages to the Friend node to add or remove
914 Select this to save the BLE Mesh related rodata code size. Enabling this option
996 Timeout value used by the node to get response of the acknowledged
1141 lets the state to be changed at any time.
1142 If IV Update test mode is going to be used, this option should be enabled.
1148 This option is used to decide whether discarding the old SeqAuth when
1164 This option is used to enable some internal functions for auto-pts test.
1171 This option is used to enable the log of auto-pts test.
1182 needs to be invoked to add the node information into the mesh stack.
1185 bool "Use white list to filter mesh advertising packets"
1188 With this option enabled, users can use white list to filter mesh
1197 Activate shell module that provides BLE Mesh commands to the console.