> 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/file-management/software-upload.md).

# Software upload

Upload supported router software.

Open **Diagnostics & Maintenance → File Management → Software upload** to install an approved Hera 604 software package.

<figure><img src="https://333373795-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBMckwRPzYNvOiZyh1fl3%2Fuploads%2FbgFPf8bSJ7Kw6EEtfwZ9%2FScreenshot%202026-08-14%20at%2016.59.25.png?alt=media&amp;token=f183d7a7-8d7e-4ee0-8ba5-d6d103aae3ec" alt="File Management software upload page."><figcaption></figcaption></figure>

Use **Upload – keeping existing configuration** to install software without overwriting the router's current configuration.

To upload software:

1. Confirm the package is approved for the Hera 604 and its upgrade path.
2. Download a current configuration backup.
3. Connect the router to stable power.
4. Select **Upload – keeping existing configuration**.
5. Select **Choose file**, and select the software archive.
6. Select **OK** to begin the upload.
7. Do not close the browser or remove power during installation.
8. After the router restarts, confirm the software version and connectivity.


---

# 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/file-management/software-upload.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.