Yaa that BLE saving in memory can be confusing when someone starts to develop BLE mesh xd

Because, as it is explained in the documentation, you can obtain faster software when hardware helps in processing.

Hi Serdar,

I would like to learn whether this issue is still actual.
If so, please extend the code with logging of the str variable content prior to the call of nvs functions and result code returned by each of the nvs functions called. Please post the values log. Please include also content of ...

Ah it was not that terribly hard. :) Quite crucial to working it out was to learn about a requirement to clean the already saved network in the device before proceeding further.
And the node (not provisisoner) needed to call example_handle_config_app_key_add_evt function from the example's code ...

- yes, it should be possible to switch between provisioner and node, as you can run both, provisioner and node, in the same time


So you say, that it sould be possible to run both a provisioner and a node in the same time.
Well I have started with the fast provisioning BLE Mesh example from the ...

I suppose you want an UART event.
Try this example: examples\peripherals\uart\uart_events

Ah, ok so you are talking about the ones that have size unit16_t.
Thanks

Well no wonder - since esp_ble_mesh_start_ble_scanning is not using its argument... :/
(though I would prefer to have just an option to have this done indefinietly long)
Am I right that in order to receive BLE mesh advertising packets I need to have BLE coexistence set?

There is a search feature in the Sdkconfig

Eee CONFIG_ESP_CONSOLE_UART and CONFIG_ESP_CONSOLE_UART_NUM?