Devices
A device is a Control4 controller that's registered to your organization. A controller registers itself when the Anvil Agent is installed on it, and from then on it's a target you can deploy drivers to with the CLI.
Managing devices requires the owner or admin role.
The Devices page
The organization-level Devices page lists every controller registered to your
organization, with its name, address, and status (for example Active or
Revoked). The driverforge device commands work against this same
list — driverforge device list shows these controllers and driverforge device select
chooses which one the CLI deploys to.
Renaming a device
Controllers register with a system-generated name; give yours something memorable.
- On the Devices page, open the ⋯ menu for the device and choose Rename.
- Enter a new name and save.
Revoking a device
Revoking cuts off a controller's access — it can no longer send telemetry or accept deploys until it re-registers.
- Open the ⋯ menu for the device and choose Revoke device.
- Confirm in the dialog.
A revoked controller shows a Revoked status. You can Remove a revoked device to delete it from the list entirely.
Device limits
Your plan sets how many active controllers your organization can have. If you hit the limit, revoke a controller you no longer use or upgrade.
Further reading
- Anvil Agent — how a controller registers and what the agent does
driverforge device— selecting the deploy target from the CLIdriverforge deploy/driverforge sync— pushing drivers to a controller