croppedHue

Hue by Dash

Login or Register to see price!


“There is more to lighting than illumination. Therefore we created Philips Hue, your personal wireless lighting system. A simple product built around you, designed for real life and all its potential. Life is what you make of it. So go on. Play around. Explore. Feel the control but let go every once in a while. Turn on your life with light.” -Philips Hue Website

Sounds cool, right?

How cool would it be if you could automate it from your URC Total Control system?

Dash makes it possible…


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

Product Description

Philips Hue has created customizable lighting solutions that can create cool and unique experiences in the home.  In the industry of Home Automation, it is imperative that we are able to control and automate this type of functionality. The Hue by Dash modules does just this. It gives full control over all connected Hue lighting devices making anything possible.

This module does not include any kind of user-interface. This module provides complete integration with all your Hue products through configurable control, making it easy to make Hue do many things from any of your URC Macros.

Available TCL Commands

  • Create Group – Allows you to create a Group Name that can be used in later commands to set multiple lights together
  • Simple Control – Provides simple settings: Off/On/ROYGBIV colors
  • Set State – Advanced control for all available paramaters
  • Increment State – Provides the ability to increment value of Hue/Brightness/Saturation
  • Recall Scene – Recalls a scene that has been create by the native Hue app
  • Query Light State – Returns the status of single light and saves chosen state to a URC integer variable



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 >Hue

Driver File:

Dash – Hue.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

 

Check here for the latest builds and all details on feature changes and fixed bugs,

Dash Community Forum – Hue Updates

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

Network Setup is a step that is required regardless of if the module is communicating with a physical device.  This step will go over how your Network Setup should be configured for this Dash App.  You will generally find the Dash App under “Network Setup > Non URC Device” in your URC Program.

This Dash App does not require that a specific IP Address is setup for it to operate.  However, it should be assigned an “Instance ID.”  When a module does not require a specific IP Address be setup, you can assign any IP Address to the Dash App that is unique from any other device in the list.

Your IP Address will be used as an “Instance ID” which will separate it from any other Dash Apps or URC Modules you have setup.  This ID is helpful when you want to create jumps to the Dash App / Module in multiple rooms / areas of your programming.

In the example below we have added two Dash Apps, “System Monitor” and “Time Tools.”  Each has been given a unique value “0.0.0.1” and “0.0.0.2.”  If they were assigned the same value the Dash App would result in an error and would not start up properly.

Step 11. 3rd Party 2-Way Settings

This app does not require any Parameters

How to link the Hue by Dash module to your Hue Bridge

This module requires that it retrieve a “username” or Link Code from the Hue bridge on initial installation. It will then store the code to persistent storage that can only be cleared by a hard reset of the MRX basestation.

Linking Process

1. Always run Dash Cloud Logging on startup when adding a new module. You will watch as the Hue module authenticates and begins to come online.

2. In cloud logging you will see some instructions telling you that it is now necessary to press the button on your Hue bridge.

3. This process will repeat every 15 seconds until the button is pressed and a code has been retrieved.

4. After a link has been made, the module will query the lights to confirm communication has been established. If it has, you will receive a message confirming it.

Dash App Parameters

You can always check here for the current information regarding the module.

A note about Hue products and their color range

Not all Hue products are created equal. They vary in their ability to reproduce color. This should be considered when creating custom groups. For example, the standard A19 bulbs can not reproduce the color green very well at all. While the LightStrip Plus does a terrific job with greens. This is because of their Color Gamut: The entire range of colors available on a particular device. You can use the information below to help choose and group the correct devices for your application.

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 Conditionals.

Creating A Group Of Lights

This command should be run in your Device Event Triggers startup macro. They will create groups that you can later use to control multiple lights with a single command.

Parameters:

Lights ID’s – Add all ID’s of any Hue lights that you would like controlled in the group.  The ID’s can be found in the native Hue app. They start from number 1 and count up. Separate the numbers with a “,”. Ex; 1,2,3,4
Group Name – This will be the name that you will use in the Set commands in order to control the entire group. At this time using spaces in the name will create errors. Please use UpperCamelCase until a future update has been released.

