This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Strategy for sending alert to phone from nrf52

Hello,

I am trying to create an application that sends a notification from the nrf52 to a smartphone when a sensor reading exceeds a certain value. Would the immediate alert service be appropriate here, or should I just add a characteristic to my custom service that indicates when my reading is too high? I am very concerned about power usage, so any solution that minimizes radio communication is preferred. Thanks.

I've looked for other solutions on the forum but haven't found anything; if I've missed something please point me in the right direction

Other info: Eclipse 4.5.2 PCA10040 SDK 13.0 or 13.1 (not sure where to find the difference)

Parents
  • The power consumption is more or less set by the architecture: you either use the connection link (and then both devices must do Tx/Rx more or less at every connection interval) or you use broadcasting/observing only. In general it's only about what reliability and latency you need, power consumption is just consequence of these parameters...

  • The trick of "immediate" notification can be done by GATT Write method (if you are on GATT Client side) or by GATT Notify method (if you are on GATT Server side - this is more likely based on your hints and based on "usual" architecture of BLE apps on mobile devices, note that in order to receive these notifications on GATT Client side you need to enable them after connection by writing to CCCD of your custom Characteristic, however this is well known procedure present in every Mobile App BLE tutorial).

Reply
  • The trick of "immediate" notification can be done by GATT Write method (if you are on GATT Client side) or by GATT Notify method (if you are on GATT Server side - this is more likely based on your hints and based on "usual" architecture of BLE apps on mobile devices, note that in order to receive these notifications on GATT Client side you need to enable them after connection by writing to CCCD of your custom Characteristic, however this is well known procedure present in every Mobile App BLE tutorial).

Children
No Data
Related