Today is Thursday, 9th September 2010

Archive for September, 2009


1.7.3 Maintenance Release is out – 1.7.3.68!

There is a new maintenance release out that fixes a number of issues for 1.7.3 platforms.

The official release version is 1.7.3.68

This upgrade is NOT meant for those who have already upgraded to 1.8, only for those not requiring the upgrade to ZigBee Pro but who would like the following improvements provided by this upgrade:

Improvements in 1.7.3 include:
· Improved responsiveness to touch on the 7″ Touch Screens – This corrects a situation where a touch was registered but not communicated to the system.
· Improved network connection stability on the 7″ WiFi Touch Panel – This resolves problems where the network connection would be dropped.
· Improved detection of the dropped WiFi connection when the product is out of range. The new release does not allow Navigator to remain blocked while waiting for a response from Director.
· Improved network throughput to alleviate audio skipping caused by insufficient network bandwidth – This resolves a problem most often occurring on new HC-300 Controllers.
· Changes to the Navigator interface in Rhapsody, Artist searches not to retrieve genre information – This change improves search performance.
· New driver for the Control4 Dock for iPod which adds the ability for the driver to be configured to disable Cover Art, removing that ability from the Navigator interface. This driver is automatically updated with the most current driver changes when the system is updated.
· Added support for the HC-200 as an endpoint for the Announcement agent.
· Corrected the Diagnostics checks used in Composer, System Diagnostics, Controller Networking, Check Internet Connection.
· Modified the Control4 Thermostat driver and set the CURRENT_TEMPERATURE variable to read/write so that it can be configured via programming to display the temperature of other devices.
· Corrected the ADT/Honeywell Vista ICM driver so that the string “ID” in a zone doesn’t cause the driver to malfunction.
· Fixed problem where Navigator wasn’t showing the correct temperature when an AprilAire system was used

Firmware Changes:
· Dimmer/Switch – Change to better handle international 240V loads.
· Control4 Dock for iPod – Resolved various problems reported with the Control4 Dock for iPod related to communications, charging, lockup, etc.
· 4 Zone Amp – Resolved an issue with setting a static IP.
· Multi-Channel Amplifier, Multi-Tuner V2, Audio Matrix Switch – Resolved problems with DHCP working with some routers/DHCP servers

If your system is affected by any of these issues, please contact your dealer and see if this update is right for your system. Remember, while the firmware update is free, you may be charged an hourly rate by your dealer to perform the update.

  • Share/Bookmark


“How Do I…” – Program the colored buttons on my remote?

The question is often asked, “What do those four colored buttons at the top part of my remote do?”. The answer is a good one….anything. The fact is that those buttons can be programmed to control anything that your Control4 system is already setup to control.

What do they do at the C4 Central Mansion? It depends on the room. In the master suite the blue button activates the sleep timer, the red button turns the fireplace on and off, etc… Hopefully that gets you an idea as to some of the basic possibilities. So, how do you do it?

SR-250 colored buttons

Open up Composer HE, and click on the programming tab. These commands are programmed at the room level, so in the top left corner select the room you are wanting to set the programming up for. Once that is selected, look just below that and click on the button next to “Commands”. In the drop down menu, select the button it is you are wanting to program. In this case, we will do “Red Button”.

Control4 remote Colored Buttons, step 1

Now, we need to move to the top right corner of Composer and select the device we want to react to the press of the “Red Button”. In this case we are going to toggle the fireplace on/off. Select the fireplace, and below that select “toggle the Main Fireplace”. Drag that line of programming to the middle of Composer.

Control4 remote colored buttons, step 2

Now test it! You can make the programming as simple or as complex as you would like.

If you have any questions, feel free to ask and discuss here.

  • Share/Bookmark


“How Do I…?” – implement a multi-tap?

One of the things that I love the most about my Control4 system is all the functionality that I squeeze out of a single light switch or dimmer.  Using “multi-taps” and “press and holds” (those will be covered in another writeup) you can get almost endless functionality out of each switch or dimmer.

For new users, the question is often asked about how to implement a multi-tap.  Before the end of this article, you will be programming multi-taps all over the house in less time than you ever thought was possible.

Now, I need to point out that this tutorial is for systems running 1.7.3.xx and OLDER! If your system is running 1.8.xx, variables are handled differently. This may be simplified when 2.0 releases, but that is a ways out and there is lots of enjoyment to be had between now and then.

The first thing you need to do is create a variable. In Composer Home Edition, this is done under the “Agents” tab. Up in the top left click on the “Variables” agent, then just below that click new variable. Now, make sure and name this something you are going to be able to identify down the road. Since we are going to be creating a multi-tap for the mud-room lights, we are going to call this variable “Mud Room Multi-Tap”. Make sure you select “Number Variable”, then click okay. You will now have a newly created number variable.

