This iOS SDK can be used to update the settings of multiple Estimote beacons at once. You no longer need to connect to each beacon individually. Instead, you use Estimote Cloud to queue ‘pending settings’ on your beacons. Then, your iOS app equipped with this SDK ( see Bulk Updater section) can propagate those settings the moment it encounters the beacons. This also means that, once you deploy the beacons, users of your app can propagate the settings by simply being around the beacons.
If you simply need to change the settings (or apply ‘pending settings’) of the nearby Estimote beacons, get Estimote iOS app. For a single beacon or a few of them, this will be the fastest method.
If you have more Estimote devices, Estimote Deployment app will be a better choice. It uses Bulk Updater to propagate settings to multiple beacons at once.
All the proximity monitoring features of this SDK have been deprecated and are no longer supported. Instead, we strongly recommend Estimote Proximity SDK for iOS powered by Estimote Monitoring. This iOS SDK, on the other hand, should be used for beacon fleet management. Keep in mind that tags & attachments from Estimote Proximity SDK are updated instantly, without the need to propagate settings to beacons
To learn more about this iOS SDK, review the SDK documentation and check the Developer Portal tutorial. Visit also Estimote Cloud API docs.
CocoaPods is an easy way to add external libraries. To use it to fetch Estimote SDK:
- Add
pod 'EstimoteSDK'to your Podfile - Run
pod install --repo-update - For Swift project: you will need a bridging header, so just add a new file with Objective-C, confirm you want to a create a bridging header and just remove the not needed Objective-C file. In the bridging header, add:
#import <EstimoteSDK/EstimoteSDK.h>For Objective-c project: add to your code#import <EstimoteSDK/EstimoteSDK.h> - You're ready to rock!
Alternatively, include a single EstimoteSDK.framework file in your project to get started:
- Drag and drop EstimoteSDK.framework file into your Xcode project. It will automatically show up in your project navigator and will be added to Linked Frameworks and Libraries section in project settings.
- That's it, congratulations and happy hacking!
The SDK requires iOS 7+, as it depends on the CoreLocation's support for iBeacon which was first introduced in iOS 7.
With this feature you can:
- Enable or disable packets (e.g. iBeacon, Eddystone-UID)
- Modify the settings of individual beacons (e.g. increase the broadcasting power, decrease the advertising interval, modify Eddystone-URL’s link)
- Update Estimote beacon firmware
To perform bulk update operations on devices represented by ESTDeviceLocationBeacon class you should use the ESTLocationBeaconBulkUpdater class.
Contrary to the ESTBulkUpdater it is not designed to be used as a singleton.
ESTLocationBeaconBulkUpdater requires an array of of ESTLocationBeaconBulkUpdaterConfiguration objects to start. ESTLocationBeaconBulkUpdaterConfiguration consists of an identifier of the device which settings you want to modify and an array of ESTSettingOperation described in the Advanced API section. All bulk updater events will be delivered to the object assigned as it's delegate which should conform to ESTLocationBeaconBulkUpdaterDelegate protocol.
I have an array of identifiers for my Location Beacons that should have their iBeacon packet on and major value set to 200.
NSMutableArray *bulkUpdateConfigurations = [NSMutableArray new];
NSArray *identifiers = @[@"identifier1", @"identifier2", @"identifier3"];
for (NSString *identifier in identifiers) {
ESTSettingIBeaconEnable *enableSetting = [[ESTSettingIBeaconEnable alloc] initWithValue:YES];
ESTBeaconOperationIBeaconEnable *enableOperation = [ESTBeaconOperationIBeaconEnable writeOperationWithSetting:enableSetting completion:^(ESTSettingIBeaconEnable *iBeaconEnableSetting, NSError *error) {
}];
unsigned short major = 200;
ESTSettingIBeaconMajor *majorSetting = [[ESTSettingIBeaconMajor alloc] initWithValue:major];
ESTBeaconOperationIBeaconMajor *majorOperation = [ESTBeaconOperationIBeaconMajor writeOperationWithSetting:majorSetting completion:^(ESTSettingIBeaconMajor *major, NSError *error) {
}];
ESTLocationBeaconBulkUpdateConfiguration *configuration = [[ESTLocationBeaconBulkUpdateConfiguration alloc] initWithDeviceIdentifier:identifier settingsOperations:@[enableOperation, majorOperation]];
[bulkUpdateConfigurations addObject:configuration];
}
[self.bulkUpdater startWithUpdateConfigurations:[NSArray arrayWithArray:bulkUpdateConfigurations]];Connecting to an Estimote beacon lets you change its settings (enable/disable packets, modify broadcasting power or advertising interval etc). If a beacon is set to Deployed & Protected access mode, you have to be the beacon's owner in Estimote Cloud to modify any settings.
Every attempt to connect with a device not logged in to your Estimote account will fail. Enable Development access mode to allow your coworkers to also edit beacon's settings.
Connectivity packets are represented by ESTDeviceConnectable subclasses, the main one being ESTDeviceLocationBeacon. It represents:
- Estimote Location Beacons (hardware revision “F”)
- Estimote Proximity Beacons (hardware revisions “G” and “J”)
If you have Estimote Nearables (Stickers), use ESTDeviceNearable instead. In order to connect to the first-generation Estimote Proximity Beacon (hardware revision "D"), use the SDK 3 API.
In this SDK, following steps are required to connect to a device:
- Create ESTDeviceManager, make sure your class conforms to ESTDeviceManagerDelegate protocol.
- Start discovery by calling startDiscoveryWithFilter: with filter object. This can be either ESTDeviceFilterLocationBeacon or ESTDeviceFilterNearable.
- Method deviceManager:didDiscoverDevices: provides discovered devices matching filter.
- Make sure your class conforms to ESTDeviceConnectableDelegate protocol and call connect on discovered ESTDeviceConnectable object. Now, the SDK verifies if the device is linked to account specified by AppID + AppToken pair, authorizes user, connects on the Bluetooth level and synchronizes settings by fetching their values from Cloud and writing to the device.
In this SDK, each device setting is represented by an ESTSettingBase subclass. There are two ways of reading/writing settings - Convenience API and Advanced API.
These classes are wrappers around basic types (both primitives and objects) such as unsigned integer or NSString,
- ESTSetting* classes are wrappers around values providing validation.
- ESTBeaconOperation* classes specify details used to read or write setting to the device.
To simply change a device setting you can use the Convenience API tree. Each device has one, here's an example of ESTDeviceLocationBeacon settings tree:
device
|- settings
|- iBeacon
|- proximityUUID
|- major
|- minor
...
|- estimote
|- enable
|- power
...
|- deviceInfo
|- color
|- name
...
...
To read/write a device setting value call readValueWithCompletion: or writeValue:completion: method on one of the tree's leaf.
I have an Estimote Location Beacon and I want to turn iBeacon packet on, change its Major value to 500, and read its Proximity UUID.
[device.settings.iBeacon.enable writeValue:YES completion:^(ESTSettingIBeaconEnable *enableSetting, NSError *error) {
NSLog(@"iBeacon packet enabled");
}];
[device.settings.iBeacon.major writeValue:500 completion:^(ESTSettingIBeaconMajor *majorSetting, NSError *error) {
NSLog(@"Major set to 500");
}];
[device.settings.iBeacon.proximityUUID readValueWithCompletion:^(ESTSettingIBeaconProximityUUID *uuidSetting, NSError *error) {
NSLog(@"Proximity UUID is %@", [uuidSetting getValue]);
}];To speed up interacting with multiple settings at once you can use the Advanced API. Each setting has its own setting and operation classes pair.
- Setting classes are subclasses of ESTSettingBase and have their names constructed by concatenating ESTSetting + SettingGroupName + SettingShortName (i.e. ESTSettingIBeaconMajor). They are wrappers around setting values (both primitive types and object types), they also provide value validation.
- Operation classes are subclasses of ESTSettingOperation and have their name constructed by concatenating ESTBeaconOperation (if it's a setting stored in the device memory, such as iBeacon Major) or ESTCloudOperation (if it's a setting stored only in Cloud, such as DeviceInfo Name) + SettingGroupName + SettingShortName (i.e. ESTBeaconOperationIBeaconMajor or ESTCloudOperationDeviceInfoName).
I have an Estimote Location Beacon and I want to turn iBeacon packet on, change its Major value to 200, read its Proximity UUID, perform many other operations and want to do this as fast as possible.
ESTSettingIBeaconEnable *enableSetting = [[ESTSettingIBeaconEnable alloc] initWithValue:YES];
ESTBeaconOperationIBeaconEnable *enableOperation = [ESTBeaconOperationIBeaconEnable writeOperationWithSetting:enableSetting completion:^(ESTSettingIBeaconEnable *setting, NSError *error)
NSLog(@"iBeacon packet enabled");
}];
unsigned short major = 200;
ESTSettingIBeaconMajor *majorSetting = [[ESTSettingIBeaconMajor alloc] initWithValue:major];
ESTBeaconOperationIBeaconMajor *majorOperation = [ESTBeaconOperationIBeaconMajor writeOperationWithSetting:majorSetting completion:^(ESTSettingIBeaconMajor *setting, NSError *error) {
NSLog(@"Major set to 200");
}];
ESTBeaconOperationIBeaconProximityUUID *uuidOperation = [ESTBeaconOperationIBeaconProximityUUID readValueWithCompletion:^(ESTSettingIBeaconProximityUUID *setting, NSError *error) {
NSLog(@"Proximity UUID is %@", [uuidSetting getValue]);
}];
...
[device.settings performOperations:enableOperation, majorOperation, uuidOperation, ..., nil];To see what has changed in recent versions of Estimote SDK, see the CHANGELOG.