17,117
edits
Changes
Jump to navigation
Jump to search
To use this service you will need an account with https://nuki.io/
Contact us if you want to participate in the beta test.
== Capabilities ==
== Limitations ==*Currently As of 1 September 2023 you will need a [https://nuki.io/en/smart-hosting/pricing/ Nuki Smart Hosting subscription].* Nuki smartlocks can store a maximum of 100 entry codes at a time.* Booking names in Nuki smartlocks have a maximum length of 20 characters and guest names may be cut off. This will not be visible to guests, only users with access to Nuki web will be able to view booking names.* A given lock can only keypad authentication is supportedbe used in one property, however it may be used for multiple rooms within that property.* If using the synchronise code option, all locks must support code entry.
== How it works ==Bookings are sent to locks "Days in Advance" prior to check-in. *An entry code/user named Booking'''Step 4:{booking number} is added Set up an Auto Action Email to the lock, viewable at [https://web.nuki.io/#/pages/smartlocks web.nuki.io] or in the Nuki app.*A booking info code named NUKI_PIN is created which will show the pin number valid for the booking.Updates are sent periodically. To instantly send updates, click "Send Bookings to Locks".If the keypad code, booking dates, or room changes, those details will be sent PIN to locks.guests'''
If a booking *Go to {{#fas:cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS. A template is cancelled available which you can further customize. Use the associated entry code will be deleted from context help (?Icons) in the Auto Action and on the help page (click on HELP in the top right menu) for further instructions.*Create an Auto Action Email which includes the template variable for the pin which is [BOOKINGINFOCODETEXT:NUKI_PIN]. '''Step 5: Activation''' *Tick "Code" if you grant access via keypad*Tick "App" if you grand access via the Nuki app*Tick "Code" and "App" if you grant access both via keypad and via the Nuki app = How it works === Syncing ==Bookings are automatically sent to locks the number of "Days in Advance" prior to check-in which you have selected.
=== Nuki pin limitations ===
[[Image:nuki_delete_user '''Bookings are not being sent to locks and cannot be viewed by clicking the view bookings in locks button''' Your account may not be properly authenticated. 1. Click "Disconnect" 2.png|900px|link=]]Click "Connect to Nuki"[[Media:nuki_delete_user 3. Sign in to your Nuki account if prompted and allow Beds24 access.png|view large]]
== Disconnect==
no edit summary
[[Category:Self-Check-in]]
[[Category:Lock Systems]]
[[Category:Automation]]<div class="heading">Nuki COMING SOON</div>
This page is about the menu {{#fas:cog}} (SETTINGS) APPS & INTEGRATIONS > NUKI
For Beds24 the normal channel manger fees apply.
*Beds24 can send booking data to Nuki locks.
*Auto-Check-in: when a lock is first opened by the guest the info code "CHECKIN" will be added to the booking.
<span style="color:#fe746c;“ >{{#fas:exclamation-triangle}} </span> One beds24 account can only connect to one Nuki account. If you want to connect to multiple Nuki accounts you could use Sub accounts (with each Sub account connected to a different Nuki account). = Set Up =What you need =
To use this service you will need:
*A At least one Nuki Smart Lock.*A Nuki Keypad.
*A [https://nuki.io nuki.io] account.
*A [https://nuki.io/en/smart-hosting/pricing/ Nuki Smart Hosting subscription].
<span class="" style="color:#fe746c; font-size: 120%" >{{#fas:gift}} </span> '''Special offer for Beds24 cusotmers: Receive a 10% discount with the voucher code Beds24/10'''
Using keypad codes requires a Nuki keypad to be setup.
= Set Up =
'''Step 1: Connect your Nuki Account'''
*Click on "Connect to Nuki".
*Sign in with your Nuki account if prompted.
[[Media:nuki_auth.png|view large]]
'''Step 2: Set when bookings should send to locks'''
*The "Start Time" and "End Time" define the earliest Check-in time and latest Check-out time.
*The "Days in Advance" sets the days before check-in that the booking is sent to the lock.
'''Step 3: Map your locks to your rooms'''
Bookings will be sent to the lock mapped to the room assigned to the booking, if there is no lock mapped for the room the booking will be sent to the common lock (if one is mapped).
If both a room lock and a common lock are mapped, the booking will be sent to both.
The room lock and the common lock will use the same PIN.
Multiple common locks can be specified with a space between each of the lock mapping codes.
*Click on "Get Codes"
You will see one identifier and name for each lock. Click Select the correct lock and save. [[Image:nuki_mapping1.png|500px|link=]][[Media:nuki_mapping1.png|view large]] For each room/unit click on the name of the lock that is associated with the room.
[[Image:nuki_mapping.png|500px|link=]]
[[Media:nuki_mapping.png|view large]]
Entry codes/users can only be used during the booking period, they will not provide access before or after.
*Updates to locks are sent periodically. To instantly send updates, click "Send Bookings to Locks".
*An entry code/user named Booking:{booking number} is added to the lock. Click on the "View Bookings in Locks" button to check which bookings have already been sent. You can also see bookings on [https://web.nuki.io/#/pages/smartlocks web.nuki.io] or in the Nuki app.
*A booking info code named NUKI_PIN is created on the "Info" tab of the booking, this will show the access code for the booking.
*If a keypad code, booking date, or room changes, those details will be sent to locks.
*If a booking is cancelled, the associated entry code or user will be deleted from locks.
*The associated entry code or user of a booking sent from Beds24 will be removed one day after check-out.
<span style="color:#fe746c;“ >{{#fas:exclamation-triangle}} </span> If a Nuki lock is offline when an update is sent, the entry code will not be added until the lock comes online again.
== App and code entry methods ==There are two ways bookings can be sent to locks: app and code. You can select one or both methods. === App entry ===If the "App' tickbox is selected, bookings will be sent to locks as users. *Nuki will send guests an email containing an invitation, guests who accept this invitation will be able to unlock the Nuki lock using the Nuki app.* Guests have 48 hours to accept the invitation.* There is no way to resend a Nuki app invitation if a guest does not accept it in time. However, you may go to [https://web.nuki.io/#/pages/smartlocks web.nuki.io], select Devices, click the desired smartlock, go to the Users tab, then find the booking and click delete. You can then visit the Beds24 Nuki integration at {{#fas:cog}} (SETTINGS) APPS & INTEGRATIONS > NUKI and click "Send bookings to Locks". This will cause Nuki to create a new user and send a new invitation to the guest.*When the user is deleted from the lock, Nuki will send an email to the guest informing them that they no longer have access to the lock. [[Image:nuki_delete_user.png|900px|link=]][[Media:nuki_delete_user.png|view large]] ==== Allow remote app access ====By default guests must be physically close to the lock to unlock it with the app. The "Allow remote app access" will allow guests to use the app to unlock a lock from anywhere.* If set to "Yes", all bookings in the room will be allowed to use remote app access.* If set to "Info code", bookings with the info code "NUKI_REMOTE" will be allowed to use remote app access. === Code entry ===If the "Code" tickbox is selected, bookings will be sent to locks as entry codes. Guests will need to enter these codes on a Nuki keypad to unlock the associated Nuki lock. === Manually changing pins codes ===# Navigate to Account, Preferences, {{#fas:cog}} (SETTINGS) ACCOUNT > PREFERENCES "Bookings, " and add "NUKI_PIN" to your Booking Info Code Values.
# You can now manually add a NUKI_PIN info code to your bookings.
[[Image:nuki_set_pin.png|x300px|link=]]
[[Media:nuki_set_pin.png|view large]]
Nuki keypad codes must:
# Be exactly six digits long.
# Not contain the number zero.
# Not start with "12".
# Be unique to the lock.
<span style="color:#fe746c;“ >{{#fas:exclamation-triangle}} </span> If you manually set an invalid NUKI_PIN, it will be overwritten with a randomly generated pin the next time bookings are sent to locks. Each code can only be used once per lock. Before you can reuse a code it has to be removed from the lock.
== Information sent to guests Custom Start and End access times ===== Keypad The access start and end times can be customized per booking using booking info codes ===. * For keypad entry A booking info code bookings, Nuki does not send any information to guests'''ACCESS_STARTTIME''' with a time of day (23:59 format) as the text will override the default start time.=== App access ===A booking info code '''ACCESS_ENDTIME''' with a time of day (not currently supported23:59 format)* For app access bookings, Nuki as the text will automatically send an email to guests that provides access via override the Nuki appdefault end time.* Guests have 48 hours Start and end dates can be set relative to accept the invitationcheck in and check out date by defining times greater than 24 or negative.* There is no way to resend For example :- ACCESS_STARTTIME = -10:00 will create a Nuki app invitation if a guest does not accept it start time 10 hours before midnight of the check in time. Howeverday, you may go to [https://webi.nukie.io/#/pages/smartlocks web.nuki.io], select Devices, click 14:00 on the desired smartlock, go to the Users tab, then find the booking and click deleteday before check in. You can then visit the [https *Booking Info code = '''ACCESS_STARTTIME'''*Booking Info Text = '''-10:00''' For example :- ACCESS_ENDTIME = 34:00 will create an end time of 10:00 one day after checkout (34 = 24 + 10 hours) *Booking Info code = '''ACCESS_STARTTIME'''*Booking Info Text = '''34://beds24.com/control2.php?pagetype00''' = Troubleshooting =syncronisernukiio Beds24 Nuki integration tool] and click "Send bookings to Locks" to make Nuki send a new invitation to the guest.
Click on "Disconnect" to terminate the connection.
