> For the complete documentation index, see [llms.txt](https://api.intecular.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://api.intecular.com/invisoutlet-aura/fetch-accessory-status/color-light.md).

# Color Light

> Fetch InvisDeco Aura's latest color lights statuses.

**Request**

* <mark style="color:red;">`packetID`</mark>: Represents the ID of the packet. This can be any six digit number, no leading zeros.
* <mark style="color:red;">`payload`</mark>:&#x20;
  * <mark style="color:red;">`callbackName`</mark>: 18
  * <mark style="color:red;">`callbackArgs`</mark>:&#x20;
    * `1`: The color light selection; 5 - Nightlight.

```json
{
    "packetID": 349027,
    "payload":
    {
        "callbackName": 18,
        "callbackArgs": [
            5
        ]
    }
}
```

#### Response

* <mark style="color:red;">`sn`</mark>: The serial number of the InvisOutlet.
* <mark style="color:red;">`packetID`</mark>: Represents the ID of the packet based on request <mark style="color:red;">`packetID`</mark>.
* <mark style="color:red;">`PUBACK`</mark> : If the request is successfully processed; 1 - Successful, 0 - Fail.
* <mark style="color:red;">`payload`</mark>:&#x20;
  * <mark style="color:red;">`callbackName`</mark> : 18
  * <mark style="color:red;">`callbackArgs`</mark> :&#x20;
    * `1` : The color light selection; 5 - Nightlight.
    * `2`: The color adjustment selection; 1 - HSV, 2 - Temperature.
    * `3`: The array that defines each LED's state and color; 9 arrays for nightlight, 7 arrays for indicator.
      * `1`: State of the LED; 1 - On, 0 - Off.
      * `2`: Brightness of the LED; 0-100.
      * `3`: Hue and saturation in an array.
        * `1`: Hue of the LED; 0-360.
        * `2`: Saturation of the LED; 0-100.
      * `4`: Temperature of the LED; 1000-40000.

{% hint style="info" %}
Note: Hue/Saturation or temperature value may not reflect the current status, depending on if the last control was based on hue/saturation or temperature, and can be known by index `2` (color adjustment selection).
{% endhint %}

```json
{
    "sn": "0003C44076",
    "packetID": 349027,
    "PUBACK": 1,
    "payload": {
        "callbackName": 18,
        "callbackArgs": [
            5,
            2,
            [
                [1, 100, [360, 100], 4000],
                [1, 100, [360, 100], 4000],
                [1, 100, [360, 100], 4000],
                [1, 100, [360, 100], 4000],
                [1, 100, [360, 100], 4000],
                [1, 100, [360, 100], 4000],
                [1, 100, [360, 100], 4000],
                [1, 100, [360, 100], 4000],
                [1, 100, [360, 100], 4000]
            ]
        ]
    }
}
```


---

# 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://api.intecular.com/invisoutlet-aura/fetch-accessory-status/color-light.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.