Friendship - BLE Mesh

RE: Friendship - BLE Mesh

Joakim Jakobsen — Fri, 24 May 2019 11:11:12 GMT

Hi.

This is up to you and how you choose to solve this. You can have a beacon device that is provisioned into the network. You can also make your mesh network listen for BLE advertisement packets from the beacon.

There are several alternatives to achieve low power besides the Low Power Node and Friendship solution.

- You can just put a normal node to sleep, it may miss packets send to it, but if it's simply a temperature sensor for example, you just need to receive data from it.

- Or you can make your device to advertise normal BLE advertising packet, and define a protocol in your normal mesh node to forward those packet into mesh, this is what we have in the Enocean energy harvesting light switch example.

- Another option is to configure your device as a GATT client proxy, to connect to a Proxy. This way you just need to maintain a normal BLE connection.

Best regards,
Joakim

RE: Friendship - BLE Mesh

erdemsimsek — Tue, 21 May 2019 07:43:54 GMT

Hi Joakim,

Do you have any update about my question ?

Best regards.

RE: Friendship - BLE Mesh

erdemsimsek — Fri, 17 May 2019 08:47:57 GMT

Hi Joakim,

Is the beacon device a part of BLE Mesh network?

If the answer is yes, how does updated network key transmitted to beacon device ?

Best regards

RE: Friendship - BLE Mesh

Joakim Jakobsen — Tue, 14 May 2019 10:16:16 GMT

Hi.

As the position of your battery powered tag, a friend node might not be the best solution here.

[quote user=""]Is it necessary to configure the second type node as low power node[/quote]

It isn't necessary to do this. You can use it as a normal mesh node just like all the other nodes. But the power consumption will be high, and the battery will most likely have to be charged or changed quite often. However, this might be acceptable for your usecase.

What I could suggest is configuring the battery powered tag as a beacon device. As you don't need the two-way comunication, this might be a good solution for you. Then it only needs to broadcast data when it needs to, but never stay in RX-mode listening for packets. We have a beaconing example in the nRF5 SDK for Mesh that you can take a look at.

Best regards,
Joakim Jakobsen