Face, palm and fingerprint devices

Besides the USB fingerprint reader, WorshipHQ works with face, palm and fingerprint terminals that mount on a wall or stand at your door. Open Devices in the sidebar (under Attendance) to add one.

Choosing a device

• It must have a cloud server, ADMS or push setting. Ask the seller to confirm this in writing before you pay.
• Ask: can it send to a web address over HTTPS? If yes, it connects straight to WorshipHQ. If it only takes an IP address or plain HTTP, it still works through the small Device Bridge program on a computer in your building (see below).
• Choose what it reads (face, palm, fingerprint or a mix) and check how many people it holds. Face models usually hold a few thousand.
• Most face terminals are for indoors or covered entrances. It needs power and Ethernet or Wi-Fi.
• Buy one first and try it at your real entrance before buying more. Distances and speeds in a brochure are best case. Recognition works best when the person faces the camera, within about a metre, in good light, with no strong light behind them.

What works

• ZKTeco and compatible terminals (SpeedFace, ProFace, MB and iClock families, and many rebranded ones).
• USB fingerprint readers (ZKTeco SLK20R), used from the Fingerprint button on Attendance. See the USB scanner setup guide.
• Any other device or software that can send a web request, using a private link and token that WorshipHQ gives you.

Add a terminal

1. 1Open Devices and choose Add a device. Pick Face, palm or fingerprint terminal, name it (for example Main door), enter the serial number (SN) from its label or its Device Info menu, and tick what it reads.
2. 2Choose Setup and details on the new device. A progress list shows where you are: added, the device has contacted WorshipHQ, first scan received.
3. 3Choose how it reaches WorshipHQ. Directly: on the terminal open Communication, then Cloud Server Setting (some models say ADMS), type the server address shown, set the port to 443 and switch HTTPS on. Through a bridge computer: see the next section.
4. 4Set the terminal's date, time and time zone to your local time. Scan times come from the terminal's own clock.
5. 5Within a couple of minutes the device shows Online on the Devices page. Press Refresh to check straight away.

If the device cannot use HTTPS: the Device Bridge

Some terminals can only send to an IP address over plain HTTP. For those, WorshipHQ gives you a small program called the Device Bridge. In Setup and details, choose Through a bridge computer and download the two files.

1. 1Pick a Windows computer that will be on during services and is on the same Wi-Fi or router as the terminal. Install Python 3 on it from python.org if needed (tick "Add Python to PATH").
2. 2Put the two downloaded files in one folder and double-click the .bat file. A window opens and shows the computer's address. Leave it open.
3. 3On the terminal, set the cloud server address to that address, the port to 8081, and switch HTTPS off.
4. 4Ask your router to always give that computer the same address, so the terminal does not lose it.

The bridge only passes on the terminal's own messages, over a secure connection to WorshipHQ, and stores nothing. If the computer is off, the terminal keeps its scans and sends them when it reconnects (up to 36 hours later).

Put members on the device

The terminal identifies each person by a User ID, which is the number at the end of their member ID (42 for GBC-0042). Choose Send members to device and every active member appears on the terminal by name within a couple of minutes. Then, on the terminal, pick each person and enrol their face, palm or finger. Members whose number is shared with someone else are skipped, so the right person is never guessed.

What happens at a scan

• A person's first scan at a service checks them in, using your service times, with the same age groups as every other check-in. Scanning again at the same service changes nothing, so walking past twice is fine.
• When two or more people are recognised together, each is counted separately.
• Only people whose User ID matches a member are counted. Anyone else shows as "ID not matched" under Recent scans, so you can fix the User ID.
• Each scan appears under Recent scans with the device, what it read, and the result.

When should scans count? (scan hours)

Under Setup and details on each device, choose when its scans count, so a cleaner after service or someone passing on a Tuesday is not counted as attendance:

• During my service times (recommended): from a little before a service starts to a little after it ends, using the grace time in Settings, Service times. If you have not set up service times yet, every scan counts until you do.
• Only these days and hours: for example Sundays from 06:00 to 13:00.
• Any time: every scan counts.

A scan outside the hours is ignored, and still shows under Recent scans as "Outside scan hours".

Other devices and software

Choose Other device or software. WorshipHQ gives you an address and a private token. Anything that can send a web request with the person's ID (and optionally the time and the method: fingerprint, face or palm) checks them in.

Troubleshooting

• Never shows Online: check the terminal has internet, the serial number matches exactly, and the server address has no "https://". Directly: port 443 with HTTPS on. Through the bridge: the bridge computer's address, port 8081, HTTPS off. Check the date and time, then press Refresh.
• Online, but scans do not count: look at Recent scans. "ID not matched" means the User ID is not the number at the end of the member's ID. "Outside scan hours" means your scan hours ignored it.
• Members did not appear after Send members to device: the terminal picks them up the next time it checks in, which can take a couple of minutes. If they still do not appear, add them on the terminal by hand.
• Scan times are wrong: set the terminal's date, time and time zone.

Good to know

• Switch off stops a device from checking anyone in without removing it. Remove deletes it and its scan history; past attendance stays.
• Visitors are not enrolled on the device. Check them in by name or with a QR code.
• Face, palm and fingerprint data is sensitive. Get each member's consent before enrolling them, and a parent's or guardian's consent for children.