This module creates the link between two great systems. It offers complete integration between Lutron Homeworks QS or Radio Ra2 and URC’s Total Control. This type of integration with whole-home lighting systems is at the core of what home automation can be.
The ability to use Lutron interfaces to control URC opens up the custom market in a huge way. The need to clutter high end homes with multiple single use keypads goes away. The ability to use Lutron keypads to do things like trigger URC events and even control volume makes things possible that never have been before. Think about retro situations with Ra2 and their RF keypads that can go into any electrical box and double as an AV keypad. Or even putting a Pico and a trim anywhere, no wires necessary. Or in very high-end homes with custom color/engraved Lutron keypads that can also be used for the A/V keypads to keep a clean consistent look through out. Having access to use occupancy sensor status from within URC gives us the ability to do things as simple as trigger music on with occupancy or we can do more complex things like home monitoring. Using CLI or level triggered events, you can have one dimmer that shuts off multiple circuits.
There are so many things that become possible with this module that you start to think differently about how you design systems. They become one system rather than two separate systems. Which in turn allows us, the integrators, the ability to deliver a nicer looking, easier to use product to our clients.
This module is the missing link between two great systems. It offers complete integration between Lutron Homeworks QS or Radio Ra2 and URC’s Total Control. This type of integration with whole-home lighting systems is at the core of what home automation can be.
Button Press & Multi Press
Incorporating button press events can create much more dynamic control from Lutron keypads. We can now create Room Off buttons that really are room off, not just lights off. It is also possible now to have Lutron interfaces run double duty. You can have a keypad or Pico that has lights on the single presses. And then have the double presses trigger A/V macros. So double press Off can trigger your Room Power Off macro from URC.
Using this feature we can capture a scene by providing the IDs we want included in the group. Then we can send a command or levels for those IDs to change to. And then later we can recall and reset the original scene, setting the IDs in that group back to their original levels.
This is automation, having a macro trigger with out even having to touch anything. Using an occupancy to trigger a macro can be used in a number of scenarios. This can be as simple as turning off audio and video devices when no one is in a room. Or it can be used to turn music on when occupancy is detected.
This is an advanced programming feature and should be thoroughly understood before attempted. This can only be used on a button that reports a press and release to Lutron, this can be tested using Telnet. This function is called “while” as it will repeat a macro or function while it is being pressed and then stop once the button has been released.
By combining Occupancy Events and Keypad Used Events, you can give your system the information about if somebody is home or not, so that you can control the way events happen based on that status. For example it gets annoying to have the lights in your home dim down to night lighting if you’re there doing something, but its also nice to come home to a house with some lighting on instead of pitch black. This allows us to trigger these types of lighting scenes only if the home is in away mode.
This is a helpful little trick for areas that just don’t justify a Lutron keypad. By using either a CLI or a Level event, we can trigger a macro to turn more circuits on or off. This way turning one dimmer off can then shut off additional circuits. Or the opposite, allowing to control multiple circuits from just one dimmer, using it as a simple scene controller.
Available TCL Commands
- Create Group/Scene – Groups a set of IDs together for group control of levels and also saves the current levels to be recalled later
- Set Group/Scene – Sets the levels of a created group to any level or can be used to recall previous levels
- Set Outputs – Set the level and fade time of any ID
- Set LED – Set the LED status of any keypad buttons
- Trigger Lutron Scenes – Trigger Lutron keypad scenes
- Get Occupancy Status – Returns the status of an occupancy sensor as a URC Integer Variable
- Get Lighting/Shade/Relay Level – Returns the level of an ID as a URC Integer
- Variable Get Scene/LED State – (Coming Soon)
- Get Astronomical Data – Can return if its Daytime or the time for Sunset and Sunrise as a URC Integer Variable
- Send to Lutron CLI – Sends any Lutron command
- Restart Lutron Processor – Restart processor
Available Device Events
- Occupancy Event – Trigger a macro based on the status of an occupancy sensor
- Button Press Event – Trigger a macro based on the press of a keypad or Pico button
- Button Multi-Press Event – Configure a number of presses within a determined amount of time to trigger a macro
- Keypad Used Event – Trigger macros or set variable based on any button used on a keypad
- LED Change Event – Trigger a macro based on the state of a keypad LED
- Lighting or Shades Level Event – Macros triggered based on lights or shades level rising above, falling below, or equaling a set percentage
- While Button Pressed – Triggering a repeat event while a button is pressed until that button is released. Must be a button that reports both press and release.
- Lutron CLI Event – Trigger a macro based on any Lutron Telnet string being sent.
File > Import & Restart
This is a two way module that is packaged as a TCM file that needs to be imported in to the Accelerator software. When you click Import TCM FIle here you will need to change the Files of type to Total Control 1.0 Module Library (*.tcm). Then navigate to where you downloaded the Spin – Lutron.tcm file and choose it. After you have imported make sure you restart Accelerator in order to complete the installation.
Step 4. Add Other Devices > Confirm & Add
After you have restarted Accelerator go to step 4. and navigate to the module.
My > IP Database > AUX > SPIN > LUTRON
When the module is selected make sure that the checkbox is checked in section 8 that says Spin – Lutron Main Functions. If not try reimporting and restart Accelerator. Once you are sure you have the checkbox checked. Click Add Selected Module to add the module to your tree.
Step 6. Network Setup
At Step 6. click on Non URC Device and fill in the IP address of your Lutron processor. Leave the port set at 23.
Step 11. System Parameters
At Step 11. under Two Way Module Settings from the first drop downs choose the room that the module is located at in the tree and in the second drop down choose the lutron module.
Next in the bottom right under System Parameter Information you will insert your BlackWire module license key where it say license=.
After that scroll down and enter your Lutron telnet login and password. It is suggested that you create a unique login and password for this module and not use the default lutron/integration.
-updated authentication to support trialsVersion 1.1 - (April 08, 2018) Version 1.1 - (March 28, 2018)
-improved volume rampingVersion 1.0 - (March 26, 2018) Version 1.0 - (March 17, 2018)
Initial public release