Check Your Prerequisites

1. Pro-series controller is required, eg. Application Controller Pro or Field Controller Pro.
2. Purchase and enable the TPI Advanced License (see FAQ for license upgrades)
3. Purchase and enable then Control4 License (see FAQ for license upgrades)
4. Hardware, Control System, Network and Control4 Director must be configured.
   • All control system/DALI setup must be performed though the zencontrol Cloud before trying to configure Control4.
   • Ensure devices, groups and scenes are labelled helpfully in the cloud. These labels will be imported into Control4.
   • The Control4 controller must be on the same network as the zencontrol Controller for discovery to work.
5. Request the zencontrol Control4 driver package from support

Add Drivers & Controller to Control4 Project

Unzip the zencontrol Control4 driver package. It does not matter where you unzip this.

In Composer Pro add all the zencontrol drivers to the project. These must be manually added so that they are uploaded to the Control4 Controller/Director.

Go to Driver > Add or Update Driver and add each .c4z file.

 

In order to support mapping of zencontrol DALI Scenes to Control4 Scenes that can be selected on Navigators, the Advanced Lighting agent must be loaded into the project.

Then in the System Design screen (bottom-left corner) look for the Discovery tab (top-right corner) and double click your zencontrol controller to add it to the project.

 

Commission with zencontrol

There are 3 steps required to commission.
1. zencontrol Cloud setup. All the normal control system setup must be completed on the zencontrol cloud. Devices cannot be configured from the Control4 side.

2. Sync. When the controller is added to the project it should begin syncing with Control4.
If sync does not automatically run or is interrupted it can manually triggered by going to Actions > Sync with zencontrol.

3. Commission. Once sync as completed on the controller drivers you can go to Actions > Commission with zencontrol to automatically commission all the Control4 devices.

Status should be "Ready" before you start commissioning.

Composer Pro may become unresponsive while commissioning. This is normal, just wait a while and restart Composer if necessary.

4.  Spawn Custom Objects for Relays, Blinds and Fan Controllers.

By default, zencontrol relays, blinds and fan controllers are imported into the system as standard lighting objects.  A further step is necessary to create custom objects to interact with.  Click on the lighting objects made by the commission step, go to Actions and click the appropriate Create step.  This will create a new device that can then be seen in the app.  At this point, you can freely delete the original spawning lighting object.  Sadly, this cannot be automated, as yet.

Double click on the item to spawn a widget and check that the controls work. 

Important step for blind objects:

When you create a blind driver, a type selection box pops up.  It seems that some or all selections in these boxes do not set the blind type

 

After choosing a "Shade",  the type field has not been set.  IOS devices appear to crash if this is not selected on all blinds.   Select the blind type in this field in Composer and refresh your navigators (shift+F5 in composer).

 

 

Configuration Tips

In general, it is wiser to modify configuration values in the zencontrol cloud, than in the C4 system.  

 

Renaming devices

Renaming devices must be done in the cloud interface on the zencontrol cloud in the device location.   Once the changes have gone from green->black, run the Sync step again in the commission section.  Also, be sure to hide fitting numbers, as described below

 

When you are done programming Control4, hide all fitting numbers (eg. "66.0 ...")
On the controller device, go to Actions > Set Fitting Number Visibility and set Show Fitting Numbers to "Hide". This will remove the fitting number prefix from the names of all the devices associated with that controller.

You may need to go to File > Refresh Navigators  to make the names change on your touch screens. 

C4 Switch Panel LED Tracking

If your C4 Switch Panel is targeting one of our TOGGLE bindings, the LED will be well adjusted for the status of the dali target.  We recommend that you consider using Led Behaviour Push/Release for dim actions.  If you have an LED behaviour that you think should be applied to our driver bindings, please contact support.

 

Troubleshooting

LEDS not tracking

If the controller also has an MQTT license, the controller must have connected to the MQTT server in order to emit events to inform the Control4 system of the current status.

Generating a controller snapshot

If you encounter general issues, you can provide snapshots for support tickets in Compose by clicking Tools->Device Logs.  Note that the logs are extremely shallow (only cover a short period of time) for some logs so that best time to perform a snapshot is immediately after experiencing the issue.

 

Problem:  No Devices are Added

If you encounter an issue where no devices add, you may have a driver installation issue.

We have witnessed an scenario where the C4 Drivers seem to only partially install. 

In this scenario, the driver can be seen in the list in Composer and can be updated but no devices will be added when running the Commission step and updating or removing and readding the driver will not remedy the situation.

Should this occur, it may be necessary to perform a file removal of the drivers from the C4 system via the terminal (it is not enough to do it via composer).

To bring up the terminal in composer, select Tools->System Manager

Right click on your controller and select terminal

You will now have terminal window up

In the terminal, run:

cd /www/c4z

You are now in the drivers section and caution to only remove the files you absolutely need is needed.

You can remove any of the drivers by removing both the directory and the file

ie.

rm -rf zc_blind_driver

rm -rf zc_blind_driver.c4z

To remove all ZC drivers, you can run the following command:  (Be sure there are no other drivers prefixed with zc_ before running!)

rm -rf zc_* 

The following drivers are currently in the package

After removing these drivers, you can re-add as usual in composer, hopefully with better results.