This is my output log:

D (1179) BLEUtils: Received a GAP event: ESP_GAP_BLE_SCAN_RESULT_EVT
D (1179) BLEUtils: search_evt: ESP_GAP_SEARCH_INQ_RES_EVT, bda: 74:91:ae:6f:ee:99, dev_type: ESP_BT_DEVICE_TYPE_BLE, ble_addr_type: BLE_ADDR_TYPE_RANDOM, ble_evt_type: ESP_BLE_EVT_CONN_ADV, rssi: -66, ble_adv: ??, flag: 26 ([LE General Discoverable Mode] [Simultaneous LE and BR/EDR to Same Device Capable (Controller)] [Simultaneous LE and BR/EDR to Same Device Capable (Host)] ), num_resps: 1, adv_data_len: 28, scan_rsp_len: 7
D (1212) BLEAdvertisedDevice: - setRSSI(): rssi: -66
D (1218) BLEAdvertisedDevice: Type: 0x01 (ESP_BLE_AD_TYPE_FLAG), length: 1, data: 1a
D (1225) BLEAdvertisedDevice: Type: 0x0a (ESP_BLE_AD_TYPE_TX_PWR), length: 1, data: f9
D (1233) BLEAdvertisedDevice: - txPower: -7
D (1238) BLEAdvertisedDevice: Type: 0x03 (ESP_BLE_AD_TYPE_16SRV_CMPL), length: 2, data: f018
D (1246) BLEAdvertisedDevice: - addServiceUUID(): serviceUUID: 000018f0-0000-1000-8000-00805f9b34fb
D (1255) BLEAdvertisedDevice: Type: 0x07 (ESP_BLE_AD_TYPE_128SRV_CMPL), length: 16, data: f2c3f0aea9fa158c9d49ae73710a81e7
D (1266) BLEAdvertisedDevice: - addServiceUUID(): serviceUUID: e7810a71-73ae-499d-8c15-faa9aef0c3f2
D (1275) BLEAdvertisedDevice: Type: 0x09 (ESP_BLE_AD_TYPE_NAME_CMPL), length: 5, data: 4368656765
D (1284) BLEAdvertisedDevice: - setName(): name: Chege
D (1289) SampleScan: Advertised Device: Name: Chege, Address: 74:91:ae:6f:ee:99, serviceUUID: 000018f0-0000-1000-8000-00805f9b34fb, txPower: -7
D (1303) BLEUtils: Received a GAP event: ESP_GAP_BLE_SCAN_RESULT_EVT
D (1309) BLEUtils: search_evt: ESP_GAP_SEARCH_INQ_RES_EVT, bda: 21:f9:d9:20:cf:6c, dev_type: ESP_BT_DEVICE_TYPE_BLE, ble_addr_type: BLE_ADDR_TYPE_RANDOM, ble_evt_type: ESP_BLE_EVT_NON_CONN_ADV, rssi: -44, ble_adv: ??, flag: 0 (), num_resps: 1, adv_data_len: 31, scan_rsp_len: 0
D (1334) BLEAdvertisedDevice: - setRSSI(): rssi: -44
D (1339) BLEAdvertisedDevice: Type: 0xff (ESP_BLE_AD_MANUFACTURER_SPECIFIC_TYPE), length: 29, data: 060001092002eb5c5fcff53c9a3877885f933fe159a9e2b6af1273d1b3
D (1353) BLEAdvertisedDevice: - manufacturer data: 060001092002eb5c5fcff53c9a3877885f933fe159a9e2b6af1273d1b3
D (1363) SampleScan: Advertised Device: Name: , Address: 21:f9:d9:20:cf:6c, manufacturer data: 060001092002eb5c5fcff53c9a3877885f933fe159a9e2b6af1273d1b3
D (1377) BLEUtils: Received a GAP event: ESP_GAP_BLE_SCAN_RESULT_EVT
D (1383) BLEUtils: search_evt: ESP_GAP_SEARCH_INQ_RES_EVT, bda: 49:c1:61:82:05:36, dev_type: ESP_BT_DEVICE_TYPE_BLE, ble_addr_type: BLE_ADDR_TYPE_RANDOM, ble_evt_type: ESP_BLE_EVT_CONN_ADV, rssi: -47, ble_adv: ??, flag: 26 ([LE General Discoverable Mode] [Simultaneous LE and BR/EDR to Same Device Capable (Controller)] [Simultaneous LE and BR/EDR to Same Device Capable (Host)] ), num_resps: 1, adv_data_len: 28, scan_rsp_len: 11
D (1421) BLEAdvertisedDevice: - setRSSI(): rssi: -47
D (1426) BLEAdvertisedDevice: Type: 0x01 (ESP_BLE_AD_TYPE_FLAG), length: 1, data: 1a
D (1433) BLEAdvertisedDevice: Type: 0x0a (ESP_BLE_AD_TYPE_TX_PWR), length: 1, data: f9
D (1441) BLEAdvertisedDevice: - txPower: -7
D (1446) BLEAdvertisedDevice: Type: 0x03 (ESP_BLE_AD_TYPE_16SRV_CMPL), length: 2, data: f018
D (1454) BLEAdvertisedDevice: - addServiceUUID(): serviceUUID: 000018f0-0000-1000-8000-00805f9b34fb
D (1463) BLEAdvertisedDevice: Type: 0x07 (ESP_BLE_AD_TYPE_128SRV_CMPL), length: 16, data: f2c3f0aea9fa158c9d49ae73710a81e7
D (1474) BLEAdvertisedDevice: - addServiceUUID(): serviceUUID: e7810a71-73ae-499d-8c15-faa9aef0c3f2
D (1484) BLEAdvertisedDevice: Type: 0x09 (ESP_BLE_AD_TYPE_NAME_CMPL), length: 9, data: 47616c617879205335
D (1493) BLEAdvertisedDevice: - setName(): name: Galaxy S5
D (1499) SampleScan: Advertised Device: Name: Galaxy S5, Address: 49:c1:61:82:05:36, serviceUUID: 000018f0-0000-1000-8000-00805f9b34fb, txPower: -7
D (1512) BLEUtils: Received a GAP event: ESP_GAP_BLE_SCAN_RESULT_EVT

