> 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/access-control/troubleshooting/verkada-ac41-status-led.md).

# AC41 Status LED

Learn the status of the Verkada AC41 LED codes

The Verkada [AC41 4-Door Controller](https://docs.verkada.com/docs/door-controller-ac41-datasheet.pdf) has an LED (at the top left) that shows the status of the device at a glance.

***

## LED statuses

**Solid orange**—The controller is on and booting up.

<div align="left" data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-f22714abe090173d22a51304b9a7d7403ba727a3%2F4e6bde85229234628286aff6bcbb822025020dfe.jpg?alt=media" alt=""></div>

**Flashing orange**—The controller is updating its firmware.

<div data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-ae014fc3d76ca8db97ae2af441832053a3d54a83%2F671ee491ae8303e173771d0012daac6333ae04b6.gif?alt=media" alt=""></div>

**Flashing blue**—The controller is managing doors, but cannot reach the server. Learn more about the [required network settings](/access-control/getting-started/access-control-network-settings.md) to help get the controller online.

<div data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-49ebae279e670d98a215960809efadb22db3039e%2Fdc159f2160c530cbc7cbc0973b871fafd83382cd.gif?alt=media" alt=""></div>

**Solid blue**—Full connection to Verkada servers.

<div data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-e41c03ccb0986f2f280fef943c66409500ea96d7%2F13a78913cb6edc34e8a7aa6f106627e71c228d80.jpg?alt=media" alt=""></div>

**Flashing pink**—When you select **identify** under the controller settings, the controller flashes pink to help you identify the device.

<div data-with-frame="true"><img src="https://134288481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaaHs5RfKqv9Z49mi02cC%2Fuploads%2Fgit-blob-5bfd0a558ba37b88155392bde31b4d58f7ef105e%2Fc27d433fee6716094ebf0049756b684aa4e4d023.gif?alt=media" alt=""></div>


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/access-control/troubleshooting/verkada-ac41-status-led.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.