How to handle a sudden disconnection of the master on the peripheral (NRF8001)

[Omnia]

Hello Nordic team,

I am working on a BLE RedBearLab shield (nrf8001) mounted on an Arduino board.

Consider that a connection is correctly made from a Master app to my nrf8001 (Peripheral) . The master have already subscribed to an advertising characteristic (with a notify mod) and every thing is fine.

If the Master suddenly stop running (for exemple if the Master is out of battery or just crashed…) I would like to know the proper way to inform my nrf8001 board that the subscription of the advertising characteristic previously made is not valid anymore.

How can I do that ? My first idea was to sent a packet every X period of time from my peripheral board with an acknowledgement and if I haven’t received any response before a pre-determined time , I can consider that the connection is lost. Is there any other/better way to do that ? How can I know that there is no more valid connection on the peripheral side?

Thanks, Regards,

[Omnia]

Thanks Ole Morten to answer to my question.

My application (Peripheral) is based on your github :: NordicSemiconducteur/ble-sdk-arduino / libraries / BLE / examples / ble_heart_rate_template /

• On the Central side I effectively have an alert when the peripheral peripheral goes out of range (iOS app).

• However, on the peripheral(nrf8001) side even if I have a ACI_EVT_DISCONNECTED (0x86) in the loop (aci_loop()) (as you made in “the ble_heart_rate_template” source code), I don’t have any callback information when I stop my application from the central side.

What/where I should have a look at the code ( ble_heart_rate_template ) to resolve this problem ? What did I do wrong ? What kind of information you need to better answer to my question ?

Thanks, Regards,