Remote tracking of a BLE beacon

This demo is intended to show how to track remotely a BLE beacon moving inside the environment, using the Accuware dashboard opened on a tablet/laptop.

Prerequisites:

  • at least 6 BLE nodes.
  • a set of Accuware credentials (to access the Accuware dashboard).
  • a high quality reference system of the test location.
  • 1 BLE Beacon configured as explained inside this page.
  • 1 PC/laptop/tablet with a valid internet connection.

Instructions:

  1. Setup Accuware Bluetooth Beacon Tracker as described in this page.
  2. Login to the Accuware dashboard with your PC/laptop/tablet.
  3. Turn on ONLY the BLE beacon of interest!
  4. Add the BLE beacon to the list of known devices by following the instructions inside this paragraph.
  5. Click on BT Beacon Tracker > Map and select the Show switch for your BLE beacon (listed into the Devices table)
  6. Click on the Selected button below the map. You should now be able to see a yellow dot!

You can now ask to a colleague to go around with the BLE beacon and track his/her movements over the floor plan. The BLE beacon should be kept out of the pockets in the hands to get the best results.

Detection frequency: during your tests please give a constant look at the Last seen value of your BLE beacon (reported into the Devices table). The Last seen value represents how often your BLE beacon is detected by Accuware Bluetooth Beacon Tracker and this value must remain between 0 and 5 seconds in order to see a fresh location. If it is not like this, there can be 2 reasons:

  • Advertisement frequency of your BLE beacon: the advertisement rate of your BLE beacon is lower than 1 advertisement every 4 seconds. Please set your BLE beacon as explained inside this page.
  • Request interval of your BLE nodes: the request interval of your BLE nodes is lower than 1 request every 5 seconds. Please set your BLE beacon as explained inside this page.

Detection of a BLE beacon

This demo is intended to show how to detect 1 BLE beacon using the Accuware dashboard opened on a tablet/laptop.

WARNING: before proceeding with test of Accuware Bluetooth Beacon Tracker using only one node, please be aware that with one node, Accuware Bluetooth Beacon Tracker will not be able to triangulate the positions of the Bluetooth beacons detected. This means that the locations of all the BLE beacons detected will be equal to the location of the unique node installed (when looking at the Accuware dashboard and when calling the Accuware Bluetooth Beacon Tracker “stations” API).

Despite this, even with only one node, you will be able to test the Accuware Bluetooth Beacon Tracker API and make assertions regarding the proximity of the Bluetooth beacons detected with respect to the node by using the RSS values returned by the Accuware Bluetooth Beacon Tracker API. Please look at this article.

Prerequisites:

  • 1 BLE node.
  • a set of Accuware credentials (to access the Accuware dashboard).
  • a high quality reference system of the test location.
  • 1 BLE Beacon configured as explained inside this page.
  • 1 PC/laptop/tablet with a valid internet connection.

Instructions:

  1. Setup Accuware Bluetooth Beacon Tracker as described in this page.
  2. Login to the Accuware dashboard with your PC/laptop/tablet.
  3. Turn on ONLY the BLE beacon of interest!
  4. Add the BLE beacon to the list of known devices by following the instructions inside this paragraph.
  5. Click on BT Beacon Tracker > Map and select the Show switch for your BLE beacon (listed into the Devices table).
  6. Click on the Selected button below the map. You should now be able to see a yellow dot that represents the location of your BLE beacon! The dot will overlay with the unique BLE node.

Detection frequency: during your tests please give a constant look at the Last seen value of your BLE beacon (reported into the Devices table). The Last seen value represents how often your BLE beacon is detected by Accuware Bluetooth Beacon Tracker and this value must remain between 0 and 5 seconds in order to see a fresh location. If it is not like this, there can be 2 reasons:

  • Advertisement frequency of your BLE beacon: the advertisement rate of your BLE beacon is lower than 1 advertisement every 4 seconds. Please set your BLE beacon as explained inside this page.
  • Request interval of your BLE nodes:  the request interval of your BLE nodes is lower than 1 request every 5 seconds. Please set your BLE beacon as explained inside this page.