> 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/3rd-party-apps-and-integrations.md).

# 3rd Party Apps and Integrations

## Native Integration

These apps have built in support for WS281x LED Status, allowing you to control your LEDs directly within them. Thank you to their respective developers for implementing support!

### [OctoApp](https://play.google.com/store/apps/details?id=de.crysxd.octoapp\&hl=en_GB\&gl=US)

OctoApp has built in support for buttons that can turn your LEDs on and off or activate the 'torch' mode. It also has support for the 'automatic torch on when viewing the webcam' feature, so you can see your prints easily. See a quick demo of this in action, check out the video below:

{% embed url="<https://www.youtube.com/watch?v=TeuOlUE25gQ>" %}

{% hint style="info" %}
App developer interested in creating a native integration? Checkout the [REST API documentation](/ws281x-led-status/documentation/rest-api.md) to get started.
{% endhint %}

## Non-native integration

Not all apps can integrate with every plugin, so many of them choose to support [Host @ Commands](/ws281x-led-status/documentation/host-commands.md) instead. This allows you, as the user to define custom controls that use these commands as you wish and use them in a variety of 3rd party apps.

Here are some examples of apps that support Host @ Commands:

* [OctoDash](https://unchartedbull.github.io/OctoDash/index.html)
* [OctoLapse](https://plugins.octoprint.org/plugins/octolapse/)
* [PSU Control](https://plugins.octoprint.org/plugins/psucontrol/)

{% hint style="info" %}
Found a cool plugin or other 3rd party software that uses action commands? Please contribute to the list!
{% 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 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/3rd-party-apps-and-integrations.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.