Advertising a service but not connectable?

[Roger Clark]

I noticed while running a Bluetooth scanner app on my iPad, while testing one of my devices, that it was showing someone else's device in the locality.

What I found strange about this was that the device was not advertising as being connectable, but did advertise a service and had manufacturer data but also service data

{
    kCBAdvDataIsConnectable = 0;
    kCBAdvDataManufacturerData = <e0000104 ca525670>;
    kCBAdvDataServiceData =     {
        FE9F = <02425043 2d425f33 367a4877 0000015d db6deb30>;
    };
    kCBAdvDataServiceUUIDs =     (
        FE9F
    );
}

Could anyone tell, me why a device would advertise as having a service but not be connectable?

And why they have Service Data as well as manufacturer data

BTW. I noticed the service uuid also looks to be very strange number.

[Nguyen Hoan Hoang]

Do you have conn_params_init() somewhere in your code ?

[Roger Clark]

OK

I found it now.

www.bluetooth.com/.../16-bit-uuids-for-members

I have not looked at robots.txt on bluetooth.org, but its strange that google didn;t show this in its list and instead from some code on sourceforge.

Edit.

I take a general interest in the devices I happen to notice while scanning BLE when testing.

I have noticed a lot of Chinese made products advertise with unlisted 16 bit UUID,s in the range 7xxx

I now see that they do this because it appears that Bluetooth.org seem to allocate 16 bit services to members, starting from 0xFEFF descending, and the general purpose 16 bit uuids are much lower 16 bit numbers e.g 1800 upwards

So I presume the companies who used these unregistered 7xxx codes hop that Bluetooth.org will not allocate that range for many many years, why which time they will be long gone