> For the complete documentation index, see [llms.txt](https://docs.akenza.io/akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/akenza.io/tutorials/add-devices/how-to-send-downlinks-to-the-kuando-busylight-device.md).
# How to send Downlinks to the Kuando Busylight device
{% hint style="success" %}
**Applications**:
The [Kuando Busylight](https://busylight.com/) can be installed in a large variety of use cases. Through a downlink it can be programmed to show any color and used as a **visual notifier**, indicating a certain event, status, or as a cue for specific handling.
**Product features**:
* Meeting room occupancy
* Office desk availability
* Parking lot availability
* Cue for calendar event
* Indicator for status in test or production line
* Indicator for bin availability in the warehouse
* Temperature/humidity/CO2/ indicator
{% endhint %}
In this tutorial, you will learn how to set downlinks to the **Kuando Busylight** to show **color status** as a visual notifier.
### 1. Create a rule
To be able to send downlinks based on a condition, you need to create a **Rule**. Go to *Rules* and select *Create Rule*. Select desired device/s as a **Rule Input**, add a **Logic block** with your defined condition and select **Downlink** as a **Rule Output**.
On the **Downlink Input Field,** you need to select your Kuando Busylight by choosing the assigned **Data Flow** and **Device**. Enter Port *15* and select **JSON** as a **payload schema**.
**Custom payload description** as follows:
```
{
"red":12, // Red intensity max 255 min 0
"green":20, // Green intensity max 255 min 0
"blue":34, // Blue intensity max 255 min 0
"offDuration":10, // Off duration max 255 min 0
"onDuration":10 // On duration max 255 min 0
}
```
If the light shall be **On** all the time, you can set the **onDuration** **to** **255** and **offDuration** **to** **0.**
Test your Rule accordingly to see the changing light colors based on your rule condition.
{% hint style="info" %}
If you do not have a device at your hand, you can use the [Device Simulator](/akenza.io/get-started/create-new-device/device-simulator.md) provided from akenza to trigger your **Downlink**.
{% 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://docs.akenza.io/akenza.io/tutorials/add-devices/how-to-send-downlinks-to-the-kuando-busylight-device.md?ask=&goal=
```
`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.