> For the complete documentation index, see [llms.txt](https://documentation.nomos-system.com/nomos-system/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.nomos-system.com/nomos-system/integrator-en/skills/eltako.md).

# Eltako

This integration connects an **Eltako Series 64 gateway** to the nomos system Controller. Everything attached to the gateway – relays, dimmers, blind actuators, thermostats as well as paired EnOcean sensors and push-buttons – can then be used in the Controller like any other device: in rooms, scenes and automations.

{% hint style="warning" %}
**Before you begin:** the installation has to be fully set up in the **Eltako Connect app**. The Controller takes over what the gateway knows – it does not pair any devices itself.

* EnOcean sensors and push-buttons are paired with the gateway through the **EOA64** add-on adapter.
  {% endhint %}

**Setting up the connection:**

1. **Enable the integration:**
   * Switch on the **Eltako** skill. The skill page then shows the list of connected gateways.
2. **Search for a gateway:**

   * Click **Add Gateway**. The Controller searches the network for gateways and lists them with **serial number** and **product type**.
   * Gateways that are already configured are marked as such and cannot be added twice.
   * If nothing is found, check that the gateway and the Controller are on the **same network**. Alternatively, enter the **serial number** and the **host address** by hand.

   <figure><img src="/files/dxuTnnbgLtvdxrbwdm3P" alt=""><figcaption></figcaption></figure>
3. **Enter the device code:**
   * Enter the **device code**. This is the code **printed on the gateway's housing** – not the password of your Eltako Connect app.
   * Confirm with **Authorize**. The Controller signs in to the gateway and stores the access.
4. **Connected:**

   * Once signed in, the gateway appears on the skill page with its **product type**, **software version** and the status **Connected**.
   * Then take over the devices – either all at once with the **Initial Setup** or one by one with **Add Device**. Both are described under [Adding Eltako devices](/nomos-system/integrator-en/skills/eltako/add-eltako-devices.md).

   <figure><img src="/files/YVJTukIZYdBk7sX70r7a" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
**A gateway hands out ten keys – and never frees a single one.**

Every connection creates a new access key inside the gateway. The gateway keeps ten of them and cannot delete any. So do not reconnect a gateway just to try things out, only when it is necessary. Once they are used up, the only way out is a factory reset of the gateway through the Eltako Connect app.
{% endhint %}

{% hint style="info" %}
**Notes on operation:**

* **Change of address:** if the gateway's IP address changes (e.g. through DHCP after a power cut), the Controller finds it on the network again by itself. The access key stays valid, no reconnection needed.
* **The stored code was rejected:** this message appears when the gateway no longer accepts the access – after a factory reset, for instance. Enter the device code again to restore the connection.
* **One connection at a time:** a Series 64 gateway only ever serves one connection. While the Controller is querying it, heavy parallel use of the Eltako Connect app can cost the occasional command. The Controller repeats them automatically, but it shows as a short delay.
  {% endhint %}

**Removing a gateway:**

Use **Edit → Delete** to remove a gateway. The Controller asks whether the **devices of this gateway** should be deleted as well:

* **Yes:** the components are removed from rooms, scenes and automations.
* **No:** the components remain, but are shown as unreachable – they cannot be controlled until the gateway is connected again.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.nomos-system.com/nomos-system/integrator-en/skills/eltako.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.