Skip to content

Diagnostics and Troubleshooting

João Miguel Tabosa Vaz Marques Silva edited this page Aug 27, 2026 · 2 revisions

Diagnostics and troubleshooting

Start on the Diagnostics page. It shows the connection label, selected speaker, speaker volume, speaker input format when available, selected computer output, output volume, mute state, and speaker-search result.

If the app says Disconnected

Work through these checks in order:

  1. Confirm that a Sonos speaker is selected under Devices.
  2. Confirm that the computer and speaker are on the same local network.
  3. Refresh the speaker list.
  4. Confirm that the selected computer output is still present and has software volume control.
  5. If following the system output, verify that the operating system has a usable default multimedia output.
  6. Temporarily test without a VPN or network-isolation rule that blocks local discovery or callbacks.
  7. Keep Keep checking if updates are missed enabled.
  8. Quit the app from its tray menu, start it again, and retest.

The runtime retries recoverable speaker, output, and network failures automatically.

On Ubuntu, a missing pactl command or unavailable PulseAudio-compatible service appears as unavailable local audio. Follow the Ubuntu troubleshooting steps before resetting Settings.

If the speaker is found but volume does not change

  • Use Test speaker volume on the Volume page.
  • Confirm that the selected Sonos device is the group coordinator for a grouped setup.
  • Confirm that the selected computer output is the device whose volume you are changing.
  • Check whether a hardware control changes a different mixer or endpoint than the operating system's selected output.

If Sonos changes do not update the computer

  • Confirm that Two-way synchronization is enabled.
  • Confirm that the local output allows software volume changes.
  • Keep fallback checking enabled in case Sonos event callbacks are blocked.
  • Remember that an explicit mute change also requires Synchronize mute.

If a Speaker control is gray

Gray means the selected device did not expose that capability or the app could not read it. Reconnect the speaker and use the refresh button on the Speaker page. If it remains gray, treat the feature as unavailable for that device.

Technical details

Expand Speaker technical details to refresh and display a sanitized diagnostic snapshot. The exact internal state can distinguish synchronization, fallback, unavailable-device, and error conditions.

Export diagnostics produces the sanitized diagnostic text. Review it before sharing. Do not paste raw logs, local paths, network addresses, device identifiers, host names, screenshots containing them, or other private details into a public issue.

Application logs are stored locally and are not uploaded automatically. They can contain technical identifiers needed for diagnosis. Use the default information level for normal operation; debug or trace logging should be limited to a short, controlled diagnostic session.

Reset settings

Use Reset settings only after recording the non-sensitive choices you want to restore. Resetting returns the app to defaults and clears the selected speaker and fixed audio output.

Request support

Search the existing issues before opening a new one. In a public report, include only:

  • The generally available app version.
  • Windows, macOS, or Ubuntu and its version.
  • The generic speaker model and audio-output class.
  • The expected behavior and a concise description of what happened.
  • Which troubleshooting steps passed or failed.

Keep raw diagnostic evidence private until a maintainer provides an approved way to share it.

Clone this wiki locally