Hi! What’s not quite right with Roon?
· None of the above quite fits
None of the above quite fits
· App interface looks or behaves oddly
Tell us what's going on
· # Display button missing despite Chromecast and Web Display registering successfully — Roon 2.71 build 1683 / Windows 11 Server
I am unable to assign a Roon Display to an audio zone because the **Display button/icon is completely absent from the Volume popup**.
The problem occurs on both the **Windows Roon client and Android Roon Remote**.
# System
·
* Roon Server: Windows 11 PC
* Roon version: 2.71 build 1683 Production
* Windows Roon client connected locally to the same Server
* Android Roon Remote on the same LAN
* Chromecast/Google Cast device: onn. Full HD Streaming Device
* Also tested using Roon Web Display
* Audio zones tested include an existing WiiM Pro zone and a newly created local WASAPI zone
# Symptoms
·
The Chromecast is discovered and appears under **Settings → Displays**.
I also opened the Roon Web Display URL in Chrome. The Web Display registers successfully and appears under **Settings → Displays**.
Despite having both available displays, there is **no Display button/icon in the Volume popup** for any audio zone.
This is true in both:
* Roon for Windows
* Roon Remote for Android
I therefore have no way to associate a Display with an audio zone.
# Troubleshooting already performed
·
I have:
* Rebooted the Windows 11 machine running Roon Server.
* Restarted the Chromecast/onn. streaming device.
* Disabled and re-enabled audio zones.
* Created a completely new WASAPI audio zone and tested it.
* Tested from both Windows and Android Roon clients.
* Created and successfully registered a Web Display.
* Confirmed that both Chromecast and Web Display appear under Settings → Displays.
The Display button remains absent.
# Relevant RoonServer log findings
·
The Server appears to discover and register the Chromecast normally.
At 14:20:41:
`Info: [cast] discovered CastDevice[DeviceId=onn.-Full-HD-Streami-fa73d8cefc3097b9f7e8a140fcba1f55._googlecast._tcp.local, Name=onn. Full HD Streaming Device, Address=192.168.50.174]`
At 14:20:42:
`Info: [transport/zonedisplay] Zone display registered: CastDevice[DeviceId=onn.-Full-HD-Streami-fa73d8cefc3097b9f7e8a140fcba1f55._googlecast._tcp.local, Name=onn. Full HD Streaming Device, Address=192.168.50.174]`
The Android Remote subsequently connects normally at 14:21:13:
`Info: [remoting/serverconnectionv2] Client connected: 192.168.50.173:52294`
The local Windows client subsequently connects normally at 14:28:52:
`Info: [remoting/serverconnectionv2] Client connected: 127.0.0.1:57275`
I then opened a Web Display at 14:31:21. The Web Display connects and registers successfully:
`GOT com.roonlabs.registry:1/register {"extension_id":"com.roonlabs.display_zone"...}`
followed by:
`CONTINUE Registered`
and:
`Info: [transport/zonedisplay] Zone display registered: [Roon API Display Zone ...]`
The Web Display reports:
`{"displays":[{"display_key":"5eda8395-e396-4431-96a7-e855b3e8f076","auto_name":"Chrome on Windows 10","active_zone_id":null}]}`
At the same time, the Web Display successfully receives the Roon transport subscription containing both of my available audio zones, including the newly created WASAPI zone.
When the Web Display is closed, the Server also cleanly reports:
`Info: [transport/zonedisplay] Zone display unregistered`
# What appears unusual
·
From the Server log, the display subsystem seems functional:
Chromecast discovery → successful
Chromecast Zone Display registration → successful
Android Remote connection → successful
Windows client connection → successful
Web Display registration → successful
Audio-zone enumeration → successful
However, the Roon UI on both Windows and Android never presents the **Display control in the Volume popup**, so the display can never be assigned to a zone. The Web Display consequently remains at `active_zone_id:null`.
Roon's documentation indicates that when displays are available, the Displays button should appear in the Volume popup.
Could Roon Support please determine whether this is a **Server/Remote display-state or UI issue in build 1683**, or whether there is another condition that would cause the clients to suppress the Display button even though `transport/zonedisplay` has successfully registered available displays?
I can provide the complete RoonServer log covering the reproduction if needed.
Tell us about your home network
· I can provide the complete RoonServer log covering the reproduction if needed.
