Choose an access method for Spaze Storage
Separate the working booking-code flow from personal credentials and reader configuration.
Before you begin
- Confirm which kiosk application and version your installation runs.
- For the current Spaze Storage handoff, open the matching booking and use its labelled codes.
- Treat personal authentication as an integration requirement until it has been connected to locker authorization and tested.
Verified against integrate-nekospaze-app at 5d1abe32660e on 8 September 2026. The implemented user flow is booking PIN access; personal and staff authentication need integration.
Step by step
Use the current booking method
The parcel-flow kiosk accepts a six-digit booking PIN. It finds matching booking-access rows for this device's mapped resources and combines their DropOff/PickUp actions. Numeric collisions can produce multiple matches; unambiguous lookup needs implementation before action separation can be guaranteed. This path does not identify the person holding the code.
Distinguish personal credentials
Face, QR, card/NFC hardware, phone number with passcode, and email with password have configuration or implementation pieces elsewhere in the source. MIFARE-specific authentication is not established by this review. None is connected to personal access in this kiosk's locker flow.
Check reader wiring separately
Setup lists HID card readers, Duali DQ-CUBE QR/NFC readers, and a HIK-VISION face terminal. Current reader listeners and Scanner test are diagnostic. A recognized scan is not linked to a person, booking authorization, or door opening in the current parcel flow.
Require authorization after identification
For a personal-access installation, the implementation must resolve the credential to a person and check that person's active entitlement to this compartment and action before sending an open command. Reader detection or a successful account login alone is insufficient.
You’re ready when
You know which method works today and what must be implemented before personal credentials can control locker access.
Troubleshooting
- Scanner test shows my card but no locker opens
- This is the current diagnostic behavior. Use the booking PIN flow where appropriate; do not treat scan output as an access decision.
- Changing receiver or staff authentication has no effect
- Those setup selections are stored but are not enforced by the current PIN or staff routes. An application change is required to implement the selected policy.
- My personal passcode or building QR is rejected
- Use the code on the locker booking. Personal passcodes, building QR credentials, and the booking code are different credentials.
Technical details
- Booking access code / accessCode
- Here, accessCode means the booking credential, not a separate login grant or resolver. The current six-digit kiosk input matches booking_accesses.code. DropOff opens for deposit; PickUp opens and completes the booking. This is bearer access, without personal identification.
- Face
- The setup hardware catalog includes a HIK-VISION face terminal. There is no personal face-authentication route that authorizes a locker open in this kiosk.
- QR
- Duali DQ-CUBE is listed for QR/NFC reader diagnostics. Scans are not connected to parcel-flow access. A booking QR, building pass, and personal QR must not be assumed interchangeable.
- Card, MIFARE, and NFC
- HID/DQ-CUBE capture and separate card provisioning exist. No MIFARE-specific authentication implementation was found. Verify the exact card technology and reader, identifier format, enrollment, and person-to-locker authorization before claiming support.
- Phone number + passcode
- A personal identity option in the wider authentication model. The current kiosk has no phone-and-passcode entry or locker authorization flow.
- Email + password
- A personal identity option in the wider authentication model. The device's Client ID and Client Secret authenticate the installation; they are not a user's email-and-password locker login.
Common questions
- Is a booking PIN the same as a personal passcode?
- No. A booking accessCode authorizes a booking action through possession of the code. Phone number with passcode is a personal identity method and is not connected to the current kiosk flow.
- Does NFC mean every phone or card will work?
- No. NFC describes an interface, not a universal credential. Confirm the exact reader, card technology, identifier format, enrollment, and authorization integration. The current kiosk has no working personal NFC unlock flow.
- Does staffAuth protect Settings or Restock?
- No. The reviewed routes do not challenge a staff credential. The setting alone cannot protect maintenance actions.
Still stuck? Tell support what happened and which step you reached.
Email support