BLEScan can't find all Bluetooth devices around me

[rfrferreira]

Hi there,

I'm using Arduino IDE do code my ESP32 and I'm having problems in identifying all the Bluetooth devices around me, it seems that ESP32 is not able to find, for example, my phone.

Note: For context, I'm trying to scan Bluetooth devices to save the Mac Addresses from the 3 devices with the strongest signal in order to send those Mac Addresses through an http request to verify if they're authorized devices to connect or not.

#include <BLEDevice.h>
#include <BLEUtils.h>
#include <BLEScan.h>
#include <BLEAdvertisedDevice.h>

const int buttonPin = 36;     // the number of the pushbutton pin
//const int ledPin =  13;      // the number of the LED pin

// variables will change:
int buttonState = 0;         // variable for reading the pushbutton status
int scanTime = 20;

class MyAdvertisedDeviceCallbacks: public BLEAdvertisedDeviceCallbacks {
    void onResult(BLEAdvertisedDevice advertisedDevice) {
      Serial.printf("*** Advertised Devices ***\n");
      Serial.printf("Name: %s // Address: %s // RSSI: %d \n\n", advertisedDevice.getName(), 
advertisedDevice.getAddress().toString().c_str(), advertisedDevice.getRSSI());
    }
};

void setup() {
  pinMode(buttonPin, INPUT);
  Serial.begin(115200);
}

void loop() {
  // read the state of the pushbutton value:
  buttonState = digitalRead(buttonPin);
  //Serial.println(buttonState);

  if (buttonState == HIGH) {
    Serial.begin(115200);
    Serial.println("Scanning...");

    BLEDevice::init("");
    BLEScan* pBLEScan = BLEDevice::getScan(); //create new scan
    pBLEScan->setAdvertisedDeviceCallbacks(new MyAdvertisedDeviceCallbacks());
    pBLEScan->setActiveScan(true); //active scan uses more power, but get results faster
    BLEScanResults foundDevices = pBLEScan->start(scanTime);
    Serial.print("Devices found: ");
    Serial.println(foundDevices.getCount());
    Serial.println("Scan done! \n");
  }
}

[Donderda]

Only to play it safe: You are sure your device is advertising itself and isn't "just" a BT-Classic device? Are you able to scan and find it with another device via BLE?

[rfrferreira]

@Donderda thank you for answering. Yes, I think it+s advertising. As I read here and in other places, it seems that ESP32 can't scan classic Bluetooth devices, scanning only the BLE devices, is that right? Is there any way to go around that? I'm trying to catch smartphones mac addresses in order to check if the user is authorized to enter the building by unlocking the door.

Thanks in advance

[Donderda]

Sorry, I'm not specialised in BT-Classic stuff :(. I'm also not sure whether it's a good idea to fetch your smartphone's BT MAC address for unlocking doors :p. AFAIK e.g. Apple changes the MAC of the BT(LE?) Controller...

But maybe someone else knows more about this topic...

[rfrferreira]

Thank you :)

[MehmetCagriK]

There may be many reasons for it. For debugging, I suggest you to use NRFConnrct, LightBlue or BlueCap apps to scan and cross check with your ESP32's results. Addition: Even though you are sure there is a working BLE device around, they might be using directed advertising or disabled their discovery. From my smartphone or ESP32, I can not discover some BLE peripheral devices like watches or heart rate monitor for example since those are personal devices.

[waldorffsmama]

BLE-scan can will only detect BLE-devices (Bluetooth Low Energy). Your phone must be configured as a beacon to be detectable with BLE-functions. There are apps which will let your phone simulate a beacon but the more elegant way to achieve your goal is using the classic Bluetooth serial libraries and start from there.

[MehmetCagriK]

BLE-scan can will only detect BLE-devices (Bluetooth Low Energy). Your phone must be configured as a beacon to be detectable with BLE-functions. There are apps which will let your phone simulate a beacon but the more elegant way to achieve your goal is using the classic Bluetooth serial libraries and start from there.

To prevent any confusion, do you mean iBeacon? Phones do not necessarily have to simulate beacons but can simulate regular Bluetooth peripherals.

[waldorffsmama]

