> 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/reference/warranty.md).

# Warranty

* Use only Eseye-approved mains power adaptors. Using the Hera 204 with any other mains power adaptor will invalidate the warranty.
* Do NOT open the casing under any circumstances, as it will invalidate the warranty. There are no user-serviceable components inside the Hera. If a fault develops with the product, please contact your service provider or reseller.
* Take all reasonable precautions when installing the Hera device. Read and understand all warnings and installation instructions. Eseye Design Ltd are not liable for consequential loss or damage that occurs should the warnings and installation instructions not be followed.
* Do not attempt to insert or remove a SIM card when the Hera 204 is powered on. This will cause problems with the Hera 204 functionality. Always power off before inserting or removing a SIM card.


---

# 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/reference/warranty.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.