RTI Remootio Driver
The Remootio RTI Driver enables control of Remootio smart gate and garage door openers from an RTI XP-series control system. It speaks the Remootio Websocket API directly over the local network — no cloud service and no internet connection is involved in control.
Overview
openers from an RTI XP-series control system. It speaks the Remootio Websocket
API directly over the local network — no cloud service and no internet connection is
involved in control.
Every action, response and event on that API travels inside an encrypted frame
(AES-256-CBC with an HMAC-SHA256 signature), keyed by the API Secret and Auth
keys the Remootio app issues. The driver uses the XP's native websocket transport
and its built-in cryptographic engine, so all of that is handled by processor firmware
rather than emulated in script.
Unlike a touchpanel template, an RTI driver is headless: it publishes System
Variables (status out), exports System Functions (commands in), and signals
System Events. The dealer builds the panel UI in Integration Designer and binds it to
these.
Features
Features — Remootio Gate Opener RTI Driver
Control of Remootio smart gate and garage door openers from an RTI XP-series processor, over the Remootio Websocket API on your local network. No cloud service is involved in control.
Gate control
- Trigger — pulses the output relay exactly as the wall button does. Works on every installation.
- Open / Close — request a specific end state. Requires a status sensor fitted; without one the driver says so and names Trigger as the alternative.
- Trigger Secondary Output — the free relay output (devices on firmware 2.21 or later).
- Hold-Open Minutes — hold the gate open for a set time on Open and Trigger (devices on firmware 2.24 or later), configurable at design time and settable from a panel at runtime.
Feedback, pushed in real time
The device reports every change as it happens — there is no polling, and feedback reflects the gate being operated from a phone, a key fob or the wall button just as it does commands from the panel.
- Gate state (open, closed, no sensor), with separate Open and Closed booleans and a Sensor Present flag so "not open" and "cannot tell" never look alike
- Left-open alert
- Last event, naming which key operated the gate and how
- API version, serial number, firmware version and uptime
- Connection state and status message
Events for macros
Gate Opened, Gate Closed, Gate Left Open, Output Triggered, Connected, Disconnected, License Activated, Trial Expired. Output Triggered fires for every operation of the gate, not only the driver's own — which is what makes an away-mode or notification macro possible.
Security
Every frame is encrypted with AES-256-CBC and signed with HMAC-SHA256, using the API key pair the Remootio app issues. The processor's own cryptographic engine does the work. The driver verifies its cipher against a known-answer vector at startup and reports the result to TraceViewer.
Reliability
- Automatic reconnection, with watchdogs on both the connection and the websocket upgrade
- Keepalive with traffic-based liveness detection
- Clean session teardown, so the device's single client slot is released immediately rather than after its two-minute timeout
Diagnostics an installer can actually reach
- Link Diagnostics — a one-line live summary that separates "nothing was sent" from "sent, never answered" from "answered, then stopped"
- Run Diagnostics — a full report to TraceViewer, with trace logging off
- Test Device Connection — one round trip, one verdict
- Status Message — the live connection phase, including raw socket state
Licensing
30-minute trial, then either an online license key or an offline activation code for processors with no route to the internet. Licensed state survives reboots with no network access.
Requirements
RTI XP-series or APEX processor on script engine 24 or later; Integration Designer 10.0+; a Remootio with the Websocket API enabled, on the same local network as the processor.
Version history
- Online activation with a license key now completes. The processor never ran the steps of the activation request, so a license key entered in License Key timed out and the driver stayed in its trial. Offline activation codes were not affected.
- No change to how the driver controls the gate. No configuration changes are needed; update the driver as usual with Update Driver.
- New documentation. The help Integration Designer shows for the driver (Get Info) now describes every setting, function, variable and event, with device setup, limitations and troubleshooting. The same text is the PDF manual.
- Hold Remaining Seconds declares its range (0 to 86400 seconds), so a bar graph bound to it scales correctly.
- The example project in the download now carries this version of the driver.
- No change to how the driver controls the gate. No configuration changes are needed; update the driver as usual with Update Driver.
- Improved startup reliability. On some processors, a leftover internal setting could interrupt the driver's start-up before it finished preparing itself. The driver now starts cleanly in every case. No configuration changes are needed; update the driver as usual with Update Driver.
- Initial Release
