BLE do not show the advertising name

Not uncommon at all.  With the BLE devices I have at hand, only the Thingy52 and HRM-PRO show the name in CIQ.  My blescan app in the store will show you want you can see from a CIQ BLE app.

I just thinked about the raw packet including the advertising names but as i see in the documentation the ADV packet is longer than 30 bytes (and supports two types of name lengths). I use your application too, but it shows null for name (Polar H10) for my own sensor (based on Thingy54 - NRF52 SoC) the name is ok but check the other threat where i mentioned. 

In blescan, if you are viewing a device, doing select will show the raw data seen by CIQ BLE.

Remember, BLE in CIQ is only a minimal implementation

Yeah i got it! And already read from my app. But as i see the raw packet does not includes names when secanning for HR sensors(Polar H10) but can seen when scanning for own tingy devices. Did you try to connect two tingy devices at the same time ? 

Never tried two thingys at the same time. My apps all use one BLE sensor.

Are you using the sim with the DK or dongle?

With nRFConnect, you can see the mac addresses.  Are they different for the devices you are trying to connect?

I checked in nRF Connect and they have totally diferent MAC address below the advertising name. I will investigate it with ble sniffer to see what is the condition that equals during the connection. It would be easier if the support can give exact answer or give a documentation about the BLE CIQ paired devices parameters. 

Ok, I was curious and did a rough hack to an app I wrote for the thingy52 a few years back.

When a thingy52 is awake, the led flashes blue, but you can configure it so the led is a different color when something is connected to it. It's handy when debugging. My hack was to connect to the first 2 devices if more than one was seen/selected.  And the led changes color on both

It works fine in both the sim and on a real device.  For the sim, I do println's when the pairs happen, and also when onConnectionStateChanged is called, And I did notice it could take a few extra seconds for the second device to connect.

And the connection is stable to both.  If I get some time over the next few days I'll try some other things.

I extended my hack a bit and turned on notify for the temperature characteristic on both devices so I could check if I was getting data from both.  I just need to have one of the thingy52 devices where the temperature is noticeably different (in my pocket for example).

And onCharacteristicChanged is called about twice a second.  Once for each thingy52, showing the different temperatures.

If you don't have the HW to test in the sim, the 52840 dongle is about $12US last I looked, and worth every penny as it's much faster to test/debug things in the sim

I'm developing embedded SW to nRF52 Soc, so i'm really into it, also developing iOS applications to communicate with my BLE sensors. I would like to extend this ecosystem with Garmin CIQ. 

I have some problems with the simulator, (have a bunch of nrf52840DK and dongle boards too) , after a connection the connected NRF52840DK communication is freezing. - Maybe i use an older code - i should check it. 

After some investigating i just noticed, i don't have Manufacturer specific description in the BLE devices. 

As I see in the BLE sniffer (82540 dongle + wireshark) the garmin connects to the 2. device and try to reach some characteristics, and after terminating the connection with "device already paired" exception. 

I assume that, Garmin BLE API does not compare the devices via advertising data -> but from other yes ( what my device misses) that can be a reason for the reconnecting and discinnecting events. 

I'm currently using win11, the 7.1.1 SDK, and 1.0.11 extension.  The 52840 dongle I use with the sim was flashed back in 2019.

As I said, I'm working fine with two thingy52 devices, both with the same FW.  The MAC addresses are different, but I'm doubting there's really much else.

The HRM-PRO is kind of an interesting device, as it's both ANT and BLE, and an interesting thing is if it's paired in the FW with ANT, you can't pair it on the same Garmin with CIQ BLE.

When I get a chance maybe I'll try 2 raspberry Pis as I have more than one of them.

From the error you are seeing, are you sure you're not trying to pair the same device more than once?  That's where debugging in the sim could help track things down.  Can you debug on your sensors to see what's going on there?