Can't read UUID while scanning

I ran into a problem that can not read the Bluetooth UUID when scanning of the device. Launched BleScan - the same result, UUID is missing. Yes, I read in the description of BleScan that "Note - there can be cases where there is no UUID." Is this my case and can't be solved? nRF Connect shows the 16-bit UUID of the same device without problems

0 jim_m_58 over 2 years ago

With BleScan, long pressing the middle left button (menu) will allow you to try pairing. Can you pair?

What I'd try then is when looking at scan results, instead of looking for a matching UUID, look for a match of the name you see in BleScan (Rover7223) In BleScan I get that with scanResult.getDeviceName()

You may need to test this on a real device instead of the sim with the dongle or DK

0 alezz over 2 years ago in reply to jim_m_58

Yes, I can connect to the device by pressing the menu button on BleScan, there is no problem. Yes, I can connect to the device by finding it by name, this is also no problem. But the problem is that these are different devices, they can have different names and there can be hundreds or even thousands of these names. All that unites devices is the same UUID and why Garmin does not see the UUID, this is a mystery ...

0 jim_m_58 over 2 years ago in reply to alezz

You can check for a name that beginning with "Rover". Why the UUID doesn't come through for some devices has been a mystery since CIQ BLE came out.

0 alezz over 2 years ago in reply to jim_m_58

If all rowing machines had a name that included the word "RoWer" it would be too simple for me :) In any case, thanks, I realized that the problem has no solution at the moment, or rather its solution depends on Garmin and not on you and me