Bluetooth Mesh Application

RE: Bluetooth Mesh Application

Simonr — Mon, 03 Aug 2020 06:32:18 GMT

Sorry, I meant you only need one node as a configurable gateway that can forward configurations to the rest of the network.

For more information on this and how nodes know which messages are meant for them and not, as well as all other concepts in Mesh, I suggest checking out our documentation, which Terje pointed to earlier, as well as this "Ultimate Bluetooth Mesh Tutorial" over on novelbits.io.

Best regards,

Simon

RE: Bluetooth Mesh Application

shyam9092 — Thu, 30 Jul 2020 22:33:24 GMT

[quote userid="75734" url="~/f/nordic-q-a/63281/bluetooth-mesh-application/262105"]You only need one node to be configurable over the GATT bearer, and that node can forward the configurations to the other nodes in the network.[/quote]

I'm sorry but I didn't quite understand it completely, can you please elaborate? In order to configure a node, we need to provide the node with subscription-publication address and keys for encryption, right? This attributes might be unique to each node, then how can one node pass the configurations?

[quote userid="75734" url="~/f/nordic-q-a/63281/bluetooth-mesh-application/262105"]. A node in a mesh network will transmit messages to all other nodes in the mesh network, as that is the concept of a Mesh network. A node will transmit its data to the nodes closest to itself, which will pass on the data to the other nodes in the network until all nodes get the memo.[/quote]

So, how does a node knows that the message it just received is meant for that node only, so it does not broadcast it to the other node and use that message for further processing? Based on opcode/opcode-handler? Based on unicast address of each node?

RE: Bluetooth Mesh Application

Simonr — Wed, 29 Jul 2020 07:22:53 GMT

I'm sorry about the late reply, but due to the summer vacation period, we're low on staff and are only now getting to Terje's (who's taking some time off) backlog.

Yes, the nRF Mesh app for Android app can be used to provision/configure the nodes in your Mesh network.

You only need one node to be configurable over the GATT bearer, and that node can forward the configurations to the other nodes in the network.

As for your final question, I'm not sure what you're asking. A node in a mesh network will transmit messages to all other nodes in the mesh network, as that is the concept of a Mesh network. A node will transmit its data to the nodes closest to itself, which will pass on the data to the other nodes in the network until all nodes get the memo.

Best regards,

Simon

RE: Bluetooth Mesh Application

shyam9092 — Thu, 16 Jul 2020 00:12:41 GMT

Thank you for your reply. I've integrated my custom model with light switch example, as MESH_FEATURE_PB_GATT_ENABLED and MESH_FEATURE_GATT_PROXY_ENABLED are by default defined to 1 so I'll be able to provision and configure all the nodes using nRF Mesh Android application right?

In the previous replies you said that

[quote userid="8164" url="~/f/nordic-q-a/63281/bluetooth-mesh-application/259266"]Note that you would also probably want to configure the nodes. For that, from a smartphone, you need at least one node in the network that the smartphone can connect to over the GATT bearer.[/quote]

Why you said at least one node? Don't I need all the nodes to be configured using the android application, for that all of the nodes should support GATT proxy, right?

Also, I understand that during provisioning and configuration, the nodes gets assigned a unicast address, publication and subscription address, and keys. So as this provisioning process happens after the device is programmed, how do I control the address that nodes send message to? For example consider access_model_reliable_publish() used in the client model, does this API publishes to the address that is assigned during configuration as publication address?

RE: Bluetooth Mesh Application

tesc — Wed, 15 Jul 2020 17:41:56 GMT

Hi,

For setting up what addresses each model should publish to, and subscribe to, as well as what application key the model should use. For that you need to configure the node. This is usually also done from the provisioner, as you do need the device key for the device in order to do configuration.

For more information on this, please consult Bluetooth Mesh concepts from our nRF5 SDK for Mesh documentation, and in particular the "Device life cycle" section of that page.

Regards,
Terje

RE: Bluetooth Mesh Application

shyam9092 — Mon, 13 Jul 2020 22:32:20 GMT

I don't understand what do you mean by the above statement. Can you please elaborate further?

RE: Bluetooth Mesh Application

tesc — Thu, 09 Jul 2020 15:51:10 GMT

Hi,

Some of this has already been answered here: nRF Mesh

In order to get provisioned from a smartphone, the project needs to enable the PB-GATT feature, which is the GATT provisioning bearer. Do this by defining MESH_FEATURE_PB_GATT_ENABLED to 1, for instance in nrf_mesh_config_app.h, which is already done by default in several examples in our SDK, including for the light switch examples.

Note that you would also probably want to configure the nodes. For that, from a smartphone, you need at least one node in the network that the smartphone can connect to over the GATT bearer. (For normal mesh communication, not only for provisioning.) To enable GATT proxy for a node, define MESH_FEATURE_GATT_PROXY_ENABLED to 1. This is also done by default for the light switch examples, in their nrf_mesh_config_app.h.

Bluetooth mesh nodes using the ADV bearer, which is the default bearer for Bluetooth mesh, will use advertising for sending messages. Any time not used for sending, will be used receiving (scanning).

For nodes using the GATT bearer, some of the time will be used in normal BLE connections.

For Low Power Nodes, advertising is used whenever they need to send a packet. They also use advertising and scanning when communicating with their Friend node.

Regards,
Terje