Problem type

Screen cannot take its display's input over CEC

HTTP 409 ยท display_cec_unsupported

What it means

The API answers with HTTP 409 Conflict and the application/problem+json document below when the condition is Screen cannot take its display's input over CEC. The document's type member is https://screenrig.ai/problems/display-cec-unsupported, the address of this page, and its code member is display_cec_unsupported.

What to do

This screen's Player did not declare the display_power.cec_active_source host capability, so it cannot switch the TV to its input. Update the Player to its current version, or clear display.cec (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_cec_unsupported",
      "type": "https://screenrig.ai/problems/display-cec-unsupported",
      "title": "Screen cannot take its display's input over CEC",
      "detail": "What went wrong in this request.",
      "hint": "This screen's Player did not declare the display_power.cec_active_source host capability, so it cannot switch the TV to its input. Update the Player to its current version, or clear display.cec (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:

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

Codedisplay_cec_unsupported
HTTP status409 Conflict
Typehttps://screenrig.ai/problems/display-cec-unsupported
Player actionnone