Besides reading punches, Device Connect can look after a terminal for you: show its health, edit and delete its users, create a user for a new employee, copy faces and fingerprints to another terminal, correct its clock and restart it. This page explains each action, who may do it and what to expect. Every change is written to the audit log.
Be careful, and start small. Reading is safe. Changes act on a real door terminal. What is possible depends on the connection type and model: an action a connection cannot do shows "not supported here". Only the ZKTeco iFace702 has been used with a real device, and then for reading only; the write actions are tested against simulators and a fake SDK. Try each action first on a test user.
#Two switches must both allow it
- In SolaHR, your role must have the permission (below).
- On the connector PC, the setting Allow changes to devices must be on. It is off by default. While it is off, SolaHR shows "Changes to this device are turned off on the connector PC. Turn on device writes in the Device Connect page there."
#Permissions: manage versus owner-only
| Action | Who |
|---|---|
| Refresh info, read users, edit a user, enable/disable, delete a user, push an employee | Manage attendance devices... (Owner and HR Manager) |
| Sync time now, Restart device, Copy face/fingerprints, giving a device user a role above User | Run advanced device commands: Owner only |
Owner-only controls are marked owner only or hidden for everyone else: "Roles above User can only be set by the owner."
#Device health
Open a device and press Refresh info. The Device health card shows:
- Users, Faces, Fingerprints and Attendance logs, each as "used - free of total";
- firmware and serial number;
- the clock: "Device clock is correct", or "Device clock is about N min off" with Sync time now.
When the log is nearly full, a warning appears: "The device log is N% full. When it is full the device may stop recording or overwrite old punches. Make sure everything is imported, then clear the log on the device." Clearing the log is done on the device itself; SolaHR does not erase device records.
#Device alerts
On Attendance → Devices, a Device alerts card appears whenever a device has an open alert (it is hidden when all is well). Alerts: Not communicating, No punches today, Few employees enrolled, Sync failing, No punches yesterday and Backlog. Each row shows the last successful communication. People with manage rights can Mute (maintenance) a device for 4, 24 or 72 hours and Unmute it. Alerts go to the people responsible for attendance and devices, and they work whether or not the punch pipeline is switched on. Open alerts also stop automatic absences for affected employees (see Attendance).
#Sync time
Sync time now sets the device clock to the current time in the device's timezone. Punch times depend on the device clock, so do this when the clock drifts. Owner only.
#Restart
Restart device restarts the terminal. It is offline for a minute or two and scans during that time are not recorded. Choose a quiet moment. Owner only.
#Edit a device user
On Device users, open a user's menu:
| Action | What it does |
|---|---|
| Edit on device | Changes the name, card number, Role and an optional numeric New password, then Save to device. The password goes to the device and is never stored in SolaHR. |
| Disable on device / Enable on device | The person cannot punch until enabled again. Nothing is deleted. Needs a connection type that supports it (the ZKTeco SDK type; not ZKTeco direct). |
| Delete from device | Removes the user and their fingerprints and face from this device. Punches already received and the mapping in SolaHR are kept. |
Roles on the device are User, Enroller, Admin, Super admin; only the Owner sets a role above User. Command results appear in Recent commands with a state: Waiting for the connector, Running, Done, Failed, Unknown result, Not picked up in time or Cancelled. Failures are explained in words, for example "The device has no free space for this" or "The device refused the change. Check the Comm Key and that the device allows remote changes".
#Push an employee to the device
Push employee to device creates a user on the terminal for an employee and links the two in one step.
- Choose the employee, then the code (the employee number is suggested) and the Name on the device.
- Confirm. The user now exists on the terminal and is already mapped.
- The person enrols their face or fingerprint on the terminal itself (or you copy it from another terminal).
Names with Arabic letters need the right text encoding on the device record (UTF-8 first; see Add a device).
#Copy faces and fingerprints between devices
Owner only. Use it when a person works at two sites and should not enrol twice.
- Open the person on the source device and choose Copy face/fingerprints to another device.
- In Copy to, pick another active device on the same connector.
- Tick Create the user on this device if missing if the target does not have the person yet.
- Confirm.
The biometric data travels source terminal → connector PC → target terminal and is held only in memory for that moment. It never reaches SolaHR and is never stored. If a device ever answered with biometric data in a normal read, SolaHR would refuse it and store nothing. If the person has no face or fingerprint on the source you see "That person has no fingerprint or face on the source device to copy." Templates from different models are not always compatible; test with one person. This needs a connection type that supports it (the ZKTeco SDK type); it is software-tested only.
#Former employees still enabled on a device
When people who have left (their status is not active) still have an enabled user on a terminal, a notice says "N former employees are still enabled on this device". Disable former employees on this device lists them and, after you confirm, disables them. It is only a suggestion: nothing changes until you confirm, nothing is deleted, and you can enable them again. This too needs a connection type that can disable users.
#The audit log
Every change you make to a device (edit, enable, disable, delete, push, copy, time sync and restart) is recorded with who did it and when. Find it in the audit log. Passwords and Comm Keys are not stored in SolaHR in readable form.