Any proximity uuid besides ESTIMOTE_PROXIMITY_UUID doesn't work


We’re developing a beacon app and until now used the uuid provided in the tutorials, that is B9407F30-F5F8-466E-AFF9-25556B57FE6D. However when I tried to change it, to B9407F30-1111-466E-AFF9-25556B57FE6D, I stopped getting didEnter and didExit events. The ranging stopped working as well.

Also IOS Estimote app doesn’t see beacons with any UUID besides one in the tutorial, but the interesting part is that Android Estimote app does see them (no matter what uuid I set)

Naturally I don’t want to be limited to only one uuid. Are there any rules for picking one?

Please advise on the issue

Have you changed the UUID of your beacons to match the one you’re monitoring/ranging for? I took a quick look at our Estimote Cloud database, and haven’t found any beacons set to broadcast “B9407F30-1111-466E-AFF9-25556B57FE6D” as their UUID.

All Estimote Beacons we ship are set to the default Estimote UUID, “B9407F30-F5F8-466E-AFF9-25556B57FE6D,” plus a randomized major and minor value for differentiating between them. If you want to change it to your own UUID, here’s how to go about it:

iOS only allows you to discover iBeacons when you know their UUID, that’s why by default you can’t see any beacons other than those with the default Estimote UUID in the Estimote app. Android doesn’t have this limitation, you can range/monitor for any beacons, no matter their UUID.

Thanks for the clarification about the differences between android and ios estimote apps. The uuid was indeed “B9407F30-1111-466E-AFF9-25556B57FE6D”, but I changed it back to “B9407F30-F5F8-466E-AFF9-25556B57FE6D”.

Following the response of didEnterRegion called multiple times I purged monitoredRegions and rangedRegions lists and app started to respond to different uuids besides the default one.