ESP BLE MESH Fast Provisioning

[koteswara]

I am using three ESP32 Modules to form a BLE Mesh Network and I have uploaded the following example code to all three ESP32 boards.

https://github.com/espressif/esp-idf/tr ... rov_server

Ultimate aim of this example is that mobile device will provision a node i.e one ESP32 and that node has to provision the other two nodes to the mesh network. I am able to provision only one node and that node is not provisioning other two devices . I followed the below steps :
1.Uploaded the all example code which is in URL to all ESP32's
2.In EspBLEMesh app I started provisioning and then filtered the available ESP32's by UUID "dddd"
3.I was able to find the all the three devices and selected one of them.
4.Before provisioning that node I selected fast provisioning and entered the Expect fast provisioning count as 3
5.My EspBleMesh application is connected and in fast provisioning application i am finding only one node which is connected and i am able to control that.

I Confirmed that connected node is not provisioning other devices by seeing the Blue LED. If the node has got provisioned then the blue light will turn off automatically. But the Blue light of other nodes are not offed as they are not provisioned .
How I have to solve this error ? Do I need to add any AppKey and NetKey to the EspBLEMesh application ?

[Wangcheng]

I am using three ESP32 Modules to form a BLE Mesh Network and I have uploaded the following example code to all three ESP32 boards.

https://github.com/espressif/esp-idf/tr ... rov_server

Ultimate aim of this example is that mobile device will provision a node i.e one ESP32 and that node has to provision the other two nodes to the mesh network. I am able to provision only one node and that node is not provisioning other two devices . I followed the below steps :
1.Uploaded the all example code which is in URL to all ESP32's
2.In EspBLEMesh app I started provisioning and then filtered the available ESP32's by UUID "dddd"
3.I was able to find the all the three devices and selected one of them.
4.Before provisioning that node I selected fast provisioning and entered the Expect fast provisioning count as 3
5.My EspBleMesh application is connected and in fast provisioning application i am finding only one node which is connected and i am able to control that.

I Confirmed that connected node is not provisioning other devices by seeing the Blue LED. If the node has got provisioned then the blue light will turn off automatically. But the Blue light of other nodes are not offed as they are not provisioned .
How I have to solve this error ? Do I need to add any AppKey and NetKey to the EspBLEMesh application ?

We will use the above code for testing. You'd better be able to add the log so that we can quickly locate the problem.

[koteswara]

These screenshots are from the device which has got provisioned by the mobile device by EspBleMesh Application.I am sharing the screenshot of other devices which are ready to provision .

[Wangcheng]

These screenshots are from the device which has got provisioned by the mobile device by EspBleMesh Application.I am sharing the screenshot of other devices which are ready to provision .

https://github.com/EspressifApp/EspBLEM ... d/releases

I use the master branch of github to try the basic function is normal, you should check the version of the app. The key operation steps are shown in the attached figure:

[koteswara]

Thank You .

Resolved by using the Updated EspBLEMesh Application

[koteswara]

After provisioning one node my mobile is disconnecting to the node and that provisioned is provisioning all other nodes. When provisioning of nodes in the network is completed, the first provisioned node is not connecting to the mobile . Thus I was not able to control the nodes.

[esp_liu]

After provisioning one node my mobile is disconnecting to the node and that provisioned is provisioning all other nodes. When provisioning of nodes in the network is completed, the first provisioned node is not connecting to the mobile . Thus I was not able to control the nodes.

Hi @koteswara

After all the nodes are provisioned, you need to choose the first provisioned node on the app and connect will it manually.

Thanks.

[Beibixian]

After provisioning one node my mobile is disconnecting to the node and that provisioned is provisioning all other nodes. When provisioning of nodes in the network is completed, the first provisioned node is not connecting to the mobile . Thus I was not able to control the nodes.

hello, I meet the same problem. However, upgrading the app didn't solve the problem. The app sucks here and the two other boards are not able to be provisioned.
My IDF is v4.0.1 and Development Kit: [ESP32-DevKitC]
Kit version (for DevKitC): [v1]
Module or chip used: [ESP32-WROOM-32]
can you give me some advice?

[mm_1993]

Hi
I run this example :
https://github.com/espressif/esp-idf/tr ... rov_server

and I have this Problem exactly and even after update app version still not solved !
the different is, so I use two dev board not 3 board but I think it's not matter

ESP-IDF : 4.3
ESP32-wroom-32 devkit

thanks

[mm_1993]

if you want to se my test log its:

Code: [Select all] [Expand/Collapse]

