---
title: "wendy cloud device camera set-control"
description: "Set tunable controls on a local camera"
---

## Syntax

```sh
wendy cloud device camera set-control <id> name=value [name=value ...] [flags]
```

## Examples

```sh
wendy cloud device camera set-control --help
```

## Arguments

Argument notation from the CLI: `<id> name=value [name=value ...]`. Angle brackets mark required values; square brackets mark optional values. See Details for command-specific validation.

## Flags

Flags below include inherited options. Types and defaults come from the CLI source. An empty default means no value is configured.

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--broker-url` | string | (empty) | Tunnel broker host:port (default: cloud :443 endpoint, otherwise &lt;cloud-host&gt;:50052) |
| `--cloud-grpc` | string | (empty) | Cloud gRPC endpoint (optional when a default session is set via 'wendy auth use') |
| `--device` | string | (empty) | Target device hostname; `wendy run` accepts a comma-separated list to deploy one build to several devices (needs a remote build host and --detach). Defaults to $WENDY_DEVICE, then the saved default device |
| `--json` | bool | `false` | Output in JSON format |
| `--no-persist` | bool | `false` | Apply once now; do not re-apply on stream reconnect or reboot |
| `--reset` | stringSlice | `[]` | Put these controls back to the driver's default and stop persisting them |
| `--reset-all` | bool | `false` | Put every mutable control back to the driver's default and forget them all |

## Output

Output depends on the operation and selected target. Use the command help for additional guidance..

## JSON output

The global `--json` option requests machine-readable output. The CLI also selects JSON mode when no interactive terminal is attached. Support and payloads are command-specific; this flag does not guarantee a single JSON document for commands that stream logs or invoke build tools. Consult Details before parsing command output.

## Exit codes

The CLI entry point returns `0` on success and for its user-cancelled or default-cleared results. Other returned errors exit with `1` and print a diagnostic to stderr. Some operations may terminate through subprocess or signal handling; do not infer application health from the CLI exit code alone.

## Common errors

Check argument values and flag combinations against the synopsis above. For discovery, build, port, and readiness failures, see [deployment troubleshooting](../../../../../../errors/). Command-specific constraints are in Details.

## See also

- [wendy cloud device camera](../../../../../../reference/cli/cloud/device/camera/)
- [CLI conventions and configuration](../../../../../../reference/)

## Details

Set tunable V4L2 controls on a local (USB/CSI) camera.

Controls are given as name=value pairs and applied in a safe order (a mode
control such as auto_exposure lands before the control it enables). Values
persist across stream reconnects and reboots unless --no-persist is given.

Example -- stop a flame or lamp from blowing out to white by forcing a short
manual exposure:

  wendy device camera set-control 0 auto_exposure=1 exposure_time_absolute=20 backlight_compensation=0

Run "wendy device camera controls &lt;id&gt;" first to see the available controls and
their ranges.

To undo: --reset puts named controls back to the driver's default and stops
persisting them, and --reset-all does that for every mutable control:

  wendy device camera set-control 0 --reset auto_exposure,exposure_time_absolute
  wendy device camera set-control 0 --reset-all

Use the command help for additional guidance.