> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/intercom/configuration/configure-a-td52/td52-status-leds.md).

# TD52 Status LEDs

The [Verkada TD52 Video Intercom](https://www.verkada.com/intercom/td52/) uses 2 sets of LED status lights:

* 1 blue LED (located above the camera)—Indicates the current status of the unit. The camera continues to record, regardless of if its visibility in Verkada Command.
* 6 white LEDs (located above the call button)—Indicates the stage of the Intercom in the setup process.

<div align="left" data-with-frame="true"><img src="/files/YZyhNLmjWPZx0jf5Rk7P" alt="" width="266"></div>

***

## Status LEDs

The LED status light consists of the following states:

* Solid orange—Booting up
* Flashing orange—Updating firmware
* Flashing blue—Establishing network connection
* Solid blue—Fully healthy
* Flashing pink—Identify

**Example**: Fully online and healthy Intercom

<div align="left" data-with-frame="true"><img src="/files/WKeoSiAhK5KEuYeQ8Biw" alt=""></div>

### Setup progression for status LEDs

When you first turn on the Intercom, a white LED appears. The LEDs progress as the setup progresses (up to 5 additional LEDs light up). These status LEDs are essentially a progress bar to indicate how far along the Intercom is in first coming online.

<div align="left" data-with-frame="true"><img src="/files/B8cgwdxDmk1338vPPcu9" alt=""></div>

{% hint style="warning" %}
The status bar does not persist after the Intercom is fully configured. The status bar only appears again, after it is decommissioned, and then added back to Command.
{% 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://help.verkada.com/intercom/configuration/configure-a-td52/td52-status-leds.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.