-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to provision the ESP - BLE-MESH Example. (IDFGH-11775) #12871
Comments
update |
hai @forx157 |
Hi @Bosemani! I have the same problem using the nrf mesh application for Android. I tried doing the same with the Apple appand it worked without any problem. If you don't have an apple product, you can try to do the same using an esp32 as provisioner. |
Hai @Herbrant |
Right now I have a problem with the provisioner and the onoff_client of the examples directory.
onoff_client:
You are able to send messages from the client to the server? @Bosemani |
I have done provisioning on the tag v5.1.2 on esp32 c3. Its working fine for me |
Hai @Herbrant |
Hai @ankit-thealchemist |
I can confirm, had problem with the master, I built today. No problem with the nRF App an v5.1.2. |
Hai @Fighter19 |
Hai @chegewara |
Hi, If you dont have any provisioned esp32 devices, then its easy solution. Grab esp32 devkit and flash any mesh example built with idf 5.1. You have tool to work with mesh 5.1, because you can continue provisioning and play with mesh v1.1. Specs says that mesh 1.1 shall be backward compatible, so any provisioner which works with mesh 1.0 should works with v1.1, just wont handle new features. |
Hai @chegewara |
There is one more thing i just learned.
|
Looks like i dont know what i am saying about, maybe except how to workaround provisioning issues with nrf mesh. Here is what i found:
|
Hai @chegewara |
I believe this is relevant info I believe there should be option to set this value in API, but either i cant find it or is not implemented. PS espressif provisioner mesh v1.0 can work with node mesh v1.1 when you disable this option in menuconfig it does not explain why nrf mesh cant provisioning mesh v1.1 node, even if EPA is disabled, so i still believe its issue with proxy out characteristic |
Hai @chegewara |
Ive found it, finally.
Thanks PS now it works with nRF connect and silab app too |
Very good work!!! Thank YOU!!! |
@chegewara |
No problem, im glad it is that easy fix I can only complain that mesh in esp-idf 5.1 is not C++ friendly (macros wont let use it in C++), but its fixed in 5.3. Thanks |
@chegewara Very good work! Thank you. |
@chegewara |
@forx157 I am trying to figure out whats wrong.
and this output:
I have more or less complicated C++ library, which should not be the cause of the problem, but who know. Thanks for attention |
Im not sure if my deduction is correct, but i found something.
and get correct result
now the strange part only for this test purpose
and here is log
we can observe 2 things:
Bear in mind that in normal use case i call only one time publish function with data passed from I hope i described it that it can be understand, even if its a bit messy Thanks |
@chegewara |
@forx157
here is my updated macro, so i could use the same
It is working with on-off server w/o issue |
@chegewara For details you can refer to the implementation in the function if (act == BTC_BLE_MESH_ACT_MODEL_PUBLISH) {
bt_mesh_model_msg_init(model->pub->msg, opcode);
// if you passed pub.msg.data in,The essence of this line of code becomes
// net_buf_simple_add_mem(model->pub->msg, model->pub->msg.data, model->pub->msg.data_len);
net_buf_simple_add_mem(model->pub->msg, data, length);
} else {
msg_data = (uint8_t *)bt_mesh_malloc(op_len + length);
if (msg_data == NULL) {
return ESP_ERR_NO_MEM;
}
esp_ble_mesh_model_msg_opcode_init(msg_data, opcode);
memcpy(msg_data + op_len, data, length);
} |
Ok, so i dont have to update data in |
Yes |
Answers checklist.
General issue report
Hai,
My sdk version is ESP-IDF v5.3-dev-1157 & Esp32-c3 development board.
I tried onoff_client, onoff_server, sensor ble mesh examples under this location
esp-idf\examples\bluetooth\esp_ble_mesh
I haven't modified anything on code. I just changed BLE mesh log level.
I'm using NRF BLE MESH Android app for provisioning but I'm not able to complete the provisioning process. It always fails.
Here is the on-off server example on esp32-c3 log:
In Nrf mesh app it's getting stop at "Sending composition data get...."
Why is this happening? How to resolve this.
Best Regards
Bose
The text was updated successfully, but these errors were encountered: