Bluetooth Mesh Provisioner Example against Mesh Sensor Example. How do I create only one subscription and one send/receive of sensor value?

[ccasebeer]

I am attempting to provision the sensor mesh example using the static provisioner example from the MESH SDK.

It works great. However, the client receives two broadcasts upon a publish at the server.

I want to reduce that to only one broadcast and one piece of data being moved.

My knowledge of mesh provisioning is getting bettter, however it is still limited.

Essentially, upon the server publishing one piece of data (the sensor value), the client receives that value twice as evidenced by two prints of the value.

I want the process to only broadcast or send/receive one piece of data.
I have tried modifying various parts of the client, server, and provisioner source code but have not be successful.

When I provision myself with the IOS nRF Mesh app, only one piece of data is sent/received in the provisioned mesh.

I think this has to do with the static provisioner creating even and odd publication groups and the server,client are added to both.

Regards.

[Mttrinh]

Hi,

Did you try this with unmodified examples? Could you provide me with all the steps you have done so I can try reproduce this?

Also, provide which Mesh SDK and nRF5 SDK version you are using? What device are you using? Custom board or a DK?

[Mttrinh]

Hi,

What you are seeing is the publication retransmission. You can find it here: https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh/blob/master/examples/provisioner/src/node_setup.c#L318 so in addition to the original publication, the message will be re-published one more time. Set this to 0 and it will solve your problem.