A site round checkpoint can use a Bluetooth beacon or an NFC tag. With a beacon, a staff member on a round checks in when the MyWatchtower phone app reads the beacon nearby. With a tag, the staff member holds the phone near the tag to check in. Your community, or a contractor that your community hires, buys the beacons and the tags and puts them up. This article tells you how to set up a KKM K4 beacon, which tags to buy, how to link each one to a checkpoint, and how to replace a battery, a beacon or a tag.
Before you start
Your role needs both of these permissions to open the checkpoints and set them up:
- The site round routes write permission (
site_round_routes:w).
- The site rounds read permission (
site_rounds:r).
The checkpoints are in Settings > Settings > Site rounds, on the Checkpoints view. If your community gave site rounds another name, the settings section and the tabs show that name.
To read a beacon or a tag while you set it up, use the MyWatchtower phone app on a phone with Bluetooth and NFC. The web app cannot read beacons or tags. On the web, you type the identifier of the beacon or the tag.
Set up a K4 beacon
Set up each K4 in the KBeaconPro app of KKM before you put it up.
A new K4 has a default password of sixteen zeros (0000000000000000). Anyone near the beacon with the KBeaconPro app and that password can change its setup. Set a new lock password on each beacon, as step 6 says.
1. Install the KBeaconPro app on a phone, and switch on Bluetooth.
2. Open the app, and connect to the beacon. Type the default password when the app asks for it.
3. Set one advertising slot to Eddystone UID. Write down its namespace (20 hex digits) and its instance (12 hex digits). Together they are the identifier of the beacon.
4. Set a second slot to Eddystone TLM. If the app offers to encrypt the TLM frames, leave them unencrypted. MyWatchtower reads the battery level of the beacon from this slot. Without it, the checkpoint shows no battery reading.
5. Set the Tx power of the Eddystone UID slot. Start with a low Tx power. A high Tx power lets a phone read the beacon from across a room, so a staff member can check in from far away. JEKA has not yet measured a K4 Tx power or an advertising interval for site rounds. This article will give those values when they are measured. Until then, keep the advertising interval that the app gives.
6. Change the lock password from sixteen zeros to a new password. Keep the password where your community keeps its other passwords. You need it to change the beacon later.
7. Save the setup to the beacon. Write a number on the beacon, so that you can tell it apart from the others.
MyWatchtower also reads iBeacon. An iPhone finds an iBeacon only by its UUID, needs precise location to read it, and does not read it while the phone is locked. Use Eddystone UID unless you have a reason to use iBeacon.
Choose NFC tags
The MyWatchtower phone app reads these tags on an iPhone and on an Android phone:
- NTAG213, NTAG215 and NTAG216 tags (NFC Forum Type 2, ISO 14443).
- ISO 15693 tags, such as NXP ICODE SLIX.
The tag's UID must be 4, 7, 8 or 10 bytes. NTAG213 and NTAG215 tags are the easiest choice. An iPhone does not read some Type 4 tags that an Android phone reads, so do not use Type 4 tags.
On a metal surface, such as a metal post, a gate or a door frame, use on-metal tags (also sold as anti-metal tags). A plain tag on metal is often not read. Outdoors, use tags that are made for outdoor use.
Link a beacon or a tag to a checkpoint
On a phone
1. In the phone app, open Settings > Settings > Site rounds.
2. On the Checkpoints view, tap a checkpoint to edit it, or tap Add checkpoint to add one.
3. In Method, select Beacon or NFC tag.
4. For a beacon, tap Find beacons, and hold the phone near the beacon. The list shows each beacon that the phone reads, with the strongest signal first. Tap the beacon to fill in its identifier. On an iPhone, an iBeacon shows only after you type its UUID in iBeacon UUID and tap Find.
5. For a tag, tap Scan tag, and hold the phone near the tag. The app fills in the Tag UID.
6. Optional: type a Label, such as the number that you wrote on the beacon or the tag.
7. For a beacon, set the range (see "Set the range of a beacon").
8. Optional: place the checkpoint on the map. A beacon or a tag checkpoint does not need a zone. The beacon or the tag proves the arrival.
9. Tap Save. For a new checkpoint, the button is Add.
If Find beacons cannot run, the app tells you why. For example, allow Bluetooth and location for MyWatchtower in the phone's settings, or switch on Bluetooth or location services. If Scan tag cannot run on an Android phone, switch on NFC in the phone's settings, or type the UID.
On the web
1. Open Settings > Settings > Site rounds.
2. On the Checkpoints view, select a checkpoint, or select Add checkpoint.
3. In Method, select Beacon or NFC tag.
4. Type the identifier:
- For a beacon, type Beacon identifier as
eddystone:<namespace>:<instance>, with the 20-digit namespace and the 12-digit instance from the KBeaconPro app. Type only the hex digits, with no0xand no spaces. For an iBeacon, typeibeacon:<uuid>:<major>:<minor>, with the UUID in its usual form with hyphens (8-4-4-4-12 digits) and a 4-digit major and minor in hex.
- For a tag, type Tag UID from the tag's label, in hex. Colons, hyphens and spaces between the bytes are allowed.
5. Select Save, or Add for a new checkpoint.
Each beacon or tag can be on one checkpoint only. If another checkpoint holds it, remove it from that checkpoint first.
Set the range of a beacon
Signal threshold (dBm) is the weakest signal that counts as an arrival, from -100 to -30 dBm. The default is -75 dBm. A higher number, such as -65, makes the staff member come closer to the beacon.
To set the range on site:
1. Put the beacon up at its place.
2. Stand where a staff member must be to check in, with the phone app open on the checkpoint.
3. Tap Set range from here. The app reads the beacon for 5 seconds. It then sets the threshold 5 dB below the average signal that it heard, so that a phone at that spot or closer counts as an arrival.
4. Tap Save.
Then test the arrival distance with Find beacons. First note the threshold that you saved on the checkpoint. Find beacons shows only while a checkpoint has no saved identifier, so use Add checkpoint for the test:
1. In the phone app, on the Checkpoints view, tap Add checkpoint, and select Beacon in Method.
2. Tap Find beacons. Walk away from the checkpoint, then walk back toward the beacon. Read the signal of the beacon in the list, and compare it with the threshold that you noted.
3. Close the dialogs without saving.
Start with a low Tx power and the -75 dBm default, and change the threshold until the arrival comes at the distance that you want.
If the app says that the phone did not hear the beacon, move closer, and try again.
Replace a beacon battery
The Checkpoints view shows the battery of each beacon in Battery and the last read in Last seen. A beacon shows Low battery when its battery is under 2.5 V. It shows Not seen when no phone read it for 14 days while rounds ran on its routes. People with the site round routes write permission also get a notification when a beacon's battery is low.
To replace the battery:
1. Replace the battery as KKM's guide for the K4 says. If the battery of your beacon cannot be replaced, replace the beacon (see "Replace a broken beacon or tag").
2. In the phone app, stand near the beacon, open its checkpoint, and tap Set range from here. If the app says that the phone did not hear the beacon, the beacon does not send its identifier.
3. In that case, connect to the beacon in the KBeaconPro app with your lock password, and check its setup (see "Set up a K4 beacon").
If Set range from here gives a threshold that you do not want, close the checkpoint without saving.
The battery reading changes after a phone reads the beacon on a round.
Replace a broken beacon or tag
When a beacon or a tag is broken or missing, put a new one up, and give the checkpoint its identifier:
1. Set up the new beacon (see "Set up a K4 beacon"), or get a new tag.
2. Open the checkpoint. The saved identifier cannot be edited. Select Replace.
3. Type the new identifier, or use Find beacons or Scan tag in the phone app.
4. Select Replace, then Save.
Rounds that already started keep the old identifier. New rounds use the new one. Take down the old beacon or tag.
Check in without a read
When the phone does not read the beacon or the tag, the staff member taps Check in without the beacon or Check in without the tag, and writes a note. The web app cannot read beacons or tags, so on the web the staff member always checks in this way at these checkpoints.
A check-in with no read is marked Not verified in Round history and in the round PDF. The note tells you why the beacon or the tag was not read. Many check-ins that are not verified at one checkpoint can mean that its beacon needs a new battery, its range is too small, or its tag needs to be replaced.
On an iPhone, keep the app open at iBeacon checkpoints. A locked iPhone does not read iBeacons.
Need help?
On a computer, select Help center in the navigation. On a phone, tap your picture at the top of the screen, then tap Help. Both open the MyWatchtower support page. You can also contact the management office of your community.