Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

onChangeAction - inconsistent results #64

Open
g-pex-aerian opened this issue May 11, 2022 · 0 comments
Open

onChangeAction - inconsistent results #64

g-pex-aerian opened this issue May 11, 2022 · 0 comments

Comments

@g-pex-aerian
Copy link

Hello, I'm currently working on an App which we are using estimote beacons in conjunction with a map. We have an issue where Beacons are intermittently flicking in and out of the zones despite not physically moving away from them nor anything interrupting the line of sight.

To try debugging this issue I have setup a new App with just Estimote installed and I'm logging the onChangeAction.

I leave the device still with 4 beacons about 1 metre away in various directions.

Two of the beacons are labeled POI which is a 2.5m zone.
Two of the beacons are labeled ROOM which is a 5m zone.

Expected behaviour:
The onChange action is called once or twice per zone populating the array with two beacons. It should then not be called again until the device is moved away from the beacons.

Actual behaviour:
With the device and beacons stationary and no more than 1m apart, the onChangeAction is called intermittently with beacons in both zones appearing and disappearing as shown in the console log below:
image

Is there anything I can do to either the App or the beacons to make this much more consistent? It makes the beacons completely unusable for our usecase if we cannot rely on the beacons to accurately report when they are in a zone and when they have left that zone.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant