Changes

Jump to navigation Jump to search

Nuki.io

2,291 bytes added, 13:52, 29 July 2020
no edit summary
[[Category:Self-Check-in]]
[[Category:Lock Systems]]
<div class="heading">Nuki COMING SOON</div>
This page is about the menu {{#fas:cog}} (SETTINGS) APPS & INTEGRATIONS > NUKI
To use this service you will need an account with NukiFor Beds24 the normal channel manger fees apply.io. <div style="display:none">
For = Capabilities =*Beds24 can send booking data to Nuki locks.*Auto-Check-in: when a lock is first opened by the normal channel manger fees applyguest the info code "CHECKIN" will be added to the booking (coming soon).
== Capabilities =Limitations =*Beds24 Nuki smartlocks can send booking data to Remotelock locks.*Multiple rooms can connect to one lockstore a maximum of 100 entry codes at a time.*Auto-Check-Booking names in: when Nuki smartlocks have a lock is first opened by the maximum length of 20 characters and guest the info code "CHECKIN" names may be cut off. This will not be visible to guests, only users with access to Nuki web will be added able to the view booking.*Support for Resortlocksnames.
Remotelock provides various regional servers, the main one we connect to is the US = What you need =To use this service, if you will need to connect to a regional : *At least one (for example Japanese) please let us know and we can configure your Nuki Smart Lock.*A [https://nuki.io nuki.io] account accordingly.
== Limitations ==Using keypad codes requires a Nuki keypad to be setup.
== Set Up =='''Step 1: Connect your Nuki Account''' *Click on "Connect to LockstateNuki". *Authorize Sign in with your Nuki account if prompted.*Click "Allow" to let Beds24 to access view and manage your Nuki accountand locks.
When successfully connected you will see the Remotelock account you are connected to[[Image:nuki_auth.png|500px|link=]][[Media:nuki_auth.png|view large]]
*The "Pin Strategy" defines how the access code is constructed. '''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'''
*Click on "Get Codes"
You will see one serial number identifier and name for each lock. Click on the serial number of the lock that is using the lock.
[[Image:agoda_room_mappingIf you have a common door with a Nuki lock i.png|500px|link=]][[Media:agoda_room_mappinge. a front door or a gate map the applicable code enter the code for this lock in "Common Lock" Click on the name of the lock that is associated with the door.png|view large]]
Leave this field blank if you do not have a common lock.
If you have a common lock for multiple units you can enter the same lock serial number for each unit[[Image:nuki_mapping1.png|500px|link=]][[Media:nuki_mapping1.png|view large]]
Note: Lockstate uses several servers. If you are not redirected back to Beds24 send us a support ticket via the SUPPORT button in the top left of your Beds24 control panel.
For each room/unit click on the name of the lock that is associated with the room.
[[Image:nuki_mapping.png|500px|link== How it works ==]]Bookings get sent to the locks at the set time prior to check-in. A booking info code named LOCKSTATE_PIN is created which will show the pin number valid for the booking[[Media:nuki_mapping. png|view large]]
You can change '''Step 4: Set up an Auto Action Email to send the pin manually in the LOCKSTATE_PIN booking info code and the new pin will be sent PIN to the lock at the next update.guests'''
To force no pin *Go to be sent {{#fas:cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS.*Create an Auto Action Email which includes the template variable for a booking, change the value of the LOCKSTATE_PIN booking info item to none, (i.epin which is [BOOKINGINFOCODETEXT:NUKI_PIN]. the word "none")
Updates are sent multiple times per day '''Step 5: Activation''' *Tick "Code" if you grant access via keypad*Tick "App" if you grand access via the Nuki app*Tick "Code" and send bookings for the selected days in advance. To instantly push updates through click "Send Data to LockstateApp". if you grant access both via keypad and via the Nuki app
If = How it works === Syncing ==Bookings are automatically sent to locks the dates number of the booking "Days in Advance" prior to check-in which you have been changed or the booking has been moved to a different room those details will be sent to the locksselected.
If bookings are cancelled we delete Entry codes/users can only be used during the guest out of LOCKSTATE. This booking period, they will remove the not provide accessbefore or after.
The Email address of *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 guest is "View Bookings in Locks" button to check which bookings have already been sent to Lockstate. You can set up Remotelock to automatically send Emails 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 guestassociated entry code or user will be deleted from locks. Alternatively you can create an Auto Action in SETTINGS > GUEST MANAGEMENT > AUTO ACTIONS*The associated entry code or user of a booking sent from Beds24 will be removed one day after check-out.
The template variable for <span style="color:#fe746c;“ >{{#fas:exclamation-triangle}} </span> If a Nuki lock is offline when an update is sent, the pin is [BOOKINGINFOCODETEXT:LOCKSTATE_PIN]entry code will not be added until the lock comes online again.
== Auto Check-in App and code entry methods ==Auto check-in will add a booking info item called CHECKIN There are two ways bookings can be sent to the booking when the guest first uses the locklocks: app and code.To use auto check-in you must setup a webhook to send notifications from the lock to Beds24You can select one or both methods.
There are two steps === App entry ===If the "App' tickbox is selected, bookings will be sent to the webhook setup:locks as users.
1*Nuki will send guests an email containing an access code that will allow them to unlock the associated Nuki lock with 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) Add APPS & INTEGRATIONS > NUKI and click "Send bookings to Locks". This will cause Nuki to create a Webhook Notification Contact in Remotelocknew 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.
the URL of the webhook must contain your Beds24 ownerId number at the end like ?ownerid[[Image:nuki_delete_user.png|900px|link=12345]][[Media:nuki_delete_user.png|view large]]
https://api=== Code entry ===If the "Code" tickbox is selected, bookings will be sent to locks as entry codes.beds24.com/lockstate.com/notify.php?ownerid=<Your Beds24 owner ID>
The Content Type must be "JSON"Guests will need to enter these codes on a Nuki keypad to unlock the associated Nuki lock.
The secret === Manually changing codes ===# Navigate to {{#fas:cog}} (SETTINGS) ACCOUNT > PREFERENCES "Bookings" and add "NUKI_PIN" to your Booking Info Code Values.# You can be left emptynow manually add a NUKI_PIN info code to your bookings.[[Image:nuki_set_pin.png|x300px|link=]][[Media:nuki_set_pin.png|view large]]
2) Add a Notification in RemotelockNuki keypad codes must:# Be exactly six digits long.# Not contain the number zero.# Not start with "12".# Be unique to the lock.
The notification type is "Webhook<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.
The Webhook Notification Contact is the contact you created in step 1)= Troubleshooting =
The source should '''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. Click "AccountConnect to Nuki" 3. Sign in to your Nuki account if prompted and allow Beds24 access.
The Events must be "Access Granted" and "First Access Only" == Common Problems ==Lockstate have two types of access: users and guests. Bookings from Beds24 create guests.  == Disconnect==
Click on "Disconnect" to terminate the connection.
 
</div ">

Navigation menu