Installing a Fixxy driver in Control4 | Docs

Requirements

Control4 OS 4.0 or later (X4). Our drivers are tested on X4. OS 3 support is not confirmed for every driver.
Composer Pro and a Control4 dealer account.
The controller needs internet access for license activation, daily check-in and updates. If the controller loses internet or our servers are down, paid drivers keep running. They pick up updates and license changes (like a refund or a release) the next time they check in. Demos still end on their date.

Download the .c4z from the Fixxy dealer portal (Portal > Downloads).
In Composer Pro, open the project and go to System Design.
On the Items pane, open the Search tab, choose Local, and use the folder button to load the .c4z (or copy it into Documents\Control4\Drivers so it appears under Local).
Drag the driver into the room it belongs to.
Open the driver's Properties and set them (each driver's docs list its properties).
Make the bindings on the Connections tab (for example HDMI Out to the TV or receiver).
Refresh Navigators so the Control4 app and touch screens show the new device.

Fixxy drivers are getting licensing built in, one release at a time. A driver that has it shows License Key, License Status and Update Available properties. If the version you installed doesn't have a License Key property yet, it runs without a key; your license is still recorded in Portal > Licenses and activates when you install the release that has it.
With a License Key property: paste the key from Portal > Licenses (format FXD-XXXX-XXXX-XXXX-XXXX). License Status shows Licensed, or Demo: N days left. The key locks to that project's controller.
One license covers one Control4 project. A product license covers every driver bundled with it (the Apple TV license covers the Apple TV Driver, Streaming Search and Custom Mini App on the same controller).
Replacing a controller: open the license in Portal > Licenses and click Release, then activate the key on the new controller.
"This license is active on another controller": release it in the portal first.
"That key is for another driver": the key belongs to a different product.

The Fixxy Cloud Driver also links a project to your Fixxy account. Add one Fixxy Cloud Driver to the project, create a link code in the dealer portal, and type it into the Fixxy Cloud Driver's Fixxy Link Code property.
After that, every Fixxy driver on that controller gets its license from your account automatically, and the Fixxy Cloud Driver shows which drivers have updates.
Pasted keys keep working too; you can use either.

Every driver has a 30-day dealer demo. Start it from the driver's page or the Demo page while signed in.
One demo per driver per dealer account.
Buying a license before the demo ends turns the demo key into the full license automatically. Nothing to reinstall, programming stays.

Licensed drivers check for updates daily and show the new version in the Update Available property.
Download the newest .c4z from Portal > Downloads and update the driver in Composer (right-click the driver > Update Driver, or load the new .c4z over the old one). Properties, bindings and programming stay.
Updates are free for the life of the license.

Any purchased license can be refunded for 30 days after purchase, no questions asked: Portal > Licenses > Refund. The license is cancelled and the driver stops on that controller.
The refund covers what was paid for that license after any promo discount, plus its share of tax. Full terms: /legal/refund. Licensing terms: /legal/license. Privacy: /legal/privacy.

Refunds go through the account owner. A tech on a team can't refund.
To refund or release a license, the controller must have checked in within the last 3 days. If it's offline, bring it back online or open a ticket and staff will handle it.
If a card payment is disputed with the bank, that order's licenses pause while the bank reviews it, and come back if the dispute closes in our favor. Calling the bank to withdraw the dispute is the fastest fix.

The account owner invites techs from Portal > Team. Each tech gets an email link that works for 7 days and must join with that exact email address.
Techs share the company's licenses, orders, downloads, linked projects and support tickets. They can buy licenses and start demos; those land on the company account.
Only the owner can refund licenses and manage the team. The owner can remove a tech any time, which signs them out right away.
An account that already bought its own licenses can't join another team. Open a ticket and staff will merge the accounts.
Staff replies to a ticket go to the owner and to any tech who wrote in that ticket.

Check the driver's Status property and Last Error.
Confirm the device has a DHCP reservation or static IP (our drivers re-find devices after IP changes, but a reservation is still best practice).
Confirm the controller and the device are on the same network/VLAN and that multicast/mDNS is not blocked if the driver uses discovery.
Turn Debug Mode on (where the driver has it) and look at the Lua output in Composer.
Confirm the driver version in Driver Version matches the latest release in the portal.
Re-pair or Reconnect from the driver's Actions tab where available.
If none of that fixes it, the driver may have a bug: escalate to the dev team.