---
title: "Somfy and KNX: map commands and statuses to group addresses"
description: "Control a Somfy shutter from the KNX bus with Link’nX: up/down button, stop, position and status feedback, with the proposed DPT for each group address."
canonical: https://wiki.can-nx.com/en/guides/link-somfy-knx/
language: en
product: Link’nX
audience:
  - administrateur
  - installateur
context: "Link’nX web: KNX gateway table of a declared Somfy box"
---

# Somfy and KNX: map commands and statuses to group addresses

Context: Link’nX web: KNX gateway table of a declared Somfy box

The Somfy gateway table in Link’nX maps the group addresses of your KNX project to the commands of the devices of a Somfy box (open, close, stop, position, orientation) and to their statuses (closure, deployment, movement, status). A KNX shutter push button can then control a Somfy shutter directly, without going through a scenario.

Intended for installers and administrators who have the KNX project. To prepare a command in a scenario, use the [Somfy actions](https://wiki.can-nx.com/en/guides/link-somfy-actions/) instead; to start a scenario on a status, use the [Somfy triggers](https://wiki.can-nx.com/en/guides/link-somfy-triggers/).

## Before you start

- The box is [declared and its discovered devices are saved](https://wiki.can-nx.com/en/guides/link-somfy-devices/).
- The group addresses and their DPTs are confirmed in the KNX project.

## Open the box’s gateway table

1. Check the Link’nX project and gateway. In **Devices → Smart Home → Somfy**, find the box.
2. On its row, click the two opposite arrows **Gateway mode configuration**, before the pencil.

The Somfy gateway uses a single table, without Actions and Feedback tabs: commands and statuses are configured row by row, by choosing **Commands** or **States** in **Command / state**. A help text at the top of the page recalls how the “KNX button” commands work.

## Add and save the associations

1. Click **Add** below the table. Each row associates a **Device**, a **Command / state**, a **DPT**, a **KNX group address** and an **Active** box.
2. In **Device**, choose the target. For a confirmed URL missing from the list, choose **✎ Enter the URL manually…**, then enter the sub-device URL in the field displayed.
3. In **Command / state**, choose the function in the **Commands** or **States** group. The functions offered depend on the device’s known capabilities.
4. Check the proposed **DPT**. This field can be edited: keep or adapt the type according to the installation’s contract. Changing the DPT does not change the Somfy function.
5. Enter the confirmed **KNX group address**, for example `1/2/3` in a fictitious project, then tick **Active** to use the association. The four fields are required on every row, including a row left inactive.
6. Add the other associations, then click the round floppy disk at the bottom right to save everything. Wait for **Updated!** with the success notification.

Save before leaving this table, without relying on a confirmation prompt for unsaved changes.

## Choose the functions and their DPT

| Functions offered depending on the device | Group | Proposed DPT |
| --- | --- | --- |
| **Open**, **Close**, **Stop**, **My position** | Commands | **1.001** |
| **Up / down (KNX button)** | Commands | **1.008** |
| **Stop (KNX step/stop button)** | Commands | **1.007** |
| **Set closure (0-100)**, **Set deployment (0-100)**, **Set orientation (0-100)** | Commands | **5.001** |
| **Closure**, **Deployment**, **Target closure**, **Slat orientation** | States | **5.001** |
| **Open / closed** | States | **1.009** |
| **Moving** | States | **1.001** |
| **Status** | States | **1.002** |

**Open**, **Close**, **Stop** and **My position** are pulses: they react to the value 1, and a value 0 triggers nothing.

For a standard KNX shutter push button, use the two “KNX button” commands. They only accept a 1-bit telegram (DPT 1.x) and react to 0 as well as 1: **Up / down (KNX button)** opens on 0 and closes on 1, **Stop (KNX step/stop button)** stops in both cases. Give them a dedicated address. For a device with known capabilities, they are offered only if it publishes the matching commands: open and close for the first one, stop for the second. They do not exist in scenario actions.

Position commands use percentages from 0 to 100, including for orientation; these are not degrees. A position setpoint of 0 remains a setpoint, not the **Stop** command.

Choosing a status configures its KNX association; this table does not show its current value. **Target closure** and **Closure** are distinct functions. An old saved list does not confirm that the statuses received are up to date. For the interpretation of binary statuses on your display, have the association confirmed by the installer or support before basing an automation on it.

## Edit, deactivate or remove an association

Edit the row directly, then save with the floppy disk. Changing the device can clear an incompatible function: choose **Command / state** again and check the proposed DPT after this choice.

- To deactivate a row while keeping its parameters, untick **Active**, then save. Deactivating it does not stop a movement in progress.
- To remove a row, first check where it is used. Click its trash can on the right, with the **Delete** tooltip, then save everything. The trash can immediately removes the row from the form, without confirmation. After saving, no button restores the row.

## Check the result

1. Go back to the Somfy list, reopen the gateway and review the device, function, DPT, address and **Active** of each row.
2. With the installer, send each command from the bus, for example with the push button or the ETS group monitor, and watch the device. For a status, check the value received on its address, for example with a read request.

Saving confirms the configuration of the associations; only this test confirms the shutter movement and reception on the KNX bus.

## Troubleshooting

- The shutter reacts to only one direction of the KNX button: a standard shutter button sends up (0) and down (1) on the same address, whereas **Open** and **Close** only react to the value 1. Map this address to **Up / down (KNX button)**.
- Only manual entry is offered: go back to the box’s declaration, refresh the discovery, save it, then reopen the gateway. If the exact URL is already confirmed, manual entry remains possible; never derive a URL from the shutter’s name.
- The command you want is missing: check the device and the capabilities of its saved list. In manual entry or without known capabilities, a broader catalog appears, without any guarantee that all its functions are supported. If the function suited to the model remains uncertain, ask support for it.
- **Issue with field 'Name'.** appears when saving: most often, a row is incomplete. Check **Device** or its URL, **Command / state**, **DPT** and **KNX group address** on all rows, and delete a row added by mistake. Do not enter an address or a DPT at random just to be able to save.
- The command or the feedback still does not work: reopen the gateway and review the box, the sub-device, the function, the DPT, the address, **Active** and the save. Then check the communication and the KNX object with the installer.

## Contact support

If these tests have already failed, write to support@can-nx.com with the context, the function, the address, the DPT, the symptom and the checks carried out, without the token or confidential data.

French labels: **Configuration de la partie passerelle**, **Équipement**, **Commande / état**, **Commandes**, **États**, **Adresse de groupe KNX**, **Actif**, **Montée / descente (bouton KNX)**, **Arrêter (bouton KNX pas/stop)**.