How to receive mesh message at nRF Mesh app (Android)?

[Jeffery]

Hi Nordic team

1. Define one vendor client model and one vendor server model at mesh nodes.

2. Provision all mesh nodes. Then, Create a mesh group 0xC000.

3. Configure all mesh nodes. Publish address of client model was 0xC000. Subscribe address of server model was 0xC000, too.

4. It can work to publish mesh message (several user bytes) to group 0xC000 at "Groups" panel of nRF Mesh app. Then, nodes can receive the message via server model.

My question is how to subscribe mesh message from 0xC000 at "Groups" panel of nRF Mesh app if a mesh node publish message via client model?

At nrf Mesh app source code, any API we can use to receive mesh message in group?

Thanks.

Jeffery

[Jeffery]

Hi Mttrinh

1. As you said,  configuration client only can publish message. Since phone's role is main provisioner, it owns whole network data.

   It shall have ability to be a configuration server to subscribe group message, right? If we want to create a configuration server for this purpose,

   would you have example code for reference?

2. About "Proxy filter" page, it can add group address or unicast address  as attachment. So, if I included the group address my phone wanna

   listen or said "subscribe", does it mean phone can receive all messages for expected group?

   But, this function already work? I tried several times but no idea how to work it. Did you have step by step guide?

Thanks

[Mttrinh]

Hi,

1. Unfortunately, we do not have an example code for reference so you would have to implement this on your own.

2. Technically you should be able to receive all messages from the group address but our sample app does not handle this, so this is also something you have to implement yourself. We do not have a step-by-step guide.

[Jeffery]

Hi Mttrinh

Ok. So,which API function of nrf mesh app do you think suitable for calling to get message data? 

[Roshan Rajaratnam]

Hi Jeffery, the following callback will be invoked when you get a mesh message from the network. Just like any other message in the mesh network. I would also suggest referring to the proxy filter sections 6.4 and 6.5 of the mesh specification