WARNING We are discontinuing support for Firmware below 4.x with these updates (Update: Firmware 4.0 and 4.x were introduced in 2017 after that in 2019 we changed firmware versioning schema. Current firmware version schema is 1.10 and 1.1x/1.x/2.x).
| Kontakt.io Secure | Kontakt.io Standard | |
| Beacon firmware | 4.0 (from 2017) or newer (starting from 2018 firmware version schema is 1.10 and 1.1x/1.x/2.x) | 3.1 or older |
| Unique ID | Not available | Part of the Scan Response Packet |
| Eddystone | Yes | Yes |
| Battery-life | No impact on battery life | No impact on battery life |
| Software lock in Beacon firmware | Yes | Yes |
| Shuffling | Shuffling available, see below. | Not available |
| Broadcast iBeacon identifiers |
Fixed: Proximity UUID |
Fixed: Proximity UUID, Major, Minor, BeaconID, MAC-address |
| Broadcast Eddystone identifiers |
Fixed: Namespace |
Fixed: Namespace ID, Instance ID, URL, MAC-address |
| Configuration method | Secure Communication: new configurations created in API as encrypted package, which is fetched, and applied in a single transmission. Beacon confirms successful config. | Configuration: new configurations created in API and fetched by the configuring device, which connects to beacon by using beacon specific password, and requires a back and forth communication for configuration of every setting. |
| Kontakt.io Proximity SDK | Required. Must be implemented in the app to resolve shuffled identifiers with Kontakt.io Proximity API. | Not required |
| Configuration can be done via? | Kontakt.io Admin Apps and/or an App that has implemented Kontakt.io Proximity SDK 2.0 | Kontakt.io Admin Apps and/or 3rd party app by using the beacon-specific passwords. |
If you would like to learn how to upgrade the firmware of your beacons visit this tutorial.
Comments
0 comments
Article is closed for comments.