---
title: BluOS player KNX integration with Link’nX
description: "Control BluOS players from KNX with Link’nX: playback, volume, presets, inputs, grouping and status feedback, with DPTs and step-by-step setup guides."
canonical: https://wiki.can-nx.com/en/integrations/bluos/
language: en
---

# BluOS player KNX integration with Link’nX

With Link’nX, a BluOS player can be controlled from the KNX bus and from the installation’s scenarios: play, pause, tracks, volume, mute, presets, repeat and shuffle. Scenario actions add input selection and player grouping. Playback status, volume, the current track or the current preset can also be mapped to KNX group addresses.

## What the BluOS integration does

| Need | Where to configure it | Guide |
| --- | --- | --- |
| Declare a player | **Devices → Audio & Media → BluOS** | [Declare BluOS players](https://wiki.can-nx.com/en/guides/link-audio-devices/) |
| Control playback, volume and presets from a KNX button | **Actions** tab of the player’s gateway configuration | [Link BluOS to KNX](https://wiki.can-nx.com/en/guides/link-audio-knx/) |
| Read playback status, volume or the current track | **Feedback** tab of the gateway configuration | [Link BluOS to KNX](https://wiki.can-nx.com/en/guides/link-audio-knx/) |
| Run a command in a scenario, on one or several players | **Bluos** action | [Prepare a BluOS command](https://wiki.can-nx.com/en/guides/link-bluos-actions/) |
| Select an input, group or ungroup players | **Select input**, **Group (add slave)** and **Ungroup (remove slave)** commands | [Prepare a BluOS command](https://wiki.can-nx.com/en/guides/link-bluos-actions/) |

## Step-by-step commissioning

1. [Declare the player](https://wiki.can-nx.com/en/guides/link-audio-devices/) with a name, its IPv4 address and its port, suggested as 11000.
2. [Map its commands and feedback to KNX group addresses](https://wiki.can-nx.com/en/guides/link-audio-knx/), with the DPT of each row. Save each tab before switching to another.
3. [Prepare the BluOS actions](https://wiki.can-nx.com/en/guides/link-bluos-actions/) for scenarios, especially inputs and groups.
4. [Add the actions to a scenario](https://wiki.can-nx.com/en/guides/link-compose-scenario/), then test each command on the player.

## Good to know

- Pulse commands in DPT 1.001, such as **Play**, **Next** or **Volume up**, act on an active value: the value 0 does not request the opposite operation. **Volume up** and **Volume down** change the volume by a 2 dB step.
- Volume is set in DPT 5.001, from 0 to 100%. **Set play/pause** uses 1 for play and 0 for pause. Repeat uses DPT 5.010: 0 for the queue, 1 for the track, 2 to disable.
- **Select input** expects a text input type confirmed for the player; the help gives “spdif-2” as an example. Inputs and groups are not in the KNX table.
- To group, select the primary player in the action, then fill in the IP and port of the secondary player.
- The port depends on the player: the help lists 11000, 11010, 11020 and 11030 for the different nodes of a NAD CI580.

For Sonos, Denon/HEOS and TVs, see [Audio and multimedia](https://wiki.can-nx.com/en/usages/audio-multimedia/).

## All BluOS 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/)
- [Create a BluOS action in Link’nX: playback, volume, input and grouping](https://wiki.can-nx.com/en/guides/link-bluos-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/)