Inconsistency in Listing Beacons

BLE Beacons
1

Hi Team,

We are using 3 Beacons for our Android app. Battery life is more than a year for all these beacons.

Identifiers:
9d2e2f21fd8fc887e6e021d6a280e737
7145d7eab1bad9d90c53b6d8d1573a0d
eaf93f649e725461cd64c62ef2736d0c

On checking in Estimote App, sometimes its not showing any of these IDs. Because of this, in our Android app we are unable to diplay the Beacon ID. Please help.

Regards,
Selva

2

It seems like you have two separate problems: one with detecting beacons with the Estimote app, and one in your own app. These are usually unrelated: the Estimote app uses a different detection mechanism than the Estimote Proximity SDK which you embed into your own app. (I assume you use the Estimote Proximity SDK?)

For the Estimote app: so the beacons are sometimes detected, but sometimes not? That sounds like some problem with the smartphone maybe, what device are you using? Could you try with another Android device, and maybe with an iPhone and the Estimote iOS app? This will help us narrow down where the problem might be. (The Estimote Android app, or your particular Android device, etc.)

For your own app: same question I guess, do you sometimes detect the beacons and sometimes don’t? Can you maybe share your code, and also, if you’re using the Proximity SDK, make sure that the beacons are tagged correctly and have Estimote Monitoring enabled?

3

Thanks for the support.

i) For Estimote App - The issue occured in Moto C Plus Android device. I have also checked with iphone SE device and there i don’t find that issue. Can you please tell, if there is any specific timeframe for detection?

ii)For Android App - Your guess is right. Estimate Monitoring is enabled. We are using the following SDK “implementation 'com.estimote:sdk:0.13.0@aar” . Kindly help’

Regards,
Selva S

4

Team. Please update ASAP.

Thanks,
Selva S

5

i) For Estimote App - The issue occured in Moto C Plus Android device. I have also checked with iphone SE device and there i don’t find that issue. Can you please tell, if there is any specific timeframe for detection?

So this means there’s probably some problem with the Moto C Plus. We’ll put it on our list to investigate.

ii)For Android App - Your guess is right. Estimate Monitoring is enabled. We are using the following SDK “implementation 'com.estimote:sdk:0.13.0@aar” . Kindly help’

That’s a very old SDK. For new deployments/integrations, we recommend the latest version of our Proximity SDK:

Add proximity events to an Android app - Estimote Developer
GitHub - Estimote/Android-Proximity-SDK: Estimote Proximity SDK for Android

implementation 'com.estimote:proximity-sdk:1.0.3'
6

Hi Team,

Thanks for your feedback.

We have emailed you Estimote code which we are using in our App.

We can detect the beacons in our Android app now, but once we close and reopen the app. we are not getting the beacon IDs.

Please help.

Regards,
Selva S

7

Any help on this?

Thanks,
Selva S

8

Hi Team,

As per your advice, we are planning to use the latest SDK 'implementation ‘com.estimote:proximity-sdk:1.0.3’,

In current app SDK libraries 'implementation ‘com.estimote:sdk:1.4.5’ ,we have used the below methods,

beaconManager.connect(() -> {
beaconManager.startRanging(Your_APP ID, APP TOKEN);
beaconManager.startNearableDiscovery(); }

beaconManager.setNearableListener(list -> {
neareableBeaconName(list);
});

Can you pls let us which methods to be used in the latest Proximity SDK mplementation ‘com.estimote:proximity-sdk:1.0.3’,

Regards,
Selva S