The Device Event Triggers startup macro happens 5 minutes after startup, and is the correct place to put commands that need to happen only one time after the system has been restarted or rebooted.


Using the Simple Set State Command

The Simple Control command can be used to control single lights, or a group of lights. It will do simple functions such as turning lights off or on to their default settings. You can also use this command to change the light to the basic colors of the rainbow.

Parameters:

Single Light ID or Group Name – You can control a single light with its ID number. Groups must be called by name using the name from the Create Group command. The light ID’s can be found in the native Hue app. They start from number 1 and count up.
State / Color– Choose state or color to set the light/group to.
Transition Time – This is an optional parameter and it is he duration of the transition from the light’s current state to the new state. This is given as a multiple of 100ms and defaults to 4 (400ms). For example, setting transistiontime:10 will make the transition last 1 second.



Set State (Advanced)

Using this command will give you access to all the available settings that Hue allows for. They are not all required and will never be used all at the same time.

Conflicting parameters

If you try and control multiple conflicting parameters at once, the lights can only physically do one, for this the following simple rule applies: xy beats ct beats hue, sat.

Parameters

There are 3 pages worth of parameters in this command.

Single Light ID or Group Name – You can control a single light with its ID number. Groups must be called by name using the name from the Create Group command. The light ID’s can be found in the native Hue app. They start from number 1 and count up.

Brightness – Brightness is set with a numeric value between 1 and 254. 254 is the brightest setting and 1 is the lowest. Using 0 will not turn the light off.

Hue – Hue is the color of the light. Its is a numeric value between 0 and 65535, both of which are red. You can refer to the chart to help determine the correct value.

Saturation – Saturation is the amount of color. It is set with a numeric value ranging between 0 which is the least saturated (white) and 254 which is the most saturated (colored).

CIE Color Space x,y – Using this chart will help you locate all possible colors using x y.

Mired Color Temperature – This is the color temperature setting. It is a numeric value ranging from 153 (6500K) to 500 (2000K).

Alert – This resource is for temporary effects and more may come in the future. At the moment it can be used to make the light do a blink in its current color either 1 cycle or continuously until stopped.

Effect – This command puts the lights in a color looping mode until it is stopped by sending the “none” command.

Transition Time – The duration of the transition from the light’s current state to the new state. This is given as a multiple of 100ms and defaults to 4 (400ms). For example, setting transistiontime:10 will make the transition last 1 second.

Increment State (Advanced)

The Increment State command is used for increasing or decreasing the level of hue, saturation, or brightness. The total value is either increased by the value set in the command, or decreased if the command holds a negative value. This can be used along with the Lutron by Dash module and the “while button pressed” event to provide brightness control form the Lutron keypad raise and lower buttons. The values used in this command will correspond to the range of values set for each specific state.

Hue : -65534 to 65534

Brightness : -254 to 254

Saturation : -254 to 254

CIE Color Space (x,y) : -0.5 to 0.5

Mired Color Temperature : -65534 to 65534

It should be noted that a value that exceeds the possible value range will be disregarded. That means that if you use a large value of say 100 to increase brightness and your light is currently at 155, then the increase command will have no affect on the light. It will be best to use smaller values here and repeat the commands in Accelerator if wanting large steps.

Parameters

Single Light ID or Group Name – You can control a single light with its ID number. Groups must be called by name using the name from the Create Group command. The light ID’s can be found in the native Hue app. They start from number 1 and count up.

State or Effect – Choose the State to be incremented.

Value – Choose the value that should be applied to the current value (use -value to reduce).





Recall Scene

The Recall Scene command can be used to recall any scene that is created with the native Hue app. Just use the name that is associated to recall that scene.

Parameters

Scene Name – Enter the scene name that has been set within the native Hue app.





Query Light State

