> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/hera204/status-indicators.md).

# Status indicators

Use the front-panel indicators to check Hera 204 status.

Use the status indicators on the front panel to check the power, Wi-Fi, WAN, and cellular signal status of the Hera 204.

### Power indicator

| **State**                                     | **Description**                                                                 |
| --------------------------------------------- | ------------------------------------------------------------------------------- |
| Solid red                                     | The router is powered, but the software is not operating yet.                   |
| Solid green                                   | The router is powered and the software is operating normally.                   |
| Flashing green in sync with another indicator | There is an error on the interface represented by the other flashing indicator. |
| Flashing green independently after startup    | There is an internal error.                                                     |
| Off                                           | There is no mains power, or the router has failed.                              |

### Wi-Fi indicator

| **State**                                                 | **Description**                           |
| --------------------------------------------------------- | ----------------------------------------- |
| Solid green                                               | A Wi-Fi connection is available.          |
| Flashing green regularly in sync with the Power indicator | There is an error on the Wi-Fi interface. |
| Flashing green irregularly                                | Wi-Fi data is being transferred.          |
| Off                                                       | No Wi-Fi connection is available.         |

### WAN indicator

| **State**                                                 | **Description**                         |
| --------------------------------------------------------- | --------------------------------------- |
| Solid green                                               | A WAN connection is available.          |
| Flashing green regularly in sync with the Power indicator | There is an error on the WAN interface. |
| Flashing green irregularly                                | WAN data is being transferred.          |
| Off                                                       | No WAN connection is available.         |

### Signal indicator

| **State**                          | **Description**                 |
| ---------------------------------- | ------------------------------- |
| Brief red flash every five seconds | No cellular signal is detected. |
| Solid red                          | The cellular signal is weak.    |
| Solid orange                       | The cellular signal is medium.  |
| Solid green                        | The cellular signal is strong.  |
| Off                                | The cellular modem is off.      |

For the location of each indicator, see [Hera 204 panels and ports](/hera204/hera-204-panels-and-ports.md).


---

# 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://docs.eseye.com/hera204/status-indicators.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.