device
Manage the active deploy target — the Control4 controller that deploy,
sync, and agent act on. The CLI remembers it so you
don't pass it every time. driverforge device on its own does nothing; run one of its
subcommands.
The driverforge CLI is in preview. Commands and flags documented here may change
before the stable release. Follow along or share feedback on our
roadmap.
Usage
driverforge device <subcommand>
Prerequisites
- You're signed in (
driverforge login) with an organization selected (driverforge org select)
Subcommands
driverforge device list
List the controllers registered to your active organization; * marks the
selected one. A controller registers itself when the Anvil Agent
is installed on it.
driverforge device list
driverforge device select [name|id]
Choose the active controller. Matches its friendly name, hostname, Control4 device id, or id — or shows a picker when given no argument. Only active controllers can be selected, and selecting one pins its TLS certificate fingerprint so later deploys verify they're talking to the right controller.
driverforge device select "Living Room Controller"
driverforge device show
Print the active controller.
driverforge device show
See Organizations & devices for how the deploy target is resolved.
Global flags
Every driverforge command also accepts these global flags: --verbose/-v, --project-dir, --no-tui, --no-update-check, and --help/-h. See the overview for details.