RE: Battery Service Good Practice

Susheel Nuguru — Tue, 06 Aug 2019 11:47:06 GMT

[quote user=""]Do I understand that the device will then send notifications to the Central device, containing the battery level? If so, does this happen on every connection or only if the level has changed?[/quote]

The example will not send the battery level on every connection interval, that would be a waste of lot of power. The sampling like you said is done based on the configurable timer expiry callback and if the sampled value is different than the one sampled before, then a notification is sent on the next connection interval. If it is same as before, then no notification is sent, as it is assumed that the central will remember the last notification value sent.

[quote user=""]What should I do with ble_bas_battery_lvl_on_reconnection_update()? The only code example I see with this is for a device operating as a Central device.[/quote]

This infocenter page says that this function can be used to send an battery level update for the bonded peers. This will be a bit faster first time update than to do the whole procedure again.

[quote user=""]Can I rely on the various constants defined in ble_app_proximity? especially DIODE_FWD_VOLT_DROP_MILLIVOLTS 270[/quote]

These are given as a reference only, these values should be adapted to your application needs. For example look at this thread

[quote user=""]Any other tips?[/quote]

All your concerns and questions are well discussed in this forum, I would recommend you to search the forum a bit to find the answers. We at Nordic take great effort to encourage the forum members to discuss things clearly, so that others like you can be benefited with that information. But to find that information, you need to put some effort to search the forum. If you have already done that, It might be tedious if you are a beginner in this forum, but trust me, there is a lot of information you can pull out once you get used to it.