Ctrlk
Create AccountLogin
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Sciener

Sciener is the company behind the TTLock platform, one of the most widely used smart lock systems for short stay rentals and small hotels. Its locks are sold under many brand names but all share the same TTLock app and the same cloud, which is what HolidayHero connects to. Sciener locks are popular because they work on batteries, need no wiring, and open with a code typed on the keypad, so a property can go keyless without an installer.

Category: Smart Device

Sciener smart lock integration

With the Sciener integration, every reservation on a listing with a connected lock gets its own door code. The code is created in the Sciener cloud, valid from a moment you choose before check in until a moment after check out, and shown to the guest in the HolidayHero guest app. Your team never has to hand over a key or read a code out over the phone.

This first release covers passcode locks without a gateway. There is no remote unlock button, and no card, fingerprint or face credentials.

Connecting your locks

You sign in with your own TTLock account, the one you use in the TTLock mobile app. Only locks where that account is the administrator can be used. On the Locks tab you press Connect on each lock you want to use, which creates a smart device in HolidayHero. You then attach that smart device to a listing in the HolidayHero backoffice, exactly as you would with any other smart device. From that point on every booking on that listing gets a code.

Door code timing

You set two offsets that apply to all your locks: how many minutes before check in the code starts working, and how many minutes after check out it stops. Bear in mind that the lock itself rounds these. For a stay of more than one day it works in whole hours, and for a same day stay in half hours. HolidayHero rounds the window the same way before creating the code, so the time you see and the time the guest sees is the time the keypad really accepts.

When codes are created

Codes are not created the moment a booking arrives. You choose how many days before check in they should be prepared, seven by default. This is deliberate and it matters, for the reason in the next section.

Cancellations and what can be withdrawn

A Sciener lock without a gateway stores its codes offline. That means the cloud, and therefore HolidayHero, cannot delete or change a code on that lock once it has been created. This is a limitation of the lock, not of the integration.

Creating codes only shortly before arrival is what protects you here. A booking cancelled earlier than your chosen window never produces a code at all, which covers the large majority of cancellations.

When a cancellation does arrive after the code exists, HolidayHero does everything it can. It attempts the deletion in the Sciener cloud anyway, which succeeds if you do run a gateway. It removes the code from the guest app, clears it from the reservation, and stops serving it. If the deletion did not reach the lock, you get a warning in the Logs tab naming the lock, the code and the date it expires, so you can decide whether to change it on the keypad yourself. HolidayHero will not tell you a code was revoked when it was not.

Keypad history

Every six hours HolidayHero reads the recent opening history from the locks that have a stay in progress, and records keypad openings on the matching reservation. That gives your team a record of when a guest actually arrived, without anyone checking the lock.

Reservation metafield

The door code is written onto the reservation as the sciener_doorcode metafield. You can use it in your own guest messaging templates, and your team can read it straight from the booking. It is cleared when the code is withdrawn. Guides

How do I integrate with Sciener?

In the TTLock app

  1. Install the TTLock app and sign in with an ordinary account. Do not use a Sciener open platform developer account, those cannot own locks.

  2. Add and initialise each lock in the app, so your account is its administrator.

In HolidayHero

  1. Go to your desired HolidayHero Workspace.

  2. Go to Integrations.

  3. Select Sciener.

  4. Walk through the authentication process. You are installing an application on top of your HolidayHero workspace.

  5. Inside the Sciener integration, go to Settings.

  6. Enter the username and password of your TTLock app account, and pick your region.

  7. Set the door code timing and how many days before check in codes should be created.

  8. Hit Save.

  9. Go to the Locks tab and press Connect on each lock you want to use.

  10. In the HolidayHero backoffice, attach each new smart device to the right listing.

  11. Activate the integration on the Home tab.

Why does my guest not see a door code yet?

Codes are only created shortly before arrival, by default seven days. If the stay is further away than that, there is no code yet and the guest app says so. Check the Settings tab to see or change the number of days.

If arrival is inside that window and there is still no code, check that the lock is connected on the Locks tab, that it is attached to the right listing in the backoffice, and that the integration is active on the Home tab. The Logs tab will show why a code was skipped.

A booking was cancelled. Does the code still work?

It depends on whether the lock has a gateway.

Without a gateway, the lock keeps the code until it expires and HolidayHero cannot remove it. The guest loses it in the app and it is cleared from the reservation, but the keypad still accepts it. You get a warning in the Logs tab naming the lock, the code and its expiry date so you can change it on the lock yourself if you need the guest locked out immediately.

With a gateway, the code is deleted from the lock and the log confirms it.

The safest setting is to create codes as late as your operation allows, so most cancellations happen before a code exists.

Do I need a gateway or WiFi bridge?

No. The integration is built for gateway free locks and creates codes in the cloud that the guest types on the keypad. A gateway is only needed if you want cancelled codes to actually disappear from the lock.

The times I set do not match what the lock does. Why?

The lock rounds the validity window itself, to whole hours for a stay longer than a day and to half hours for a same day stay. HolidayHero applies the same rounding before creating the code, so what you see in HolidayHero is what the lock enforces. If you set 45 minutes before check in on a multi night stay, the code will start on the hour.

What is the API limit I keep reading about?

Sciener limits how many calls can be made each month, and that limit is shared across all HolidayHero customers using the integration, not per property. HolidayHero is careful with it: the lock list is cached, and keypad history is only read every six hours and only for locks with a stay in progress. If the limit is ever reached you will see an error in the Logs tab rather than silence.

HolidayHero Permissions

Each integration has its own set of permissions. Please find below what this integration will be able to do.

Permission
Description

reservation.read

The integration will be able to read your reservations to know when a door code is needed and for how long.

listing.read

The integration will be able to read your listings to know which lock belongs to which property.

user.read

The integration will be able to read the guests on a reservation so the right person sees the door code.

smart_device.create

The integration will be able to create a smart device in HolidayHero for each lock you connect.

smart_device.update

The integration will be able to update a smart device when the lock changes in Sciener.

smart_device.delete

The integration will be able to remove a smart device when you disconnect a lock.

smart_device_log.create

The integration will be able to record door code views and keypad openings on the reservation.

metafield.read

The integration will be able to read your metafields to find the door code field.

metafield.write

The integration will be able to write the door code onto the reservation.

HolidayHero Webhooks

Webhook
Description

installation.uninstalled

The integration cleans up its data when you remove the app from your workspace.

listing.deleted

The integration detects when a listing has been removed and will remove the corresponding matched listings.

smart_device.created

Picks up the listing you attached a lock to, so bookings on that listing start getting door codes.

smart_device.updated

Picks up a change to which listing a lock is attached to.

smart_device.deleted

Removes the matched lock when you delete the smart device in HolidayHero.

reservation.created

Checks a new booking and prepares a door code if arrival is close enough.

reservation.updated

Reissues the door code when the dates of a booking change.

reservation.cancelled

Withdraws the door code when a booking is cancelled.

reservation.deleted

Withdraws the door code when a booking is removed.

Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the ask query parameter:

The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.

PreviousGoki
NextSalto

Last updated