Intermittent Issue with Group Model Subscription Add in BLE Mesh

[Eshwar487]

Hi,
I am working with a BLE Mesh project that involves using five different models. Occasionally, I encounter issues where only four of the models are successfully added, while one or two models are missing from the group.

1.What might cause the Model Subscription Add operation to intermittently fail?
2.Is there any way to get more detailed logs or debugging information to help trace this issue?
3.Has anyone faced similar issues, and what solutions were applied?
4.Could this issue be related to the provisioner (smartphone) I am using?
5.Is it possible that the problem lies within the mesh network communication (from master to slave nodes)?

Below is the 5 model log

Code: Select all

I (3931457) EXAMPLE: elem_addr 0x0005, sub_addr 0xc003, cid 0xffff, mod_id 0x1000
I (3931583) EXAMPLE: elem_addr 0x0005, sub_addr 0xc003, cid 0xffff, mod_id 0x1307
I (3931645) EXAMPLE: elem_addr 0x0005, sub_addr 0xc003, cid 0xffff, mod_id 0x1300
I (3931735) EXAMPLE: elem_addr 0x0005, sub_addr 0xc003, cid 0xffff, mod_id 0x1303
I (3931855) EXAMPLE: elem_addr 0x0005, sub_addr 0xc003, cid 0x02e5, mod_id 0x0001

[chegewara]

1. please describe provisioning procedure (what smartphone type, android or iOS, what application etc)
2. i believe you should be able to add more logs in the code to see what data are sent from provisioner app
3. any more information you can provide?

[Eshwar487]

Hi, thank you for your response.

1.We are using a custom app designed for both iPhone and Android devices.
2.Below are the logs.
3.Is the mesh network responsible for grouping, or is it managed by the smartphone?

Code: Select all

I (2722859) BLE_MESH: Settings store, waiting 5 seconds
I (2722861) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0002
I (2722861) BLE_MESH: recv, len 8: 801b020002c00010
I (2722867) BLE_MESH: Settings store, waiting 1 seconds
I (2722873) BLE_MESH: send, app_idx 0xfffe src 0x0002 dst 0x0001
I (2722879) BLE_MESH: send, len 9: 801f00020002c00010
I (2722895) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (2722897) EXAMPLE: elem_addr 0x0002, sub_addr 0xc002, cid 0xffff, mod_id 0x1000
I (2723099) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0002
I (2723101) BLE_MESH: recv, len 8: 801b020002c00713
I (2723103) BLE_MESH: send, app_idx 0xfffe src 0x0002 dst 0x0001
I (2723109) BLE_MESH: send, len 9: 801f00020002c00713
I (2723125) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (2723125) EXAMPLE: elem_addr 0x0002, sub_addr 0xc002, cid 0xffff, mod_id 0x1307       
I (2723239) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0002
I (2723241) BLE_MESH: recv, len 8: 801b020002c00013
I (2723243) BLE_MESH: send, app_idx 0xfffe src 0x0002 dst 0x0001
I (2723249) BLE_MESH: send, len 9: 801f00020002c00013
I (2723265) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (2723265) EXAMPLE: elem_addr 0x0002, sub_addr 0xc002, cid 0xffff, mod_id 0x1300       
I (2723281) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0002
I (2723281) BLE_MESH: recv, len 8: 801b020002c00313
I (2723283) BLE_MESH: send, app_idx 0xfffe src 0x0002 dst 0x0001
I (2723289) BLE_MESH: send, len 9: 801f00020002c00313
I (2723297) BLE_MESH: Settings store, waiting 0 seconds
I (2723401) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0002
I (2723403) BLE_MESH: recv, len 10: 801b020002c0e5020100
I (2723405) BLE_MESH: send, app_idx 0xfffe src 0x0002 dst 0x0001
I (2723411) BLE_MESH: send, len 11: 801f00020002c0e5020100
I (2723421) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (2723423) EXAMPLE: elem_addr 0x0002, sub_addr 0xc002, cid 0xffff, mod_id 0x1303
I (2723431) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (2723437) EXAMPLE: elem_addr 0x0002, sub_addr 0xc002, cid 0x02e5, mod_id 0x0001
I (2728523) BLE_MESH: net_idx 0x000 iv_index 0x00000000 flags 0x00
I (2745599) BLE_MESH: Settings store, waiting 5 seconds

[chegewara]

Usually it is provisioner app which is responsible to assign groups and all configurations, but it is also possible that you can control this in firmware, for example if you know that every single node will use the same group to publish or receive data then it is better to do it in firmware.
In this case of course it is good to let the provisioner to change it and unregister from group too.

Code: Select all

I (3931855) EXAMPLE: elem_addr 0x0005, sub_addr 0xc003, cid 0x02e5, mod_id 0x0001

