Solved - it was an issue with the device.

Hi, Thanks for the fast reply on @melle's post. I am a colleague of him, we had a session today doing some research on this and trying to implement a way to detect all of our existing products. Unfortunately we didn't have success and could observe a few things as well as a few questions came up. From your response it seems like bluetoothCompanyIdentifier is required to work with bluetoothManufacturerDataBlob as well as bluetoothManufacturerDataMask, so we need to set a company identifier on the descriptor and enter the remaining announced manufacturer data into the bluetoothManufacturerDataBlob? We could not find out if it is necessary to enter the entire announced manufacturer data into the bluetoothManufacturerDataBlob or if it would be sufficient to enter parts of it? Moreover we could not find out how to order the blob, we had different data from different apps (we used BlueSee as well as LightBlue). For example for one of our products the results looked like this: BlueSee (mac): Manufacturer Data: d20a0031000000 LighBlue (iOS): 0x0031000ad2 We tried based on this example: Product A 0xd2 0a ff d2 0a 00 00 00 00 00 Manufacturer 0xD20A Device ID: 0xFFD2 color: 0a Product B 0xd20a 00 31 00 00 00 Manufacturer 0xD20A If we try a descriptor just defining the bluetoothServiceUUID, which all of our products announce, we can only see 1 device in the session having multiple around. We also could see a single device announcing it but never get detected by AccessorySetupKit. Any idea what it could be? Even tho we are still having troubles implementing it for our products we are super excited about AccessorySetupKit, would love to be able to implement it for all of our existing products providing an unique experience for our customers 🤗

Hey there 👋 Thanks for the nice explanation, I'll do further research and discuss this together with @melle upcoming week. I did want to ask you about this part : descriptor.bluetoothServiceUUID = CBUUID(string: "ce1eb45c-> 1bd2-45be-8163-acc88be94cb2") Can you share a complete sample of your ADV payload ? Are > you advertising a 16byte UUID in addition to the manufacturer > data ? Do you also have flags in your payload ? A sample > payload would help me get more context. We're publishing this additionally to the manufacturer data in case a device is in pairing mode. There are flags in our manufacturer data's payload regarding device specifications. Guess that's also the reason for a lot of confusion on our side in what order to put the bytes. We can surely provide you with a more detailed sample upcoming week after we did some research. Have a nice weekend and thank you very much for your help 😊