Difference between revisions of "Remotelock.com"
m (1版 をインポートしました) |
Beds24>Markkinchin (→Capabilities) |
||
Line 1: | Line 1: | ||
[[Category:Apps]] | [[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] | To use this service you will need an account with [http://www.remotelock.com Remotelock] | ||
Line 6: | Line 9: | ||
For Beds24 the normal channel manger fees apply. | For Beds24 the normal channel manger fees apply. | ||
− | + | = Capabilities = | |
− | Beds24 can send booking data to Remotelock locks. | + | *Beds24 can send booking data to Remotelock locks. |
+ | *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. | ||
− | + | If you have a common door, e.g. front door or gate, you can set this up in Remotelock. If you do map the common door in Remotelock, do not map the common door in Beds24. | |
− | = | + | <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) please let us know and we can configure your account accordingly.</div> |
− | == Set Up | + | = Limitations = |
+ | = Set Up = | ||
*Click on "Connect to Lockstate". | *Click on "Connect to Lockstate". | ||
*Authorize Beds24 to access your account | *Authorize Beds24 to access your account | ||
Line 27: | Line 34: | ||
[[Image:agoda_room_mapping.png|500px|link=]] | [[Image:agoda_room_mapping.png|500px|link=]] | ||
[[Media:agoda_room_mapping.png|view large]] | [[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. | 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. | ||
− | + | = How it works = | |
− | Bookings get sent to the locks at the set time prior to check-in. | + | 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. | 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. | ||
Line 38: | Line 45: | ||
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") | 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 | + | 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. | ||
+ | |||
+ | ==Commuication with guests == | ||
+ | The Email address of the guest is sent to Lockstate. You can set up Remotelock to automatically send Emails to the guest. Alternatively you can create an Auto Action in {{#fas:cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS. | ||
+ | |||
+ | The template variable for the pin is [BOOKINGINFOCODETEXT:LOCKSTATE_PIN]. | ||
+ | |||
+ | == Auto Check-in == | ||
+ | Auto check-in will add a booking info item called CHECKIN to the booking when the guest first uses the lock. | ||
+ | To use auto check-in you must setup a webhook to send notifications from the lock to Beds24. | ||
+ | |||
+ | There are two steps to the webhook setup: | ||
+ | |||
+ | 1) Add a Webhook Notification Contact in Remotelock | ||
+ | |||
+ | the URL of the webhook must contain your Beds24 ownerId number at the end like ?ownerid=12345 | ||
+ | |||
+ | https://api.beds24.com/lockstate.com/notify.php?ownerid=<Your Beds24 owner ID> | ||
+ | |||
+ | The Content Type must be "JSON" | ||
+ | |||
+ | The secret can be left empty | ||
+ | |||
+ | 2) Add a Notification in Remotelock | ||
+ | |||
+ | The notification type is "Webhook" | ||
− | + | The Webhook Notification Contact is the contact you created in step 1) | |
− | The | + | The source should be "Account" |
− | The | + | 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. | Lockstate have two types of access: users and guests. Bookings from Beds24 create guests. | ||
− | + | = Disconnect= | |
Click on "Disconnect" to terminate the connection. | Click on "Disconnect" to terminate the connection. |
Revision as of 08:58, 4 August 2020
This page is about the menu {{#fas:cog}} (SETTINGS) APPS & INTEGRATIONS > REMOTELOCK
To use this service you will need an account with Remotelock
For Beds24 the normal channel manger fees apply.
Contents
Capabilities
- Beds24 can send booking data to Remotelock locks.
- 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.
If you have a common door, e.g. front door or gate, you can set this up in Remotelock. If you do map the common door in Remotelock, do not map the common door in Beds24.
Limitations
Set Up
- Click on "Connect to Lockstate".
- Authorize Beds24 to access your account
When successfully connected you will see the Remotelock account you are connected to.
- The "Pin Strategy" defines how the access code is constructed.
- 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.
- 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.
If you have a common lock for multiple units you can enter the same lock serial number for each unit. {{#fas:exclamation-triangle}} 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 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.
Commuication with guests
The Email address of the guest is sent to Lockstate. You can set up Remotelock to automatically send Emails to the guest. Alternatively you can create an Auto Action in {{#fas:cog}} (SETTINGS) GUEST MANAGEMENT > AUTO ACTIONS.
The template variable for the pin is [BOOKINGINFOCODETEXT:LOCKSTATE_PIN].
Auto Check-in
Auto check-in will add a booking info item called CHECKIN to the booking when the guest first uses the lock. To use auto check-in you must setup a webhook to send notifications from the lock to Beds24.
There are two steps to the webhook setup:
1) Add a Webhook Notification Contact in Remotelock
the URL of the webhook must contain your Beds24 ownerId number at the end like ?ownerid=12345
https://api.beds24.com/lockstate.com/notify.php?ownerid=<Your Beds24 owner ID>
The Content Type must be "JSON"
The secret can be left empty
2) Add a Notification in Remotelock
The notification type is "Webhook"
The Webhook Notification Contact is the contact you created in step 1)
The source should be "Account"
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.