Adding a third-party driver to Control4 in Composer Pro

Third-party drivers are where a lot of the magic happens in a Control4 system. The certified driver library covers most of the big names, but the moment a customer drops in a pool controller, a quirky European AV brand or a niche energy monitor, you’re reaching for a community or commercial driver. We do this most weeks, and there’s a right way to go about it so you don’t end up chasing ghosts later.

This one’s aimed at fellow integrators running Composer Pro on OS 3.4 or later. If you’re a homeowner reading this, driver work isn’t something you can do yourself — Composer Pro is dealer-only software, so give our team a call and we’ll sort it.

Know what kind of driver you’re dealing with

Before you install anything, work out where the driver came from, because that determines how much you can trust it and who supports it when it breaks.

• Certified drivers — written or vetted by Control4/Snap One and available straight from the online database in Composer. These are the safest bet: they’re tested against current OS versions and get updated when something changes. Always check here first before going hunting elsewhere.
• Community drivers — written by other dealers or enthusiasts and shared on forums or sites like Houzz/the C4 community. Quality is all over the map. Some are brilliant and better-maintained than certified ones; others are abandoned and will fall over after an OS update. Read the notes, check the last update date, and treat them as “use at your own risk”.
• Chowmain and other commercial drivers — paid drivers from established third-party developers like Chowmain, DriverCentral and Cinegration. These are properly supported, documented and licensed. When a customer needs something the certified library doesn’t cover, a paid driver is usually the most reliable route, and the licensing cost is trivial against the labour you’ll save.

Installing a .c4z driver into Composer

A Control4 driver is a single .c4z file. To use one that isn’t in the online database, you drop it into your local driver directory so Composer can see it.

1. Download the .c4z file from the developer and save it somewhere you’ll remember (we keep a per-job folder).
2. On the Composer Pro PC, browse to Documents\Control4\Drivers. If the folder doesn’t exist, create it.
3. Copy the .c4z file into that folder.
4. Open Composer Pro and connect to the project’s controller.
5. In the System Design view, click Search in the Items pane and tick Local Database (alongside Online Database). Type the driver or manufacturer name and it’ll appear in the list.

Adding and binding the device

Once the driver’s visible, adding it is the same as any other device.

1. Drag the driver from the Items pane onto the correct room in your project tree. Get the room right — it matters for how the device surfaces on touchscreens and in the app.
2. Select the new device and open the Properties tab to set things like IP address, polling intervals or any developer-specific options.
3. Switch to the Connections view to bind it. Control connections (the data link to the device) live under the Control/AV bindings; if it’s an AV product you’ll also wire up audio and video bindings to your matrix or receiver here.
4. For network devices, check the Network tab to confirm the controller can see the device’s IP. For serial, bind the driver’s serial connection to the right port on your controller or serial expander.

Take your time on the connections page. A device that’s been added but not bound will sit in the project looking healthy and do absolutely nothing — that’s the classic head-scratcher on commissioning day.

IP versus serial: pick the right transport

A lot of drivers support both IP and serial control, and the choice isn’t just about convenience.

• IP is our default where the device supports it. Cleaner cabling, faster, and feedback (current state, volume, power) is usually more reliable. The catch is the device needs a fixed IP — set a DHCP reservation on the network so it never drifts. We run our gear behind Pakedge/Araknis switching and reserve everything by MAC.
• Serial (RS-232) is the fallback for older AV gear, projectors and anything without a network stack. You’ll bind it to a serial port on an EA/Core controller or a dedicated serial expander. Mind the baud rate, parity and flow control in the driver properties — they have to match the device exactly or you’ll get garbage or silence. Keep serial runs short and use proper shielded cable.

Licensing a paid driver

Commercial drivers run in a trial or demo mode until they’re licensed — typically they’ll work for a short window each day, then stop, which is a great way to look silly if you forget to license before handover.

1. Add the DriverCentral cloud driver to the project (one per project) and enter the customer’s DriverCentral credentials, or your dealer account credentials per the developer’s instructions.
2. Purchase the driver licence through the developer’s portal (DriverCentral, Chowmain, etc.) and assign it to the controller’s unique ID or the project.
3. Back in Composer, the paid driver’s status should flip from Trial to Licensed — check the driver’s own properties for a licence status field.
4. Allow a few minutes for the cloud sync, then refresh. If it won’t activate, confirm the controller has internet access and that the licence is assigned to the right controller ID.

Read each developer’s licensing notes — some tie the licence to the controller’s MAC/serial, others to a project. Get this wrong and the licence won’t transfer if the controller is ever swapped.

Testing and documenting properly

This is the bit that separates a tidy system from a callback waiting to happen. Don’t just confirm power on/off and walk away.

• Test every command path the customer will actually use — and confirm feedback comes back the other way. A button that fires but never shows correct state will confuse people in the app.
• Run any programming and scenes that touch the device, not just manual control.
• Check the driver’s logging output (Composer’s Lua/driver log) for repeated errors or timeouts — a driver that works but spams the log will bog the controller over time.
• Note the driver name, version, source, licence reference and any custom property settings in the project notes. We keep a running “third-party drivers” entry per job so the next tech (or future us at 9pm on a service call) knows exactly what’s in there and where it came from.

If the device involves any mains wiring, switchboard work or fixed lighting circuits to get it into the system, that’s licensed-electrician territory under AS/NZS 3000 and our crew handles that side. The Control4 documentation at control4.com is also worth a look for current driver database behaviour.

That’s our workflow for getting a third-party driver in cleanly and keeping it stable. Get the source right, bind it properly, license it before you leave site, and write it all down — future you will be grateful. Any curly ones, or you want a hand sourcing a driver for something obscure, give us a shout.

— Adam and the DUKE team