# Screen cannot set its output mode

> Canonical HTML: https://screenrig.ai/problems/display-output-unsupported

HTTP 409 · `display_output_unsupported`

## What it means

The API answers with HTTP 409 Conflict and an `application/problem+json` document when the condition is Screen cannot set its output mode. The document's `type` member is `https://screenrig.ai/problems/display-output-unsupported`, the address of this page, and its `code` member is `display_output_unsupported`.

## What to do

This screen's Player did not declare the display_output.mode host capability, so it cannot set its video output mode. Update the Player to its current version, or clear display.output (null).

## Should you retry?

The `retryable` member appears only on HTTP 5xx problems, so this one has none. Follow the steps under What to do before sending the request again.

## Example response

Most routes answer with the error in the first entry of `errors`, and the document members `instance` and `request_id` beside it. The `type`, `code`, `title` and `status` of this problem type are fixed; `detail` varies per request, and `hint` is the registry default unless the handler sets a more specific one.

~~~http
HTTP/1.1 409 Conflict
Content-Type: application/problem+json

{
  "errors": [
    {
      "status": 409,
      "code": "display_output_unsupported",
      "type": "https://screenrig.ai/problems/display-output-unsupported",
      "title": "Screen cannot set its output mode",
      "detail": "What went wrong in this request.",
      "hint": "This screen's Player did not declare the display_output.mode host capability, so it cannot set its video output mode. Update the Player to its current version, or clear display.output (null)."
    }
  ],
  "instance": "INSTANCE",
  "request_id": "REQUEST_ID",
  "server_time": "2026-01-01T00:00:00Z"
}
~~~

## In the API contract

The OpenAPI contract describes this problem in these words:

> A display.output other than auto needs a Player that declared the display_output.mode host capability, else 409 display_output_unsupported, and when the Player has reported the modes it can set (observation.display_output.modes) a mode outside that list is invalid_request naming display.output.mode; display.cec with take_input true needs display_power.cec_active_source, else 409 display_cec_unsupported.

> A member you send replaces it, null clears it, and a member left out stays as it is; a null display clears all four. display.output other than auto and display.cec with take_input true need a Player that declared display_output.mode or display_power.cec_active_source, else 409 display_output_unsupported or display_cec_unsupported.

## Operations that name this problem

These operations name this problem in the API reference:

- [Update Screen](https://screenrig.ai/docs/api/screens#op-updateScreen) — `PATCH /api/screens/{id}`
- [Patch Screen Device Settings](https://screenrig.ai/docs/api/screens#op-patchScreenDeviceSettings) — `PATCH /api/screens/{id}/device-settings`

## Related problems

The contract mentions these problems alongside this one:

- [Request is invalid](https://screenrig.ai/problems/invalid-request) — `invalid_request`
- [Screen cannot take its display's input over CEC](https://screenrig.ai/problems/display-cec-unsupported) — `display_cec_unsupported`

## Player action

This problem defines no Player action class. It belongs to a project, pairing or account flow that an agent or the dashboard drives.

## Reference

| Field | Value |
| --- | --- |
| Code | `display_output_unsupported` |
| HTTP status | `409 Conflict` |
| Type | `https://screenrig.ai/problems/display-output-unsupported` |
| Player action | `none` |

- [All problem types](https://screenrig.ai/problems)
- [API reference](https://screenrig.ai/docs/api#problems)
- [Problem registry YAML](https://screenrig.ai/docs/api/problems.yaml)
