Issue: BLE Beacons RSSI and MAC Address Values are incorrect

[Dheeraj]

Hi,

I have flashed lte_ble_gateway on nRf9160 DK (PCA10090) and hci_uart on nRF52840 SoC. 

After flashing, I am getting some random RSSI values and MAC Address, instead of getting the actual MAC address of BLE beacons present nearby.

The following logs observed on Terminal which are not expected:

RSSI: -31 dB
Address: fc:9a:4d:c2:6:57:20
RSSI: -74 dB
Address: fc:9a:4d:c2:6:57:20
RSSI: -70 dB
Address: 2a:17:7c:87:40:5f:20
RSSI: -69 dB
Address: e:12:60:55:8e:67:20

In nRF Connect v3.3.0, In RSSI Viewer also no logs are observed.

Please let me know how can I get actual RSSI and MAC Address of nearby BLE Beacons.

Thanks

[Andreas]

Hi,

 

Looks like your scanner is picking up random beacons nearby, which could be all kinds of products which you have no control over. The RSSI viewer just scans the RSSI in the configured channels and does not link it to advertisements or anything.

 

Best regards,

Andreas

[Dheeraj]

Hi, 

Thank you for your reply. 

I have only two BLE beacons nearby the nRF9160 DK (PCA10090). But I am able to see so many addresses with different RSSI values. 

Please find the same on the below logs. 

Bluetooth ready
Scanning...

RSSI: -25 dB
Address: 52:cb:13:87:62:16:20

RSSI: -70 dB
Address: 3b:b2:5c:30:b4:18:20

RSSI: -48 dB
Address: 8e:a5:7b:21:18:9:20

RSSI: -82 dB
Address: 8a:9c:7a:e:e:4e:20

RSSI: -78 dB
Address: 3b:b2:5c:30:b4:18:0

RSSI: -87 dB
Address: a3:21:3d:43:bb:4a:20

RSSI: -82 dB
Address: 46:33:4:ce:2b:7e:20

RSSI: -81 dB
Address: 46:33:4:ce:2b:7e:0

RSSI: -73 dB
Address: 1e:e9:98:be:1a:6f:20

RSSI: -73 dB
Address: 1e:e9:98:be:1a:6f:0

RSSI: -71 dB
Address: 8a:9c:7a:e:e:4e:20

RSSI: -78 dB
Address: a3:21:3d:43:bb:4a:20

RSSI: -86 dB
Address: b:e1:7e:2e:4:f8:20

RSSI: -72 dB
Address: 5d:d8:8:16:98:6c:20

RSSI: -71 dB
Address: 5d:d8:8:16:98:6c:0

RSSI: -83 dB
Address: a3:28:8a:9a:d2:ef:20

RSSI: -83 dB
Address: a3:28:8a:9a:d2:ef:0

RSSI: -87 dB
Address: 88:33:ba:79:bd:54:20

RSSI: -89 dB
Address: c7:3e:30:19:6e:72:20

RSSI: -81 dB
Address: 36:e0:61:44:a2:6e:21

RSSI: -81 dB
Address: 36:e0:61:44:a2:6e:0

RSSI: -89 dB
Address: 45:c7:32:68:10:46:20

RSSI: -43 dB
Address: 7f:61:eb:ce:56:3c:20

RSSI: -82 dB
Address: 1:37:35:c2:80:6e:20

RSSI: -82 dB
Address: 1:37:35:c2:80:6e:0

RSSI: -89 dB
Address: 93:25:43:81:c8:e8:20

But from the above logs, I did NOT see my BLE beacon device address (I have cross verified). 

Please let me know if I am missing anything. 

Thank you.     

[Andreas]

Hi,

 

Are you certain you know about all BLE beacons in your area? Have you compared using nRF Connect?

 

Best regards,

Andreas

[Dheeraj]

Hi, 

Yes. My device is at home and I have only 2 BLE beacons nearby DK. I would like to capture the RSSI and the Address of those two beacons. 

Andreas said:

Have you compared using nRF Connect?

Yes. I have tried to use the RSSI viewer on nRF Connect v3.3.0. But I am getting the following Error. 

" Error while setting up device 000960041169: No firmware defined for selected device "

Please help me, how can I get the RSSI and address values of the BLE beacons, nearby. 

Thank you.  

[Andreas]

Hi,

 

I see, but there might still be devices that are advertising that your board is picking up, and unless you live in a very remote area it might be devices that do not belong to you.

I do not believe the BLE nRF Connect BLE app supports nRF9160-DK, even though it does not have a nRF52840 on it. Do you perhaps have a nRF52 DK? If not there is also a mobile (Android and iPhone) app that you can use.

 

Best regards,

Andreas

[Dheeraj]

Hi,

Thanks for your reply.

I am currently working on asset tracker application.

Actually, I need to read 128-bit UUID values of the ibeacons present nearby the board (PCA10090)  to be captured in "asset_tracker", application.

I have build and flashed lte_ble_gateway on nRf9160 DK (PCA10090) and hci_uart on nRF52840 SoC.

Looking forward to your help.

Please guide me in the correct way and let me know how to read 128-bit UUID values and implement the same for asset tracker application.