Driver Type
Categories
- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Networking
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
Driver Type
Categories
- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Networking
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
Flic Hub Trigger
By: David Bowdler
Updated: July 7, 2026
Version: 0.3
Flic Hub Trigger
Turn any Flic smart button into an RTI trigger. The Flic Hub Trigger lets a Flic button fire RTI events and macros over your local network — press a button to run a scene, toggle lights, jump a page, or launch any macro in your project. No cloud and no middleware; the button talks straight to your RTI processor.
Key Features
- Single, double and hold: every button gesture fires its own RTI event.
- Up to 16 buttons: name each one and wire it independently.
- Any macro: attach any RTI macro to any gesture in Driver Events.
- Feedback variables: Last Button, Last Action and per-button press counts to bind to panels.
- Optional shared secret: lock the receiver so only your Hub can trigger it.
- Built-in diagnostics: button-reference printout, test-button simulation and a telnet debug console.
Requirements
- A Flic Hub LR (bridges the Bluetooth buttons onto your network).
- One or more Flic buttons and the Flic mobile app.
- An RTI XP processor on the same network; Integration Designer 11.
How It Works
The Flic Hub sends a simple HTTP request to the driver on each press (configured as an “Internet Request” action in the Flic app). The driver, running on the RTI processor, turns that request into an RTI event you wire to a macro. Comes with a fully illustrated Integration Note covering setup end to end.
Flic Hub Trigger
Version 0.3
Turn Flic smart-button presses into RTI events and macros. A Flic Hub LR bridges the Bluetooth buttons to your network and fires an HTTP request to this driver on each press. The driver hosts a small HTTP receiver on the RTI processor and fires a separate event for every button and gesture (single click, double click, hold).
Requirements
- A Flic Hub LR (the Bluetooth buttons cannot reach the network on their own).
- The Flic Hub and the RTI processor on the same LAN.
- The Flic mobile app to pair buttons and configure their actions.
How It Works
1. In Driver Properties set the HTTP Port (default 9222) and the Number of Buttons. If another driver on the same processor already uses that port, change it to any free port - the driver will report Server Bind Failed if the port is taken.
2. Give each button a Name. Optionally set a URL id (leave blank to address the button by its number).
3. In the Flic app, add an Internet Request action to each button gesture pointing at the processor:
http://PROCESSOR-IP:9222/flic?btn=1&act=single
http://PROCESSOR-IP:9222/flic?btn=1&act=double
http://PROCESSOR-IP:9222/flic?btn=1&act=hold
Replace PROCESSOR-IP with the RTI processor address and btn=1 with the button number (or its URL id, e.g. btn=Kitchen).
4. In Integration Designer, open Driver Events and wire each Single Click / Double Click / Hold event to a macro. The driver also updates feedback system variables (Last Button, Last Action, per-button Last Action and press counts) you can bind to panels.
Optional Shared Secret
Set a value in Shared Secret to require it on every request. Add it as a query parameter (&token=YOURSECRET) or an Authorization header in the Flic app. Requests without it are rejected.
Events
- Button N Single Click / Double Click / Hold - one set per configured button.
- Any Button Press - fires on every recognised press.
- Server Bind Failed - the HTTP port could not be bound (in use by another driver).
- Trial Warning / Trial Expired - licensing.
Diagnostics
- Print Button Reference - logs each button's URL to TraceView.
- Test Button - simulates a single click for wiring tests.
- A telnet debug console runs on the Debug Console Port (default 12545). Type help() for commands.
Licensing
The driver runs a 120-minute trial, then requires a free licence key tied to the processor MAC address. Enter the key in the Licence Key field. During the trial and once licensed, all events fire normally; after the trial expires events are paused (feedback variables keep updating) until a key is entered.
Support
Smart Home Programming and Automation - smarthomeprogramming.com.au