-
Notifications
You must be signed in to change notification settings - Fork 1
Clearing a device
A ZKTeco machine holds a limited number of punches — an F22 holds about 30,000. When it fills, it stops recording. So sooner or later you will want to empty one.
Reading a machine never erases it. That is deliberate. A punch that has not yet been matched to an Active employee exists nowhere but on the device, and a read that erased it could not give it back.
Some other integrations offer a "clear on fetch" checkbox. This app does not, because the moment such a box is ticked, one mis-typed Attendance Device ID turns into permanently lost attendance.
On Nexus ZKT Settings, press Clear Device Memory.

You have to pick the machine and type its name back before the red Erase button will do anything. If the name does not match, nothing happens.
- Run a sync, and let it finish.
- Open the Nexus Attendance Log and check the line for that machine. If it says punches came from people with no matching active Employee, those punches are not in ERPNext and will be lost. Fix the Attendance Device ID on those people and sync again first.
- Then erase.
bench --site your-site execute \
nexus_zkt_integration.nexus_biometric_attendance.api.erase_device \
--kwargs "{'device_id': 'front-door'}"The same warning applies, without the confirmation box to save you.
Getting started
Using it
When it goes wrong
For developers
Legal