Lutron Interfacing Backgrounder
This section details important information regarding interoperability with current and legacy Lutron lighting platforms.
- What Lutron LEAP protocol devices (RadioRA3, Homeworks QSX, and Athena) does Converging Systems support natively?
Converging Systems is an approved development partner of Lutron. Converging Systems supports these LEAP platforms natively using secure TLS encryption technology.
Lutron Platform Converging Systems Models
Supports CCT Output Support Full Color Output RadioRA3 e-Node 4000/4100 models Through Lumaris interface Through Hue/Saturation /Brightness Dimmers Homeworks QSX e-Node 4000/4100 models Through Ketra UI Through Ketra UI Athena e-Node 4000/4100 models Through Ketra UI Through Ketra UI - What legacy Lutron platforms are supported with Converging Systems' products?
Converging Systems has long history supporting a range of Lutron platforms. See list below for more information.
Lutron Platform Supported Converging Systems e-Nodes
Supports CCT Output Support Full Color Output Latest Lutron OS Version Tested HWI (consult factory) e-Node 2000/2100 models Through Phantom Dimmers (CCT + Intensity) Through Phantom Dimmers (Hue/Saturation/Brightness) Homeworks Ilumination 1.49.02 RadioRA2 e-Node 2x00 or 4x00 models Through Phantom Dimmers (CCT + Intensity) Through Phantom Dimmers (Hue/Saturation/Brightness) RadioRA2 Inclusive v 2.12.2 (final Lutron version) Homeworks QS e-Node 2x00 or 4x00 models Through Phantom Dimmers (CCT + Intensity) Through Phantom Dimmers (Hue/Saturation/Brightness) Homeworks Designer (QS) V15.13.6 (final Lutron version) Quantum e-Node 2x00 or 4x00 models Through Phantom Dimmers (CCT + Intensity) Through Phantom Dimmers (Hue/Saturation/Brightness) Quantum Q-Admin Software - How many e-Nodes can be setup to work with Lutron processors. This might of interest if you wanted to drive PURE Mode products (using ILC-xx0 controllers), and DMX devices (using e-Node/dmx gateway) and DALI II devices (using ILC-640d controllers).
Lutron permits quite a number of Telnet sockets (for legacy products) and TLS encryption sockets (for LEAP protocol devices). We have not seen any issues to date with respect to any limits exceeded.
- How do I set up a user name and passphrase within Lutron Legacy platforms (RadioRA2/QS) to enable Telnet connectivity with the e-Node 2x00/4x00 gateways?
Within the Lutron software, got to Tools/Configure Integration/Telnet Logins and create a new entry with Access Level of USER (not ADMIN). Lutron requires "USER" for integrations that require notifications to be automatically forwarded to connected platforms. If you select User for our credentials, the proper monitoring of activity within the Lutron system will not occur.
- How do I set up a user name and passphrase within Lutron current LEAP platforms (RadioRA32/QSX/Athena) to enable encrytped TLS connectivity with the e-Node 4000/4100 gateways?
Within the Lutron software, got to Tools/Configure Integration/Integration Logins and create a new entry (Add Integration Login) that is enabled. Hit Done and upload to your project.
- With respect to LEAP protocol devices (RadioRA3, QSX and Athena) what type of keypads, loads, time clock events and occupancy triggers can work with the e-Node 4x00 gateway and connected devices?
Our platform can support both real and phantom keypad operations, real and phantom Ketra and Lumaris loads (where supported), and any occupancy sensor and time clock events as they control any real or phantom load that we track.
- With LEAP integration, I notice that once I entered the IP address and passphrase that I set up within Lutron Designer, within 20 seconds all discovered Lutron devices (loads, keypads, etc.) auto appear. However, I have a very large systems with 2000+ devices but only the first 800 devices auto-populate within the e-Node web-page under Lutron. What happened to the other 1200 devices?
Even though you are required to add Lutron processors within your installation to handle additional loads, keypads, etc., we have been able thus far to handle extremely large systems with just single e-Node 4x00 device. We are currently capped at bringing in to display more than 800 unique devices during the exceedingly quick handshaking discovery process, but any keypads or loads that exceeds the magic 800 number still can be tracked and trigged by the logic within the e-Node. Note, that if you don't see your Lutron device ID in the Device list, simply open up the TRACE window (on our Lutron tab within the e-Node web-page for Lutron) or look at the Lutron Integration Report for the Lutron ID associated with that (missing in the list) device and document it. Then, within the Lutron table (within the e-Node web-page for Lutron), simply enter that "missing" ID and the action that you wish to perform as if it were a displayed (on our list) device. As long as we can see the device within TRACE, we can track it.