Which is the most efficient way to disable and enable Bluetooth mesh stack in order to extend battery life?

[harid]

Hi,

I am using sensor server model to build our application on top of it. We want to save juice in the battery as much as possible. In order to that, I must disable bluetooth mesh stack and enable the stack on a periodic basis. On enabling, the node should publish data to the destined address (Set through model configuration) and the stack should be disabled immediately and enabled after a specific interval for periodic publishing.  I do not want to use low power node feature as we only want to publish the data and not poll data from a friend node. What would be the efficient way to achieve this? Thanks in advance.

Best Regards,

Hariharan D

[Einar Thorsrud]

Hi Hariharan,

If you are using the nRF Connect SDK you can use bt_mesh_suspend() to temporarily suspend the meth network. Then use bt_mesh_resume() to resume at a later point

How is this intended to work on the system level? Is this a mesh of only/mostly this type of device? If so, it seems like a problem that most devices sleep most of the time, as when a device wakes up to publish data there will perhaps not be any others awake to receive it.

Einar

[harid]

Hi Einar,

Thank you for getting back to me. I am not using nRF Connect SDK. I am using the nrf5 mesh SDK. The role of the sensor server node device would be to only publish data periodically (and going to sleep in between) to a constantly listening sensor client node. So, the case you mentioned will not happen in our design.

[Einar Thorsrud]

Hi,

For the nRF5 SDK you have the mesh_stack_power_down() function. See this thread. You should also be aware of the issue (and fix) described in this thread.

[harid]

Thank you Einar for the sugggestion. What would be the preferred way to enable the mesh stack again?

[Einar Thorsrud]

Hi,

This disables the mesh stack so it has to be initialized again. I must admit I have not had a chance to look into the details, but I would expect you need to do more or less the same sequence as you do at startup.