Hi,
We currently use the following code to range beacons.
self.region = [[CLBeaconRegion alloc] initWithProximityUUID:ESTIMOTE_PROXIMITY_UUID
identifier:@"EstimoteSampleRegion"];
self.beaconManager = [[ESTBeaconManager alloc] init];
self.beaconManager.delegate = self;
[self startRangingBeacons];
That works great until I turn on Secure UUID on my beacons. Then none of my secure beacons show up in the ranging. Can you please let me know how I can get this to work with Secure UUIDs
You just need to change the ESTBeaconManager
for ESTSecureBeaconManager
, and also make sure that you’ve set up you app ID and token*, so that your app can access Estimote Cloud. (Estimote Cloud is doing the decryption of the rotating UUIDs.)
* here’s how:
[ESTConfig setupAppID:@"<app id>" andAppToken:@"<app token>"];
If you don’t yet have your app created in the cloud, you can obtain the token here:
https://cloud.estimote.com/#/apps/add/your-own-app
Hi,
Looks like currently at 3:43pm estimate cloud is down. I am unable to login to the website and even in my apps, I can’t connect to my beacon.
Can you please confirm if there’s some issue going on with estimate cloud right now?
Also in the future if estimate cloud is down, how would it effect our operations? We mainly use ESTSecureBeaconManager to range for beacons and check it’s secure UUID and major/minor. Will that stop working too when estimate cloud is down?
thanks
Yes, apologies, we had a temporary outage yesterday, as Heroku was experiencing some issues. Many other services and websites on the Internet were down for the duration.
The best place to go to check if there are any issues going on: http://status.estimote.com
Secure UUID needs to contact Estimote Cloud to have the identifier of your beacons resolved, so yes, in case of an outage, your app won’t be receiving any beacon events since it can’t decrypt the UUIDs. Many of our paying customers use Secure UUID and expect very high uptime of Estimote Cloud (in the 99.5%'ish per month), so we designed in full robustness and redundancy, to the benefit of everyone using Estimote Cloud.
If you take a look at the past 3 months, so far so good:
http://status.estimote.com/1564485/history
As in life though, sometimes things fail in a very unexpected way, but we make sure to learn from that and keep improving our service.