Difference between revisions of "Lockstate.com"

From Booking Automation Wiki
Jump to: navigation, search
(How it works)
(Auto Check-in)
Line 58: Line 58:
 
the URL of the webhook must contain your BookingAutomation ownerId number at the end like ?ownerid=12345
 
the URL of the webhook must contain your BookingAutomation ownerId number at the end like ?ownerid=12345
  
https://api.bookingautomation.com/lockstate.com/notify.php?ownerid=<Your BookingAutomation owner ID>
+
http://manage.bookingautomation.com/api/lockstate.com/notify.php?ownerid=<Your BookingAutomation owner ID>
  
 
The Content Type must be "JSON"
 
The Content Type must be "JSON"

Revision as of 21:06, 8 January 2020

This page is about the menu SETTINGS->APPS & INTEGRATIONS->LOCKSTATE

To use this service you will need an account with Lockstate

For BookingAutomation the normal channel manger fees apply.

Capabilities

BookingAutomation can send booking data to Lockstate locks.

Limitations

Set Up

  • Click on "Connect to Lockstate".
  • Authorize BookingAutomation to access your account

When successfully connected you will see the Lockstate 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.

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.

Note: Lockstate uses several servers. If you are not redirected back to BookingAutomation send us a support ticket via the SUPPORT button in the top left of your BookingAutomation control panel.

How it works

Bookings get sent to the locks one week prior to check-in. A booking info item LOCKSTATE_PIN which will show the pin number is 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 of the LOCKSTATE_PIN booking info item to none, (i.e. the word "none")

Updates are sent once per day seven 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 of LOCKSTATE this will remove the access.

The Email address of the guest is sent to Lockstate. You can set Lockstate up to automatically send Emails to the guest. Alternatively you can set up an Auto Action in 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 BookingAutomation.

There are two steps to the webhook setup:

1) Add a Webhook Notification Contact in Remotelock

the URL of the webhook must contain your BookingAutomation ownerId number at the end like ?ownerid=12345

http://manage.bookingautomation.com/api/lockstate.com/notify.php?ownerid=<Your BookingAutomation 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 BookingAutomation create guests.

Disconnect

Click on "Disconnect" to terminate the connection.