D (3631) SampleScan: We found 3 devices
D (3635) BLEScan: >> Dump scan results:
D (3639) BLEScan: - Name: Chege, Address: 74:91:ae:6f:ee:99, serviceUUID: 000018f0-0000-1000-8000-00805f9b34fb, txPower: -7
D (3650) BLEScan: - Name: , Address: 21:f9:d9:20:cf:6c, manufacturer data: 060001092002eb5c5fcff53c9a3877885f933fe159a9e2b6af1273d1b3
D (3662) BLEScan: - Name: Galaxy S5, Address: 49:c1:61:82:05:36, serviceUUID: 000018f0-0000-1000-8000-00805f9b34fb, txPower: -7
D (3674) SampleScan: Scanning sample ended

As you can see 2 devices has given name, the third is my laptop and is not advertising name at all.
My esp-idf is master commit.

As Ingineerix says "First off: Thanks for your Awesome work Neil!"
I love BLE beacon device and your work is very usefull for me.

I have exactly the same issue as Ingineerix, I have to get the "name" of some ble beacon for my project but it always return null... I have made a test with an android application, and it s works (I get a name).

BTW, do you now a way to get the complete BLE frame (in hex) ?

thank again and best regards

dear all,

I have try to use getPayload() to check if my device name is in the payload or not,

I have had this on the toString method on the BLEAdvertisedDevice.h file

	if (haveRSSI()) {
		ss << ", Rssi: " << (int)getRSSI();
	}

	ss << "\nPayload:!!\n"<< getPayload();
	ss << "!!\n";

And the only stuff on the serial monitor is

Name: , Address: c2:00:a4:00:01:80, txPower: -16, Rssi: -66
Payload:!!
����⸮L!!

I m not familar with java but I have see TX power, name, and other stuff are parsed on BLEAdvertisedDevice::parseAdvertisement.

In my case my device name is 17 char long.

Is someone have an idea ?

