bt_mesh_model_send relayable?

[Shahin97]

Hello, 

I am looking into relay nodes and my nodes do not seem to relay,

All nodes are provisioned with the same provisioner and have the same keys 

The following configs are enabled - 

CONFIG_BT_MESH_RELAY=y
CONFIG_BT_MESH_RELAY_ENABLED=y
CONFIG_BT_MESH_RELAY_RETRANSMIT_COUNT=5


The messages that are sent are vendor model messages using:

bt_mesh_model_send sent to BT_MESH_ADDR_ALL_NODES. 

bt_mesh_model_send does not have any acknowledgement, am I correct in saying bt_mesh_model_send cannot be relayed? and if not any pointers what to look for in this issue

[AHaug]

Hi,

I've picked up your case and will be looking into this early next week. In the meanwhile, do you got access to the Mesh specification? And which version of NCS are you using (it is relevant w.r.t what version of the Mesh spec you're using)?

Kind regards,
Andreas

[Shahin97]

Hello, 

I am using nRF Connect SDK latest release branch v2.6.0, I have read the material on Nordic semi website, if you have a link to a Bluetooth sig spec that would be a good reference material.

I have made some development.

Turning on Access level mesh logs, my second node is indeed receiving the message from the first node, which makes sense as the send address is  BT_MESH_ADDR_ALL_NODES, however, it is not relaying the message after receiving it

[12:08:12.000,000] <dbg> bt_mesh_access: bt_mesh_model_recv: OpCode 0x00e20059
[12:08:12.000,000] <dbg> bt_mesh_access: element_model_recv: No OpCode 0x00e20059 for elem 0x10
[12:08:13.000,000] <dbg> bt_mesh_access: bt_mesh_model_recv: app_idx 0x0000 src 0x0011 dst 0xffff
[12:08:13.000,000] <dbg> bt_mesh_access: bt_mesh_model_recv: len 25: e25900f250ec65000000000a01b8010000505436aca9b03440


[12:08:13.000,000] <dbg> bt_mesh_access: bt_mesh_model_recv: OpCode 0x00e20059
[12:08:13.000,000] <dbg> bt_mesh_access: element_model_recv: No OpCode 0x00e20059 for elem 0x10
[12:08:15.000,000] <dbg> bt_mesh_access: bt_mesh_model_recv: app_idx 0x0000 src 0x0011 dst 0xffff
[12:08:15.000,000] <dbg> bt_mesh_access: bt_mesh_model_recv: len 25: e25900f350ec65000000000a01b9010000a75a0bb3d0b63440


[12:08:15.000,000] <dbg> bt_mesh_access: bt_mesh_model_recv: OpCode 0x00e20059
[12:08:15.000,000] <dbg> bt_mesh_access: element_model_recv: No OpCode 0x00e20059 for elem 0x10
[12:08:15.000,000] <dbg> bt_mesh_access: bt_mesh_model_recv: app_idx 0x0000 src 0x0011 dst 0xffff
[12:08:15.000,000] <dbg> bt_mesh_access: bt_mesh_model_recv: len 25: e25900f450ec65000000000a01ba010000d10836ae7fb73440

The No "OpCode 0x00e20059 for elem 0x10" shouldn't be an issue as it is for a different node.