Category Archives: Control4

All about C4

Connect Chromecast Audio devices to Control4

Control4

To enable your Control4 to play Chromecast Audio you need to buy a Chromecast Audio device and follow these steps.

  1. Setup the Chromecast Audio device as usual, join into your WLAN
  2. Connect the Chromecast Audio on any analog input of any Control4 Controller
  3. Add this modified Chromecast driver to the Project and connect in Composer the audio output to the Controller input. Its name will be shown in Composer as Chromecast Audio. nocontrol_google_chromecast_audio
  4. That’s it. Refresh Navigators and enjoy!

How to replace GT KNX dimmer and switch drivers by C4 dimmer and switch drivers

Control4

The process is identical for switch and dimmer, in this example we take a look at a dimmer driver which needs to be replaced.

  1. Make sure you have updated the driver to Version 10.6.2 or higher. Go to Driver -> Add or update Driver and select the driver file.
  2. Check version by right clicking on the driver
  3. Refresh the project in Composer by pressing F5 or File -> Refresh
  4. If the version is correct add a new KNX Dimmer driver from the online database to the project.
  5. Jump to the old driver and select in the popup window of the Property Replace with C4 Dimmer driver the new inserted KNX Dimmer driver.
  6. Press Set
  7. Jump to the new driver and see if all Properties were correct transferred.
    The driver name also is taken over, and the old driver is marked with obsolete.
  8. Buttons connected to the old driver were also transferred to the new driver
  9. Delete the old driver, AFTER you have checked Programming if there is anything to do.

 

Control4 driver for Cisco SBS series switches and network monitoring tools

This driver set is the Swiss army knife, it combines network monitoring tools with the ability to automatic reset power lines and/or ports of a switch. So first we need to make sure to have s Cisco Small Business Series switch in the project, a SG300-28 or whatever, 500 series also should work. It does not matter in which configuration the switches are running.

So for simple port control of the switch we just need the switch driver, setup as follows:

  1. Setup the Switch to allow Telnet access
    Login with your credentials and find the point to activate telnet. Usually Security->TCP/UDP Services
    CropperCapture[485]
  2. Setup the driver in Control4
    Find the driver by tipping “cisco” into the search field
    CropperCapture[476]
    And insert the properties
    CropperCapture[479]
    If the driver starts correctly under Programming all ports are listed
    CropperCapture[486]
    Each port can be switched on/off/toggled using this variables.

But wait, what about my ADSL that hangs every 2 days? No need for expensive power relays (that hang by itself…), we use C4 combined with the Cisco switch to do the job!

How to restart my ADSL modem if its not responding anymore

  1. Add the ping check driver
    CropperCapture[477]
    Insert the IP of the router or in case of a modem a IP from the internet/from your provider
    CropperCapture[480]
    Careful set the properties, in the drivers Documentation tab is explained what they do.
  2. Set the actions to take on ping loss
    To get something happen if the ping is lost, we have a variable named device_power_control, it goes to false if the ping times out, true if it the device answers correct. Furthermore a direct relay connection can be done
    CropperCapture[482]
    The relay connection can be connected to a low voltage relay (to break 12V or such) like the  one from the Controller, also possible to connect to a high voltage relay from a DIN-8REL module to break the power. The down time is 10 seconds, after that the relay closes again
  3. Switch a POE port of the switch on ping  loss
    Jump to programming and set the ports variable to the device_power_control variable
    CropperCapture[484]

Ping is ok but can I test also a telnet port, like the one from Director? Hang on!

Restart devices that should be checked on a telnet/TCP port

  1. Add the telnet check driver
    CropperCapture[481]
    And set the properties, again read the Documentation tab of the driver..
  2. Set the actions to take if port is not available
    The telnet driver has the same variables and relay outputs as the telnet driver, see above how to set up

The drivers for all this you find here (login needed)
ping_check_network_diagnostic_driverworks
telnet_check_network_diagnostic_driverworks

Latest switch driver version 1.00.005. Does expose a relay binding for each port
Download here (login needed)
switch_300-500_Series_Managed_IP_driverworks_cisco

Latest version switch driver 1.00.009

  • For each POE port and each link port a separate Relay connections is available in Connections
  • Only ports that are physically available are listed
  • Divers improvements

Download here (login needed) switch_300-500_Series_Managed_IP_driverworks_cisco_1_00_009

 

Control4 multi dwelling intercom with Koch

Control4

Control4’s doorstation solution has a big lack, it does not support multi dwelling houses which are very regular in Europe.
Koch provides the multi dwelling door intercom system TC-Bus which can support up to 115 members.

For each to TC-Bus connected C4 system a SIP gateway is needed, if the TC-Bus has less than 10 members the FBI6101 module should be used. Above the FBI6100 is suitable. To open the door a BRE2/SG module needs to be purchased, it connects from a C4 relay to the TC-Bus and sends the DTMF 7 when the relay is closed, the door opens. (Mention on order that is should send DTMF 7)

Limitations:

  • There is no way to call out, from panel to the doorstation
  • Only audio is supported, video can be inserted via webcam (which is mounted in the TC_Bus doorstation anyway) and a pageflip on the C4 touchpanel

Setup:
Login to the Koch SIP gateway default ip 192.168.1.200, password 1234
Setup the phone-book that  it rings to the intercom group 123:
CropperCapture[464]

Save it!

On C4, create a intercom group 123, assign all panels to the group.
Insert a “3rd party SIP phone” driver and set username and password (numbers only), insert the same credentials in the SIP gateway:
CropperCapture[467]
Save everything and try!
Opening the door can be done via “Custom Button”.

