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
Fibaro HC3 (Discovery)
By: David Bowdler
Updated: July 29, 2026
Version: 0.25
Fibaro HC3 (Discovery)
Local, cloud-free two-way control of a Fibaro Home Center 3, HC3 Lite or Yubii Home on RTI, over the controller's own local REST API — no Fibaro cloud and no internet dependency. A right-click Discover Fibaro Devices step inside Integration Designer reads every device, scene and room straight from the controller and rebuilds the driver to match, so it always mirrors the real installation.
Key Features
- One-click device discovery: reads every device, scene and room from the controller and rebuilds the driver — re-run any time after adding gear; your custom device names are preserved
- Friendly-named auto-programming tags: every device and scene gets tags named after it (e.g. Office Light On, Front Door Lock Lock, Masterbed AC Heat) — one drag wires the command macro AND its matching feedback variable together
- Full device coverage: lights, dimmers, RGBW, blinds and shutters, door locks, thermostats / AC, and motion / temperature / lux / contact sensors — all with genuine two-way feedback
- Scenes, profiles and alarm partitions: run and stop scenes, activate profiles, arm / disarm and monitor alarm zones per partition
- Saved projects rebuild automatically: discovered tags, macros and feedback persist across save and reopen — no need to re-Discover
- Telnet debug console for commissioning: connection status, device list and forced resync
Requirements
- Fibaro Home Center 3, HC3 Lite or Yubii Home on the same LAN as the RTI XP processor
- A controller account with local API access (username + password)
- Integration Designer 11.2 or newer (design-time discovery runs in IDesign's Python)
How It Works
Enter the controller's IP address, port, username and password in Driver Properties, then right-click the driver and choose Discover Fibaro Devices. The driver connects over the local REST API and rebuilds its variables, functions and events from your live devices. Tick the Show Tags checkbox to populate the Tag Browser, then drag a device's tag onto a button — the command macro and its matching feedback variable wire together in a single drop.
Fibaro HC3 (Discovery) RTI Driver
Two-way control of Fibaro/Yubii HC3 and HC3 Lite controllers over the local network.
1. Configuration
1. Set TCP Address to your controller's IP (Connection setup)
2. Set TCP Port (default: 80)
3. Enter the controller Username and Password
4. Set the Security PIN for alarm control (System)
2. Discover Devices
After entering the connection details, right-click the driver in Integration Designer and choose Discover Fibaro Devices.
The driver connects to the controller and rebuilds its variables, functions and events from your live devices, scenes and rooms.
Re-run Discover any time - your custom device names are preserved.
Show your tags: After a Discover, tick (or untick) the Show Tags checkbox at the very top of the driver's configuration. This refreshes the Tag Browser / Macro tree so your new device tags appear (IDesign only repaints that tree when a property changes).
Saved projects: Your discovered tags, macros and feedback are stored in the project and rebuilt automatically every time you reopen it - you do NOT need to re-Discover after saving and reopening.
3. Wiring Your Interface (Tags)
Every discovered device and scene is given tags named after it, so you can wire a button in one drag. Open the Tag Browser, find the tag (for example Office Light On) and drop it onto a button - the driver auto-programs BOTH the command (the button's macro) AND the matching feedback (the button's variable) in a single drop.
Tags created per device type:
- Lights / switches: On, Off, Toggle (dimmers and RGBW also get Slider)
- Blinds / shutters: Open, Close, Stop, Slider
- Door locks: Lock, Unlock
- Thermostats / AC: one button per supported mode (Heat, Cool, Auto, Off, Dry, Fan) plus Setpoint Up and Setpoint Down
- Scenes: Run, Stop
- Sensors (feedback only): Motion, Temp, Lux, Contact
Each tag carries the friendly device name, e.g. Front Door Lock Lock, Masterbed AC Heat, Kitchen Blind Open.
Important: tag names are set from the device name at Discover time. Wire your interface AFTER your device names are final - if you rename a device and re-Discover, its tag names change and any button already wired to the old name must be re-wired.
Advanced controls without tags: RGBW colour (set R/G/B/W, set colour, presets) and the thermostat absolute setpoint are available as functions under the driver in the Sources list - drag them onto a button's macro manually.
4. Supported Features
- Binary switches (on/off)
- Dimmers (on/off/set level/dim up/down)
- RGBW lights (colour, presets, programs)
- Blinds/Shutters (open/close/stop/set level)
- Door locks (lock/unlock/toggle)
- Thermostats (mode/setpoint)
- Motion, temperature and door/window sensors
- Remote controllers / scene controllers (key events)
- Scenes, Profiles and Alarm partitions
5. Debug / Diagnostics
The Debug / Diagnostics category (Advanced) provides two support tools. Leave both OFF/default in production - only enable when asked.
Debug Console Port (default 12508)
A live telnet console on the processor. Telnet the processor's IP on this port and type help for the command list. Useful commands:
- status - connection state, init stage, device count, log level
- vars - current system / alarm / profile variables
- devices / device <id> - list discovered devices / show one device's properties
- resync / scenes - force a device or scene resync
- api <path> - run an authenticated GET against the controller (e.g. api /api/devices)
- log [n] - show the last n buffered log lines
- debug <0-5> - set the log level (5 includes DEBUG)
Set the port to 0 to disable the console.
Enable Remote Logging (default OFF)
When enabled, the driver streams its log lines to the Smart Home Programming cloud dev-log so support can watch the driver remotely. The Remote Log Host and Remote Log Port are advanced settings - leave them at their defaults. Turn this OFF again once diagnostics are complete.
Licence
The driver runs on a 120-minute free trial. Once the trial ends the driver stops updating (feedback and control both pause) until a valid key is entered. To licence it, enter your per-processor Licence Key in the Licence category - the processor MAC the key is tied to is shown in the "MAC for key" system variable. Contact Smart Home Programming for a key.
Support
Smart Home Programming - https://smarthomeprogramming.com.au
This driver requires a licence key tied to your RTI processor's MAC address.
- Trial: 120-minute fully functional trial — no key required
- Purchase: Visit https://smarthomeprogramming.com.au/store/ to buy a licence
- Licence is per-processor — one key per XP processor