I dont think config cli model can subscribe to group, but im not sure. I didnt work with mesh for few months so i am a bit rusty.
Probably you have a bug in your code and this suppose to be different model.

[Eshwar487]

Hi,
I am using a custom vendor model and have defined the ID as 0x0001, similar to what is shown in the attached image (nRF Mesh). Am I doing something wrong with this setup? Any advice or corrections would be helpful.

[chegewara]

Like i said, i am a bit rusted and i missed the fact it is for vendor model, sorry.
In that case it looks fine.

I see some inconsistency in logs

Code: Select all

I (2722895) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (2722897) EXAMPLE: elem_addr 0x0002, sub_addr 0xc002, cid 0xffff, mod_id 0x1000
I (2723099) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0002
I (2723101) BLE_MESH: recv, len 8: 801b020002c00713
I (2723103) BLE_MESH: send, app_idx 0xfffe src 0x0002 dst 0x0001
I (2723109) BLE_MESH: send, len 9: 801f00020002c00713

and

Code: Select all

I (2723421) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (2723423) EXAMPLE: elem_addr 0x0002, sub_addr 0xc002, cid 0xffff, mod_id 0x1303
I (2723431) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (2723437) EXAMPLE: elem_addr 0x0002, sub_addr 0xc002, cid 0x02e5, mod_id 0x0001

I am suggesting to study this example code, which has vendor model, and maybe add some logs like this, if you dont have it yet
https://github.com/espressif/esp-idf/bl ... emo.c#L964

[Eshwar487]

Hi,

1.Is a Health Server model required for BLE Mesh nodes?
2.Does not using relay nodes affect message subscription?
3.Does the app developer receive acknowledgments for messages sent to nodes that are not connected to GATT?

Here are the logs from the connection using nRF Mesh:
Starting provisioning log

Code: Select all

I (293040) GATTS_TABLE_DEMO: ESP_GATTS_CONNECT_EVT, conn_id = 0
I (293040) GATTS_TABLE_DEMO: 65 1d 54 f3 f0 43
I (293042) GATTS_DEMO: Connected, conn_id 0, remote 65:1d:54:f3:f0:43
W (293050) BT_L2CAP: l2cble_start_conn_update, the last connection update command still pending.
I (293120) GATTS_DEMO: MTU exchange, MTU 517
I (293420) GATTS_TABLE_DEMO: update connection params status = 0, min_int = 16, max_int = 32,conn_int = 24,latency = 0, timeout = 400
I (293810) EXAMPLE: ESP_BLE_MESH_NODE_PROV_LINK_OPEN_EVT, bearer PB-GATT
W (293870) BLE_MESH: No Health Server context provided
I (294800) BLE_MESH: Algorithm:   0x00
I (294800) BLE_MESH: Public Key:  0x00
I (294800) BLE_MESH: Auth Method: 0x00
I (294802) BLE_MESH: Auth Action: 0x00
I (294806) BLE_MESH: Auth Size:   0x00
I (295072) BLE_MESH: Primary Element: 0x0011
I (295072) BLE_MESH: net_idx 0x0000 flags 0x00 iv_index 0x0000
I (295074) BLE_MESH: dev_key 7b333402ca69b6502c54bd6d485ec13d
W (295080) BLE_MESH: No Health Server context provided
I (295092) BLE_MESH: Primary address 0x0011, element count 1
I (295092) BLE_MESH: Settings store, waiting 0 seconds
I (295100) BLE_MESH: Settings store, waiting 0 seconds
I (295108) BLE_MESH: Settings store, waiting 0 seconds
I (295110) BLE_MESH: Settings store, waiting 0 seconds
I (295118) BLE_MESH: net_idx 0x000 iv_index 0x00000000 flags 0x00
I (295126) BLE_MESH: Scan is already started
I (295136) EXAMPLE: ESP_BLE_MESH_NODE_PROV_LINK_CLOSE_EVT, bearer PB-GATT
I (295138) EXAMPLE: ESP_BLE_MESH_NODE_PROV_COMPLETE_EVT
I (295140) EXAMPLE: net_idx: 0x0000, addr: 0x0011
I (295146) EXAMPLE: flags: 0x00, iv_index: 0x00000000
W (295222) BT_HCI: hcif disc complete: hdl 0x0, rsn 0x13
I (295232) GATTS_TABLE_DEMO: ESP_GATTS_DISCONNECT_EVT, reason = 0x13
I (295232) GATTS_DEMO: Disconnected, remote 65:1d:54:f3:f0:43, reason 0x13
I (295244) GATTS_TABLE_DEMO: advertising start successfully
I (295250) GATTS_TABLE_DEMO: advertising start successfully 

for binding Key

Code: Select all

