RE: BLE_OBSERVER_PRIO - priorities with Advertising and the Connection State module

awneil — Thu, 30 Apr 2020 12:53:25 GMT

Thanks.

I went for the 1st option - adjusting priorities.

RE: BLE_OBSERVER_PRIO - priorities with Advertising and the Connection State module

Vidar Berg — Thu, 30 Apr 2020 12:21:46 GMT

Hello,

[quote user=""]It looks like this is due to the altered priorities - so the Connection State module is not seeing the events until after the application and the advertising modules.[/quote]

Yes, this is the problem. The connection state module use observer priority '0' by default, same as the app in this case, so it's not guaranteed to receive the event first.

I see two solutions to this. One is to reduce the priority of the advertiser module (BLE_ADV_BLE_OBSERVER_PRIO), so you can set APP_BLE_OBSERVER_PRIO to '1' or more. The other option is to set the .ble_adv_on_disconnect_disabled flag to prevent the module from automatically starting advertising on disconnect events. You can start advertising when receiving the disconnect event inside your app handler instead.