We are developing a Windows Forms Application that reads beacons using
Windows.Devices.Bluetooth.Advertisement. BluetoothLEAdvertisementWatcher class.
This app is installed in a Windows 10 PC with a Bluetooth dongle, and we are testing estimote beacons technology to check if it fits our needs. In our observations we see (in our application, but also in the Settings panel -> Bluetooth option) that beacons seem to disappear for time to time (sometimes for more than 30 seconds), even if they are still (for example sitting on top of a table).
Is this a correct behavior? Has it something to do with Windows, or estimate beacons? What can we do to get more reliable readings? We have tried using a smaller Advertisement interval, stronger TX Power, but none of these options seems to help.
We were planning to place a big order of estimate beacons, but as it stands right now this does not fit our needs, because we need to read beacons that are in a closed space (and can be in motion) and all readings must be as accurate as possible so we can check when a beacon leaves the space (within a threshold of time that is acceptable), but since we cannot get consistent readings, it seems that we may have to check what other options are available.
We would appreciate your comments since we are in the process of reviewing what technology to use in our project.