> 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/diagnostics-and-maintenance/device-recovery.md).

# Device Recovery

The following section describes available options for recovery of malfunctioning device. Should a device become unreachable due to power failure during firmware upgrade, or if its core files were wrongly modified in the file system, Eseye's routers offer several options for recovery.

## Reset button

Reset button is located on the back panel of the device. The reset button has two functions:

Reboot the device. After the device has powered up, the reset button can be pressed to reboot the device. Start of the reboot will be indicated by the Power LED turning solid red.

Reset to factory defaults. After the device has powered on, press the reset button for at least 5 seconds. The device will reset all user changes to factory defaults and reboot. Start of the factory reset will be indicated by the Power LED turning solid red.


---

# 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/diagnostics-and-maintenance/device-recovery.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.