Clock IoT device type A

The Clock IoT Device is needed for various interfaces to devices or systems in your local network. The role of the Clock IoT Device is to create a "bridge" between the systems in your local network and Clock PMS+ API servers.

The Clock IoT device is powered by a Raspberry Pi mini-computer that comes with preinstalled state-of-the-art system software developed by Clock. This special software enables the above-mentioned bridge to devices and software, installed in your local area network.

The Clock IoT device bundle includes:

• Raspberry Pi mini-computer;
• Clock's system software license
• SD card with an encryption key
• Preload of the specific services to be connected. Additional services can be installed remotely
• Association with the respective Clock PMS+ or Clock POS account;

Clock IoT Device is designed with strong security in mind.

Two types of devices are available:

Clock IoT type A (Raspberry Pi)

Network/Firewall

• The Clock IoT Device requires DHCP in the network to automatically obtain its IP address. Fixed IP addresses are not supported.
• Keep in mind that Clock IoT device need to be placed in the same network as the third party device/system subject to the interface (for TCP/IP protocols) or physically near to the device/system (for USB cabled interfaces). Check each interface for the specific protocol/port requirements.

Device/Installation

• The Clock IoT device requires an Ethernet cable (not included) and a power adapter (included). A Wi-Fi connection is not supported.
• The Clock IoT device should be constantly ON. The usage of an uninterruptible power supply (UPS) is recommended. Restarting the device is strongly NOT recommended, as this may lead to device bricking.
• Device LEDs. The green LED light (power) should be steady. The yellow LED light (SD card read/write) may blink or be steady.

Checking connections/ports

• Contact your system administrator and find the IP address of the Clock IoT Device. The device hostname of Clock IoT Device is "clockrpi-" followed by the serial number of the device.

  Example: "clockrpi-a02082-000000006ecb6e0b".

  

  Example host name and local IP in a router

  

  Example host name and local IP in a router

  Successful connection test:

  

• Open a browser and enter the device's IP address.
• The Diagnostics page will be opened
• Please contact the system administrator if any of the checks is marked as Failed and ask them to re-check the above "Network / Firewall" section.

Communication with Third-party software

The purpose of the IoT device is to act as a communication bridge between the Clock PMS+ cloud servers and local servers of third-party systems. Please note that a single IoT device can handle communication with several systems - for example, if you have a Door Lock system and an Elavon card payment terminal, you need only 1 IoT device to handle the communication with both (as long as the requirements outlined below are met). 

Door lock systems

The majority of Door Lock systems require a Clock IoT device for communication. The list includes Salto, VisiOnline, Assa Abloy, Onity, Messerschmitt, Saflok, Hotek, and others. For proper communication between the systems:

• The Clock IoT device and the door lock server (system) must be connected to the same local (internet) network.

Payment Service Provider

If you are using Elavon as a payment service provider and their payment terminal you will need a Clock IoT device for the communication between Clock PMS+ and the terminal. For proper communication:

• The Clock IoT device and the card terminal must be connected to the same local (internet) network. 1 IoT device is needed regardless of how many terminals you use.

Receipt (thermal) printers in Clock POS

For the communication between Clock POS and the printers (kitchen receipts, bills) in your F&B outlet you need a Clock IoT device. For proper communication:

• The Clock IoT device and the printers must be connected to the same local (internet) network. 1 IoT device can process communication with many printers.

Fiscal devices

Communication with fiscal devices for certain counties requires a Clock IoT device. Currently, the integrations with fiscal devices in Greece, Italy, and Romania require a Clock IoT device.

• Romania - the Clock IoT device and the Datecs fiscal printer with DxPrint driver must be connected to the same local network.
• Italy - the Clock IoT device and the Epson RT fiscal printer must be connected to the same local network.
• Greece - the Clock IoT device and the fiscal printer must be connected to the same local network.