-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Eddystone wrong results #111
Comments
I would assume that this is a calibration related issue. The
It could also be possible that the actual distance calculation is flawed. You can find the implementation in |
The problem here, that with You need to get it from the You should override the
However when you choose these values below should be changed when we use
|
Thanks for the detailed explanation! May I ask what values you are setting for the That value will be used in Either the |
The I have checked the distance calculation and the result seems fine (sure it depends on the RSSI). The problem is the square error thresholds values should be changed for Eddystone. |
Changing the thresholds means accepting more errors in the equation system. That does not resolve the issue, it just hides it. Multilateration doesn't depend on the beacon you use. It just accepts distances. The fact that it produces larger errors for your Eddystone beacons means that either the distance calculation or the beacons calibration is flawed. Regarding the naming of |
Regardless of the table that said Different devices will receive advertising frames with very different signal strengths (because of their housing, placement of the BT radio antenna, ...). See RSSI Measurements for details. This is something we want to compensate for, I created issue #127 for that. |
Yes, it's around |
As stated above (edited, you might have read it before the edit):
|
So I am getting very different distances => very different root mean square => thresholds values are not accurate. Some devices may never receive a new locations if a developer choose one of the 3 thresholds. |
I am totally agree on this, but please read the comment on the other issue #127 |
Does this Library has been tested with Eddystone beacons ?
I am getting wrong location when i choose Eddystone protocol to my Kontakt beacon.
For Kontakt there is different values of RSSI :
Why all the locations are so far when using Eddystone and when i use iBeacon everything works fine ?
The text was updated successfully, but these errors were encountered: