Setting up the Evoko Home integration: steps on the Evoko and i-Reserve side
The Evoko Home integration needs configuration on two sides: first a few details from Evoko Home (server URL and API token), then the integration in i-Reserve — authentication, behaviour (statuses, poll, paid rooms) and the room mapping.
1. On the Evoko Home side
- Note the WebSocket URL of the Evoko Home server, e.g.
wss://rooms.example.com:3002/websocket. - Under Global Settings get the “Default API Token” — this is the group token that acts as the password.
- Make sure the rooms (Liso displays) to be linked are configured and online in Evoko Home.
- Check whether the rooms have PIN authentication enabled; if so, note the PIN.
2. On the i-Reserve side — Authentication tab
In Administration > Integrations add a new integration of type Evoko Home and fill in the authentication.
| Field | What to enter |
|---|---|
| WebSocket URL | Full DDP endpoint of the server (e.g. wss://rooms.example.com:3002/websocket). Required. |
| Integration user | Leave empty for the default defaultDevIntegrationUser. |
| Group token | The “Default API Token” from Evoko Home (Global Settings). Required. |
| Verify TLS certificate | Port 3002 ships a self-signed certificate by default; keep off unless a valid public certificate is installed there. |
Click Test connection: i-Reserve connects, logs in and reports whether it succeeds.
3. Configuration tab
| Field | What it does |
|---|---|
| Create Evoko event on status | The booking status(es) at which the booking is pushed to its mapped Evoko room. Multiple selection. |
| Remove Evoko event on status | The status(es) at which the booking is removed from the display again. Multiple selection. |
| Display subject template | The single line shown on the display (Evoko bookings have only a subject, no body). Uses the standard booking variables such as {PROD_DESC}, {BOOKING_NUMBER}, {FROMDATE}. Default: {PROD_DESC} - {BOOKING_NUMBER}. |
| PIN | PIN sent with booking changes. Only needed if the rooms have PIN authentication enabled (otherwise PinIsRequired). Leave empty if no PIN is required. |
| Poll interval (minutes) | How often the inbound poll takes a snapshot to detect display bookings (1–60). |
| Paid-room policy | How display bookings on paid rooms are handled (booking on the display bypasses the payment flow). |
| Inbound sync (display bookings) | When on, a poll picks up bookings made on the displays and creates them in i-Reserve. When off, the integration is outbound only. |
| Inbound booking status | The status given to bookings created from a display booking. Use a non-charging status so display bookings do not bypass payment. |
3.1 Mapping: object → Evoko room
On the Mapping tab you link each i-Reserve object (product) to an Evoko room. First click Refresh room list to fetch the rooms live from Evoko (allRooms); then choose the product on the left and the matching room on the right. Only mapped rooms are synchronised.
4. Activate
Save and set the integration to active. Test outbound by moving a booking to the “create” status and verifying it appears on the display; test inbound (if enabled) by booking on a display and waiting for the poll to create the booking in i-Reserve.
