What do I need to know to add mesh functionality into a normal BLE application ?
What do I need to know to add mesh functionality into a normal BLE application ?
Hi Hung, I have the same problem like Butu. I've mearged two examples from SDKv14.1 and SDK for Mesh. I have done everything like Butu after your recomendations. Now, I see the same message "Device is busy". Butu asked (Nov 29) where to change intervals value, but did not get any answer. Could you help us?
@aszka: As mentioned in the comment on 29Nov, I found an issue when integrating observer and mesh. I haven't got time to work on a workaround yet. I will get back in about 1 week.
Has going , everyone? I look foward to getting a fixed thing, too. Need a Beta version ASAP, please!
@Hung Bui: Do you know something more about above problem with combined SDKs? Why have I message that "device is busy"? I tried 3 times to combine ble_app_uart and light_swtich_client and always I had the same issue. I think about connect two DK via etc. GPIO_UART, on one DK I will have ble_app_uart, on the second DK light_switch_client and send data between them. What do you think about this solution? Is it possible? I was trying find more about this solution in the forum, but I can not find something useful.
"device is busy" meaning the reliable packet has not been acked by the peer device. Most likely happens when mesh communication is not operate as it should. I assume you have the issue when testing with mesh + BLE central ? There is a bug with that combination that I haven't got time to look into it yet. Will try to find some time this week or next week.