Multi-tap step 1

Once that is out of the way, we move on to the fun part….PROGRAMMING!

Click on the programming tab, found in the bottom left hand corner of Composer. The first thing we are going to do is start in the top left corner, and select the light or keypad that you want to add the multi-tap to. In this instance, we are going to select the “Mud Room Lights”. Once you select the dimmer, just below that a field will pop-up that shows the available actions that you can program around. The options for a dimmer or switch are Top Button Pushed, Top Button Released, Bottom Button Pushed, Bottom Button Released, and Level Changes. For multi-taps I recommend programming around the release of the button as opposed to the push of the button. In this instance we are going to be setting our double tap for the bottom button, so we will click on “Bottom Button Released”.

(Note: if you are using a 3 or 6 button keypad instead of a list of options as I posted above, you will see a small picture of a keypad. You can click the button you are looking to base your multi-tap on, and then select press or release).

Now we are going to move over to the right side of Composer, and select the item we want to control based on the actions performed on the left. In this case, we are going to want to increment the variable, so it can keep track of how many times that button is pressed or released. If you look at the box in the top right corner, we are going to scroll all the way down until you see “Variables”. Click on the little “+” next to variables, and a list of available variables will drop down. Please select the newly created variable, in the case “Mud Room Multi-Tap”. Now in the field on the bottom right corner of Composer you will see a list of optional commands that can be executed. We are going to select the third option down, and select + 1. Now in the center box on the right had column you should see something like this:

Multi-tap step 2


Now, click on the line of code, and drag it into the middle of the screen. It should end up looking like this:

Multi-tap step 3

Now, we have a functioning counter. Essentially every time the bottom button on the mud-room lights is released, that variable will increase +1. Now, we need to tell the system what to do when that variable changes. While there is more than one way to accomplish this, I feel as though the best way is to execute the programming around the variable. Since the variable is what we are going to be dealing with now, we are going to move back over the left most column on Composer. In the top left box, scroll all the way down “Variables”, and click the “+” sign next to. Highlight our newly created variable out of the drop down list.

Multi-tap step 4

Now we are going to move back over to the right hand side, and scroll down until we see “Programming Control”. Down in the bottom right click delay, and pick the amount of time you want to execute the number of taps. I personally select 500 milliseconds (1/2 of 1 second). This is the amount of time you will have to push the button the appropriate number of times. Drag the programming line to the middle of the screen and drop it. Now, go up to the top right corner and select our newly created variable. In the box on the lower right, select the tab that says “Conditionals”. We are going to program the double tap right now, so we are going to select “= 2″.

Multi-tap step 4

Go ahead and drag that programming into the middle of the screen.

Now we need to move to the top right corner, and select the item(s) that we want to do something once the double tap is executed. For this write-up we are going to turn off all the lights in the living room, and turn the room off. Turning the room off will shut off any audio/video that is going on in the room. Lastly, we will turn off the fireplace. First start by highlighting the “? If Variables -> Mud Room Multi-Tap = 2″ in the center of the screen. What this will do is “indent’ any programming under that conditional. Lines that are indented will only execute if the conditional above it is met. Now, move over to the left and one by one chose the commands you want to take place when the double tap occurs. By double clicking on the programming line on the left side, you will insert it underneath the highlighted conditional. When it is all said and done it should look like this:

Multi-tap step 5

Now, to create a triple-tap or quad-tap (I don’t recommend doing anything more than a quad-tap, and even those are to be used sparingly), just start back at where we set the conditional to “=2″ and set to “=3″ or “=4″. Once you have all the taps done, there is one thing we need to do to finish this off. At the end of the script, we need to reset the variable to zero so that it will work for future multi-taps. If we don’t reset it to zero, it will just continue counting up to infinity and never work again. The good news is that setting the variable to zero is easy. In the top right scroll down to “Variables” and highlight the variable we are working. Down in the bottom right click on commands, and select “Set value to 0″. Drag this programming line to the very bottom of the script. Make sure that it is not indented under anything because we want this line to execute no matter what.

No, we’re all done! What we have done is used a variable to track the number of button presses/releases, put a delay in place to allow us a set period of time to press the button the desired number of times, set our programming based around the number of button presses, and reset our variable!

Obviously there are endless possibilities for what you can do with a multi-tap. This is just one of many ideas. You can literally have any part of your house that is controlled via Control4 execute something, based on multi-taps. Hopefully the write-up gets you a general idea as to how a multi-tap works, and how to program one. Feel free to discuss this write-up, and multi-taps in general here.

  • Share/Bookmark



Top