3,040
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.
<div style="display:none">
== Capabilities ==*Beds24 can send booking data to Remotelock Nuki locks.*Multiple rooms can connect to one lock.
*Support for Resortlocks.
Remotelock provides various regional servers, the main one we connect = Limitations =* 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 is the US serviceguests, if you need only users with access to connect Nuki web will be able to a regional one (for example Japanese) please let us know and we can configure your account accordinglyview booking names.
== Set Up ==*Click on "Connect Using keypad codes requires a Nuki keypad to Lockstate"be setup. *Authorize Beds24 to access your account
When successfully connected you will see the Remotelock = Set Up ='''Step 1: Connect your Nuki Account''' *Click on "Connect to Nuki". *Sign in with your Nuki account you are connected if prompted.*Click "Allow" tolet Beds24 view and manage your Nuki account and locks.
*The "Pin Strategy" defines how the access code is constructed[[Image:nuki_auth. png|500px|link=]][[Media:nuki_auth.png|view large]] '''Step 2: Set when bookings should send to locks'''
*Click on "Get Codes"
You will see one serial number for each lock. Click on the serial number of the lock that is using the lock.
[[Image'''Step 3:agoda_room_mapping.png|500px|link=]][[Media:agoda_room_mapping.png|view large]]Map your locks to your rooms'''
If you have a common *Click on "Get Codes" You will see one identifier and name for each lock for multiple units you can enter . Select the same correct lock serial number for each unitand save.
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.
== 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.
You can change For each room/unit click on the pin manually in the LOCKSTATE_PIN booking info code and the new pin will be sent to name of the lock at that is associated with the next updateroom.
To force no pin to be sent for a booking, change the value of the LOCKSTATE_PIN booking info item to none, (i[[Image:nuki_mapping.epng|500px|link=]][[Media:nuki_mapping. the word "none")png|view large]]
Updates are sent multiple times per day and '''Step 4: Set up an Auto Action Email to send bookings for the selected days in advance. To instantly push updates through click "Send Data PIN to Lockstate". guests'''
If *Go to {{#fas:cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS.*Create an Auto Action Email which includes the dates of the booking have been changed or the booking has been moved to a different room those details will be sent to template variable for the lockspin which is [BOOKINGINFOCODETEXT:NUKI_PIN].
If bookings are cancelled we delete '''Step 5: Activation''' *Tick "Code" if you grant access via keypad*Tick "App" if you grand access via the guest out of LOCKSTATE. This will remove Nuki app*Tick "Code" and "App" if you grant access both via keypad and via the access. Nuki app
The Email address of the guest is = How it works === Syncing ==Bookings are automatically sent to Lockstate. You can set up Remotelock locks the number of "Days in Advance" prior to automatically send Emails to the guest. Alternatively check-in which you can create an Auto Action in SETTINGS > GUEST MANAGEMENT > AUTO ACTIONShave selected.
The template variable for Entry codes/users can only be used during the pin is [BOOKINGINFOCODETEXT:LOCKSTATE_PIN]booking period, they will not provide access before or after.
== Auto Check-*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 ==Auto 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 will add a the Nuki app.*A booking info item called CHECKIN to code named NUKI_PIN is created on the "Info" tab of the booking when , this will show the guest first uses access code for the lockbooking.To use auto check-in you must setup *If a webhook keypad code, booking date, or room changes, those details will be sent to send notifications 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 the lock to Beds24will be removed one day after check-out.
There are two steps to <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 webhook setup:lock comes online again.
1) Add a Webhook Notification Contact in Remotelock== 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.
The Content Type must be "JSON"[[Image:nuki_delete_user.png|900px|link=]][[Media:nuki_delete_user.png|view large]]
The secret can === Code entry ===If the "Code" tickbox is selected, bookings will be left emptysent to locks as entry codes.
2) Add Guests will need to enter these codes on a Notification in RemotelockNuki keypad to unlock the associated Nuki lock.
The notification type is === Manually changing codes ===# Navigate to {{#fas:cog}} (SETTINGS) ACCOUNT > PREFERENCES "WebhookBookings"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]]
The Webhook Notification Contact is Nuki keypad codes must:# Be exactly six digits long.# Not contain the contact you created in step 1)number zero.# Not start with "12".# Be unique to the lock.
The source should <span style="color:#fe746c;“ >{{#fas:exclamation-triangle}} </span> If you manually set an invalid NUKI_PIN, it will be "Account"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 Events must be "Access Granted" and "First Access Only"= Troubleshooting =
== Common Problems == '''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.Lockstate have two types of access: users 1. Click "Disconnect" 2. Click "Connect to Nuki" 3. Sign in to your Nuki account if prompted and guests. Bookings from allow Beds24 create guestsaccess.
== Disconnect==
</div ">
[[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.
*Auto-Check-in: when a lock is first opened by the guest the info code "CHECKIN" will be added to the booking.
=What you need = Limitations ==To use this service you will need: *At least one Nuki Smart Lock.*A [https://nuki.io nuki.io] account.
*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.
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.
[[Image:nuki_mapping1.png|500px|link=]]
[[Media:nuki_mapping1.png|view large]]
=== App entry ===If the URL of the webhook must contain your Beds24 ownerId number at the end like ?ownerid=12345"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://apiweb.beds24nuki.comio/#/lockstatepages/smartlocks web.com/notifynuki.io], select Devices, click the desired smartlock, go to the Users tab, then find the booking and click delete.php?ownerid=<Your You can then visit the Beds24 owner IDNuki 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.
Click on "Disconnect" to terminate the connection.