For information, I use 1.8.10 arduino
regards

Hi,

I am also seeing a very similar issue, I am surrounded by BLE devices and the scan using ESP32 and the nkolban library is regularly returning 15+ addresses, but very few (maybe 1 or 2) have a name.

For info I see name for Tiles, Garmin devices, Bose headphones, Fitbits and other fitness trackers as people walk into range.
But I do not see name for any Apple devices (Watch, iPhone, iPad, AirPods) and I do not see name for any Android phones despite the fact that I have an iPhone on my desk and an Apple Watch on my wrist. I also have an iBeacon on my desk but I can't see the name for that.

I am using an active scan with the default interval and window values.

I even added this to BLEAdvertisedDevice::parseAdvertisement but it made no difference:
case ESP_BLE_AD_TYPE_NAME_SHORT: { // Adv Data Type: 0x08
if(!haveName()) {
setName(std::string(reinterpret_cast<char*>(payload), length)); }
break;
} // ESP_BLE_AD_TYPE_NAME_CMPL

If I scan using any BLE scanner on my iPhone I see names for many more devices (but certainly not all), so there must be some advertising data I am not seeing for some reason.

I have not completed my investigations yet, so maybe I will find my missing data but any help would be appreciated.

Hi,
sorry for my incompetence. Finally ive found that bug. Please try to change 31 in this line to 62.
https://github.com/nkolban/esp32-snippets/blob/master/cpp_utils/BLEAdvertisedDevice.cpp#L355

@chegewara , sorry if I’m being a bit thick, but is that value always 62? Or only 62 if parsing a scan response from an active scan?

62 bytes max. 31 bytes for advertising and 31 bytes for scan response. Its quick fix now, i will fix it later by sending length value from parameters.

https://docs.espressif.com/projects/esp-idf/en/latest/api-reference/bluetooth/esp_gap_ble.html#_CPPv2N22esp_ble_gap_cb_param_t25ble_scan_result_evt_param12ble_evt_typeE

@chegewara, Thanks for this! At least now I know I'm not going crazy. I'll try my project again.

@chegewara I changed the value to 62 and now I get back the name of the iBeacon on my desk (but only when it is connectable for some reason) but the many phones (and my apple watch) in my vicinity still return no names, so I assume they do not advertise their names even in the extra active response data.

You can check this with nRF connect on android or nRF beacon on android.

@chegewara I think my investigations are pretty much complete.

My conclusion is that the library is awesome, I have been messing about with BLE for a while but this library makes it accessible to anyone with some common sense.

Your fix in BLEAdvertisedDevice.cpp ::parseAdvertisement sizeConsumed >=62 is definitely required to get the response data.

I found some devices (maybe Garmin?) include the null terminator in the device name, which messes up your toString method (as it stops when it reaches \0). In ::setName m_name = name.c_str() fixes this.

I found some beacons (Jaalee?) only advertise the short name so I added in ::parseAdvertisment
case ESP_BLE_AD_TYPE_NAME_SHORT: { // Adv Data Type: 0x08
if(!haveName()) {
setName(std::string(reinterpret_cast<char*>(payload), length));
}
break;
} // ESP_BLE_AD_TYPE_NAME_SHORT

I found many devices don't advertise any name at all or more annoyingly only advertise a single space 0x20 (???) but your amazing method BLEDevice::getValue(address, BLEUUID((uint16_t)0x1800), BLEUUID((uint16_t)0x2A00) ) will get something reasonable back. I am assuming that, if you can connect at all, the Generic Access service will be available but I do get a few hangs from time to time so maybe not! I might add a ::haveService method to your library, also is there a way to tell if a device is connectable before I try to connect?

I have found that if you don't get back what you expect (especially from an Apple device) maybe iPad rather than Name's iPad or iPhone rather than Name's iPhone then this is because it isn't being transmitted, I'm sure there is a way but I don't know it yet. Interestingly my household is totally devoid of Android devices which probably indicates that I am giving my kids too much pocket money.

On a final note, is there any way to set a timeout on BLEClient::connect as I have found this call can take an absolute age when failing to connect?

