title: Kontakt Beacons: Inconsistent and unreliable results when determining beacon distance
body: <p>Using Kontakt SDK, I've implemented a simple application to monitor and range Kontakt beacons in my area. I've noticed that the reported distance of detected beacons fluctuate heavily (e.g. beacon is really at 10m but it comes back as 2m and could jump around in distance quite significantly), even if the beacon is not that far away. I've gone through the documentation and played with all the different variables on the beacon hardware side (tx power / frequency), SDK side (scan mode and related) and tried multiple devices - nothing I do seem to improve the accuracy. Just wondering if anyone might be able to point me in the right direction on what could be the issue.</p>
  
  <p>I do know that a beacon signal can be vary significantly based on many factors of the environment and hardware of the receiving device itself; but, I'm at a lost how one can possibly create a user experience that is based on accurate proximity to beacons, when there doesn't seem to be a way to get consistent distance information?</p>
  
  <p>Any type of guidance, input or suggestion would be greatly appreciated. Thanks.</p>