I (436980) BLE_MESH: Received 0/1
I (437040) BLE_MESH: Received 1/1
I (437040) BLE_MESH: Settings store, waiting 0 seconds
I (437054) BLE_MESH: Settings store, waiting 0 seconds
I (437066) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (437066) BLE_MESH: recv, len 20: 00000000ab10ae3edf91d18e515dc614c9217341
I (437070) BLE_MESH: Settings store, waiting 0 seconds
I (437080) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (437082) BLE_MESH: send, len 6: 800300000000
I (437088) BLE_MESH: Settings store, waiting 0 seconds
I (437108) EXAMPLE: ESP_BLE_MESH_MODEL_OP_APP_KEY_ADD
I (437110) EXAMPLE: net_idx 0x0000, app_idx 0x0000
I (437110) AppKey: ab 10 ae 3e df 91 d1 8e 51 5d c6 14 c9 21 73 41
I (437160) BLE_MESH: Settings store, waiting 0 seconds
I (437174) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (437174) BLE_MESH: recv, len 8: 803d110000000010
I (437176) BLE_MESH: Settings store, waiting 0 seconds
I (437186) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (437188) BLE_MESH: send, len 9: 803e00110000000010
I (437194) BLE_MESH: Settings store, waiting 0 seconds
I (437214) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_APP_BIND
I (437216) EXAMPLE: elem_addr 0x0011, app_idx 0x0000, cid 0xffff, mod_id 0x1000
I (437280) BLE_MESH: Settings store, waiting 0 seconds
I (437294) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (437294) BLE_MESH: recv, len 8: 803d110000000713
I (437296) BLE_MESH: Settings store, waiting 0 seconds
I (437314) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (437316) BLE_MESH: send, len 9: 803e00110000000713
I (437318) BLE_MESH: Settings store, waiting 0 seconds
I (437338) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_APP_BIND
I (437340) EXAMPLE: elem_addr 0x0011, app_idx 0x0000, cid 0xffff, mod_id 0x1307
I (437400) BLE_MESH: Settings store, waiting 0 seconds
I (437414) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (437414) BLE_MESH: recv, len 8: 803d110000000013
I (437416) BLE_MESH: Settings store, waiting 0 seconds
I (437436) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (437436) BLE_MESH: send, len 9: 803e00110000000013
I (437438) BLE_MESH: Settings store, waiting 0 seconds
I (437460) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_APP_BIND
I (437460) EXAMPLE: elem_addr 0x0011, app_idx 0x0000, cid 0xffff, mod_id 0x1300
I (437550) BLE_MESH: Settings store, waiting 0 seconds
I (437564) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (437564) BLE_MESH: recv, len 8: 803d110000000313
I (437566) BLE_MESH: Settings store, waiting 0 seconds
I (437586) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (437586) BLE_MESH: send, len 9: 803e00110000000313
I (437588) BLE_MESH: Settings store, waiting 0 seconds
I (437608) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_APP_BIND
I (437610) EXAMPLE: elem_addr 0x0011, app_idx 0x0000, cid 0xffff, mod_id 0x1303
I (437670) BLE_MESH: Settings store, waiting 0 seconds
I (437684) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (437684) BLE_MESH: recv, len 8: 803d110000000c13
I (437686) BLE_MESH: Settings store, waiting 0 seconds
I (437706) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (437706) BLE_MESH: send, len 9: 803e00110000000c13
I (437708) BLE_MESH: Settings store, waiting 0 seconds
I (437728) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_APP_BIND
I (437730) EXAMPLE: elem_addr 0x0011, app_idx 0x0000, cid 0xffff, mod_id 0x130c
I (437790) BLE_MESH: Settings store, waiting 0 seconds
I (437804) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (437804) BLE_MESH: recv, len 10: 803d11000000e5020100
I (437806) BLE_MESH: Settings store, waiting 0 seconds
I (437816) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (437818) BLE_MESH: send, len 11: 803e0011000000e5020100
I (437826) BLE_MESH: Settings store, waiting 0 seconds
I (437846) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_APP_BIND
I (437846) EXAMPLE: elem_addr 0x0011, app_idx 0x0000, cid 0x02e5, mod_id 0x0001

for Subscribing

Code: Select all

