> For the complete documentation index, see [llms.txt](https://docs.xibosignage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xibosignage.com/kb/media-players/backlight-support-led-control-and-mute-audio-commands-for-philips-soc.md).

# Backlight Support/ LED control and mute Audio Commands for Philips SoC

Remotely switch the Philips SoC display backlights, control LED's and mute Audio using Commands

### Power Backlight

Use the following commands:

```
tpv|backlighton
tpv|backlightoff
```

If you are using the [2016 model 10BDL3051T](https://www.philips.co.uk/p-p/10BDL3051T_00/signage-solutions-multi-touch-display) use the following commands to turn the screen off and put into a lower power state and then turned back on:

```
tpv|screenoff
tpv|screenon
```

{% hint style="info" %}
For all other models, use `backlighton/off` as `screenoff` will completely power off resulting in the need for an on site restart!
{% endhint %}

### LED Control

The following commands can be used to control LED's located on the sides of some commercial Philips displays:

```
tpv_led|off
tpv_led|red
tpv_led|green
tpv_led|blue
tpv_led|white
```

### Mute Audio

```
tpv|mute
tpv|unmute
```

{% hint style="info" %}
`backlighton/off` doesn’t mute audio, so if you have audio playing you will will also want to schedule the above `mute/unmute` commands at the same time.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xibosignage.com/kb/media-players/backlight-support-led-control-and-mute-audio-commands-for-philips-soc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.