Nope, not an iBeacon. Any phone with a bluetooth chip 4.0 or higher should be capable of simulating Bluetooth Low Energy beacons. I am using Beacon simulator. You can simulate a beacon and in the settings make it "resilient", so it stays on even if you restart the phone

[chegewara]

Its not beacon simulating. Since android 5.0 every android device with ble 4.0 chip should be capable of advertising like any any other peripheral devices can do. Best start is with nRF connect.

[waldorffsmama]

Its not beacon simulating. Since android 5.0 every android device with ble 4.0 chip should be capable of advertising like any any other peripheral devices can do. Best start is with nRF connect.

You are right in saying that they are capable of advertising. They just don´t do it. And that is why a Beacon simulator is a useful tool. I was not capable of reading out the MAC address of my phone with any BLE-lib based sketch. You would need a classic bluetooth library but the only one which I have seen so far is BluetoothSerial.h and that is not good for anything, really. See https://www.esp32.com/viewtopic.php?f=19&t=7728&p=34802&hilit=bluetooth#p34802 (does not suppoort values like signal strength, MAC address, etc)

If you have any better ideas to scan and recognize the MAC of an android phone with the ESP32, I would be interested to learn how

[chegewara]

That's not true. I can read my Samsung s4 and s9+ with this exactly library every single time. Like I said, use nRF connect as starting point.

[waldorffsmama]

Interesting. My OnePlus 3t is not being recognized. Now I do have nRF connect installed but would it find my own phone? Improbable.

[chegewara]

No, you can't scan for your own advertising.

[z4nD4R]

Hello All,

I'm facing the same issue over here. I'd like to build simple presence sensor based on BT, but my Honor 9 (neither iPhone of my gf) aren't recognized.

As far as I understand it correctly it is caused by the fact the smartphones aren't advertising? Or Am I missing smth? (I'm using BTE_scan example without any modification).

Is there any way how to solve it?

PS: my FitBit band is recognized everytime without any issues.

Thx.

Y

[MehmetCagriK]

Hello All,

I'm facing the same issue over here. I'd like to build simple presence sensor based on BT, but my Honor 9 (neither iPhone of my gf) aren't recognized.

As far as I understand it correctly it is caused by the fact the smartphones aren't advertising? Or Am I missing smth? (I'm using BTE_scan example without any modification).

Is there any way how to solve it?

PS: my FitBit band is recognized everytime without any issues.

Thx.

Y

Smartphones are not specialized Bluetooth consumer products. Therefore, they would not advertise in BLE even though you enabled Bluetooth via settings. You might want to use various BLE applications that mimic different BLE profiles. For example, LightBlue app for IOS can create virtual peripherals(such as Heart Rate) that would probably allow you to scan with ESP-32.

[z4nD4R]

@MehmetCagriK

thank you for your swift response. You're right, indeed with nRF Connect app I'm able to create advertisment profile and then BLE_scan basic example is able to find my phone. Unfortunately that isn't much confortable wasy as it only works while App is running, and so doesn't really met the expectation.

Do I understand it correctly, the problem here is the ESP32 is looking for BLE devices but smartphones are in default not set to behave like that? Is there any option to scan for "Normal" Bluetooth devices?

As far as I remember correctly I was able to detect my smartphone without any issue with python and pybluez lib, but I suppose is different kind of story.

Y

[MehmetCagriK]

Yes, smartphones does not automatically advertise in BLE since they are not BLE product like a HeartRateMonitors, so it would not make sense that a smartphone advertise in BLE.

According to the datasheet of ESP-32, it does only have BLE Radio(hardware) and is not hybrid hardware like phones have. Without classic Bluetooth Radio, you can not sense Bluetooth devices.

Your best bet is using your phone and ordering another ESP-32, they are really cheap(I have 5 of them from Banggood) and use spare ones as peripherals.

[z4nD4R]

Your best bet is using your phone and ordering another ESP-32, they are really cheap(I have 5 of them from Banggood) and use spare ones as peripherals.

Did you mean just use spare ESP-32 as some kind of "BLE key fob"? Or maybe there is some?

Y

[MehmetCagriK]

