Configure BLE beacons
Configuration for BLE beacon in NFC passes
When issuing an Apple Wallet pass for Apple iPhone/iPad applications, a pass provider can set a location value, which could comprise GPS coordinates or a BLE beacon UUID, with optional major and minor values. Refer to the Apple developer documentation on beacons for information on setting the beacons for a specific pass. If more involved with designing your own passes there is Apple developer information about adding "relevance information" using iBeacons to display passes on a lock screen.
Configuration for BLE beacons on the VTAP reader
When a VTAP100‑PRO‑BW reader is in Cloud mode, the necessary beacon settings will be defined through VTAP Cloud.
For a VTAP100‑PRO‑BW reader in Local mode, the UUID, major and minor are all defined in the VTAP config.txt file by the BLEBeacon setting, along with optional beacon name (for logging). Multiple beacons can be defined in config.txt but only one can be active at any one time. Alternatively, remote management command for beacons (@BLEBeacon) can be used to dynamically change the advertised beacon.
Example: Demonstrate BLE beacon using OriginPass
The OriginPass demo mobile NFC pass already has a UUID assigned:
4CE2EF69-4414-469D-9D55-3EC7FCC31234.
If you don't already have one, obtain an OriginPass from Dot Origin by visiting https://originpass.com/VTAP/ and add it to your NFC Wallet. (You will require a username and password - contact vtap‑support@dotorigin.com to get these.)
Then add this line to your config.txt file:
BLEBeacon=i,loyaltybeacon,4CE2EF69-4414-469D-9D55-3EC7FCC31234,1,1
When an Apple iPhone, with this demo pass in its NFC Wallet, comes within range of your VTAP reader, the BLEBeacon will trigger an alert about the pass, which looks like this: