Hello, I went through a myriad of network changes and experiments not necessarily trying to fix this issue but hopping it would.
I reduced the amount of NATs that happen in my network by moving all the Routers into AP mode. Now everything is handled on OPNSense. I’ve exposed the ports on both OPNSense and my ISP router, I sadly cannot use it on bridge mode (I tried), maybe I’ll get a better ISP router soon.
Let me know if should forward more ports, so you can debug
I attempted to move to a dedicated Roon Server under Ubuntu 24LTS on my Proxmox server, but I was having issues with audio devices getting randomly stuck on Enabling.... or not shown at all. After reading the documentation I discovered that different ip ranges are not supported, and my server is hosted on 10.10.23.0/24 rather than 10.10.22.0/24 like my home network. Im guessing that was causing the issues with device discovery.
But well I sorta managed after random restarts of Roon Remote and reducing the network complexity of my main machine. I discovered that the Hyper-V virtual network switch can confuse Roon Remote in some situations and cause it to scan only in that IP range. Which was very odd.
I deleted my VPN software and Hyper-V.
I reinstalled Roon Remote locally, removed all the settings manually and from the AppData folders, and using the Roon Server on my Proxmox machine the issue was still present. As soon as I connect the Logitech Headset headset to the computer I get the same error I reported.
Aftermath
I scrapped all of that and returned to my original Roon Server host which was my Windows PC but I left the new network configuration. I have another Windows PC that now is able to communicate with my Roon Server.
- The new PC Runs Windows 11 Pro, its a fresh install so nothing cluttering it, less variables.
- The Roon server is running on the original Windows 11 PC where I first encountered the issue.
- Is notable that this issue appeared even when the Roon Server was hosted on the Linux VM, so its something happening at the Client side.
So I tried connecting the headphones, at first everything worked fine but after a restart of the PC the problems reappeared.
I also did some experiments with the Logitech software, I tried installing it, uninstalling it probing around to see if that was the ultimate cause of this problem, but I dont think so at this point.
All the logs are coming from the New PC
I saw the RAATserver logs. I think I found the errors mentioned before.
09/22 18:31:09 Trace: [RAAT::System Output] [lua@0000000026DB1138] [10.10.22.50:60706] GOT [6] {"request":"setup","format":{"sample_type":"pcm","sample_rate":44100,"bits_per_sample":16,"channels":2,"sample_subtype":"none"}}
09/22 18:31:09 Trace: [RAAT::System Output] [output/wasapi] output setup: format is pcm 44100/16/2
09/22 18:31:09 Warn: [RAAT::System Output] [lua@0000000026DB1138] [10.10.22.50:60706] setup failed: RAAT__OUTPUT_PLUGIN_STATUS_FORMAT_NOT_SUPPORTED
09/22 18:31:09 Trace: [RAAT::System Output] [lua@0000000026DB1138] [10.10.22.50:60706] SENT [6] {"status":"UnexpectedError","message":"RAAT__OUTPUT_PLUGIN_STATUS_FORMAT_NOT_SUPPORTED"}
09/22 18:31:09 Trace: [RAAT::System Output] [lua@0000000026DB1138] [10.10.22.50:60706] GOT [7] {"request":"setup","format":{"sample_type":"pcm","sample_rate":44100,"bits_per_sample":16,"channels":2,"sample_subtype":"none"}}
09/22 18:31:09 Trace: [RAAT::System Output] [output/wasapi] output setup: format is pcm 44100/16/2
09/22 18:31:09 Warn: [RAAT::System Output] [lua@0000000026DB1138] [10.10.22.50:60706] setup failed: RAAT__OUTPUT_PLUGIN_STATUS_FORMAT_NOT_SUPPORTED
I’m somewhat out of clues on what to provide in order to help the dev team diagnose and solve this issue. Its quite consistent with this Logitech model.
Fresh install of Windows 11, plug the device. Reboot the computer. And it should start happening.
I have the logs from the RAATServer of the PC, where I did all this new testing. Maybe that can help.
Let me know if I can facilitate the debugging.