I (509310) BLE_MESH: Settings store, waiting 0 seconds
I (509324) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (509326) BLE_MESH: recv, len 8: 801b110000c00010
I (509326) BLE_MESH: Settings store, waiting 0 seconds
I (509336) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (509338) BLE_MESH: send, len 9: 801f00110000c00010
I (509346) BLE_MESH: Settings store, waiting 0 seconds
I (509366) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (509368) EXAMPLE: elem_addr 0x0011, sub_addr 0xc000, cid 0xffff, mod_id 0x1000
I (509430) BLE_MESH: Settings store, waiting 0 seconds
I (509446) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (509448) BLE_MESH: recv, len 8: 801b110000c00713
I (509448) BLE_MESH: Settings store, waiting 0 seconds
I (509458) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (509460) BLE_MESH: send, len 9: 801f00110000c00713
I (509468) BLE_MESH: Settings store, waiting 0 seconds
I (509488) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (509490) EXAMPLE: elem_addr 0x0011, sub_addr 0xc000, cid 0xffff, mod_id 0x1307
I (509550) BLE_MESH: Settings store, waiting 0 seconds
I (509568) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (509568) BLE_MESH: recv, len 8: 801b110000c00013
I (509570) BLE_MESH: Settings store, waiting 0 seconds
I (509580) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (509582) BLE_MESH: send, len 9: 801f00110000c00013
I (509590) BLE_MESH: Settings store, waiting 0 seconds
I (509610) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (509610) EXAMPLE: elem_addr 0x0011, sub_addr 0xc000, cid 0xffff, mod_id 0x1300
I (509670) BLE_MESH: Settings store, waiting 0 seconds
I (509688) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (509690) BLE_MESH: recv, len 8: 801b110000c00313
I (509690) BLE_MESH: Settings store, waiting 0 seconds
I (509700) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (509702) BLE_MESH: send, len 9: 801f00110000c00313
I (509710) BLE_MESH: Settings store, waiting 0 seconds
I (509732) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (509734) EXAMPLE: elem_addr 0x0011, sub_addr 0xc000, cid 0xffff, mod_id 0x1303
I (509790) BLE_MESH: Settings store, waiting 0 seconds
I (509808) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (509810) BLE_MESH: recv, len 8: 801b110000c00c13
I (509810) BLE_MESH: Settings store, waiting 0 seconds
I (509820) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (509822) BLE_MESH: send, len 9: 801f00110000c00c13
I (509830) BLE_MESH: Settings store, waiting 0 seconds
I (509852) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (509852) EXAMPLE: elem_addr 0x0011, sub_addr 0xc000, cid 0xffff, mod_id 0x130c
I (509910) BLE_MESH: Settings store, waiting 0 seconds
I (509928) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (509930) BLE_MESH: recv, len 10: 801b110000c0e5020100
I (509932) BLE_MESH: Settings store, waiting 0 seconds
I (509940) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (509944) BLE_MESH: send, len 11: 801f00110000c0e5020100
I (509950) BLE_MESH: Settings store, waiting 0 seconds
I (509974) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_SUB_ADD
I (509974) EXAMPLE: elem_addr 0x0011, sub_addr 0xc000, cid 0x02e5, mod_id 0x0001

[chegewara]

Hi,

1.Is a Health Server model required for BLE Mesh nodes?
2.Does not using relay nodes affect message subscription?
3.Does the app developer receive acknowledgments for messages sent to nodes that are not connected to GATT?

1. no, its not required model
2. you dont need relays; relays are used to extend range of mesh network
3. yes, in most cases nodes will respond on received messages, as you can see in your logs, but you wont get feedback when you are publishing to group address

here is example. node is receiving app key bind message from provisioner, which address is 0x0001

Code: Select all

I (437214) EXAMPLE: ESP_BLE_MESH_MODEL_OP_MODEL_APP_BIND
I (437216) EXAMPLE: elem_addr 0x0011, app_idx 0x0000, cid 0xffff, mod_id 0x1000
I (437280) BLE_MESH: Settings store, waiting 0 seconds
I (437294) BLE_MESH: recv, app_idx 0xfffe src 0x0001 dst 0x0011
I (437294) BLE_MESH: recv, len 8: 803d110000000713
I (437296) BLE_MESH: Settings store, waiting 0 seconds

and then is sending back confirmation

Code: Select all

I (437314) BLE_MESH: send, app_idx 0xfffe src 0x0011 dst 0x0001
I (437316) BLE_MESH: send, len 9: 803e00110000000713

To learn more about responses its good to play with esp32 provisioner examples.

[Eshwar487]

In this case, while subscribing, the device will still receive acknowledgments from the smartphone even if it is not connected via GATT.

I am using BLE Mesh for multiple lighting devices. Is it advisable to enable every device as a relay node?

thanks

[chegewara]

In this case, while subscribing, the device will still receive acknowledgments from the smartphone even if it is not connected via GATT.

This is how ble mesh works, with one exception. Smartphones cant work with ADV type, so you need at least one device which works in GATT and relay mode. Then other devices in range can work in ADV (connectionless) mode.

I am using BLE Mesh for multiple lighting devices. Is it advisable to enable every device as a relay node?

It all depends. Disadvantage of running relay is power consumption. If your lights are battery powered then this may be problem, in other case it should not hurt.