You can use second ESP-32 as advertiser device, like NRF Connect allows you. The second one would be always working, so better option than trying to use phone if you need a constantly working BLE advertiser. I assume you need a device that is always on so you can easily develop your software.

[z4nD4R]

Your assumption is right, but I didn't get it. Do you mean to develop small moveble ESP-32 with battery? Wouldn't be easy to use smth like: https://www.global-tag.com/portfolio/keyfob-beacony-ble-keychain/ ?

[MehmetCagriK]

You can buy it but with another ESP-32 you would be more flexible, since you can not program BLE keychain. But if you only want to develop Presence Sensor, BLE keychain would work jsut fine.

[z4nD4R]

That's exactly my point. I'm looking for presense sensor and therefore some cheep BLE keychain (can buy for 1-2$) will be enough.

Most probably I'll go this way. Anyway thanks a for explanation about how BLE works on ESP-32.

Much appreciated.

Y

[MehmetCagriK]

You are welcome.

[waldorffsmama]

It seems there is great interest in scanning for classic bluetooth devices. But I still haven´t found out on how to get it work. My idea is to unlock a door as long as my phone is in range without any need to constantly run a beacon on the phone

[MehmetCagriK]

Why would you use classic bluetooth devices? Should not low energy option be great for that kind of operation, by the name implying lower energy consumption? And your phone must be always advertising IF you want it to be automatically recognized by the door. Otherwise, you have to manually use your phone to activate Bluetooth advertisement.

[waldorffsmama]

Mehmet, some people have classic Bluetooth activated all the time as they might use their phone constantly in the car or so. Lower energy consumption is not my concern. Phone gets recharged anyhow at night.

What do you mean with "the phone must be always advertising IF"?

[MehmetCagriK]

I do not know specifics of Classic Bluetooth honestly. Per my research, car bluetooth connects to your smartphone, so it must be periodically scanning bluetooth devices after car power is on. But ESP-32 is not the device that supports Classic Bluetooth protocol, if that is your purpose.

[waldorffsmama]

Mehmet, the ESP32 actually does support Classic Bluetooth and there is a library. I have managed to compile a test-sketch on the IDF but my programming skills are rudimentary and working with the espressif IDF is not easy for me.

Anyhow, I do appreciate your effort here. Thanks for your clarifications!

[arunbm123]

Hello Is there a limitations on how many beacons esp32 can scan.i have some 100beacons. Esp32 crashes when all are made on

[chegewara]

Probably you are run out of heap. This is very good example to study the case: https://github.com/tobozo/ESP32-BLECollector

@tobozo did great job

[marcoavaccaro]

Hello, i'm making a project where the ESP32 scans every 5sec for ble beacons on range and send their mac address and rssi to the clould. For me is better that the scan is made more frequently, but if i down the scan time the ble cannot found every ble beacon on range.

My question is: I'm programming my esp32 in arduino ide and using the lib "ESP32_BLE_Arduino". Does this lib have some configuring for me to find more devices in less time?

Any tips are welcome also.

I did a test with different scan times, this is the result.

Thanks

[Donderda]

Maybe you should have a look at the configuration of your beacon: they send their data in (maybe configurable) intervals.

Am 27.03.2019 um 18:09 schrieb Marco Antônio Vaccaro notifications@github.com:

Hello, i'm making a project where the ESP32 scans every 5sec for ble beacons on range and send their mac address and rssi to the clould. For me is better that the scan is made more frequently, but if i down the scan time the ble cannot found every ble beacon on range.

My question is: I'm programming my esp32 in arduino ide and using the lib "ESP32_BLE_Arduino". Does this lib have some configuring for me to find more devices in less time?

Any tips are welcome also.

I did a test with different scan times, this is the result.

Thanks

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[marcoavaccaro]

@Donderda It's worked. I down the tx time of the beacons (3s to 1s) and now with a scan time of 5s i always find my beacons.

Thanks

[alviyandi]

Why can't the eps 32 Ble Scanner program prevent Bluetooth from mobile phone Samsung? please provide a solution

[Donderda]

Sorry, I did not understand your question. What exactly is your problem?

On 4. Nov 2019, at 08:30, alviyandi notifications@github.com wrote:

