search

Estimote / Android-Fleet-Management-SDK

Estimote Fleet Management SDK for Android
https://developer.estimote.com
MIT License
836 stars 451 forks source link

SDK not working with non Estimote devices #29

Closed cosminstefanxp closed 10 years ago

cosminstefanxp commented 10 years ago

I've integrated the SDK (great work, btw! ) into an application trying to do a prototype, but I've run into an interesting issue. When testing it with an Estimote beacon, everything works as expected.

However, I also have a non-Estimote beacon which is not being detected by the SDK. By looking in the logs, I see that the Bluetooth adapter identifies the device, as seen in:

Estimote -> 02-26 09:37:15.057    6227-6238/com.estimote.examples.demos D/BluetoothAdapter﹕ onScanResult() - Device=C1:91:C6:58:FE:E4 RSSI=-86
Non-Estimote -> 02-26 09:37:15.127    6227-6239/com.estimote.examples.demos D/BluetoothAdapter﹕ onScanResult() - Device=00:07:80:67:D6:10 RSSI=-45

But it does not show in ranging results, even after setting regions with just the UUID of the device or without any uuid (null).

So is this an intended limitation (not to work with something else besides Estimote) or it's just a bug/temporary thing?

LE: I've also tested this with RadiusNetwork's sample app and it seems to show both my beacons, so it shouldn't be an issue with my beacon.

wiktor commented 10 years ago

That is correct observation. Estimote SDK works only with Estimote beacons.

chrisjenx commented 10 years ago

I guess I could fork the project to fix this! Oh wait...