Detected beacon accuracy is rounded to 2 decimals. Let us do this in JS when it's necessary please. about cordova-plugin-ibeacon HOT 2 CLOSED

You are scanning for a trigger at a distance of 1.5mm! That really isn't a sane use-case for iBeacons, For a start you have to know exactly where your Bluetooth aerial is in your phone, to put up against your iBeacon, even if the accuracy property where remotely accurate to that order of magnitude. If you monitor the values delivered by the phone, they bounce around so much you can't possibly guarantee that scale. Accuracy is a big misnomer, I'd think of it as "very rough distance assuming you have calibrated your iBeacon properly".

Therefore it makes more sense to cap the "accuracy" property at the 1cm level, and not give anyone the false impression it is a reliable measure of distance. If you think you have a case where you have found a way to be accurate beyond this level then firstly I'd love to hear about it and also I would imagine you would be using the raw RSSI and Tx values to calculate the distance yourself rather than using the Android and iOS algorithms which are doing that their own way.

from cordova-plugin-ibeacon.

You are right. This is a weird issue request / bug report.

We currently have some iBeacons that seem to behave a lot different than the newer Estimote beacons we now have.

You can close this issue, as it's not a sensible request.

from cordova-plugin-ibeacon.