We have an enhancement to our existing solution in the education space which will be utilizing beacons around a point-based use case. These beacons will be deployed at client sites around the US but we would need to manage them centrally from our head office.
I have a few questions which I couldn't find answers to elsewhere on the site:
1) As I understand it our model would require a Kontakt Gateway on each site (eg; a GW16-2) to which each on-site beacon such as the SB16-2 or BP16-3 would communicate. As the Gateway is WiFi enabled and assuming each client was internet-connected, the Gateway would be integrated into our Kontact.io account allowing us to remotely manage each beacon that the Gateway could see. Is that correct?
2) Concerning the Gateway & Beacons at each client site; Judging by the product page on Koktakt.io I'm assuming that beacons such as the SB16-2 and BP16-3 are not WiFi enabled? Therefore if we had a large client-site or a site with lots of thick walls and so on, how would the site's gateway see all installed beacons? I could understand it if beacons were WiFi-enabled, they would register with the site's WiFi LAN and could be seen from any Gateway on that WLAN. Would a large-client-site require multiple on-site Gateways?
3) Finally; when adding beacons to my basket via the Kontakt Store there's a note which says: "You'll be able to choose the beacon format (iBeacon or Eddystone) after you add beacons to your cart." This could be taken to mean there are two fixed types of Beacon - one which supports Eddystone & one iBeacon. Yet elsewhere on the very same page, it states "Don't limit yourself to either Eddystone or iBeacon
Broadcast iBeacon and Eddystone frames together or just the ones you need."
I'm confused about the purpose of specifying the beacon format at the cart stage if Kontakt beacons offer both beacon protocols? Do we have to decide which protocol our beacons will use when ordering them?
Any help would be much appreciated. :-)
Please sign in to leave a comment.