Changes

Jump to navigation Jump to search

Nuki.io

4,802 bytes added, 9 February
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
To use this service you will need an account with https://nukiFor Beds24 the normal channel manger fees apply.io/
Contact us if you want = Capabilities =*Beds24 can send booking data to participate Nuki locks.*Auto-Check-in : when a lock is first opened by the beta testguest the info code "CHECKIN" will be added to the booking.
<div style="displayLimitations =* As of 1 September 2023 you will need a [https:none"> //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 be 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.
For Beds24 the normal channel manger fees apply<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).
== Capabilities =What you need =*Beds24 can send booking data to Remotelock locks.To use this service you will need: *Multiple rooms can connect to At least one lockNuki Smart Lock.*Auto-Check-inA [https: when a lock is first opened by the guest the info code "CHECKIN" will be added to the booking//nuki.io nuki.io] account.*Support for ResortlocksA [https://nuki.io/en/smart-hosting/pricing/ Nuki Smart Hosting subscription].
Remotelock provides various regional servers, <span class="" style="color:#fe746c; font-size: 120%" >{{#fas:gift}} </span> '''Special offer for Beds24 cusotmers: Receive a 10% discount with the main one we connect to is the US service, if you need to connect to a regional one (for example Japanese) please let us know and we can configure your account accordingly.voucher code Beds24/10'''
== 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'''
 
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 serial number identifier and name for each lock. Click on the serial number of the lock that is using Select the correct lockand save.  
[[Image:agoda_room_mappingnuki_mapping1.png|500px|link=]][[Media:agoda_room_mappingnuki_mapping1.png|view large]]
If you have a common For each room/unit click on the name of the lock for multiple units you can enter that is associated with the same lock serial number for each unitroom.
Note[[Image: Lockstate uses several serversnuki_mapping. 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 panelpng|500px|link=]][[Media:nuki_mapping.png|view large]]
'''Step 4: Set up an Auto Action Email to send the PIN to guests'''
== How it works ==Bookings get sent *Go to {{#fas:cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS. A template is available which you can further customize. Use the context help (?Icons) in the locks at Auto Action and on the set time prior to check-help page (click on HELP inthe top right menu) for further instructions. A booking info code named LOCKSTATE_PIN is created *Create an Auto Action Email which will show includes the pin number valid template variable for the bookingpin which is [BOOKINGINFOCODETEXT:NUKI_PIN].
You can change '''Step 5: Activation''' *Tick "Code" if you grant access via keypad*Tick "App" if you grand access via the pin manually in the LOCKSTATE_PIN booking info code Nuki app*Tick "Code" and "App" if you grant access both via keypad and via the new pin will be sent to the lock at the next update.Nuki app
To force no pin = How it works === Syncing ==Bookings are automatically sent to be sent for a booking, change locks the value number of the LOCKSTATE_PIN booking info item "Days in Advance" prior to none, (icheck-in which you have selected.e. the word "none")
Updates are sent multiple times per day and send bookings for Entry codes/users can only be used during the selected days in advance. To instantly push updates through click "Send Data to Lockstate"booking period, they will not provide access before or after.
If *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 dates of lock. Click on the booking "View Bookings in Locks" button to check which bookings have already been changed 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 has been moved to .*If a different 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 bookings are cancelled we delete a Nuki lock is offline when an update is sent, the guest out of LOCKSTATE. This entry code will remove not be added until the accesslock comes online again.
The Email address of the guest is == App and code entry methods ==There are two ways bookings can be sent to Lockstatelocks: app and code. You can set up Remotelock to automatically send Emails to the guest. Alternatively you can create an Auto Action in SETTINGS > GUEST MANAGEMENT > AUTO ACTIONSselect one or both methods.
The template variable for === App entry ===If the pin "App' tickbox is [BOOKINGINFOCODETEXT:LOCKSTATE_PIN]selected, bookings will be sent to locks as users.
== Auto Check-in ==Auto check-in *Nuki will send guests an email containing an invitation, guests who accept this invitation will add a booking info item called CHECKIN be able to unlock the booking when Nuki lock using the guest first uses Nuki app.* Guests have 48 hours to accept the lockinvitation.To use auto check-* There is no way to resend a Nuki app invitation if a guest does not accept it in time. However, you must setup 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 webhook new invitation to send notifications the guest.*When the user is deleted from the lock , Nuki will send an email to Beds24the guest informing them that they no longer have access to the lock.
There are two steps to the webhook setup[[Image:nuki_delete_user.png|900px|link=]][[Media:nuki_delete_user.png|view large]]
1) Add a Webhook Notification Contact in Remotelock==== 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 URL of app to unlock a lock from anywhere.* If set to "Yes", all bookings in the webhook must contain your Beds24 ownerId number at room will be allowed to use remote app access.* If set to "Info code", bookings with the end like ?ownerid=12345info code "NUKI_REMOTE" will be allowed to use remote app access.
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)==Custom Start and End access times ==
The source should access start and end times can be "Account"customized per booking using booking info codes.
The Events must be "Access Granted" and "First Access Only"A booking info code '''ACCESS_STARTTIME''' with a time of day (23:59 format) as the text will override the default start time.
== Common Problems ==Lockstate have two types A booking info code '''ACCESS_ENDTIME''' with a time of accessday (23: users and guests. Bookings from Beds24 create guests59 format) as the text will override the default end time.
Start and end dates can be set relative to the check in and check out date by defining times greater than 24 or negative.  For example :- ACCESS_STARTTIME =-10:00 will create a start time 10 hours before midnight of the check in day, i.e. 14:00 on the day before check in. *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:00''' = Troubleshooting =  '''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 "Connect to Nuki" 3. Sign in to your Nuki account if prompted and allow Beds24 access. =Disconnect=
Click on "Disconnect" to terminate the connection.
 
</div ">

Navigation menu