Control4 drivers for the gear you’re actually installing.

Install on the customer’s real gear before you pay. Every driver includes a 7-day trial, a clear supported-model list and direct help from the developers. One licence per driver, per controller. No subscription.

Find your driver and try it free Need a custom driver?

Why installers use us

Built by guys who do this for a living.

Made in the field We build drivers for the stuff we keep running into on jobs. They act the way you’d expect in Composer.
IP, both ways Local IP control with status back to Control4. No IR emitters to stick on, re-aim or babysit.
Pay once One licence per controller covers every instance of that driver. No monthly bill.
Call the developers Something not right? Call us. You’re talking to the guys who wrote it, and we’ll fix it right then.
Remote help on site Our support app lets us jump on and sort it out with you while you’re at the client’s place.
Kept current Firmware changes and Control4 updates, we keep up. New versions go up on each driver’s page.

Drivers

Pick the customer’s gear. Check compatibility. Install the free trial.

Every driver is a one-time licence per controller. Install it and pair it first. Buy when you’re happy and it unlocks by itself.

Browse by category: Cable TV Control4 Drivers · Streaming Mini Apps for Cable Boxes

Custom drivers

Need a driver that doesn’t exist yet?

Tell us what you’re installing and what it needs to do.

You’ll hear back from the guy who’d actually build it, with a straight answer and a timeline.

If the gear’s on site, we can jump on remotely and build against the real thing. Way faster that way.

X4 driver fixes

Driver died after an update?

Old and encrypted drivers break after OS 3 and X4 upgrades all the time. Send it over and tell us what changed. We’ll find out why and, where it can be fixed, send back a working driver that keeps your project bindings. Send us the details or start a support session .

About

Built on real Control4 jobs.

Driver Cave is run by Control4 installers. We build the drivers we kept wishing we had on site, and we back them the way we’d want to be backed: pick up the phone and fix the problem.

Licensing

Pay once. Done.

Install it Add the driver to the project in Composer Pro.
Pair it Point it at the device and pair. You’ll see it connect before you spend a dime.
Buy the licence Copy the Site ID from the driver and buy on that driver’s page.
It unlocks itself Most drivers unlock on their own in about 30 seconds. Yamaha and Orei: paste the key we email you.
One-time licence per driver, per controller: every TV box driver $70 USD (TELUS, Bell Fibe, Bell MTS, Cogeco, Eastlink, SaskTel, Rogers, Videotron, Xfinity X1, Hotwire, Verizon Fios, DIRECTV, DISH, Optimum, US cable boxes, Sky, Xumo, MagentaTV, KPN, Google TV) · TDC Orei 8x8 Matrix $65 USD · TDC Xbox $50 USD · TDC Yamaha AVR $45 USD.

Support

You call, we answer.

Every driver we sell, we back. Stuck on site? Call or text +1 (650) 689-1892 or start a remote session . You’re talking to the developers.

Can I try a driver before I buy?

Yep. Every driver comes with a free 7-day trial. Add it to the project and connect it. Every TV box driver and Xbox start the trial by themselves; for Yamaha and Orei, grab a trial key on that driver’s page. Full control for a week. Buy when you’re happy.

Does one driver’s key work on another?

No. Every driver has its own licence. One key covers every instance of that driver on one controller.

Any subscriptions?

None. Pay once per controller.

Does it need Driver Cave online?

No. The licence is checked on the controller and our drivers don’t call home. A few devices use their maker’s cloud for some features (Xbox power-on goes through Microsoft), and that driver’s page says so.

What if a TV provider driver doesn’t work with the box?

Call us and we’ll sort it out with you. If it doesn’t work with the box, you get your money back.

Are you part of Control4?

No. Driver Cave is an independent driver developer, not affiliated with Control4 or Snap One.

What do you need when I call?

The driver name and version, the Site ID from Composer, the Status text, the device model and what changed before it broke.