Garage Integration+
Cindev Experience Driver
Compatible Control4 Systems:
Control4 OS 3.4.0+, X4
Navigators: iOS, Android, Control4 Touchscreens
Transform your Control4 system with complete garage door control and notifications.
- Control all different kinds of garage doors
- Single Relay, Dual Relay + Relay with Stop
- Momentary or Latching Relays supported
- Read Door Position
- Single Contact or Dual Contact styles
- Powerful Events
- Open,Closed
- Partially Open (Only available with Dual-Contact integrations)
- Failed to Open/Close
- Left Open
Dealer Notes
For Full Documentation please go to Product Webpage.
- Make sure garage door is safe to move before using the driver. DO NOT close or control garage door if unsafe to do so.
- Partially Open, Fully Open, and Fully Close events and variables are only functional when there are two contacts for the door position.
- When using two contacts the following icon styles are available with PARTIAL support
- Add driver to the project
- Connect Relay and Contact bindings
- Set Door Open/Close times
- Refresh Navigators
- Use Integrator Tools to Set configure notification actions.
Garage Configuration Types
There are many different types of garage doors and gate systems that can be controlled. The options below describe the available configuration settings and how they are typically used.
Important: From the Control4 perspective:
- A Relay is used for control. It tells the door or gate operator to do something.
- A Contact Sensor is used for feedback. It tells the driver the actual position or state of the door.
For example, a relay output from the Control4 system is typically wired to an input or trigger on the garage motor or gate controller.
In most cases, you will need the following:
- A Relay to control the door. This is typically a wired connection from a relay output device. This is required for the driver to control the door.
- A Contact Sensor to read the door position. This is a physical sensor used to report door status back to the driver. Without a contact sensor, the driver cannot reliably provide events such as Failed to Open, Failed to Close, Left Open, or Partially Open.
- In most installations, only a single momentary relay and a single contact sensor are needed.
We recommend Control4 Z2IO or Z2C devices due to the contact and relay flexibility they provide.
Relay Modes
- Momentary: This is the most common mode for standard garage door openers. When triggered, the driver closes the relay, waits for the configured Pulse Length (ms), and then opens the relay again. This simulates a button press. Many garage motors also treat another momentary trigger while moving as a stop command.
- Toggle: This mode maintains the relay state until a different state is requested. It is typically used only for systems that require maintained control, often with two relays - one dedicated to Open and one dedicated to Close. This is not the correct mode for most standard garage door openers.
- Pulse: This mode sends an open or close command to the bound connection without maintaining relay state. This is typically used for software-controlled or non-traditional integrations and is uncommon in standard garage door installations.
Contact Sensor Configuration
- No Contact: Contact feedback can be disabled, but this is not recommended. Without a contact sensor, the driver cannot reliably report events such as Failed to Open, Failed to Close, Left Open, or Partially Open.
- Single Contact: This is the most common sensor configuration. A single contact sensor is used to determine door position based on the configured sensor behavior. With proper setup, the driver can determine whether the door is open or closed.
- Dual Contact: This is used when two separate sensors are available - one for Fully Closed and one for Fully Open. The Primary Sensor should be the Fully Closed sensor, and the Secondary Sensor should be the Fully Open sensor. If neither sensor is active, the driver will report the door as Partially Open.
Sensor Type
Contact sensors may be wired as Normally Open or Normally Closed. This describes the electrical behavior of the sensor circuit, not the physical position of the door.
Choose the setting that matches how the installed sensor behaves. For example, if the garage door is closed and the sensor circuit is also closed in that state, then the sensor would typically be configured as Normally Closed.
Cindev drivers include a streamlined debug workflow and a one-click pipeline to DriverCentral Support. Use the steps below to capture the right data fast and get help without leaving ComposerPro.
Once Property Debug Mode is on, a Property Debug Actions will appear with the following options:
- View Diagnostics Prints driver stats to the Lua tab.
- View Project Hierarchy Lists drivers, filenames, and proxies.
- Create Support Ticket Preps logging + fields for Support.
- Submit Ticket Sends the information to DriverCentral.
Create and Submit a Ticket
- Turn On Debug Mode (driver property).
- Go to Debug Actions Create Support Ticket.
- Enter your Tech Reply Email (where Support should respond).
- Enter an Issue Description (what you did, expected, and observed).
- Reproduce the issue or run your test steps.
- Select Debug Actions Submit Ticket.
- A Ticket ID will be displayed under Driver Status and also printed on the Lua tab for reference.
- Support will receive your information and email you back at the address you provided.
Click here for more information
All Cindev drivers for Control4 come with a 30-day trial. Simply add the DriverCentral licensing driver, Cloud Driver, along with this driver and you can fully test the driver before purchasing. Including Cindev drivers in your drivercentral showroom project will give you unlimited use without purchase.
www.cindev.com/terms-and-conditions
brought to you by:
Cinegration Development, LLC
www.cindev.com
www.drivercentral.io/cindev/
We are always looking to improve our drivers.
Please send your suggestions to: info@cindev.com