> For the complete documentation index, see [llms.txt](https://doc.engenius.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.engenius.ai/home-cloud-user-manual/appendix/access-point-led-behavior.md).

# Access Point LED Behavior

## Access Point LEDs and what they mean

The table below describes the LEDs on the access point, their flashing patterns, and what those mean for its function.

| LED   | Static                                   | Flash                                             | Off                   |
| ----- | ---------------------------------------- | ------------------------------------------------- | --------------------- |
| Power | Power is on                              | Cloud is connecting                               | Power is off          |
| LAN   | Connected to LAN                         | Data is transmitting between AP and the Internet. | No connections to LAN |
| 2.4G  | AP is not transmitting data, Radio is on | AP is transmitting data between AP and client     | Radio  is off         |
| 5G    | AP is not transmitting data, Radio is on | AP is transmitting data between AP and client     | Radio is off          |

{% hint style="info" %}
If four LEDs are flashing, it means that AP is performing a firmware upgrade.
{% 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 by asking a question.

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

```
GET https://doc.engenius.ai/home-cloud-user-manual/appendix/access-point-led-behavior.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.