Certified Control4 Integration

From IC Realtech Wiki
Revision as of 21:51, 27 November 2018 by IC-CCallaway (talk | contribs) (Created page with "200px|thumb|right|Control4: Home Automation and Smart Home Systems The aim of this guide is to cover the integration of IC Realtime IP Cameras in...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Control4: Home Automation and Smart Home Systems

The aim of this guide is to cover the integration of IC Realtime IP Cameras into the Control4 automated home using the Composer software. This wiki article is specific to the SDDP compatible, certified Control4 drivers which were released on 11-26-2018.

Hardware Setup

Ensure that the camera has the latest available firmware installed. Physically connect the camera to the same Network as the Control4 host, and provide power to the camera (via PoE or DC power connection).

Control Connection Setup

SDDP If the camera was added to the project via SDDP then the control connection will have automatically been set up. Check to ensure that the camera is on the same IP subnet as the Control4 system.

Manual We recommend that the camera be identified by SDDP. However you can also manually identify the camera via the Connections - Network tab. To identify the camera, you should trigger video tampering to let the camera send the identify message.(make sure that the camera's video tamper function is enable.you can enable the function via the camera's web page - Event - Video Detect - Video Tamper tab)


  • SerialNumber - It will show the camera's SerialNumber.
  • Camera Model - It will show the camera's Camera Model.
  • Firmware - It will show the camera's Firmware.
  • Motion - The value of this property mean: if the value is not 0, for example the value is 3, the driver would check the camera's motion state evenry 3 second. if the value is 0, it mean disable this function.

(To use this function, ensure that the motion detect function is enable. you can enable this function via the camera's webpage - Setup - Event - Video Detect - Motion Detect tab, also in this tab, you can change the areas and schedules about the motion detect.)

  • Brightness,Contrast,Saturation,Sharpness - Change these values, it will change the camera's value about Brightness,Contrast,Saturation and Sharpness.
  • Debug Level and Mode are for testing purposes.


A number of actions are available to assist with the setup of the driver.

  • Reboot Camera - Will cause the camera to reboot - It may be several minutes before the camera is back online.
  • Toggle Mirror - Allows you to toggle image mirroring - useful if the camera was physically installed incorrectly.
  • Sync Time - Will synchronize the camera time to the controller's time.

Motion Detection Event Programming

  • In order to use the Motion Detection event from the IP Camera in the Programming tab of Composer, you must have Motion Detection enabled in the Cameras Setup Menu:
  • Checkmark Enable in the Motion Detection Menu (Setup > Event > Video Detection > Motion Detection). Confirm you have a valid period, and area set. Anti-dither should be set to 0 in most instances.
  • On the properties tab of the driver, you can change the Motion property to determine how frequently Control4 will check for changes to the Motion state. Set this to 1 to poll every one second (or higher, if desired) and click Set to enable the feature.

The IC Realtime Motion Detection Event is structured as follows:

0) Anti Dither (The cooldown period. If a previous event just ended, the system waits for the 'Anti-Dither' duration to expire before starting a new event) 1) Event Start (Occurs when the Alarm starts (Alarm Input, Motion, IVS rule, etc)) 2) Event payload (In the case of motion, this will be for the entire length of the motion event plus a required additional 10 seconds of uninterrupted "no motion" delay. If motion occurs again during the delay period, the loop resets) 3) Event Stop (Camera closes the event state, stop recording to memory, and update the API C4 interacts with).

Therefore, a motion event that is 4 seconds of length will have a full clip / event duration of 14 seconds.

Limitations & Gotchas

  • This driver is for IP cameras only; not the NVR. Address each camera sepearately using these drivers - do not try and address the NVR with this driver.
  • Not all features are available on all cameras.


If communication cannot be established with the camera then this is likely to be caused by one of the following:

  • Incompatible camera firmware - ensure camera is running latest firmware
  • Camera not on same IP subnet as Control4 controller.
  • If manually entered IP address then this is incorrect
  • Contacts not bound correctly to Control4 contact devices.

Custom Programming

As well as the standard Control4 programming actions the following are available:


NOTE: Not all cameras will support all these functions.

For a more detailed setup on configuring the IC Realtime equipment and troubleshooting tips, please see the general integration guide.