MOCA Console has a batch beacon import tool. This tool allows enables users to upload of any number of beacons, only limited by your licence, in an easy way.
To upload beacons in bulk please do the following:
- Open the MOCA Console.
- Go to Beacons
- Click on Upload Beacons
- Download the example CSV as to have a guide of the basic headers supported.
- Edit that CSV file so it has all the beacons you want to upload and their attributes.
- Click on Choose File and select the edited CSV.
- Upload the CSV file.
Here is a list of supported headers:
| Header | Example Value | Description |
| config.name* | TestBeacon | Unique name for the beacon |
| config.code | 1234 | Unique identifier of the beacon. Used to update beacons. |
| config.description | Hi I'm a test beacon | Description of the beacon |
| config.provider* | MOCA | Beacon provider |
| config.uuid* | 03a53b90-d07a-11e9-826f-2a2ae2dbcce4 | iBeacon UUID on the device |
| config.major* | 1 | iBeacon major on the device |
| config.minor* | 2 | iBeacon minor on the device |
| config.eddystone.namespace | namespace | Eddystone namespace on the device |
| config.eddystone.instanceId | 1234567 | Eddystone instance ID on the device |
| config.eddystone.uidEnabled | true | Eddystone status of UID |
| config.eddystone.telemetryEnabled | true | Eddystone status of TLM |
| config.eddystone.eidEnabled | true | Eddystone status of EID |
| config.eddystone.urlEnabled | true | Eddystone status of URL |
| config.eddystone.url | https://www.mocaplatform.com | Eddystone URL on device |
| config.password | immapasword | Device password (only Kontakt devices) |
| config.enterRssi | -20 | RSSI at which beacon is entered |
| config.exitRssi | -90 | RSSI at which beacon is exited |
| config.txPower | 5 | Device TX Power (only Kontakt devices) |
| config.advertisingInterval | 350 | Device Advertising Interval (only Kontakt devices) |
| modelId* | 1 | Hardware definition in database |
| state | INSTALLED | Install status and health of the device |
| locationGroup.name | MOCA_HQ | Region where the device is registered |
| place.name | Barcelona | Place where the device is registered |
| zone.name | Sants | Zone where the device is registered |
| geoCoordinates.floor | 12 | Floor where the device is installed |
| geoCoordinates.longitude | 41.3781148 | Longitude where the device is installed |
| geoCoordinates.latitude | 2.1408857 | Latitude where the device is installed |
Values with * are considered not optional.
Our experience with large Beacon deployments has taught us to always fill all possible fields to maximize both deployment efficiency and data quality given by the deployed devices.
Comments
0 comments
Article is closed for comments.