The Query Light State command is multi-purpose. It will return and store a value to a URC Integer variable as well as post all values into Dash Cloud Logging. This can be extremely helpful in trying to find that perfect color. You can use the native Hue app to set a perfect color and then run this command and take the values form Cloud Logging and use them in a Set State command to replicate that color. This can also be used to return values like brightness and use them in conditionals to control the way programming will be executed.

Parameters

Single Light ID – You can control a single light with its ID number. The light ID’s can be found in the native Hue app. They start from number 1 and count up.

State – State determines what value will be saved to the chosen variable. All values will be stored to an Integer variable with State returning 1 for on and 0 for off.





Alert (Light Flash)

Please see the tab “Set State (Advanced)”




Color Loop (Basic)

Please see the tab “Set State (Advanced)”




Color Loop (Advanced)

This is a very advanced example of what can be accomplished using the Hue by Dash module. There are multiple things happening in this example. The first thing that a custom color loop is created that loops the colors that are in the painting. Then this is furthered by adding three different brightness levels of this loop. The goal was to get this loop to be able to react to the level of the other lights in the room. And above that, I wanted the loop to adjust brightness without having to reset the loop. Once the loop has been initiated, it can be adjusted without ever breaking its color looping cycle. It gets turned on anytime the lights in the room are turned on, and turned off when the room lights are off.

Multiple Dash modules are being used in this example. Lutron by Dash, Event Triggers, and this Hue Module are what was needed to make this happen.

Lets first take a look at the macro that actually controls the looping and brightness levels. This is the actual macro that will continue to loop until a variable is set to break the loop.

We will be using 2 integer variables to accomplish everything we want. The first will be the variable that breaks the color loop. Its an integer variable with possible values of 0 or 1. A value of 1 will complete the loop and a value of 0 will break the loop. The second is an integer variable that will determine one of 3 levels of brightness. 1 being the dimmest and 3 being the brightest.

The reason the macro was split into smaller 3-4 second chunks was to make it more reactive to breaking the loop. This will provide a more responsive off command. There are really only 4 main commands in the macro. The first command sets a starting color for the loop and turns the LED strip on. The second command sets a new color with a 10 second transition time. The third command sets it back to the original color with another 10 second transition time. And the last command triggers the macro again.

Now lets take a look at the universal macro that controls the loop.

This macro is a lot simpler than it looks. It runs twice because sometimes the Lutron by Dash module can react to a scene being set faster than Lutron can update the light levels in the processor. So for reliability it runs a second check just in case the first one did not yield accurate levels. The first command that gets run is a Lutron query to get the current level of the lights in the room. This level is then run through a conditional. If the level is greater than or equal to 1% that means the lights are on and it will set the variable for the color loop to 1 and trigger the loop. The important thing here is that it checks the color loop variable first. This way if the color loop is already running, it will not create a multiple loop situation. Then it does the opposite if the lights are not on. It sets the variable to 0 and sends a command to shut the light strip off.

The second conditional uses that level to set the brightness of the color loop. If the room lights are between 1-40% then the loop will be set to level 1. If they are between 40-75% then the loop is set to level 2. And if they are brighter than 75% they will be set to level 3, full bright.

 

The only thing left to do is trigger this macro. The best way to do it in a perfect environment is to use the Lutron by Dash Device Event for keypad used. That means anytime the keypad is used to set the lights, the macro will run and adjust the loop accordingly. In my scenario I did this for both my hybrid keypad and my nightstand Pico. And for safe measures I added it to a Level Event for when the room lights drop below 1% to make sure that it will always shut off no matter how they get shut off.

Here is what it looks like in action.





Custom Color Loop

Here is an example video of whats possible with this module. You can see in the video that we are using the module to control a loop of light colors that are consistent with the colors of the painting. You can’t see it in the video, but it also adjust brightness based on the other lights in the room. This requires some advanced programming and a combination of other Dash modules but it is a great example of the unlimited potential