ble_gap_addr_t address is not right?

RE: ble_gap_addr_t address is not right?

qoboty — Wed, 23 Dec 2015 07:39:55 GMT

I use nRF UART V2.0 app in two different phone. I got different peer_address.addr_type. how to use the public address (peer_address.addr_type=0) when connect to device ??

RE: ble_gap_addr_t address is not right?

qoboty — Wed, 23 Dec 2015 07:34:37 GMT

how to set type =0 in android app ? is there an API ??

RE: ble_gap_addr_t address is not right?

RK — Wed, 23 Dec 2015 07:26:25 GMT

The address is right in both cases, when the type is '1' it's a random static address which isn't going to be the same as the public static address, because it's random. In both cases that's the address the link is using.

RE: ble_gap_addr_t address is not right?

qoboty — Wed, 23 Dec 2015 07:22:40 GMT

when I chang code to below:

peer_address =p_ble_evt->evt.gap_evt.params.connected.peer_addr

I got the correct bluetooth address sometimes. sometimes I got wrong address,when I debug peer_address.addr_type, I find out, when peer_address.addr_type=0 , peer_address is same with the phone address, when peer_address.addr_type=1, the address is wong ! how to get the correct address whether peer_address.addr_type is 0 or not? Thanks!

RE: ble_gap_addr_t address is not right?

monpetit — Wed, 23 Dec 2015 06:34:02 GMT

@RK: I see. Thank you. :)

RE: ble_gap_addr_t address is not right?

RK — Wed, 23 Dec 2015 06:29:30 GMT

It's not a bug - your code is correct because it gets the correct event type out of the event, his gets the 'scan request' structure out, however what's in there isn't a scan request, so the data is wrong.

RE: ble_gap_addr_t address is not right?

monpetit — Wed, 23 Dec 2015 06:22:23 GMT

I don't know whether it is a bug or not. But you can avoid this problem with modifying your code like this:

peer_address = p_ble_evt->evt.gap_evt.params.connected.peer_addr;