Changes

Jump to navigation Jump to search

Remotelock.com

457 bytes added, 10:58, 4 August 2020
[[Category:Apps]]
''[[Category:Self-Check-in]][[Category:Lock Systems]]<div class="heading">Remotelock</div> This page is about the menu {{#fas:cog}} (SETTINGS->) APPS & INTEGRATIONS->REMOTELOCK
To use this service you will need an account with [http://www.remotelock.com Remotelock]
For Beds24 the normal channel manger fees apply.
== Capabilities ==
*Beds24 can send booking data to Remotelock locks.
*Multiple rooms can connect to one lock.
*Support for Resortlocks.
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.
<div class== Limitations =="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) please let us know and we can configure your account accordingly.</div>
=Limitations == Set Up ==
*Click on "Connect to Lockstate".
*Authorize Beds24 to access your account
[[Image:agoda_room_mapping.png|500px|link=]]
[[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> 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.
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 Remotelock_PIN named LOCKSTATE_PIN is created which will show the pin number created 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 sends send bookings for the selected days in advance. 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 dates of LOCKSTATE this the booking have been changed or the booking has been moved to a different room those details will remove be sent to the accesslocks.
The Email address of If bookings are cancelled we delete the guest is sent to Lockstateout of LOCKSTATE. You can set Remotelock up to automatically send Emails to This will remove the guest. Alternatively you can set up an Auto Action in SETTINGS->GUEST MANAGEMENT->AUTO ACTIONSaccess.
==Commuication with guests ==The template variable for Email address of the Pin guest is [BOOKINGINFOCODETEXTsent to Lockstate. You can set up Remotelock to automatically send Emails to the guest. Alternatively you can create an Auto Action in {{#fas:LOCKSTATE_PIN]cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS.
The template variable for the pin is [BOOKINGINFOCODETEXT:LOCKSTATE_PIN].
== Auto Check-in ==
1) Add a Webhook Notification Contact in Remotelock
the URL of the webhook must contain your Beds24 ownerId number at the end after like ?ownerid=12345
https://api.beds24.com/lockstate.com/notify.php?ownerid=<Your Beds24 owner ID>
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.

Navigation menu