Greetings.
We've been developing a product that uses BLE Mesh. We are currently using the Waveshare nRF52840 Bluetooth 5.0 Evaluation Kit for prototyping purposes. As far as I know, we are using the latest SDK and our firmware is based off the "sensor" project example.
I am seeing two unexpected behaviors with nRFMesh. I would welcome any feedback you all might have.
Issue #1
I currently have seven nodes provisioned and reporting to a gateway. Five are definitely within range of the gateway. One is definitely out of range. One is right on the border (sometimes it seems to report directly and other times the message seems to get relayed).
I am provisioning the mesh using an Android phone and nRFMesh. We have two custom element models defined in the node server profile (a server model and a setup model). The server model is set to publish to a group address every 10s (the publish period is set to 10s). Within "Publication Settings" for the element model that is publishing messages, I set the "Publish TTL" value manually to 15.
Here's what's odd: when I come back to review the mesh settings at a later time, I often find that TTL has reset to a value of 1. Please note that I am connected to the mesh within nRFMesh when I check this value. However, I am still receiving messages at the gateway, so the data must be being relayed. i.e. the TTL cannot be 1.
Equally confusing, the default TTL on the node configuration page of the app still shows a value of 15.
Is this normal behavior? It seems odd that the value is reset to 1 when it clearly cannot be 1.
Issue #2
Let's say I want to update the Publication Settings for the nodes in my mesh. I connect to the mesh within the nRFMesh app and then change the parameters for each provisioned node.
This works fine for nodes that are definitely within range of wherever I am at the time. I can connect to any of the five nodes in range and make changes to any of those five without reconnecting/changing which node I connect to within nRFMesh.
Here's what's odd: For the two nodes that are out of range, I have to move to be within their range and connect to the node I want to change within nRFMesh.
Since this is a mesh and data is being relayed, I would expect to be able to change the settings of any provisioned node in the mesh, regardless of its location (as long as it is connected to another node).
My concern with both issues is that we may have something set incorrectly, or some underlying bug we need to squash. All suggestions/comments are most welcome.
