Identify Device Based on Advertising Data

RE: Identify Device Based on Advertising Data

danbujak — Wed, 02 Sep 2015 00:40:48 GMT

I just realized that I need to also identify which device was bonded with under device_manager_event_handler(). Can you let me know what parameter I can correlate here? Currently I'm storing p_ble_evt->evt.gap_evt.conn_handle on connection but it doesn't match the p_event->event_param.p_gap_param->conn_handle I have at bonding.

RE: Identify Device Based on Advertising Data

danbujak — Wed, 02 Sep 2015 00:17:52 GMT

Thanks, I was checking the address in the device_manager_event_handler() for the connection event, but I'm looking under on_ble_evt() now.

RE: Identify Device Based on Advertising Data

danbujak — Fri, 28 Aug 2015 16:12:46 GMT

Where should I be identifying the peer address? I tried doing what I describe in my edit above, but like I say, the addresses do not match in the last byte.

RE: Identify Device Based on Advertising Data

Anders Strand — Fri, 28 Aug 2015 08:55:34 GMT

Hey!

I would create a data struct for each device with the following info:

Peer Adress
Peer Configuration (A or B)
Connection Handle

When reading the advertisement report and deciding to connect, save the peer address along with the configuration. When the connection event happens. Find the correct device data struct, and fill inn the connection handle. When the disconnect (or other events) happen, use the connection handle to identify the device, and check the corresponding configuration.

EDIT: If the addresses of the two devices are identical for some reason, you can add a custom read only characteristic to your service which describes the configuration.

EDIT2, finding the addresses: This is where you should find the address in the two events:

        case BLE_GAP_EVT_CONNECTED:
			adress = p_ble_evt->evt.gap_evt.params.connected.peer_addr;
			break;
		case BLE_GAP_EVT_ADV_REPORT:
			adress = p_ble_evt->evt.gap_evt.params.adv_report.peer_addr;
			break