ESP32 BLE mesh example fails to provision [BMCI-87]

[cowens]

Device: ESP32-WROOM-32D
SDK: 4.01
Example Instructions URL: https://docs.espressif.com/projects/esp ... index.html

I am following the instructions and everything is working fine except provisioning. The android nrf-mesh app returns:
"Provisioning Failed, Prohibited" (see attached image). I have tried the Cypress mesh app, and ST mesh app and they also fail as well. The ST mesh app appears to complete, but when I attempt to examine an element the app crashes.

Any assistance with this would be appreciated.

To follow is the monitor when I attempt to provision with nrf-mesh

$ idf.py monitor
Setting IDF_PATH environment variable: c:\eds\call_light\idf_test\no_vscode\esp-
idf-v4.0.1
Checking Python dependencies...
Python requirements from c:\eds\call_light\idf_test\no_vscode\esp-idf-v4.0.1\req
uirements.txt are satisfied.
Executing action: monitor
Choosing default port b'COM4' (use '-p PORT' option to set a specific serial por
t)
Running idf_monitor in directory c:\eds\call_light\idf_test\no_vscode\esp-idf-v4
.0.1\examples\bluetooth\esp_ble_mesh\ble_mesh_node\onoff_server
Executing "winpty C:\Users\owens\AppData\Local\Programs\Python\Python37\python.e
xe c:\eds\call_light\idf_test\no_vscode\esp-idf-v4.0.1\tools/idf_monitor.py -p C
OM4 -b 115200 c:\eds\call_light\idf_test\no_vscode\esp-idf-v4.0.1\examples\bluet
ooth\esp_ble_mesh\ble_mesh_node\onoff_server\build\onoff_server.elf -m 'C:\Users
\owens\AppData\Local\Programs\Python\Python37\python.exe' 'C:/eds/call_light/idf
_test/no_vscode/esp-idf-v4.0.1/tools/idf.py'"...
--- idf_monitor on COM4 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:6984
load:0x40078000,len:14076
load:0x40080400,len:4304
entry 0x400806e8
I (71) boot: Chip Revision: 1
I (71) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (39) boot: ESP-IDF v4.0.1-dirty 2nd stage bootloader
I (39) boot: compile time 15:21:04
I (39) boot: Enabling RNG early entropy source...
I (44) boot: SPI Speed : 40MHz
I (48) boot: SPI Mode : DIO
I (52) boot: SPI Flash Size : 2MB
I (56) boot: Partition Table:
I (60) boot: ## Label Usage Type ST Offset Length
I (67) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (74) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (82) boot: 2 factory factory app 00 00 00010000 00100000
I (89) boot: End of partition table
I (94) boot_comm: chip revision: 1, min. application chip revision: 0
I (101) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x2bf00 (17

I (1118) onoff_server: ESP_BLE_MESH_PROV_REGISTER_COMP_EVT, err_code 0
I (1128) onoff_server: ESP_BLE_MESH_NODE_PROV_ENABLE_COMP_EVT, err_code 0
I (1128) onoff_server: BLE Mesh Node initialized
I (21198) onoff_server: ESP_BLE_MESH_NODE_PROV_LINK_OPEN_EVT, bearer PB-GATT
W (23968) BLE_MESH: bt_mesh_attention, No Health Server context provided

[iamkkk]

It seems nRF APK detect Provsionee public key X, Y is invalidate
in ECPoint ecPoint = curve.validatePoint(x, y); and nRF APK call exception

I use bt_mesh_check_public_key to check Provsionee 's bt_mesh_public_key and bt_mesh_check_public_key also show fail.
It seem esp mesh profile generate wrong bt_mesh_public_key.

[ESP_Alvin]

Moderator's note: edit the topic title for issue tracking, thanks for reporting.

[esp_liu]

It seems nRF APK detect Provsionee public key X, Y is invalidate
in ECPoint ecPoint = curve.validatePoint(x, y); and nRF APK call exception

I use bt_mesh_check_public_key to check Provsionee 's bt_mesh_public_key and bt_mesh_check_public_key also show fail.
It seem esp mesh profile generate wrong bt_mesh_public_key.

Hi iamkkk,

This issue has been updated in the esp-idf Github Issues, please refer to https://github.com/espressif/esp-idf/issues/5341

Thanks.