> 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/reference/compliance-and-disposal.md).

# Compliance and disposal

Review Hera 604 compliance information and disposal requirements.

## Compliance and disposal

The Hera 604 complies with these European requirements:

* RoHS Directive 2015/863/EU
* WEEE Directive 2012/19/EU
* Ecodesign Directive 2009/125/EC
* Batteries Directive 2013/56/EU
* Radio Equipment Directive 2014/53/EU
* Low Voltage Directive 2014/35/EU
* EMC Directive 2014/30/EU

The router carries the CE mark. The CE mark was affixed in 2024. It also carries FCC and ISED declarations.

Maintain at least 20 cm between the router antennas and people during operation. Use only approved antennas within their stated gain limits.

The router contains lithium coin cell batteries. Only manufacturer-authorised personnel may replace them.

At end of life, separate the router and accessories from other waste. Send them to your national WEEE collection system for recycling under EU Directive 2012/19/EC.


---

# 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/reference/compliance-and-disposal.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.