Hi,
thanks for taking time to describe all your findings. I hope we all can learn something from that.

There is few things i can help you with. First of all, service 0x1800 is obligatory and evry single ble device that you can connect to will have it, also characteristic 0x2A00. But you have to know that value of this characteristic can be empty string or something not printable.
Next, there is few bugs in this library i am just discovering. To be honest i didnt look through code to search for any, but now i am working hard on improving this library. You are having difficulties to connect to some devices because of this line:
https://github.com/nkolban/esp32-snippets/blob/master/cpp_utils/BLEClient.cpp#L114
as you can see here we have hardcoded what kind address is using peer device you are trying to connect and most of peripherals, and all apple devices are using not public address. Its to keep privacy and do not allow to keep tracking device. It has been fixed in code i am working on now, but its not merged yet. Another thing is that esp-idf bt stack have bug with this parameter, all not public addresses are recognized as RANDOM.
If you wish you can prepare merge with addition to BLEAdvertising to parse short data also with fix to parsing response packet too.

If you are brave you can try my latest code:
https://github.com/chegewara/esp32-snippets-enchancements-test/tree/multi_connect_test

parsing scan response fixed by a4e3d43.

I will add short name parse when i have time and dont forget about it.

Hi,
I have a question that's kinda related to this thread.
Is there a way to get the raw names of the found devices?
something like foundDevices.getName() ?
I searched a lot and was unable to find some useful information...

I wand to use this to get by the apple mac address randomization.
I want to use an app like "nrf connect" to make an advertiser with an name to trigger an action the esp32?

Is this impossible or am I just to stupid to find the way?

thanks and best regards

I'm not sure I understand what you require but you could try something like:
for(int idx(0); idx < foundDevices.getCount(); ++idx)
{
std::string deviceName = foundDevices.getDevice(idx).getName();
}

That's exactly what i meant.
Thanks

@chegewara Did you ever get round to also implementing short name parsing?

Thanks,
Arjan

First of all thanks for fixing the „31/62“ issue. Though it now works in the first scan, all following scans (15 sec delay between scans) do not show any device name. Any solution for that?

I'm also only seeing the name only on the first scan. I'm just starting to dig into but the data length passed to the parseAdvertisement is shorter by the length of the name + 2. Coincidence?

Its hard to do anything if i cant reproduce issue:

03:27:33.927 -> Device: 
03:27:33.927 -> TX power => -7
03:27:33.927 -> RSSI => -96
03:27:33.927 -> Name: Chege
03:27:34.226 -> Device: 
03:27:34.226 -> TX power => -7
03:27:34.226 -> RSSI => -85
03:27:34.226 -> Name: Chege
03:27:34.493 -> Device: 
03:27:34.493 -> TX power => -7
03:27:34.493 -> RSSI => -85
03:27:34.493 -> Name: Chege
03:27:34.792 -> Device: 
03:27:34.792 -> TX power => -7
03:27:34.792 -> RSSI => -86
03:27:34.792 -> Name: Chege
03:27:35.092 -> Device: 
03:27:35.092 -> TX power => -7
03:27:35.092 -> RSSI => -84
03:27:35.092 -> Name: Chege
03:27:35.658 -> Device: 
03:27:35.658 -> TX power => -7
03:27:35.658 -> RSSI => -89
03:27:35.658 -> Name: Chege
03:27:36.233 -> Device: 
03:27:36.233 -> TX power => -7
03:27:36.233 -> RSSI => -91
03:27:36.233 -> Name: Chege
03:27:36.529 -> Device: 
03:27:36.529 -> TX power => -7
03:27:36.529 -> RSSI => -81
03:27:36.529 -> Name: Chege

My peer device is android smartphone running nRF connect with advertising.
Here is scan callback:

class ScanResults: public BLEAdvertisedDeviceCallbacks {
  void onResult(BLEAdvertisedDevice device)
  {
    if(device.haveName())
    {
      Serial.printf("Device: \nTX power => %d\nRSSI => %d\n", device.getTXPower(), device.getRSSI());
      Serial.printf("Name: %s\n", device.getName().c_str());
    }
  }
};

