17,117
edits
Changes
Jump to navigation
Jump to search
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.
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).
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'''
[[Image:agoda_room_mappingEntry codes/users can only be used during the booking period, they will not provide access before or after.png|500px|link=]][[Media:agoda_room_mapping.png|view large]]
Note== App and code entry methods ==There are two ways bookings can be sent to locks: Lockstate uses several serversapp and code. 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 panelYou can select one or both methods.
== How it works ==*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.Bookings get sent * Guests have 48 hours to accept the locks at the set invitation.* There is no way to resend a Nuki app invitation if a guest does not accept it in time prior . However, you may go to check-in[https://web.nuki.io/#/pages/smartlocks web.nuki. A io], select Devices, click the desired smartlock, go to the Users tab, then find the booking info code named LOCKSTATE_PIN 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 created which deleted from the lock, Nuki will show send an email to the pin number valid for guest informing them that they no longer have access to the bookinglock.
You can change the pin manually in the LOCKSTATE_PIN booking info code and the new pin will be sent to the lock at the next update[[Image:nuki_delete_user.png|900px|link=]][[Media:nuki_delete_user.png|view large]]
To force no pin ==== Allow remote app access ====By default guests must be physically close to be sent for a booking, change the value of lock to unlock it with the LOCKSTATE_PIN booking info item to none, (iapp.e. the word "none")
Updates are sent multiple times per day and send The "Allow remote app access" will allow guests to use the app to unlock a lock from anywhere.* If set to "Yes", all bookings for in the selected days in advanceroom will be allowed to use remote app access. To instantly push updates through click * If set to "Send Data Info code", bookings with the info code "NUKI_REMOTE" will be allowed to Lockstate"use remote app access.
If bookings are cancelled we delete the guest out of LOCKSTATE. This Guests will remove need to enter these codes on a Nuki keypad to unlock the accessassociated Nuki lock.
The Email address of the guest is sent === Manually changing codes ===# Navigate to Lockstate {{#fas:cog}} (SETTINGS) ACCOUNT > PREFERENCES "Bookings" and add "NUKI_PIN" to your Booking Info Code Values. # You can set up Remotelock now manually add a NUKI_PIN info code to automatically send Emails to the guestyour bookings.[[Image:nuki_set_pin. Alternatively you can create an Auto Action in SETTINGS > GUEST MANAGEMENT > AUTO ACTIONSpng|x300px|link=]][[Media:nuki_set_pin.png|view large]]
The template variable for Nuki keypad codes must:# Be exactly six digits long.# Not contain the pin is [BOOKINGINFOCODETEXT:LOCKSTATE_PIN]number zero.# Not start with "12".# Be unique to the lock.
There are two steps to the webhook setup:==Custom Start and End access times ==
1) Add a Webhook Notification Contact in RemotelockThe access start and end times can be customized per booking using booking info codes.
the URL A booking info code '''ACCESS_STARTTIME''' with a time of day (23:59 format) as the webhook must contain your Beds24 ownerId number at text will override the end like ?ownerid=12345default start time.
httpsA booking info code '''ACCESS_ENDTIME''' with a time of day (23://api59 format) as the text will override the default end time.beds24.com/lockstate.com/notify.php?ownerid=<Your Beds24 owner ID>
The Content Type must Start and end dates can be "JSON"set relative to the check in and check out date by defining times greater than 24 or negative.
The secret can be left empty
2) Add For example :- ACCESS_STARTTIME = -10:00 will create a Notification start time 10 hours before midnight of the check in Remotelockday, i.e. 14:00 on the day before check in.
The notification type is "Webhook"*Booking Info code = '''ACCESS_STARTTIME'''*Booking Info Text = '''-10:00'''
The Webhook Notification Contact is the contact you created in step 1For example :- ACCESS_ENDTIME = 34:00 will create an end time of 10:00 one day after checkout (34 = 24 + 10 hours)
The source should be "Account"*Booking Info code = '''ACCESS_STARTTIME'''*Booking Info Text = '''34:00'''
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==
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
= Limitations =
* 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 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.
== 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].
*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 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 serial number name of the lock that is using associated with the room. [[Image:nuki_mapping.png|500px|link=]][[Media:nuki_mapping.png|view large]] '''Step 4: Set up an Auto Action Email to send the PIN to guests''' *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 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 locknumber of "Days in Advance" prior to check-in which you have selected.
*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 you have a common Nuki lock for multiple units you can enter is offline when an update is sent, the entry code will not be added until the same lock serial number for each unitcomes online again.
=== App entry ===
If the "App' tickbox is selected, bookings will be sent to locks as users.
=== Code entry ===If the dates of the booking have been changed or the booking has been moved to a different room those details "Code" tickbox is selected, bookings will be sent to the locksas entry codes.
<span style== Auto Check"color:#fe746c;“ >{{#fas:exclamation-in ==Auto check-in triangle}} </span> If you manually set an invalid NUKI_PIN, it will add be overwritten with a booking info item called CHECKIN randomly generated pin the next time bookings are sent to the booking when the guest first uses the locks. Each code can only be used once per lock.To use auto check-in Before you must setup can reuse a webhook code it has to send notifications be removed from the lock to Beds24.
Click on "Disconnect" to terminate the connection.
