Publication retransmit count and interval

[bluetooth_mdw]

Hi

it looks like the Publication Retransmit Count and Interval states default to 1 time and 100ms respectively. Is there a reason these defaults apply? I don't think it will be common to use this set of state values and it would be better to default them to zero.

Also, I have found that after provisioning a node, if I then go into the publication states and change the retransmit count and interval fields to zero/disabled, a composite value of 32 is still being transmitted to the node (I added some debug to my code to watch this). If I then apply the change a second time, I see the expected value of zero. This looks like a bug to me.

Regards

Martin

[bluetooth_mdw]

p.s. I'm using Zephyr on my nodes so https://devzone.nordicsemi.com/f/nordic-q-a/42253/model-publish-retransmit/164765#164765 does not apply.

[Øyvind]

Hello Martin, 

Can you please provide some more information about your system? I presume you are using the nRF5 SDK for Mesh, but what version? 

I will more information to forward to the correct team.

Thanks!

Kind regards,
Øyvind

[bluetooth_mdw]

Hi, no I'm using Zephyr but my query is about nRF Mesh, the smartphone application so I don't think the SDK on the device side matters in this case.

I'm just suggesting that defaulting the Publish Retransmit states to non-zero values in nRF Mesh when a new node is provisioned and configured may be sub-optimal. I'm also suggesting there may be a bug relating to the updating of these state values from nRF Mesh since it seems to send the pre-change values the first time you click Apply and then your new values the second time.

Martin

[Øyvind]

Thanks for clarifying, Martin! 

We really appreciate your feedback. I will forward this to our team working with the nRF Mesh application. 

Kind regards,
Øyvind

[Aleksander Nowakowski]

Hello,

Are you talking about Android or iOS version of nRF Mesh?
On iOS, the values default to Disabled, while on Android to 1 time and 0ms (which actually should be displayed as 50 ms). On Android there's also a bug, that the interval should come in 50 ms steps, starting from 50ms up to 1600ms, but the slider allows any value from 0 to 1600.

We will investigate the other issue, but we need to know on which OS did you test it.