Writing a Custom Control4 Driver for the EA-5
Most "custom driver" questions end before any code is written, because the driver already exists. The question that shows up on the Control4 forums every week is some version of "is there a driver for this?", and the answer is usually yes, from Control4 or from a third-party developer. So this page starts where the work starts: finding one. Writing your own comes last, and it's covered at the end.

One thing to clear up first: nothing about this is specific to the EA-5. Control4's driver documentation says completed drivers "do not require platform or version-specific compiling." The same driver runs on an EA-5, a CORE 3 or a CA-1. What a driver can set is a minimum OS version, and some developers also exclude older controllers (more on that below).
Step 1: search Control4's own driver database
Control4 keeps a public database of drivers at drivers.control4.com. Each entry shows who made the driver, how it controls the device (IP, IR or serial), whether Control4 has certified it, and the OS it needs. A dealer sees the same database from inside Composer Pro, where the search has a "Local" and an "Online" option and marks certified drivers with an icon.
Search by the exact model number. TVs in particular are listed model by model: LG alone has thousands of entries, most of them Control4's own certified drivers that control the TV over the network.
Many network devices also announce themselves. Control4 calls this auto-discovery (SDDP): a device that supports it tells the controller what it is and which driver it uses, and it shows up in Composer's Discovered tab ready to add. Manufacturers have to sign an agreement with Snap One to support it, so plenty of devices don't.
Step 2: check the third-party driver stores
If Control4 doesn't list it, a third-party developer often does. The two big stores:
- DriverCentral sells drivers from many developers. A purchased driver needs DriverCentral's free cloud driver in the project, and most drivers start with a trial of 7 to 30 days that begins when the driver is added.
- Chowmain sells its own drivers. Licensed ones run through Chowmain's project agent on the main controller; trials don't need it.
Both sell to dealers, who install the driver in the project. Prices are on each driver's page and are usually in the tens of dollars to low hundreds.
The devices people ask about most
These come straight from owner questions on the forums. Checked in September 2026 against Control4's database and the stores' own listings; new drivers appear all the time, so check again before you buy.
| Device | What exists | Worth knowing |
|---|---|---|
| Google TV (Google TV Streamer, Chromecast with Google TV) | Third-party: Solidified Systems' Google TV driver (DriverCentral, $150, IP) and Chowmain's Google TV driver | Control4's own database has no Google TV driver. Chowmain's needs OS 3.4.3 or later. |
| LG TVs | Control4's own drivers, listed by model, controlled over IP | Search the exact model number. |
| Google Cast speakers (Nest, Google Home, Chromecast Audio) | Chowmain's Google Cast driver, which turns them into Control4 audio endpoints | Needs OS 3.4.3 or later. |
| Amazon Echo Link | No driver found | Echo devices aren't Google Cast receivers either. Treat it as a plain audio source. |
| Philips Hue, including the smart plug | Control4's own Hue Bridge driver; Chowmain's Hue driver and Whistle Projects' Hue Lighting Pack ($65, DriverCentral) both list the smart plug | Chowmain's bridge drivers need OS 3.4.3 or later and a Hue Bridge V2 or Bridge Pro. Its bridgeless Zigbee 3.0 drivers need OS 4.3 or later and a CORE-series controller. |
| Navidrome (self-hosted music) | Chowmain's Navidrome driver, released September 2026 | Needs OS 3.4.3 or later. |
| Matter devices | Third-party only: Solidified Systems' Matter driver (DriverCentral, $125) | Needs X4 (OS 4.0 or later); Thread devices aren't supported. |
Notice the pattern: several newer drivers need OS 3.4.3 or later, and some developers state that HC-series controllers are not supported. If you're on an older controller or OS, that is often the real answer to "why can't I get this driver," and our free controller check tells you what your controller can still run.
Step 3: the fallbacks when nothing exists
Control4's dealer software has built-in ways to handle a device with no driver:
- Infrared. Composer's driver wizard builds IR drivers, and it can learn codes from the device's own remote. One-way, but enough for many AV devices.
- One-way serial. The same wizard builds simple serial drivers for devices with an RS-232 port.
- Generic network commands. For a device that accepts simple network or HTTP commands, a generic command driver (Chowmain sells one) can send them from Control4 programming without a dedicated driver.
Two-way control, where the device reports its state back, needs a proper driver. That's where writing one comes in.
Step 4: writing your own
Control4 publishes its driver development documentation (DriverWorks) openly on GitHub. The essentials, from that documentation:
- A driver is a .c4z file, which is a zip holding
driver.xml(what the driver is: its properties, commands, connections and the kind of device it presents) anddriver.lua(what it does). - The language is Lua 5.1. Since OS 3, drivers can run on LuaJIT, which keeps to the Lua 5.1 standard. Code written for newer Lua versions won't run as-is.
- The work happens in a handful of callbacks the controller calls:
OnDriverInitandOnDriverLateInitwhen the driver loads,OnPropertyChangedwhen a setting changes,ExecuteCommandandReceivedFromProxywhen the system asks the device to do something,ReceivedFromNetworkandOnConnectionStatusChangedfor the conversation with the device, andOnDriverDestroyedon the way out. - The minimum OS is declared in driver.xml (
minimum_os_version). There are no "API levels" and there is no OS 3.5: Control4 went from OS 3.4.3 to X4 (OS 4). - Testing needs a licensed copy of Composer Pro and a controller. Control4's documentation says so directly, and Composer Pro licenses are for dealers and their employees only.
That last point is the practical one for an owner. You can read the documentation and write the code, but loading a driver into your project, custom or bought, is done in Composer Pro, so it goes through a dealer. The developer's own advice is the same as ours: build a new driver only when a search has come up empty and the device genuinely needs two-way control.
What to do next
Write down the device's exact make and model and your controller's model and OS version, then search drivers.control4.com and the two stores above. If a driver exists, installing it is a remote job: nobody needs to come to the house to add a driver to a project.