Why can't the eps 32 Ble Scanner program prevent Bluetooth from mobile phone Samsung? please provide a solution

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nkolban/esp32-snippets/issues/578?email_source=notifications&email_token=AA4FKPTVH2T2YOGRRMD7753QR7FQ5A5CNFSM4FGPR3JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC6NJOY#issuecomment-549246139, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FKPUT6PPPZIXJCKQUWODQR7FQ5ANCNFSM4FGPR3JA.

[alviyandi]

Why is the BLE ESP32 Scanner Program, Bluetooth Mobile Phone is not detected? Please give the solution

[Donderda]

The scanner scans only for Bluetooth Low Energy devices. Are you sure your mobile phone is capable of that feature? Are you sure it sends BLE packages?

On 4. Nov 2019, at 10:17, alviyandi notifications@github.com wrote:

Why is the BLE ESP32 Scanner Program, Bluetooth Mobile Phone is not detected? Please give the solution

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nkolban/esp32-snippets/issues/578?email_source=notifications&email_token=AA4FKPSRKT4O2SNDRHZAWVTQR7SDTA5CNFSM4FGPR3JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC6TQFI#issuecomment-549271573, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FKPX7PE6SIX4OGWO6HHTQR7SDTANCNFSM4FGPR3JA.

[jigassa]

I have the same problem like some people here. But my idea was, if i put the ESP32 on server or notify mode, and connect my phone to him.

There is some way to know the mac address of who is connected to my ESP32 server?

If it is, when you are in range, the phone connect itself, the ESP32 see the mac address in the "handshake" and do stuff.

[chegewara]

I see this problem a lot, but it is really hard to help because i cant reproduce it. I am using esp32 ble a lot and i did not have 1 case when esp32 didnt scan as expected or maybe just im not doing very acurate tests.

There is some way to know the mac address of who is connected to my ESP32 server?

yes, but there is few problems:

• you have to use ble scan on esp32 to discover other devices,
• device you want to find, which is smartphone i presume, is using random mac, which means you have to pair with it, then it can be discovered even if change mac address,
• you can use server and client on esp32 at the same time, or even switch roles, but you need to have more advanced knowledge

[mobby6kl]

Hi, I'm also having trouble detecting the one BT device I actually need. I bought this exact remote control for my project:

The ESP never finds it, but I can connect to it with the phone or desktop PC. NRFConnect doesn't seem to find it during the scan either for some reason, but as I mentioned it actually connects fine:

The seller didn't say exactly that it was BLE, but I would assume so - the device is even called BLE and runs from a coin cell. Is there a quick way to make sure? I'd rather not spend a day learning Bluetooth Classic just to test it that way.

The VR Box controller (as in the screenshot) actually is detected fine, but it's not suitable for this project unfortunately.

[chegewara]

nRF connect is only BLE suitable app, so if you can scan and/or connect using it then its ble device.

NRFConnect doesn't seem to find it during the scan either

probably there is very long interval between advertising, which in other hand is very short. Its due to preserve battery

[rrn04]

I am building a project wherein, if two esp32 comes closer than a particular distance both esp32 should turn their inbuild led. I am successful in searching my laptop and turn on the built-in led of one esp32 by the following code:

include

include

include

const int PIN = 2; const int CUTOFF = -60; int rssi;

void setup() { pinMode(PIN, OUTPUT); BLEDevice::init(""); Serial.begin(9600); }

void loop() { BLEScan *scan = BLEDevice::getScan(); scan->setActiveScan(true); BLEScanResults results = scan->start(1); int best = CUTOFF; for (int i = 0; i < results.getCount(); i++) { BLEAdvertisedDevice device = results.getDevice(i); rssi = device.getRSSI(); if (rssi > -60) { best = rssi; Serial.print(best); } } if(best>CUTOFF) digitalWrite(PIN, HIGH); else digitalWrite(PIN, LOW); } @MehmetCagriK , Thank you for the discussion above (even though it was 2 years back). It helped me to understand why my phone or bt speakers were unable to be detected. Can you please answer my question mentioned below?

Also can anyone please answer this: " Is it possible to search for another esp32 and to turn-on the in-built led of both esp32 simultaneously if they come closer than the set limit? (i'm using RSSI to set range) " Any help would be appreciated, Thanks in advance.