1.  
2. Windows PowerShell
3. Copyright (C) Microsoft Corporation. All rights reserved.
4.  
5. PS E:\Test-ESP32\ESP32_Bluetooth\fast_prov_server> C:\ESP32\.espressif\python_env\idf4.3_py3.8_env\Scripts\python.exe C:\ESP32\esp-idf\tools\idf.py -p COM11 monitor
6. Executing action: monitor
7. Running idf_monitor in directory e:\test-esp32\esp32_bluetooth\fast_prov_server
8. Executing "C:\ESP32\.espressif\python_env\idf4.3_py3.8_env\Scripts\python.exe C:/ESP32/esp-idf/tools/idf_monitor.py -p COM11 -b 115200 --toolchain-prefix xtensa-esp32-elf- e:\test-esp32\esp32_bluetooth\fast_prov_server\build\fast_prov_server.elf -m 'C:\ESP32\.espressif\python_env\idf4.3_py3.8_env\Scripts\python.exe' 'C:\ESP32\esp-idf\tools\idf.py' '-p' 'COM11'"...
9. ?[0;33m--- WARNING: GDB cannot open serial ports accessed as COMx?[0m
10. ?[0;33m--- Using \\.\COM11 instead...?[0m
11. --- idf_monitor on \\.\COM11 115200 ---
12. --- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
13. ets Jun  8 2016 00:22:57
14.  
15. rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
16. configsip: 0, SPIWP:0xee
17. clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
18. mode:DIO, clock div:2
19. load:0x3fff0030,len:6912
20. load:0x40078000,len:14292
21. ho 0 tail 12 room 4
22. load:0x40080400,len:3688
23. 0x40080400: _init at ??:?
24.  
25. entry 0x40080678
26. I (28) boot: ESP-IDF v4.3 2nd stage bootloader
27. I (28) boot: compile time 17:38:22
28. I (28) boot: chip revision: 1
29. I (31) boot_comm: chip revision: 1, min. bootloader chip revision: 0
30. I (38) boot.esp32: SPI Speed      : 40MHz
31. I (43) boot.esp32: SPI Mode       : DIO
32. I (47) boot.esp32: SPI Flash Size : 4MB
33. I (52) boot: Enabling RNG early entropy source...
34. I (57) boot: Partition Table:
35. I (61) boot: ## Label            Usage          Type ST Offset   Length
36. I (68) boot:  0 nvs              WiFi data        01 02 00009000 00004000
37. I (76) boot:  1 otadata          OTA data         01 00 0000d000 00002000
38. I (83) boot:  2 phy_init         RF data          01 01 0000f000 00001000
39. I (90) boot:  3 factory          factory app      00 00 00010000 00200000
40. I (98) boot: End of partition table
41. I (102) boot: Defaulting to factory image
42. I (107) boot_comm: chip revision: 1, min. application chip revision: 0
43. I (114) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=2a8a4h (174244) map
44. I (188) esp_image: segment 1: paddr=0003a8cc vaddr=3ffbdb60 size=04eb4h ( 20148) load
45. I (197) esp_image: segment 2: paddr=0003f788 vaddr=40080000 size=00890h (  2192) load
46. I (198) esp_image: segment 3: paddr=00040020 vaddr=400d0020 size=a4c3ch (674876) map
47. I (457) esp_image: segment 4: paddr=000e4c64 vaddr=40080890 size=163d4h ( 91092) load
48. I (496) esp_image: segment 5: paddr=000fb040 vaddr=50000000 size=00010h (    16) load
49. I (509) boot: Loaded app from partition at offset 0x10000
50. I (509) boot: Disabling RNG early entropy source...
51. I (521) cpu_start: Pro cpu up.
52. I (521) cpu_start: Starting app cpu, entry point is 0x400812bc
53. 0x400812bc: call_start_cpu1 at C:/ESP32/esp-idf/components/esp_system/port/cpu_start.c:141
54.  
55. I (0) cpu_start: App cpu up.
56. I (537) cpu_start: Pro cpu start user code
57. I (537) cpu_start: cpu freq: 160000000
58. I (537) cpu_start: Application information:
59. I (542) cpu_start: Project name:     fast_prov_server
60. I (548) cpu_start: App version:      1
61. I (552) cpu_start: Compile time:     Aug 28 2021 17:38:01
62. I (558) cpu_start: ELF file SHA256:  438f775dd716c2ce...
63. I (564) cpu_start: ESP-IDF:          v4.3
64. I (569) heap_init: Initializing. RAM available for dynamic allocation:
65. I (576) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
66. I (582) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
67. I (588) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
68. I (594) heap_init: At 3FFCCC90 len 00013370 (76 KiB): DRAM
69. I (600) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
70. I (607) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
71. I (613) heap_init: At 40096C64 len 0000939C (36 KiB): IRAM
72. I (620) spi_flash: detected chip: generic
73. I (624) spi_flash: flash io: dio
74. I (629) cpu_start: Starting scheduler on PRO CPU.
75. I (0) cpu_start: Starting scheduler on APP CPU.
76. I (639) EXAMPLE: Initializing...
77. I (639) gpio: GPIO[17]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
78. I (649) gpio: GPIO[18]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
79. I (659) gpio: GPIO[19]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
80. I (689) BTDM_INIT: BT controller compile version [1342a48]
81. I (689) system_api: Base MAC address is not set
82. I (689) system_api: read default base MAC address from EFUSE
83. I (699) phy_init: phy_version 4670,719f9f6,Feb 18 2021,17:07:07
84. I (3399) EXAMPLE: ESP_BLE_MESH_PROV_REGISTER_COMP_EVT, err_code: 0
85. I (3399) EXAMPLE: BLE Mesh Fast Prov Node initialized
86. I (3409) EXAMPLE: ESP_BLE_MESH_NODE_PROV_ENABLE_COMP_EVT, err_code: 0
87. I (86209) EXAMPLE: ESP_BLE_MESH_NODE_PROV_LINK_OPEN_EVT, bearer: PB-GATT
88. I (86689) EXAMPLE: ESP_BLE_MESH_NODE_PROV_LINK_CLOSE_EVT, bearer: PB-GATT
89. I (86689) EXAMPLE: ESP_BLE_MESH_NODE_PROV_COMPLETE_EVT
90. I (86689) EXAMPLE: net_idx: 0x0001, unicast_addr: 0x0002
91. I (86699) EXAMPLE: flags: 0x00, iv_index: 0x00000000
92. W (88819) BT_APPL: gattc_conn_cb: if=4 st=0 id=4 rsn=0x13
93. I (98339) EXAMPLE: example_ble_mesh_config_server_cb, event = 0x00, opcode = 0x0000, addr: 0x0001
94. I (98339) EXAMPLE: Config Server get Config AppKey Add
95.  
96.  

GeSHi © Codebox Plus Extension