I can only say that i am running this code on platformio with arduino + esp-idf, wifi and mqtt (code omitted).

PS scan for 10 or 30 sec, delay 1000ms between scans

Perhaps a better test would be: don't filter on the devices where the name is there but print all the devices picked up in the scan and see if the name on any of them disappears on subsequent scans.

I looked into it a bit but decided to use the service UUID instead. It was happening consistently with me so I might have time to do some testing - if you want to suggest some things to try.

My use case is that I am trying to connect to multiple nrf52840s that are running the same code (arduino+adafruit_ble) with the same service UUIDs and the same 5 characteristics (we already know the arduino code doesn't handle multiple characteristics and I've posted a fix for that somewhere). I can't remember whether the problem happens when only a single device is active or whether is requires multiple devices to be active.

I'm also using pio+arduino+esp-idf.

Perhaps a better test would be: don't filter on the devices where the name is there but print all the devices picked up in the scan and see if the name on any of them disappears on subsequent scans.

I am using filtering here only to show it is working. This issue title stands that name is ALWAYS null, and i am providing logs that i can scan very quick, multiple times and get peer device name every time, just check timestamps.
My test code is very simple, i dont even use any special scan settings now and i really dont know what i can do to reproduce this or any similar issue with advertised name.

I even thought it may be issue when name is split between advertising packed and scan response packet, but code should handle this case too:
https://github.com/nkolban/esp32-snippets/blob/master/cpp_utils/BLEScan.cpp#L119

If I get time later in the week, I'll make a repo with the client and server code that generates the issue (It could be in the adafruit stack or, of course, my own error). Thanks for taking the time to look at it - I do appreciate your hard work.

Has anyone found a workaround for this issue?

Using BLE server and scanner example sketches in Arduino, names are empty even for devices that labelled using BLEDevice::init

Example:
BLEDevice::init("ESP32 1-18");

BLE Advertised Device: Name: , Address: 76:e9:c4:7d:9b:b2, manufacturer data: 4c0010067119799a1180, txPower: 7
BLE_Address: 76:e9:c4:7d:9b:b2
RSSI: -99
name of device:  .
BLE Advertised Device: Name: , Address: 38:0b:84:57:35:3a, manufacturer data: 060001092002cd6159c4eb148b0ed9dfcb3dce2831423c0a99128a30e1
BLE_Address: 38:0b:84:57:35:3a
RSSI: -91
name of device:  .
BLE Advertised Device: Name: , Address: 61:9c:64:5f:6d:0a, manufacturer data: 4c00071901022002f58f000000644d70096bec6bd59cccb62465737f4b
BLE_Address: 61:9c:64:5f:6d:0a
RSSI: -93
name of device:  .
BLE Advertised Device: Name: , Address: 5e:54:bf:65:ad:b8, manufacturer data: 4c0010050318945f66
BLE_Address: 5e:54:bf:65:ad:b8
RSSI: -95
name of device:  .
Devices found: 4
Scan done!
BLE Advertised Device: Name: , Address: 76:e9:c4:7d:9b:b2, manufacturer data: 4c0010067119799a1180, txPower: 7
BLE_Address: 76:e9:c4:7d:9b:b2
RSSI: -90
name of device:  .
BLE Advertised Device: Name: , Address: 61:9c:64:5f:6d:0a, manufacturer data: 4c00071901022002f58f0000004b21b5f69a3fcf2050a3a63265892a05
BLE_Address: 61:9c:64:5f:6d:0a
RSSI: -95
name of device:  .
Devices found: 2
Scan done!

I managed to fix this issue, well, sort of... The library isn't using the ESP_BLE_AD_TYPE_NAME_SHORT Advertising Type in the BLEAdvertisedDevice.cpp file in the parseAdvertisement sub... So, I added it in, and hey presto... Problem solved...

My fork is here... https://github.com/pjgpetecodes/ESP32_BLE_Arduino.

The code is basically...

