RE: Switching keyboard/mouse between 3 paired devices

Kenneth — Tue, 14 Aug 2018 13:59:34 GMT

That is the correct api you can use to bond with a new central yes.

-Kenneth

RE: Switching keyboard/mouse between 3 paired devices

joric — Tue, 14 Aug 2018 09:42:52 GMT

OK I think ble_advertising_restart_without_whitelist() worked. I'll test it and maybe post full solution then.

RE: Switching keyboard/mouse between 3 paired devices

joric — Tue, 14 Aug 2018 09:14:45 GMT

I didn't quite get the thing the the address. I can change the address, but how do I advertise to a second peer when I already have one bonded peer? Should I advertise with an empty whitelist or something?

RE: Switching keyboard/mouse between 3 paired devices

Kenneth — Mon, 13 Aug 2018 11:56:47 GMT

Hi,

I guess there are difference ways of doing this, but the simplest may be to just control the GAP address for the peripheral device before starting to advertise:

    ble_gap_addr_t gap_addr;
    err_code = sd_ble_gap_addr_get(&gap_addr);
    APP_ERROR_CHECK(err_code);
        
    gap_addr.addr[3] = 1; // switch status 1, 2, or 3
    
    err_code = sd_ble_gap_addr_set(&gap_addr);
    APP_ERROR_CHECK(err_code);

That way the peripheral device will appear as a new peripheral device depending on the current GAP address, and only the specific central that have bonded with the current GAP address will connect to it.

The next problem you will face is to know which old bond you should delete if you pair with a new central. This may be solved by storing the state of the switch (or GAP address) after successful bonding by calling something like:

                uint16_t length = 8; 
                uint8_t addr[8];
                
                for(uint8_t i=0; i<BLE_GAP_ADDR_LEN; i++)
                    addr[i] = gap_addr.addr[i];
                
                err_code = pm_peer_data_app_data_store(m_peer_id,addr,length,NULL);
                APP_ERROR_CHECK(err_code);

To retrieve saved states of the switch (or GAP address) later you can call pm_peer_data_bonding_load() followed by pm_peer_delete() to delete a specific bond. You should look at the implementation of peer_list_get() on how to cycle through bonds (bonded peer id's). E.g.:

static void peer_list_find_and_delete_bonds(void)
{
    pm_peer_id_t peer_id;

    peer_id = pm_next_peer_id_get(PM_PEER_ID_INVALID);

    while (peer_id != PM_PEER_ID_INVALID)
    {
        // Call pm_peer_data_app_data_load()
        // Check stored switch (or GAP address)
        // if previously bonded you can call pm_peer_delete()
        
        peer_id = pm_next_peer_id_get(peer_id);
    }
}

Best regards,
Kenneth