meetsSpecification not working with all ibeacons

Hello,

I am currently using 4 beacons supplied by Kontakt, (2 Pro and 2 standard).

The beacons (Pro), doesn’t meet the specification of IBeaconAdvertisingPacket class.

I am getting different values of EXPECTED_TYPE and EXPECTED_BEACON_TYPE for the pro type of beacon. I don’t know if Kontakt change something in these beacons or not.

I used also (aruba, estimote, averos, standard kontakt) and every beacon worked fine except the Kontakt pro beacon.

I guess the problem that some companies who provide beacons, change some bits from the advertising packets to add like battery life, led and sensors. So we cannot just test the ibeacon if it meets specification in a static way.

 public static boolean meetsSpecification(byte[] data) {
        if (data == null || data.length < 29) {
            return false;
        }
        if (getTypeBytes(data) != EXPECTED_TYPE) {
            return false;
        }
        if (!Arrays.equals(getFlagsBytes(data), EXPECTED_FLAGS)) {
            return false;
        }
        if (!Arrays.equals(getBeaconTypeBytes(data), EXPECTED_BEACON_TYPE)) {
            return false;
        }
        return true;
    }

Thank you

[Steppschuh]

Yes, I did notice that. The difference is the length of the advertising data from the Kontakt Pro beacon, which makes it not compliant with the iBeacon specification (see the table from my last comment).

[Steppschuh]

I’ve adjusted the check in PR #83 to tolerate changes in byte 4 (EXPECTED_TYPE). Make sure to change your dependency to compile 'com.github.neXenio:BLE-Indoor-Positioning:dev-SNAPSHOT' in order to get the changes.

I wouldn’t consider the advertising data from your Kontakt Pro beacon to be an iBeacon frame. According to Apple’s specification:

Bytes	Description
09-24	Proximity UUID
25-26	Major
27-28	Minor
29	Signal Power

However, you can create your own classes for your use case, e.g. KontaktProAdvertisingPacket extends AdvertisingPacket and KontaktProBeacon<P extends KontaktProAdvertisingPacket> extends Beacon<P>. Have a look at the AdvertisingPacketFactoryTest and BeaconFactoryTest to see how you can use your own classes.