Estimote Fleet Management SDK allows you to configure and update your Estimote Beacons via your own Android app, for example:
You can configure your beacons one by one, or use Estimote Cloud to queue "pending settings" on your beacons and apply these settings with the Bulk Updater.
Integrating this SDK into your app means the users of your app can automatically propagate any configuration changes to your beacons. Say, you deployed the beacons, but the initial usage suggests you need to bump the transmit power up a notch, or maybe make the Telemetry advertise more frequently. With Bulk Updater integrated into the app, any user of the app in range of a "pending settings" beacon will apply the new settings.
(Settings that live entirely in Estimote Cloud, like the beacon's name, tags, and attachments, are always updated instantly, without the need to propagate settings to beacons.)
Short version: no, use the Proximity SDK instead.
Longer version: this SDK was previously known as "Estimote SDK", and it included APIs for detecting your beacons, which you could use to show notifications, etc. These APIs are now deprecated and are no longer supported. They have been replaced with the Estimote Proximity SDK for Android, powered by Estimote Monitoring.
You can, and are encouraged to, use the Fleet Management SDK alongside the Proximity SDK: Proximity SDK for driving the proximity-based events in your app, and Fleet Management SDK for remotely managing your beacons.
No, you can use our Estimote Android app to change the most common settings, and to apply "pending settings" to individual beacons. Connecting to the beacon in the app automatically applies the latest settings from Estimote Cloud.
If you have more Estimote devices, Estimote Deployment app can apply "pending settings" in bulk. At this time, it's available on iOS only.
Android 4.3 or later, and an Android device with Bluetooth Low Energy.
The minimum Android API level this SDK will run on is 9 (= Android 2.3), but the Bluetooth-detection features (which is most of them) won't work. You can handle this gracefully in your app by not using the fleet management features if you detect Android < 4.3, or no Bluetooth Low Energy available.
Bluetooth Low Energy scanning on Android also requires the app to obtain the location permissions from the user, and "location" must also be enabled system-wide. Chances are, if your app is using beacons (e.g., via the Estimote Proximity SDK), you already have this permission.
This SDK is distributed via JCenter repository. Most of the time, you'll already have JCenter repo configured in your Android project, with these lines in the Project build.gradle:
allprojects {
repositories {
jcenter()
// ...
}
}If not, add jcenter() inside repositories, as shown above. Then, in the Module build.gradle, add:
dependencies {
implementation 'com.estimote:mgmtsdk:1.4.6'
implementation 'com.estimote:coresdk:1.3.4'
// if using an older version of Gradle, try "compile" instead of "implementation"
}This SDK needs to be able to access your Estimote Cloud account in order to configure your beacons.
To do that, register your mobile app in Estimote Cloud in the "Mobile Apps" section. You'll get an App ID and App Token, which you can use to initialize the SDK:
// do this before you use any of the fleet management features
EstimoteSDK.initialize(applicationContext, "my-app-bf6", "7bcabedcb4f...");Your Estimote Cloud account needs to have a fleet management subscription. As of now, there's a free, indefinite trial available if you have less than 20 devices.
This is how to set up the Bulk Updater: (we recommend doing this in an Application subclass)
private BulkUpdater bulkUpdater;
@Override
protected void onCreate() {
super.onCreate();
Context context = getApplicationContext();
bulkUpdater = new BulkUpdaterBuilder(context)
.withFirmwareUpdate()
.withCloudFetchInterval(1, TimeUnit.HOURS)
.withTimeout(0)
.withRetryCount(3)
.build()
}And this is how to use it:
bulkUpdater.start(new BulkUpdater.BulkUpdaterCallback() {
@Override
public void onDeviceStatusChange(ConfigurableDevice device,
BulkUpdater.Status newStatus, String message) {
Log.d("BulkUpdater", device.deviceId + ": " + newStatus);
}
@Override
public void onFinished(int updatedCount, int failedCount) {
Log.d("BulkUpdater", "Finished. Updated: " +
updatedCount + ", Failed: " + failedCount);
}
@Override
public void onError(DeviceConnectionException e) {
Log.d("BulkUpdater", "Error: " + e.getMessage());
}
});One more thing: you need to feed the BulkUpdater with data from the beacons' Connectivity packets:
private BeaconManager beaconManager;
// ...
beaconManager = new BeaconManager(context);
// this will make the beacon attempt to detect Connectivity packets for 10 seconds,
// then wait 50 seconds before the next detection, then repeat the cycle
beaconManager.setForegroundScanPeriod(10000, 50000);
// this connects to an underlying service, not to the beacon (-;
beaconManager.connect(new BeaconManager.ServiceReadyCallback() {
@Override
public void onServiceReady() {
beaconManager.setConfigurableDevicesListener(new BeaconManager.ConfigurableDevicesListener() {
@Override
public void onConfigurableDevicesFound(List<ConfigurableDevice> configurableDevices) {
bulkUpdater.onDevicesFound(configurableDevices);
}
});
}
});
beaconManager.startConfigurableDevicesDiscovery();To stop, and clean up after the BulkUpdater, do:
beaconManager.stopConfigurableDevicesDiscovery()
bulkUpdater.stop();
bulkUpdater.destroy();If you want to individually configure a beacon, you'll need to connect to it first: Connecting to beacons.
Once connected, you can read and write settings, as well as update the beacon's firmware: Basic operations on connected device and Advanced operations on connected device.
… is available here:
http://estimote.github.io/Android-Fleet-Management-SDK/JavaDocs/
Post your questions and feedback to Estimote Forums, we'd love to hear from you!
Report issues on the issues page.
See CHANGELOG.md.