Rahul

[konacurrents]

I found this thread while trying to connect my ESP32 to a current BLE device. I cannot get it to connect, although it finds the services. But there is no service UUID in the ESP code so it doesn't connect.

The BLEAdvertisedDevice.cpp -- is not finding a serviceUUID for valid BLE device. Also the "getName()" is garbled, but the advertisedDevice.toString().c_str() shows the name as shown below

The following are 3 BLE devices discovered. The first is a current BLE device called PTFeeder, but the "serviceUUID" isn't available as the haveServiceUUID() returns false. When scanning with iOS, it easily finds the UUID which equals the 3rd "serviceUUID" below.

The 2nd is a Punchthrough device which doesn't support the newer BLE CBService methods. This does show the serviceUUID.

The 3rd is a ESP32 device that advertises the same service, my ESP code finds this serviceUUID and connects.

Example: (1) BLE Advertised Device found: Name: PTFeeder, Address: 00:05:c6:75:55:15, txPower: 0 (2) BLE Advertised Device found: Name: Test, Address: c4:be:84:49:d9:7f, manufacturer data: 4c000215a495ff10c5b14b44b5121370f02d74de00000000c5, serviceUUID: a495ff10-c5b1-4b44-b512-1370f02d74de, txPower: 4 (3) BLE Advertised Device found: Name: PTFeeder, Address: 08:3a:f2:51:7c:3e, serviceUUID: b0e6a4bf-cccc-ffff-330c-0000000000f0, txPower: 3

It seems the BLEDevice.h (and the rest of the code) isn't finding the serviceUUID of traditional BLE devices.

UPDATE: After running in verbose mode, it seems the BLE code isn't parsing the advertisements from the item (1) above. It never finds the "serviceUUID". In particular, it sees data type 0x21, but parses it wrong. Looking closer, the data here should be the serviceUUID but (a) it doesn't recognize it, and (b) the data if backwards. (eg. f000000000000c33ffffccccbfa4e6b0 vs b0e6a4bf-cccc-ffff-330c-0000000000f0) shown in #3 above.

[V][BLEUtils.cpp:747] advTypeToString(): adv data type: 0x21 [D][BLEAdvertisedDevice.cpp:253] parseAdvertisement(): Type: 0x21 (), length: 16, data: f000000000000c33ffffccccbfa4e6b0

Example #3 (the other ESP serving bluetooth) - sees type 0x07 as the "serviceUUID" [D][BLEAdvertisedDevice.cpp:253] parseAdvertisement(): Type: 0x07 (), length: 16, data: f000000000000c33ffffccccbfa4e6b0 [D][BLEAdvertisedDevice.cpp:453] setServiceUUID(): - addServiceUUID(): serviceUUID: b0e6a4bf-cccc-ffff-330c-0000000000f0

Any ideas? thanks

[mbrunton22]

There seems to be an issue with this example. It lists a bunch of bluetooth data, but then says there are 0 devices found.

I tried editing BLEScan.cpp to the following, but that doesn't seem to work either???

''' if (m_pAdvertisedDeviceCallbacks) { // if has callback, no need to record to vector

                } else if (!m_wantDuplicates && !found) {   // if no callback and not want duplicate, and not already in vector, record it
                    m_pAdvertisedDeviceCallbacks->onResult(*advertisedDevice);
                    m_scanResults.m_vectorAdvertisedDevices.insert(std::pair<std::string, BLEAdvertisedDevice*>(advertisedAddress.toString(), advertisedDevice));
                    shouldDelete = false;
                }

'''

