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?

This happens not only when you start WiFi, but also when you start Bluetooth Mesh with external JTAG (and I think the processor gets stuck) - in this case also until you change the console (or until you just wont use it).

espmpo wrote: ↑

Thu Nov 14, 2024 11:35 pm

Related to all of this: is there a way with VS Code to view the stack's contents short of dumping raw memory to the terminal?
Thanks, mpo

Isn't this possible in debuging?

CONFIG_ESP_INT_WDT or CONFIG_BOOTLOADER_WDT_TIME_MS?

This is a basic question - but somehow the answer does not seem to be easily found in documentation. How do we address nodes in ESP BLE Mesh? example_msg_common_info_t and esp_ble_mesh_msg_ctx_t expect that they are given uint16_t. But the addresses used in IDF have lengths of 6 == BLE_MESH_ADDR_LEN...

Ok it is not that hard to combine a node and a provisioner in single software. I mean from the fast provisioning example you can take all the files and simply run one or the other role (server or client) depending on a condition that is deciding if this particular device now should be a provisioner ...

Thank you for kind words, but i am not that "knowledgable" as you may think. I am just hard working with some topics, like ble, ble mesh or usb, and it takes me hundreds hours to learn stuff. Then, when i have some knowledge and i see other people struggling with problems like this, i am trying to ...