---
title: "wendy device camera view"
description: "Stream video from a device camera"
---

## Syntax

```sh
wendy device camera view [flags]
```

## Examples

```sh
wendy device camera view --help
```

## Arguments

No positional arguments are declared in the command synopsis.

## 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 |
| --- | --- | --- | --- |
| `--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 |
| `--fps` | uint32 | `0` | Framerate (0 = device default) |
| `--height` | uint32 | `0` | Frame height (0 = device default) |
| `--id` | uint32 | `0` | Camera device ID, or SensorLink channel ID on Wendy Lite |
| `--json` | bool | `false` | Output in JSON format |
| `--non-interactive` | bool | `false` | Disable terminal prompts and automatic installs; select a camera with --id or --stable-id when several are available |
| `--raw` | bool | `false` | With --stdout: write the camera's uncompressed capture frames (one whole frame per message, layout printed to stderr) instead of encoded video. Only cameras captured in a raw pixel format offer this; viewers of the same camera keep receiving H.264. |
| `--stable-id` | string | (empty) | Camera stable ID from `camera list --json` — survives reboots and re-plugging |
| `--stdout` | bool | `false` | Pipe encoded video to stdout instead of opening a window (codec: H.264, VP8/WebM, or Wendy Lite MJPEG) |
| `--width` | uint32 | `0` | Frame width (0 = device default) |

## 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 device camera](../../../../../reference/cli/device/camera/)
- [CLI conventions and configuration](../../../../../reference/)

## Details



Use the command help for additional guidance.