With Nuki connected, QuietStay creates and removes keypad codes on the physical lock itself, so nobody has to programme one per booking.
Set it up
- In Settings, then Integrations, set Provider to Nuki smart locks.
- Paste a token generated in Nuki Web, under API, into API key, and press Connect. The token is checked against Nuki before it is stored.
- A row then appears for each published property. Paste its Smartlock ID — Nuki Web, your lock, its ID — and click away. A tick shows it saved.
How codes are created
Each night, for every mapped lock:
- bookings arriving within the next three days that have no code yet get a fresh six-digit code
- the code is valid from midnight the day before arrival until the end of the departure day
- no two live codes on the same lock are the same
- a booking with no guest surname is skipped, because a code with no name attached could be unlocked by anyone who knew the dates
Codes are removed when a booking is cancelled, and the authorisation is cleared about a day after the guest leaves.
Where a guest gets their code
The same place as any entry code — inside the guidebook, once they have identified themselves under the rules you set in Access codes.
If codes are not being created
Check the booking has a surname, then look at the property's card in Access codes: a failing lock shows Smart lock sync is failing, with the reason and how long since the last success. Reply to any email from QuietStay with that message and we will look at it with you.