I am looking for help in understanding some of the iBeacon reliability issues that I observed while monitoring iBeacons using CoreLocation.
I have a set of beacons with the same UUID, but different primary and lower numbers. My program is configured to monitor all of them (not the range). I have transmit power at an absolute minimum for beacons (presumably as a result of a radius radius of 5 feet). Sometimes it works fine, but I have observed some inconsistent behavior, including:
- Approaching a lighthouse and never receiving an input event (even when standing next to it for several minutes).
- Receiving incoming events from distant beacons (when it is already inside another area and does not move)
- Intermittent exit / entry of events when sitting inside the area of the lighthouse (this seems to be common when reading other messages).
I'm interested in any best practices that people may know about iBeacons. The problems that I observe are apparently related to unreliable transmission ranges and fluctuations in strong beacon signals. Is there an easy way to improve this problem?
My goal is to have several lighthouses in the immediate vicinity. Should I consider a range to help reduce some reliability? If so, I understand that you cannot have reliability in the background.
In addition, I am trying to confirm whether you will receive or introduce an event if your application starts already in the beacon zone?