17,110
edits
Changes
Jump to navigation
Jump to search
''[[Category:Automation]][[Category:Self-Check-in]][[Category:Lock Systems]]<div class="heading">Remotelock, Resortlock, Igloohome, Yale Access, August, Schlage </div> This page is about the menu {{#fas:cog}} (SETTINGS->) APPS & INTEGRATIONS->REMOTELOCKand explains how to set up a connection with locks from Remotelock, Resortlock and Igloohome.
== Capabilities ==*Beds24 can send booking data to Remotelock locks.
Remotelock provides various regional serversIf you have a common door, the main one we connect to is the US servicee.g. front door or gate, if you need to connect to a regional one (for example Japanese) please let us know and we can configure your account accordinglyset this up in Remotelock. If you do map the common door in Remotelock, do not map the common door in Beds24.
== Set Up ==
If ==Communication with guests ==The Email address of the guest is sent to Remotelock. You can set up Remotelock to automatically send Emails to the guest. Alternatively you have a common lock for multiple units can create an Auto Action in {{#fas:cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS. A template is available which you can enter further customize. Use the context help (?Icons) in the Auto Action and on the help page (click on HELP in the same lock serial number top right menu) for each unitfurther instructions.
NoteThe template variable for the pin is [BOOKINGINFOCODETEXT: 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 panelLOCKSTATE_PIN].
== Common Problems == '''Pin codes are not being generated'''Lockstate have two types of "Cannot create resource, 90 days per accessguest is the limit for your billing plan","type": users and guests. Bookings from Beds24 create guests"billing_plan_resource_limit_reached Check your contract type in Remotelocks to ensure your bookings meet the contract details.
== Disconnect==
no edit summary
[[Category:Apps]]
To use this service you will need an account with [http://www.remotelock.com Remotelock]
For Beds24 the normal channel manger fees apply.
*Multiple rooms can connect to one lock.
*Auto-Check-in: when a lock is first opened by the guest the info code "CHECKIN" will be added to the booking.
*Support for Resortlocks., Schlage, Yale Access, August and Igloohome
<div class="warning">{{#fas:exclamation-triangle}} Remotelock provides various regional servers, the main one we connect to is the US service, if you need to connect to a regional one (for example Japanese, UK or EU) please let us know and we can configure your account accordingly.</div> <span style="color:#019cde; font-size: 150%;“ >{{#fas:info-circle}} </span> You can also connect Igloohome via Make (formerly Integromat). Watch this [https://www.youtube.com/watch?v=6iTGZcTGEZI] video or and contact Igloohome support if you have any problems. = Limitations =For Resortlock an Igloohome the PIN is created by the lock so you can not use a custom PIN.= Set Up =
*Click on "Connect to Lockstate".
*Authorize Beds24 to access your account
One Beds24 account can connect to one Remotelock account, if you have multiple Remotelock accounts use a Beds24 sub account for each.
When successfully connected you will see the Remotelock account you are connected to.
[[Media:agoda_room_mapping.png|view large]]
If you have a common lock for multiple units you can enter the same lock serial number for each unit.
<span style="color:#fe746c;“ >{{#fas:exclamation-triangle}} </span> Remotelock 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.
<span style="color: #f3e504; font-size: 150%;" >{{#fas:lightbulb}} </span> One Beds24 account connects with one Remotelock account. If you have multiple Remotelock accounts, create sub accounts for each ensure the sub account 'owns' the property, not just has access to the respective properties in Beds24.
= 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 the pin manually in the LOCKSTATE_PIN booking info code and the new pin will be sent to the lock at the next update.
To force no pin to be sent for a booking, change the value of the LOCKSTATE_PIN booking info item to none, (i.e. the word "none")
Updates are sent multiple times per day and send bookings for the selected days in advance. To instantly push updates through click "Send Data to Lockstate".
If the dates of the booking have been changed or the booking has been moved to a different room those details will be sent to the locks.
If bookings are cancelled we delete the guest out of LOCKSTATE. This will remove the access.
==Custom Start and End access times ==
The access start and end times can be customized per booking using booking info codes.
A booking info code '''ACCESS_STARTTIME''' with a time of day (23:59 format) as the text will override the default start time.
A booking info code '''ACCESS_ENDTIME''' with a time of day (23:59 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_ENDTIME = 34:00 would create an end time of 10:00 one day after checkout (34 = 24 + 10 hours)
ACCESS_STARTTIME = -10:00 would create a start time 10 hours before midnight of the check in day, i.e. 14:00 on the day before check in.
If booking info codes are not used to set the time, the property default is used when creating the access, in this case if the time of day is changed in remotelock, it will not be overridden unless a date change is required.
== Auto Check-in ==
1) Add a Webhook Notification Contact in Remotelock
the URL of the webhook must contain your the Beds24 ownerId account Id number that owns the property at the end after like ?ownerid=:12345
https://api.beds24.com/locktatelockstate.com/notify.php?ownerid=<Your Beds24 owner ID>
The Content Type must be "JSON"
The Events must be "Access Granted" and "First Access Only"
== How it works =Common Problems =Bookings get sent to the locks at the set time prior to check-in. A booking info code Remotelock_PIN which will show the pin number created for the booking. 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. To force no pin to be sent for a booking, change the value Remotelock have two types of the LOCKSTATE_PIN booking info item to none, (i.e. the word "none") Updates are sent multiple times per day access: users and sends bookings for the selected days in advanceguests. To instantly push updates through click "Send Data to Lockstate". If the dates of the booking is changed or the booking is moved to a different room those details will be sent to the locks. If bookings are cancelled we delete the guest out of LOCKSTATE this will remove the access. The Email address of the guest is sent to Lockstate. You can set Remotelock up to automatically send Emails to the guest. Alternatively you can set up an Auto Action in SETTINGS->GUEST MANAGEMENT->AUTO ACTIONSBookings from Beds24 create guests.
'''Pin-Code does not match the 'PIN Strategy' ''' The template variable pin code has been previously used in another booking for the Pin is [BOOKINGINFOCODETEXT:LOCKSTATE_PIN]this room. The pin-code needs to be unique.
Click on "Disconnect" to terminate the connection.
