Lutron Home Automation Integration by Dash OS

Lutron By Dash

Login or Register to see price!


Dash OS’s Lutron App provides a wealth of features above the standard URC Lutron Module.  Not meant to replace, but rather to enhance the offering from URC, this app is a welcome addition to any Lutron System you may integrate.


Sold by: Justin Spiniolas
SKU: lutron-by-dash. Category: .

Product Description

Lutron by Dash 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.

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 so complete that its impossible to show all of the possibilities, but here are a few uses that will help you to grasp its potential. Also check out the Walkthroughs for specific examples and how to implement them.

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.

Scene Recall

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.

Occupancy Events

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.

 

While

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.

Occupancy Monitoring

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. There is an entire blog post dedicated to the setup of Occupancy Monitoring. Check out the DashOS blog for more helpful tutorials.

Level Events

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.

Dash App Documentation Overview

This page will guide you through the installation, configuration, and programming of the specified Dash App.  You can navigate to various sections of the documentation by using the menu to the left.  New information is always being added to Dash’s Documentation so be sure to check back often to discover new ways to utilize your apps!

Download App:

Driver Location:

My > IP Database > AUX > Dash Apps > Lutron

Driver File:

Dash – Lutron.csd

Dash OS Update History

Whenever an update is available for a Dash App, a log of the major changes in the version will be provided below.  This does not necessarily reflect every change that was made as some minor changes may have been made that are undocumented, but it should reflect any changes that affect the operation of the Dash App.

Version 1

 

Download & Import the Dash App

In order for the Dash App to become recognized by the URC Programming Software we will need to import the provided TCM File into the Software.  Once this has been done properly the Dash App should show up in the “Add Other Devices” programming step in the “Accelerator Location” provided on the overview tab.

Import TCM

In your Programming Software locate the “Import TCM Files” button in the File tab of the top menu toolbar.  Click it to open the Windows File Browsing window.  Browse to the TCM file you wish to import and select it.

Import Dialog

Based on the Dash App / Module you are importing, a dialog similar to the below will appear.  This window indicates what interfaces are supported by the TCM File you selected.  System Plugins may only show “Driver” and “Base Station Files” when no User Interface is provided by the module.

Restart

After Importing your TCM File it is always safe to quickly restart your Accelerator Software to make sure your changes are properly made.  While this isn’t required every time, it is a good step to make sure everything is changed as needed.

Confirm

Confirm that the Dash App was successfully imported.  You can do this by navigating to the driver where the Dash App is installed (see Overview Tab) and making sure a checkbox is provided for “8. Select 2-Way Modules for Network Remotes / Keypads”

Non URC Network Setup

This Dash App requires that the IP Address of the Lutron Processor be used in order to establish commnication. Port 23 will be filled in automatically.

Step 11. 3rd Party 2-Way Settings

Properly configuring the Dash App Parameters in your Automation Programming Software is important in order to make the App work as you want it to.  These Parameters will be used each time the App starts up to configure how the App will operate.  Below we will go over each available parameter.

We are going to need to create a unique Username and Password for Lutron Telnet Login specifically for Lutron by Dash. This is done through Integration Settings within the Lutron Software.

Dash App Parameters

Lutron Login=

This is the Username that we have created just for this module. Do not use the default Lutron Username User or Lutron here.

Lutron Password=

This is the Password that we have created just for this module. Do not use the default Lutron Password 1234 or Integration here.

Dash App Feature Tour / Walkthroughs

Welcome to the Dash App Feature Tour!   This page will go over the features available to you when using the Dash App within your Dash OS-powered systems.  These tours may include specific programming guides, file examples, drivers, or simply detailed explanations of the features listed on the Product Description tab.  Use the tabs to the left to select a feature that you would like to learn more about!  Enjoy!

These examples will require a basic understanding of TCL Commands and Device Events.

Lutron Keypad Room Off

Lutron Button Press Events are very simple Device Events to setup. All the necessary ID’s can be found in the Lutron Integration Report. I prefer to import the Integration Report in to my XLS file where I keep track of all my equipment IP addresses and any other pertinent info. We can see that the Master Bedroom keypad has an ID of 25 and the Suite Off button has an ID of 6. We use these IDs to complete the Parameters section of the Device Event.

Then we just add the Room Power Off command into the macro. So when the Suite Off button is pressed on the keypad, it will trigger this event and in turn send the command.

Pico Double Press Off

Lutron by Dash makes it possible to make Picos run double duty now. You can have a nightstand Pico on the pedestal that has bedroom lights on and off 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 and you could use double press ON to trigger a morning “wake up” macro. This could do things like set the lights, turn the TV on to the weather channel and turn music on to start the morning.

Again by using the information from our Lutron Integration report, we can simply create an event for our Pico. We select the Button Multi-Press Event. Then we fill in the ID for our Pico and its Off button. We choose 2 button presses within 1000ms or 1 sec. This Pico is programmed through Lutron to turn off the Master Suite lights if the Off button is pressed. Now when we double tap it, it will also turn off any audio or video that is on.

