> For the complete documentation index, see [llms.txt](https://cp2004.gitbook.io/ws281x-led-status/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cp2004.gitbook.io/ws281x-led-status/documentation/m150-intercept.md).

# M150 Intercept

Commands should be formatted as such:

`M150 [P{intensity}] [R{intensity}] [G{intensity}] [B{intensity}] [W{intensity}]`

| Parameter | Explanation                                                                          |
| --------- | ------------------------------------------------------------------------------------ |
| `P`       | Brightness, max 255. If not included, defaults to maximum brightness in the settings |
| `R`       | Red intensity, max 255.                                                              |
| `G`       | Green intensity, max 255. Can also be `U` for Marlin compatibility.                  |
| `B`       | Blue intensity, max 255.                                                             |
| `W`       | White intensity, max 255.                                                            |

All of the parameters are optional, and can be included in any order. If an option is not included, its value is 0 - as a result sending an empty `M150` command will turn the LEDs off.

{% hint style="warning" %}
It's not recommended to send an empty `M150`, and instead use [@ commands](/ws281x-led-status/documentation/host-commands.md) to turn the LEDs on and off.
{% endhint %}

Examples:

```
M150 R255 G255  # Sets LEDs to yellow
M150 G238 B255  # Sets to light-ish blue
M150 W100       # Sets to white, at 100 intensity
M150 R255 P200  # Sets LEDs to red, at 200 brightness
```

## What does the W parameter do?

On a standard RGB WS281x strip, the W parameter sets an equal value of R, G and B on the LEDs.

If you have an RGBW strip and enable the 'Use dedicated white' setting, the W parameter will control the white LEDs only.

Sending any of R, G or B with the command takes priority over the W.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cp2004.gitbook.io/ws281x-led-status/documentation/m150-intercept.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.