Instruction
Difficulty level:
Implementing the Evoko Home integration: test and production checklist
Practical implementation guide for the Evoko Home integration (bidirectional booking sync with Liso room displays), with a checklist for test and production. The steps describe the order; then use the per-environment checklists.
Things to watch
- The rooms (Liso displays) must be configured and online in Evoko Home.
- The group token (Default API Token) is the password; TLS verification is usually off on port 3002 (self-signed).
- Inbound is a poll (not real-time); set a realistic poll interval and a non-charging inbound status.
- Set the paid-room policy deliberately; fill in a PIN if the rooms require it.
Checklist — test environment
- ☐ WebSocket URL of the Evoko Home server noted.
- ☐ Group token (Default API Token, Global Settings) obtained.
- ☐ Rooms (Liso displays) configured and online; PIN noted if required.
- ☐ i-Reserve: integration of type "Evoko Home" created; Auth tab filled (URL, group token, TLS verification off); "Test connection" succeeded.
- ☐ Configuration tab: create and remove status, display subject template, PIN (if needed), poll interval, paid-room policy, inbound sync and inbound status set.
- ☐ Mapping: "Refresh room list" run; products linked to the right Evoko rooms.
- ☐ Integration set to active.
- ☐ Outbound tested: booking → create status → appears on the display; update/delete verified.
- ☐ Inbound tested (if enabled): booking on display → created in i-Reserve after the poll with the inbound status.
Checklist — production environment
- ☐ Production server URL and production group token used.
- ☐ Real rooms mapped correctly to the production products (Refresh room list).
- ☐ Statuses (create/remove + inbound) aligned with the real booking flow.
- ☐ Paid-room policy and inbound status set so the payment flow is not bypassed.
- ☐ First live sync verified in both directions.
- ☐ Rollback known: setting the integration inactive stops outbound; turning inbound sync off stops picking up display bookings.
Note the server WebSocket URL and get the group token (Default API Token) under Global Settings; make sure the rooms (Liso displays) are configured and online.
In Administration > Integrations add an integration of type "Evoko Home"; fill the WebSocket URL, integration user and group token, turn TLS verification off (self-signed port 3002) and click Test connection.
On the Configuration tab set the create and remove status, the display subject template, an optional PIN, the poll interval, the paid-room policy and (for two-way) inbound sync + inbound status.
On the Mapping tab click "Refresh room list" to fetch the Evoko rooms (allRooms) and link each i-Reserve object (product) to the right room.
Set the integration active; test outbound (booking to create status → appears on display) and, if enabled, inbound (booking on display → created in i-Reserve after the poll).
