> 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/get-started/log-in-to-the-hera-604.md).
# Log in to the Hera 604
Sign in to the Hera 604 web interface.
1. In a browser, enter the Hera web interface address. For example, `http://192.168.0.1`.
2. Your browser might show an untrusted certificate or private-connection warning. This is expected with Hera's local certificate. Continue to the address.
3. At the sign-in prompt, enter the username and password from your Configuration Information Sheet.
{% hint style="info" %}
You can change your username and password later.
{% endhint %}
Enter the credentials supplied with your router.
4. Select **OK**.
The Hera web interface opens.
The Hera interface appears after you sign in.
You can use the Hera web interface to configure the device. In most cases, the device applies a predefined setup after it first connects to the Eseye device management system.
---
# 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/get-started/log-in-to-the-hera-604.md?ask=&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.