Output: 16:26:15.285 -> Scan done! 16:26:17.302 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:17.339 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:17.339 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:17.377 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:17.377 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:17.451 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:17.489 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:17.489 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:17.559 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:17.559 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:17.559 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:17.597 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:17.597 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:17.633 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:17.668 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:17.668 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:17.703 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:17.741 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:17.741 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:17.778 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:17.815 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:17.852 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:17.852 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:17.886 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:17.886 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:17.922 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:17.956 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:17.999 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:17.999 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:17.999 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:18.036 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:18.069 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:18.069 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:18.107 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:18.107 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:18.180 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:18.180 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:18.180 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:18.217 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:18.289 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:18.289 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:18.289 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:18.327 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:18.327 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:18.364 -> Advertised Device: Name: , Address: 70:b3:3e:40:a6:b4, manufacturer data: 7500021821a14f83ff91a2a1ec6d42a617db0a9a 16:26:18.364 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:18.403 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:18.403 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:18.440 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:18.476 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:18.476 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:18.512 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:18.512 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:18.581 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:18.616 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:18.653 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:18.653 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:18.690 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:18.764 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:18.800 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:18.800 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:18.800 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:18.834 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:18.871 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:18.907 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:18.907 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:18.907 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:18.907 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:18.977 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:19.014 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:19.014 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:19.051 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:19.088 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:19.125 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:19.125 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:19.170 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:19.198 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:19.198 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:19.198 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:19.233 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:19.305 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:19.305 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:19.378 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:19.416 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:19.416 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:19.484 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:19.484 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:19.521 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:19.521 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:19.593 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:19.593 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:19.593 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:19.630 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:19.630 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:19.668 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:19.705 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:19.705 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:19.741 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:19.775 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:19.775 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:19.812 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:19.850 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:19.850 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:19.850 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:19.888 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:19.888 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:19.925 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:19.962 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:19.962 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:19.999 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:19.999 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:19.999 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:20.037 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:20.074 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:20.110 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:20.147 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:20.147 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:20.147 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:20.181 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:20.181 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:20.251 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:20.251 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:20.288 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:20.362 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:20.399 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:20.399 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:20.399 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:20.474 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:20.474 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:20.474 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:20.474 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:20.508 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:20.544 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:20.582 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:20.620 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:20.620 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:20.655 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:20.692 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:20.763 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:20.763 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:20.799 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:20.799 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:20.799 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:20.835 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:20.873 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:20.944 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:20.981 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:20.981 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:20.981 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:21.018 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:21.055 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:21.093 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:21.093 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:21.093 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:21.130 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:21.130 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:21.165 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:21.203 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:21.238 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:21.308 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:21.308 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:21.344 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:21.344 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:21.377 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:21.377 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:21.415 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:21.562 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:21.598 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:21.598 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:21.598 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:21.634 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:21.634 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:21.634 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:21.668 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:21.702 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:21.774 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:21.811 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:21.811 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:21.849 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:21.883 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:21.918 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:21.918 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:21.918 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:21.990 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:21.990 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:22.062 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:22.062 -> Advertised Device: Name: , Address: 64:e6:61:56:68:b1, manufacturer data: 7500021811a112e590d6c0eae78f51ad1946edd4 16:26:22.062 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:22.132 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:22.132 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:22.168 -> Advertised Device: Name: , Address: 79:cc:ea:6b:73:94, manufacturer data: 4c00100503180efef6, txPower: 12 16:26:22.168 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:22.168 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:22.168 -> Advertised Device: Name: , Address: 67:fc:f8:76:11:73, manufacturer data: 4c001005071c5090bd 16:26:22.206 -> Advertised Device: Name: , Address: 70:b3:3e:40:a6:b4, manufacturer data: 7500021821a14f83ff91a2a1ec6d42a617db0a9a 16:26:22.243 -> Advertised Device: Name: , Address: 4b:64:bd:d9:81:c7, manufacturer data: 0600010920020f44a4f7fe63c0b57ecb9b0f9052f23fb98442d02f5ecf 16:26:22.243 -> Advertised Device: Name: , Address: 50:3f:9a:38:4a:fe, manufacturer data: 060001092002e81f219b0a99b78caf97b91d6b98d74bf0439a246d97fc 16:26:22.243 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401206f17070000000000000000000000000000000000 16:26:22.277 -> Advertised Device: Name: , Address: d8:e0:e1:85:05:c9, manufacturer data: 7500420401016fd8e0e18505c9dae0e18505c899435200000000 16:26:22.313 -> Devices found: 0 16:26:22.313 -> Scan done!

[pedrobuelna]

i need to connect ionic 7 app capacitor with my esp32 but when i run ionic app not detect esp32, and my app ionic 7 capacitor detect others Bluetooth devices but esp32 is not detected helpme please