Professional two-way IP control drivers for RTI integration systems. Licensed per processor MAC address.
$129 AUD per processor · Version 0.16 · 120-minute free trial · RTI XP processors
Two-way control of zencontrol DALI lighting from RTI: groups, scenes, fittings and system variables, with self-healing feedback.
Control zencontrol DALI lighting from RTI over the zencontrol TPI Advanced interface. On, off, toggle, brighten, dim, stop fade and set level for each of the 16 DALI groups and for up to 64 individual fittings, plus scene recall, controller profile changes and zencontrol system variables.
Live two-way feedback means changes made outside RTI - a wall plate, an occupancy sensor, a timeclock, the zencontrol app - are reflected back into the RTI interface. Group state is worked out from the fittings themselves, so a group shows on, off or mixed correctly even when it was changed by something other than a group command.
Set up is quick. Discover from Controller (in Driver Utilities) reads the group, scene, fitting and system variable names straight from the controller, or Import Group Names reads them from the zencontrol commissioning spreadsheet. The names appear in the command and tag lists, so nobody types room names twice. Export and Import Configuration are included for moving a setup between jobs.
zencontrol controllers do not remember, across a restart, that anything asked them to send event notifications. When a controller reboots it comes back up healthy and simply stops reporting - control keeps working, only feedback dies, which is why the fault is so often blamed on the wrong thing. This driver checks its own event registration on a watchdog and re-asserts it the moment it lapses, so feedback repairs itself without anyone visiting site.
A ready-made sample project is included, with group pages, scene keypads, fittings, system variables, sensors and a driver status page.
IMPORTANT: quote the zencontrol TPI Advanced licence (part code zc-tpi-adv) for every controller. It is purchased from zencontrol, is charged per DALI line rather than per controller, and runs only on Pro-series controllers. TPI Advanced is what provides live feedback, button and sensor events and the names. Without it the driver can still send commands and will try to read levels back on a timer, but that fallback has not been confirmed on a controller without TPI Advanced.
LICENSING: this driver is licensed per RTI processor - one key covers every zencontrol controller connected to that processor, so a site with several controllers still needs only one key. A 120-minute trial runs without a key; after it ends control stops but feedback keeps working. The zencontrol TPI Advanced licence is separate, priced by zencontrol and bought from zencontrol or a distributor.
Two-way control of zencontrol DALI lighting from RTI, over the zencontrol TPI Advanced interface.
zencontrol makes DALI-2 lighting control systems: application controllers, sensors, switches and commissioning software. This driver is written and supported by Smart Home Programming and Automation, an independent RTI driver developer, and is not made or endorsed by zencontrol.
Quote the zencontrol TPI Advanced licence for every controller.
zencontrol TPI Advanced - purchased from zencontrol, not from us. Part code zc-tpi-adv. It is charged per DALI line, not per controller, so a three-line controller needs three of them. It runs only on Pro-series controllers (Application Controller Pro, Field Controller Pro, ACx3 Pro).
TPI Advanced is what provides live feedback: changes made at wall plates, sensors and the zencontrol app appearing in RTI immediately, plus button, sensor and slider events and the group and scene names. Without it the driver can still send commands, and it will try to read levels back on a timer instead, but that slower fallback has not been confirmed on a controller without TPI Advanced - so do not quote a job on it.
Also required: the controller must be reachable from the processor on UDP port 5108, and the processor must be able to receive UDP on the Event Listen Port (default 5109).
External services. The driver talks only to the zencontrol controller on the local network. The one exception is optional Remote Logging (off by default): when an integrator turns it on, the driver sends its log lines over HTTPS (port 443) to shpdrivers.services, run by Smart Home Programming and Automation, so support can see what the driver is doing. Nothing else is sent, and lighting control and feedback do not depend on it. If that server cannot be reached the log lines are simply dropped.
Field-tested on a zencontrol Application Controller Pro running firmware 2.2.145 with TPI Advanced enabled: group, scene and fitting control, live feedback, occupancy, button events and system variables in both directions. Other Pro controllers use the same TPI Advanced protocol. If yours is a different model, run the 120-minute trial first - you will know within minutes whether feedback arrives.
This is worth understanding, because it is the most common complaint about DALI integrations generally and it usually gets blamed on the wrong thing.
zencontrol controllers do not remember, across a restart, that anything asked them to send event notifications. Their own documentation is explicit about it: when a controller boots, whatever is integrating with it must re-assert that events should be enabled. If nothing does, the controller comes back up perfectly healthy and simply stops reporting. Lighting control keeps working, so the system looks fine - only the feedback is dead, and rebooting the controller appears to fix it at random.
This driver checks its own event registration on a watchdog and silently re-asserts it the moment it lapses, so feedback repairs itself within a minute without anyone visiting site. The Feedback Recoveries variable counts how many times it has done so - if that number is climbing, something is restarting the controller repeatedly and that is worth investigating.
The driver also detects the case where a second control system registers itself as the controller's event destination and takes the stream away. It reports that separately, and takes it back.
If Feedback State reads not licensed, the controller does not have the zencontrol TPI Advanced licence on that DALI line. See Requirements above.
Whenever live events are not arriving, the driver reads levels back from the controller on a timer, so the RTI interface keeps showing what the lights are actually doing rather than only what RTI last asked for. It is slower than live events. Adjust the Fallback Poll setting if needed. On a controller without TPI Advanced this depends on the controller answering those level queries, which has not yet been confirmed.
A hidden Debug category provides a debug level, a telnet console port (default 12558) and optional remote logging to Smart Home Programming for support. Remote logging is off unless you turn it on, and can also be switched on from a macro.
The Debug category is hidden in Driver Properties; use the console instead. Telnet the processor on the console port and type help for the command list. Remote logging can be switched on from the console or with the Remote Logging On function. The two most useful are status (everything at once) and events, which reports how many events have actually been received - registration succeeding is not the same as events arriving.
Loading products...