Connect IQ BLE scan issue

Hi, thanks for the response. If you read the last part of my post you see that I tested your app and found that it got me the same results as my own application. So those 3 UUID's that I wrote about are more or less the only 3 I get when I run your BleScan app.

When you do a 16 bit UUID you typically use 0x02 or 0x03 as the common data type and then your 2 byte UUID. This translates to the UUID + base UUID seen in the app. 

I can see that the devices that I get results of advertise their UUID in that way.

Our device has 0x07 as common data type and a 128 bit UUID. 

When I run in the simulator using the nRF dongle everything works perfectly.

On a similar Watch (Fenix 6x pro) I only seem to ge the 16 bit UUID responses.

Our full raw advertise data is 29 bytes long (so shorter than some that are actually found which are 30 bytes long). So we have a flag 0x04, then our 128 bit UUID and then our 9 byte local name.  

Is it just that simple that Garmin watches only support 16 bit UUID's? I find it very strange that they never mention that anywhere. 

First thing is make sure you watch the breakout session where this was announced

https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/adding-bluetooth-connectivity-to-your-connect-iq-projects

Understand this is a very limited implementation on the garmin devices, where things like the amount of data you can receive is minimal. no security, you need to define your services and characteristics in your app, you don't always see names and/or UUIDS, etc, and you are limited to .registering at most 3 profiles.

Without seeing your code, what I usually suggest is a simple hack to the NordicThingy52 sample in the SDK to see what's happening with scanning.  In the ThingyDelegate.mc, add the following line to contains, and you'll see everything seen when scanning

    private function contains(iter as Iterator, obj as Uuid) as Boolean {
        for (var uuid = iter.next(); uuid != null; uuid = iter.next()) {
//Add this line
//System.println(uuid.toString());    
            if (uuid.equals(obj)) {
                return true;
            }
        }

        return false;
    }
}

As far as the real device, I have an app that shows you exactly what the Garmin can see with scanning and you can see a time stamp for when the scan result was seen.

https://apps.garmin.com/apps/9bcc8b66-8385-4afb-b93e-f69e01422284

Different size UUIDs also come into play,  For example, I need to use the base UUID for a BLE HRM.

//Using 16 bit UUIDs
//Ref. the Bluetooth Core Specification 5.2, Vol 3, Part B, section 2.5.1 UUID:

//The first UUID in this pre-allocated range is known as the
//Bluetooth Base UUID and has the value 00000000-0000-1000-8000-00805F9B34FB

//(...)

//The full 128-bit value of a 16-bit or 32-bit UUID may be computed by a simple
//arithmetic operation.

//128_bit_value = 16_bit_value * 2^96 + Bluetooth_Base_UUID


//128_bit_value = 32_bit_value * 2^96 + Bluetooth_Base_UUID"

//What it means in practice, is that you take a "base UUID" of 0000xxxx-0000-1000-8000-00805F9B34FB, 
//and replace the x-es with the 16 bit UUID.