The driver for the dorstation webcam can be found in my other post about Koch:
https://technet.genesis-technologies.ch/koch-doorstation-compatible-with-control4/
Create a bookmark on your touchpanel for the webcam and have it called when the intercom session is accepted. Then you can speak and see the person outside.

International dealers may please contact Koch for sales directly:
http://www.kochag.ch/de/home.html

Control4 Zigbee: The definitive magic button press guide (..)

Control4
ProductIdentifyRebootChannel
Blink		Reset
Defaults		Leave Zigbee
Mesh & Reset
Factory Defaults
In-wall Lighting4 x top 15 x Top 7 x top,
4 x bottom,
7 x top 		9 x top,
4 x bottom,
9 x top
(or 9, 9, 9)		13 x top,
4 x bottom,
13 x top
Inwall 2-3
button keypads		4 x top 15 x top 7 x top,
4 x bottom,
7 x top 		9 x top,
4 x bottom,
9 x top
(or 9, 9, 9)		13 x top,
4 x bottom,
13 x top
Inwall 6
button keypads		4 x top left 15 x top left 7 x top left,
4 x bottom left,
7 x top left 		9 x top left,
4 x bottom left,
9 x top left
(or 9, 9, 9)		13 x top left,
4 x bottom left,
13 x top left
Light devices,
2-3 button
keypads in
Mini-App Mode		Press and
hold bottom
button		N/AN/AN/APress and hold
bottom button
for 13 seconds
6 button
keypad in
Mini-App Mode		Press and
hold bottom
left button		N/AN/AN/APress and hold
left bottom button
for 13 seconds
1-Button
Products		4157913
Thermostats4 x center 15 x center 7 x first left
4 x center
7 x first left

9 x first left
4 x center
9 x first left
(or 9, 9, 9)		13 x first left
4 x center
13 x first left
System Remote
SR-150		4 x red
C4 button		Room off, #,
*, 1, 5, 4, 1, 5		Room Off, #, *, 7, 4, 7N/ARoom Off, #, *, 1, 3, 4, 1, 3
System Remote
SR-250		4 x red
C4 button		Room Off, #,
*, 1, 5, 4, 1, 5		List, Info, Config, 2, 4,
8, 6, #, *		List, Info, Config,
Factory Defaults		Room Off, #, *, 1, 3, 4, 1, 3
Puck
(Button on puck)		4x15x7x9x13x
Puck
(Aux Contact 1)
(with momentary
switch connected)		4x15x7x22x30x
Puck
(Aux Contact 1)
(with latch
switch connected)		8x30x14x44x60x
Puck
(Aux Contact 1&2)
(with momentary
switch connected)		N/AN/AN/A9 x aux1,
4 x aux2,
9 x aux1		13 x aux1,
4 x aux2,
13 x aux1
Puck
(Aux Contact 1&2)
(with latch
switch connected)		N/AN/AN/A18 x aux1,
8 x aux2,
18 x aux1		26 x aux1,
8 x aux2,
26 x aux1
Cardaccess
relay and
contact sensor		4 x id buttonN/AN/AN/AHold id button, apply
power, keep holding until
LED is amber
Cardaccess
motion sensor		4 x id buttonN/AN/AN/AHold id button, apply
power, keep holding until
LED is amber
Cardaccess
mini remote		4 x bottom
button		Pull batteriesN/AN/AHold top left,
insert batteries
LED goes from
green to blue,
release top left,
press bottom right
Axxess
Wireless consact sensor		4 x N/AN/A15 x13 x
Axxess
Doorbell button		4 x internal
button		N/AN/A15 x internal
button		13 x internal
button
Axxess
Relay & contact sensor		4 xN/AN/A15 x13 x

Advanced logging not using Composer

Control4

This is a Control4 knowledgebase entry, compressed to the imported facts

Composer logging is good for issues that you can reproduce on the fly. If you have an issue that is random and sporadic then Composer logging is not the best option

Using the command c4log you are able to enable logging on any service running on the device. This will save the log on the device under the /log/debug directory. It will create a text file that will fill upto 1 mb (megabyte). Once it gets to 1 mb it will zip that file into a .gz (gzip) file. Then start a new text file that will fill to 1 mb again. Then also will create a gzip file with .2.gz on the extension. It will create a max of 5 .gz files. Once there are 5 .gz files it will overwrite the 1.gz file and next the 2.gz and so on.. (logging zigbee will create a total of 20 .gz fi les.)
Activate/deactivate the log process:

  1. Login to the Controller by using openssh. Ask Google where to download: https://www.google.ch/#q=openssh
  2. install openssh
  3. Open the windows command prompt and type ssh 192.168.0.1 -l root (Enter button)
    (For sure replace the IP with the one of your Controller)
  4. Accept the warning by typing “yes” and copy and paste in the password: t0talc0ntr0l4!
  5. In the command prompt type c4log (Enter button) and you see the list which services can be log’d:
    •     all
    •     amgserver
    •     audio
    •     c4lookup
    •     c4rmengined
    •     daemon
    •     dhcp
    •     director
    •     dtserver
    •     intercom
    •     ioserver
    •     kernel
    •     mp3d
    •     navigator
    •     netusbserver
    •     performance
    •     raproxyd
    •     ripd
    •     sipproxy
    •     sysmand
    •     upman
    •     zap
    •     zserver
  6. To start the logging use the command c4log enable (service).
  7. To stop the logging use the command c4log disable (service).

To have a look to the log process youo can use the command tail to any file that is logged in /var/log/debug. Example: tail -f /var/log/debug/director.log

If you need to send the logs to someone you can locate the logs from SAMBA share of the device.