Custom mobile app control

Unlike conventional room control and building automation systems where possible IP-based control endpoints reside inside the building's internal network, all Mount Kelvin sites are always connected to the Mount Kelvin cloud.

Mount Kelvin offers partners and customers the use of a cloud-based Application Programming Interface (API) which allows external systems to control, configure and monitor the Mount Kelvin system and connected peripherals.

Any Internet-connected device can access this API and with the right authorization, make use of the functionality available in the API.

API documentation for 401-D

icon

API

For controlling a single room

icon

Site group API

For controlling multiple rooms or monitoring the whole hotel

Mount Kelvin does not perform any type of verification of customer-specific custom integrations. If you wish to productize a Mount Kelvin based solution for multiple customers, please let us know and we'll help you find the right solution.

Making a phone or web app

icon

Examples of use cases for phone or web app

  • Control interfaces displayed on a hotel TV are fundamentally often web applications which the hotel TV displays, allowing the guest to control room lighting with the TV remote
  • Guest loyalty applications in bleeding-edge hospitality concepts often include a guest loyalty app with room service and add-on service options. Many Mount Kelvin customers have opted to also include a room control interface
  • An occupancy dashboard displaying room occupancy state can help housekeeping optimize their routes and prioritize empty rooms

Workflow for building a guest application

  1. Create an API key for the integration
    1. When requesting a key, tell us which API you intend to use
  2. Build an interface for sharing credentials with the users
    1. Depending on your hotel concept you will somehow need to get credentials to the end-user. This may take the form of adding a privilege to the guest in your own backend or providing a user with a magic sign-in link via SMS or email.
    2. Note that the primary API key should not be stored in end-user mobile applications or worse yet a Javascript frontend in the web. Either use limited scope keys with a pre-set expiry date to the guest's departure date and store that on the end user's device or route control requests through your own backend.
  3. Select scenes to be used by the integration and store their IDs for each room
    1. You may also use scene names for selecting the scenes, but a backup strategy for scene selection should be chosen in case someone changes the scene names
    2. We recommend replicating the control layout used in room buttons in the app to ensure consistent user experience and learnability. Mount Kelvin also provides the switch symbols used in switches for use in end-user apps.
  4. Select devices to be used by the integration
    1. Store the device IDs for each room or use consistent naming across rooms. Ensure that the app fails gracefully if a device is renamed or removed.
    2. We recommend avoiding direct device control for most devices, guests rarely look for a high degree of control over room lighting: the simplest possible control interface is the best.
  5. Build your application.

Integrating web-based systems

icon

Web-based systems are typically integrated less for direct control of room features and more in search of operational efficiencies, for example:

  • Arming welcome lights when a guest checks in
  • Showing room occupancy state in a Property Management System (eg. Opera or MEWS)

Workflow for building an integration to an external web service

  1. Create an API key for the external system by requesting it via email
    1. In your request, tell us that you are integrating a web-based system, we will give you a Site Group Key, which allows access to all rooms
    2. Store the API key in a secure place
  2. Store a mapping between the needed object IDs in the external system and Mount Kelvin
  3. Build your application