---
title: "Atmoce KNX integration with Link’nX: PV and battery"
description: "Connect an Atmoce gateway to KNX with Link’nX: remote control, power setpoints, battery dispatch and PV, battery and grid measurements with their DPTs."
canonical: https://wiki.can-nx.com/en/integrations/atmoce/
language: en
---

# Atmoce KNX integration with Link’nX: PV and battery

With Link’nX, the Atmoce gateway of a photovoltaic system with storage connects to the KNX bus. Group addresses control remote mode, power setpoints and battery dispatch. Others read the storage status, the state of charge, PV, battery and grid power, voltages, currents and energy meters. Atmoce scenario actions also prepare forced charging and discharging.

## What the Atmoce integration does

| Need | Where to configure it | Guide |
| --- | --- | --- |
| Declare the Atmoce gateway | **Devices → Climate & Energy → Atmoce** | [Declare Daikin, Gude or Atmoce](https://wiki.can-nx.com/en/guides/link-dga-devices/) |
| Switch to remote control or give control back to local mode | **Remote control mode** row of the gateway configuration | [Associate Atmoce commands and measurements with KNX](https://wiki.can-nx.com/en/guides/link-atmoce-knx/) |
| Set a power or a battery dispatch from KNX | Power setpoints and **Dispatch power (W, signed)** | [Associate Atmoce commands and measurements with KNX](https://wiki.can-nx.com/en/guides/link-atmoce-knx/) |
| Read power, state of charge, voltages and energies | Second tab of the gateway configuration | [Associate Atmoce commands and measurements with KNX](https://wiki.can-nx.com/en/guides/link-atmoce-knx/) |
| Prepare a forced charge or discharge | **Atmoce** action | [Prepare Atmoce commands](https://wiki.can-nx.com/en/guides/link-atmoce-actions/) |

## Step-by-step commissioning

1. [Declare the Atmoce gateway](https://wiki.can-nx.com/en/guides/link-dga-devices/): name, IPv4 address, port and **Slave ID** confirmed for the installation. The prefilled values 502 and 1 do not prove your gateway’s settings.
2. [Map the KNX commands](https://wiki.can-nx.com/en/guides/link-atmoce-knx/) in the **Actions** tab, then the feedback in the second tab. Save each tab.
3. For forced charging or discharging, [prepare the Atmoce command](https://wiki.can-nx.com/en/guides/link-atmoce-actions/). Its saving and execution path must be confirmed for your version with support.
4. After each command, check the **Operating mode** feedback and the measurements, without assuming an immediate result.

## Good to know

- Stopping dispatch or exiting forced mode does not give control back to local mode. Use **Remote control mode** set to OFF, in DPT 1.001. **Operating mode** is 1 in self-consumption, 2 in time-of-use (TOU) and 10 in remote control.
- **Dispatch power (W, signed)** uses DPT 14.056: a negative value charges, a positive value discharges, 0 stops dispatch.
- **Storage status** at 99 means neither charging nor discharging. The percentage is read in **Battery SoC**, in DPT 5.001.
- **System reset** restarts the entire plant: PV, battery and gateway. It requires Modbus protocol V1.2 or later and two activation telegrams within three seconds.
- Energies use DPT 13.013, in Wh, with cumulative meters and today’s meters.

For metering and consumption monitoring in the other applications, see [Energy and metering](https://wiki.can-nx.com/en/usages/energie/).

## All Atmoce guides

### Devices and integrations

- [Atmoce actions: force charge, dispatch and return to local mode](https://wiki.can-nx.com/en/guides/link-atmoce-actions/)

### Protocols, imports and monitoring

- [Atmoce and KNX: control the battery and read PV measurements](https://wiki.can-nx.com/en/guides/link-atmoce-knx/)