Dimmer Scene Off

This is a helpful little trick for areas that just don’t justify a Lutron keypad. In a bathroom with two circuits, you can use two dimmers and have both circuits shut off if either dimmer is shut off.

Its pretty simple to implement. We just create a Device Event for each dimmer. These will be CLI events, They will be identical except for the ID of each dimmer.  The CLI is the string that Lutron sends out over Telnet when a device is used or controlled. So we want our events to trigger whenever one of the dimmers have been turned off. For ID 26 that would look like this.

~OUTPUT,26,1,0.00

So our Device Events will look like this.

Then in each of these events, we are going to have a TCL command that sets the output of the other dimmer to 0%. Since we have a zone of DMS audio in this bathroom, we will also send the Room Power Off command. And of course we will report this Automation Macro to our Dashboard Timeline.

Scene Recall

Scene Recall is a great feature and provides some really versatile functionality. By combining the Create Group/Scene TCL Command with Set Group/Scene we can change a series of lights and then later return them to their previous levels. We use the Create command to save the current lighting levels and change them to their new levels. Then we use the Set command with recall to replace the lights to their previous levels.

In this example, we are using an occupancy sensor to run some checks first and then raise the level of the lights in a certain room. This event is a simple Occupancy Device Event and gets triggered whenever the sensor senses occupancy. The conditionals filter out if anybody is watching TV in the area, if it is night time, and if the lights are below 50%. Here in parameter we are using the Send Command function to trigger one of our Lutron scenes.

 

 

 

 

 

 

 

Then we use the Set Group/Scene TCL Command triggered by an Occupancy Device Event that is set for Unoccupied. This will set the lights all back to the levels they were at prior to the occupancy.

 

 

Homeworks QS Press And Hold

By using CLI Device Events, we can integrate to the native QS press and hold functionality. We just need to program the button from within the QS software to have press and hold. Then we use that telnet string that the press and hold reports to put into our CLI event. Then we can add anything we want into that macro.

Occupancy Room Sync (advanced)

This is the kind of automation that is about as cool as it gets. Using an Occupancy to trigger a room sync, we can provide a system that automatically matches the audio in a bathroom to the audio thats playing in the bedroom just by walking in to the bathroom. This make me smile every time it happens. And then we can throw in some added checks, that way if nothing is on in the bedroom we can check the time and if its between a set time, the system will turn on some music for our time in the bathroom. This is very cool, trust me.

This is a bit more advanced, and will require an understanding of using String Variable to set sources. This allows us to easily run a Universal Macro that will sync the sources from the two rooms.

The first thing we do is create a Device Event that will be triggered by the occupancy. We get the Integration ID for the occupancy and choose to have this event triggered when occupied.

Next we create a macro that will run some checks for us. We will be using a combination of Dash Apps here, Lutron and Time Tools, in order to refine what happens and when it happens. The first conditional will check our bedroom string variable and see if anything is playing in the bedroom. If nothing is, we use a Time Tools TCL Command to check if it is between 9am-9pm. The next conditional uses that info to determine if it will turn on Pandora or not. If it is between 9am-9pm, there is another conditional to check if Pandora is already playing somewhere else. If it is, then it just sets the bathroom source to Pandora, but if it isnt then it sends the Pandora play last command. Now it triggers the Universal Macro that turns this source on in the bathroom.

If however, the bedroom was playing something, then a Universal macro is run that will sync the sources between the bedroom and bathroom.

Then we go an extra step and check to see if its Daytime. If Time Tools returns that it is indeed Daytime, we send a TCL Command that will turn on the additional circuit of lights in the bathroom.

We finish up with a System Monitor Timeline event to let us know that an Automation Macro has been triggered. And all this happened automatically with out touching anything. This is an advanced example, but this should show the real potential in combining these Dash Apps with some advanced programming techniques.

Keypad Volume Control

“While” is an advanced programming feature and should be thoroughly understood before being attempted. This  function can only be used on a button that reports a press and release to Lutron, which can be tested using Telnet. This is a great way to turn raise/lower buttons into volume controls. The first thing necessary in order to do this is to clear these buttons of Lutron programming from with in the Lutron software.

We change the raise lower buttons to the option for “Raise programmed device” and then dont tie any light circuits to this button. This opens this button up to be used for whatever we program in URC. In this case since we are controlling volume, so we want to make sure that we are controlling any lights at the same time.

Next we set up the “While Button Pressed” events. We will tie a command to these buttons that will be sent recurring at whatever interval we set. For DMS volume, setting it to occur every 600ms seems to work well.

Also what I like to do is adjust the setting for DMS volume so that the command repeats twice. What this does is make a single tap actually increase or decrease the volume a noticeable amount.

iPort Launchport Button Sleeve Integration