Cloud Beacon Settings

Your Cloud Beacon is a multi-functional device.  It can act as a 'traditional' Beacon, connect and communicate with the Cloud, scan for local WiFi devices and for local Bluetooth devices.  You can configure these settings for all these functions from your Web Panel.

If you haven't already configured your Cloud Beacon, you'll need to do this first. Just follow our Cloud Beacon Quickstart guide.

We can breakdown Cloud Beacon settings into four basic groups

  • Beacon settings
  • Wifi Connectivity
  • Wifi Scanning
  • Bluetooth scanning
  • Communicating with the Cloud

Beacon settings

Your Cloud Beacon acts as a traditional Beacon with the exception that it is set in non-connectable mode.  This means that you cannot connect to the Beacon with their mobile device, enter a password and change its settings.  You can only change Beacon settings for your Cloud Beacon from the kontakt.io Web Panel.

Wifi Connectivity

To be able to communicate with the cloud, your Cloud Beacon needs to connect to a local access point (router).  This group of settings is responsible for setting your WiFi connection.

  • SSID Name (network name)
  • SSID Key (network password)
  • SSID Auth
  • SSID Crypt

The network name and password are the values you would normally enter to connect any device to your WiFi network.

SSID Auth is the security protocol for your network.  This can be NONE, WPA_PSK or WPA_PSK2.

SSID Crypt can be NONE (if SSID Auth is also NONE), TKIP or AES.

Most modern networks use a combination of WPA_PSK2 and AES - considered to be the most secure.  If you are not sure what your router supports, then this combination is probably a good place to start.

Wifi Scanning

Your Cloud Beacon can identify and collection information for all in-range WiFi devices.  The Cloud Beacon will scan for WiFi devices according to the value of the WiFi Scan Interval, every 3 minutes by default.  Range 1 - 30 minutes.

Bluetooth scanning

The Cloud Beacon can also scan and collection information for BLE enabled devices.  These could be Beacons (kontakt.io and from other manufacturers), smartphones, or other Bluetooth Devices.

The BLE Scan Interval determines the wait time between each scan and the BLE Scan duration, the time the scan period lasts.  By default, these values are set at 5 seconds.  The Interval can have a range from 0 - 86400 seconds, and the duration, 0 - 3600 seconds.

Communicating with the Cloud

Finally, your Cloud Beacon will buffer information locally for all devices it is scanning and will send this information periodically to the cloud where it can be accessed using the kontakt.io Web Panel or our REST API.  It can also receive Cloud updates during Cloud Communication.

The Data Send Interval determines the wait between each connection to the cloud and data transfer.  The default is 5 minutes.  The interval can be set to between 2 - 60 minutes.

- 2016-03-07 16:23:59 UTC
Was this article helpful?
0 out of 0 found this helpful

Comments

Follow
  • Avatar
    Maximilian D

    Hi, I have got the cloud beacon configured and can see it in the web panel but can't find any data from scans and you said that "... the cloud beacon will send this information periodically to the cloud where it can be accessed using the kontakt.io Web Panel" . Would be great if you could point me in the right direction.

  • Avatar
    Marcel Florian

    Hello, same problem here. Can I access the collected data in any way (maybe from the beacon directly)? Thank you!

  • Avatar
    Adrian Ziobro

    Currently the data gathered by Cloud Beacons is available only through the API. You will find all the necessary documentation here: http://docs.kontakt.io/rest-api/guide/#analytics

    Web Panel will be update later (don't have an ETA yet, I'm sorry) with analytics functions, allowing you to visualise this data.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Review our cookies information for more details.