What we do
Ready-made drivers
Drivers for the equipment integrators ask about most. Each one ships with setup documentation and gets updates when Control4 or the device changes.
Custom driver development
Send us the device and its protocol document. We build the driver, test it on the real hardware, and hand over something you can support on site.
Updates and support
A direct line to the person who wrote the driver, not a ticket queue. Bugs get fixed in the driver, not worked around in the project.
Devices we cover
These are the categories we integrate most, with the protocols we usually work over. If your device is not here, send us its protocol document and we will tell you what it takes.
Send a driver request- IP cameras and NVRsIP
- HVAC, VRF and heat pumpsIPSerial
- Security and intrusion panelsIPSerial
- Motorized shades and blindsIPSerial
- Music streamers and multiroom audioIP
- TVs, displays and projectorsIPSerialIR
- Gates, doors and intercomsIPRelay
- Energy meters and solar invertersIPModbus
How licensing will work
Driver store opening soonInstall the driver from Composer Pro
Add the driver to the project like any other. No key to type, no account to create first.
The driver registers the controller
On first connection it sends the controller's details to DriverForAll and starts a trial so you can finish the install.
Activate the license for that controller
Buy a license for the registered controller. The driver picks it up on its own; the customer never sees a prompt.
Built by an integrator, for integrators
DriverForAll started because waiting months for a driver, or being told a device is unsupported, stalls projects. Every driver here is written in Lua for Control4, tested on real controllers and real devices, and supported directly by the developer who wrote it.
Get notified when the driver store opens
One email when the catalog and licensing go live. Nothing else.