mesh publish issues under zephyr

[AndyM]

I have a custom model server that sends 8 bytes of data 

I set up 2 nodes - one to publish to an address 0xC002, one to subscribe to publication

Provisioning and publish parameter configuration was done in mesh shell

It works as expected - every n seconds I see a  mesh "set_unack" function executes on the subscriber node and the data is all good

Added a second device to publish to the same address . Gave it the node address one greater than the first one: 0x100 and 0x101

But the subscriber node only reports messages from from 0x100. It does see something - there are debug messages "Unable to find matching net for packet"

but the data from node 0x101 is not propagated to the app layer

Reprovisioned both nodes in mesh shell and gave them the addresses used by nRF mesh app.  (0x001d and 0x001c)

Now  the subscriber node sees data from both publishers. Any ideas why changing the node address made its messages reach the subscriber?

Also, I'm noticing that even with the addresses from the nRF mesh app the subscriber does not always receive messages from both devices . And it is always the higher address that drops off. Message from the lower one is <always> delivered. All 3 devices are very close to each other

My device composition has 1 element with 2 vendor models and 5 SIG models

Mesh relay is enabled

Any help would be much appreciated

Thanks

[AndyM]

OK, answering my own question

It appears that the issue was due to low TTL that I set for publishing. It was set to 0 and sometimes to 5

I set it to 100 and now the subscriber node reliably sees all publishers.  In my network topology multiple publisher nodes must reach a single subscriber node so it probably makes sense for the TTL to be set higher.. Any suggestions on the TTL size in my case are appreciated.