case ESP_BLE_AD_TYPE_NAME_SHORT: {   // Adv Data Type: 0x08
    setName(std::string(reinterpret_cast<char*>(payload), length));
    break;
}// ESP_BLE_AD_TYPE_NAME_SHORT
case ESP_BLE_AD_TYPE_NAME_CMPL: {   // Adv Data Type: 0x09
    setName(std::string(reinterpret_cast<char*>(payload), length));
    break;
} // ESP_BLE_AD_TYPE_NAME_CMPL

However, I've left in the full name, which I could possibly cause an issue... Need a way of choosing between them, or perhaps adding in the functions for short name as well as name perhaps?

Hi, is there any fix for the getName() issue which returns names in the first scan and returns nothing after that. I would highly appriciate if i can be pointed out to resolving the issue. Thanks in advance

I am using ESP32 HUZZAH Feather and trying to run BLE_scan sample.

I found out that name is returned using getName() , it is returned in every scan, but if I call getRSSI() the name will no longer be returned in the next scans.
So looks like getRSSI() is causing the issue, if I don't call it the name will be returned...strange

I found out that name is returned using getName() , it is returned in every scan, but if I call getRSSI() the name will no longer be returned in the next scans.
So looks like getRSSI() is causing the issue, if I don't call it the name will be returned...strange

I found this article posted which does a BLEDevice::init("myBLEScan"); in the loop and at the end of scan process BLEDevice::deinit(false);
I have not checked the impact on the code of initializing every loop and scan but it does consistently gives all the outputs.

espressif/arduino-esp32#3677 (comment)

Hope this helps as a quick fix.

I've submitted this PR to espressif arduino-esp32 which seems to resolve the scan issues described here:

espressif/arduino-esp32#4126

This is still not registering the name and is quite frustrating. Is there any progress on the matter? When I run the scan it will not populate with my ESP32 device name.

@chegewara any help would be appreciated.

Hi,
like i mentioned many times i dont have that problem, but i am guessing i just didnt test all possible scenarios.
Maybe raw advertising data could say more if you can take it with nRF connect. I also no longer work on this library, just trying to provide some support answering in issues with best of my knowledge.

Thank you for getting back so quickly @chegewara and I will continue to try to experiment however I have tried all versions of the library and in all circumstances I get:
Name: , Address: 55:44:33:22:11:11, manufacturer data : blah
The name does not appear however is found on any Android or iPhone with any Bluetooth app. This is challenging because there is no way the ESP32 can detect another as from my experience when you reformat a device the manufacturer data and the address changes. If anyone has a work around I would love to hear.

Have you applied the changes in the PR I linked above?

Have you applied the changes in the PR I linked above?

@buxtronix I have I added:
m_scan_params.scan_duplicate = BLE_SCAN_DUPLICATE_DISABLE;
It is still showing:
Advertises Device: Name: , Address...

On the server ESP32 I tried both the BLE_server and BLE_server_multiconnect and they both allow me to find the device on my phone. I wonder if the BLE_scan example is not actually finding the other device at all.

My goal is to simply use a BLE_scan example to find a name of an ESP32 that I can check for.

I assume that Advertises Device: Name: , Address... will populate when i set:
BLEDevice::init("ESP_32");

Or is there another BLEDevice param that I need to set for this to work?

So.... It turns out I had a bad BLE device in my ESP32. I tested again with @buxtronix code and it works. Sorry for any confusion.

@buxtronix

BLEScan::BLEScan() {
memset(&m_scan_params, 0, sizeof(m_scan_params)); // Initialize all params
m_scan_params.scan_type = BLE_SCAN_TYPE_PASSIVE; // Default is a passive scan.
m_scan_params.own_addr_type = BLE_ADDR_TYPE_PUBLIC;
m_scan_params.scan_filter_policy = BLE_SCAN_FILTER_ALLOW_ALL;
m_scan_params.scan_duplicate = BLE_SCAN_DUPLICATE_DISABLE;
m_pAdvertisedDeviceCallbacks = nullptr;
m_stopped = true;
m_wantDuplicates = false;
m_shouldParse = true;
setInterval(100);
setWindow(100);
} // BLEScan

but it still does not work:(