---
title: "Sonos in Link’nX: troubleshooting and frequently asked questions"
description: "Sonos speaker missing, favorites not shown, KNX command with no effect or no status feedback: causes and the checks to run in Link’nX."
canonical: https://wiki.can-nx.com/en/guides/link-sonos-help/
language: en
product: Link’nX
audience:
  - administrateur
  - installateur
context: "Link’nX web: Sonos devices, scenario actions and KNX gateway table"
---

# Sonos in Link’nX: troubleshooting and frequently asked questions

Context: Link’nX web: Sonos devices, scenario actions and KNX gateway table

Speaker missing or refused, favorites not shown, KNX command with no effect, no status feedback: here are the answers to the most common Sonos problems in Link’nX, for installers and administrators. Always start by checking the project, the gateway and the device name shown.

## Where do I find my Sonos speaker?

Open **Sonos** in the device navigation: the list shows the [declared devices](https://wiki.can-nx.com/en/guides/link-sonos-device/). If it is empty, check the context before adding a declaration. If the Sonos entry is missing or unavailable, see the [mobile navigation and options](https://wiki.can-nx.com/en/guides/link-navigation/).

## Why is saving the device refused?

Check the format of the two fields:

- **Name**: required, 64 characters maximum;
- **IP address**: four numbers from 0 to 255 separated by dots, without port or protocol.

If correct values are still refused, note the message and contact support. Do not create several declarations to work around the refusal.

## Should a Sonos command be programmed in a scenario or in the KNX gateway?

- For a scenario: **Actions**, **Sonos** type, as described in the [Sonos actions guide](https://wiki.can-nx.com/en/guides/link-sonos-action/).
- For a KNX object to control the device directly or read a state: the two arrows **Gateway mode configuration** on the Sonos row, as described in the [KNX associations guide](https://wiki.can-nx.com/en/guides/link-sonos-gateway/).

## Why does my action show only one device?

The field shows the first name followed by **(+N others)**. Reopen **Sonos device** to see all the checked boxes. In a scenario’s details, the list of names is for viewing only: edit the action itself to change its recipients.

## Why are my Sonos favorites missing?

First select the device, then **Play favorite** and **Favorite to start**. Only the Radio and Spotify favorites offered are concerned; see the [favorites guide](https://wiki.can-nx.com/en/guides/link-sonos-favorites/). A list that stays empty does not mean the favorites were deleted: report it to support with the favorite type and the attempts made.

## Why is the sound no longer muted after a volume change?

This is the expected behavior: **Volume +/-** and **Set volume** in an action, like their gateway rows, unmute the sound before applying the level. If you then need to mute the sound, check the order of the scenario’s actions.

## Why does a KNX command at 0 do nothing?

The pulse commands of the [Sonos gateway table](https://wiki.can-nx.com/en/guides/link-sonos-gateway/) react to the value 1: 0 does not request the opposite action. Check that the KNX button sends 1 with DPT 1.001 on the right row, with **Active** checked. To set the volume to zero, use **Set volume** with its DPT 5.001.

## Why has a row disappeared from the gateway table?

Clear **Type to filter...** and uncheck **Show only active**: this filter hides deactivated rows. If the row is still missing, tell support which tab and function you are looking for.

## Why are my KNX addresses not kept?

**KNX addresses updated!** does not save the table yet: then click the floppy disk and wait for **Données sauvegardées avec succès !** (Data saved successfully!). Save before each tab change. To check, reopen the gateway from the list and read the values again.

## Why do I get no KNX status feedback?

Check the second tab, the address, the **Active** checkbox, then the DPT of the read object. Feedback answers a KNX read request: it is not sent spontaneously and continuously.

## What if the action is saved but the speaker plays nothing?

Check the selected devices and the command, then that the action was added to the right scenario and that this scenario was saved. If the command comes from the bus, check the association and its **Active** checkbox. For an audio URL, an uncertain favorites list or a group change that requires a specific coordinator, contact support without changing settings at random.

## Contact support

If the problem persists after these checks, write to support@can-nx.com with: Link’nX — Sonos, the project and gateway, the device concerned, the scenario action or KNX association involved, the symptom, the exact message and the checks already done. A screenshot without sensitive data can help. Never send a password, a private link or a secret.