---
title: Denon/HEOS and KNX integration with Link’nX
description: "Control Denon/HEOS players from KNX with Link’nX: volume, mute, playback, tracks and status feedback, with declaration and step-by-step setup guides."
canonical: https://wiki.can-nx.com/en/integrations/denon/
language: en
---

# Denon/HEOS and KNX integration with Link’nX

With Link’nX, a Denon/HEOS player can be controlled from the KNX bus and from scenarios: absolute or stepped volume, mute, play, pause, stop, next or previous track. Its volume, mute state, playback status and information about the current media can also be associated with KNX group addresses. This page sums up what the integration does and the commissioning order.

## What the Denon/HEOS integration does

| Need | Where to configure it | Guide |
| --- | --- | --- |
| Declare a HEOS player exposed by a Denon controller | **Devices → Audio & Media → Denon** | [Declare BluOS or Denon/HEOS players](https://wiki.can-nx.com/en/guides/link-audio-devices/) |
| Set volume, mute or playback from a KNX button | Player’s gateway table, **Actions** tab | [Link commands and feedback to KNX](https://wiki.can-nx.com/en/guides/link-audio-knx/) |
| Read volume, mute, playback status or current media back on the bus | Gateway table, **Feedback** tab | [Link commands and feedback to KNX](https://wiki.can-nx.com/en/guides/link-audio-knx/) |
| Run a command in a scenario, on one or several players | **Denon** actions | [Prepare a Denon/HEOS command](https://wiki.can-nx.com/en/guides/link-denon-actions/) |

## Step-by-step commissioning

1. [Declare the player](https://wiki.can-nx.com/en/guides/link-audio-devices/): name, IPv4 address and port of the Denon controller (**1255** suggested), then **Player ID**, chosen from the suggestions or provided for this controller.
2. [Associate its commands and feedback with KNX group addresses](https://wiki.can-nx.com/en/guides/link-audio-knx/), saving each tab before switching to another.
3. [Prepare the Denon actions](https://wiki.can-nx.com/en/guides/link-denon-actions/), then [add them to the scenario concerned](https://wiki.can-nx.com/en/guides/link-compose-scenario/).
4. Choose a suitable sound level, test each command on the player, then check the corresponding feedback.

## Good to know

- **Set volume** expects a level from 0 to 100; **Volume up** and **Volume down**, a step from 1 to 10. In the KNX table, these three commands use DPT 5.001, and a step of zero requests no change.
- The KNX table combines play and pause in **Set play/pause** (1 play, 0 pause) and mute in **Set mute** (1 mutes, 0 restores the sound), in DPT 1.001. The separate commands exist in the Denon action. **Toggle mute**, **Stop**, **Next** and **Previous** are pulses: the release to 0 does not request the opposite operation.
- Feedback consists of **Current volume** (DPT 5.001), **Mute state** (DPT 1.001), **Playback status** (DPT 5.010) and **Now playing** (DPT 16.001). Have the Playback status values confirmed by support before building logic on them.
- An IP address or Player ID already used by another Denon declaration is refused. For several players on the same controller, have the procedure confirmed by support.
- Players selected together in an action receive the same command without forming a synchronized audio group.

BluOS players follow the same declaration and gateway guides: see [BluOS](https://wiki.can-nx.com/en/integrations/bluos/). For other audio players and TVs, see [Audio and multimedia](https://wiki.can-nx.com/en/usages/audio-multimedia/).

## All Denon / HEOS guides

### Devices and integrations

- [Add a BluOS or Denon/HEOS player in Link’nX: IP address, port and ID](https://wiki.can-nx.com/en/guides/link-audio-devices/)
- [Denon HEOS in Link’nX: create a volume, playback or mute action](https://wiki.can-nx.com/en/guides/link-denon-actions/)

### Protocols, imports and monitoring

- [BluOS, Denon/HEOS and KNX: map commands and status feedback](https://wiki.can-nx.com/en/guides/link-audio-knx/)