> 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/hera604/diagnostics-and-maintenance/restart-and-reset/factory-reset.md).

# Factory reset

Restore the router to factory defaults.

Open **Diagnostics & Maintenance → Restart → Factory reset**, then select **Reset** to return the router to its factory configuration.

<figure><img src="https://333373795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBMckwRPzYNvOiZyh1fl3%2Fuploads%2FUL49hq0w4qGIKieWMwac%2FScreenshot%202026-08-14%20at%2017.00.03.png?alt=media&amp;token=a6c626b4-9b05-41db-949e-97627356ec58" alt="Restart page with the Factory reset button."><figcaption></figcaption></figure>

{% hint style="warning" %}
A factory reset removes the operational configuration. It can make the router unreachable at its previous address. Download a backup first. Use factory reset only when rebuilding the router or when Eseye Support instructs you to do so.
{% endhint %}

Before you reset the router, confirm that you have:

* An approved configuration backup.
* The initial access details and expected default LAN address.
* The settings needed to rebuild the router.
* On-site or direct local access.
* An approved outage window.


---

# 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/hera604/diagnostics-and-maintenance/restart-and-reset/factory-reset.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.
