Issue with Audio Devices Disappearing After Remote Wake from Sleep via WoL on Windows Headless [Ticket In]

Support
26

Hi @Matthew_Jobling,
Thanks for getting those timestamps to us. I noticed this trace in your logs at 09:10 when you logged into Windows.

09/22 09:10:04 Trace: [mobile] [remoteconnectivity] Port Verification started due to: load status changed, port verification not in progress, starting a new attempt
09/22 09:10:04 Trace: [raat] RAATServer discovered: RaatServer SPIKE1-DESKTOP3 @ 127.0.0.1:9200
09/22 09:10:04 Info: [raatserver] GOT SERVER 1e25c8c7-1703-400c-be2e-75bd0ef99110::0e20396c-cb34-4556-a3cd-855634d5f54f @ 127.0.0.1:9200 SPIKE1-DESKTOP3 PROTOVER=1 RAATVER=1.1.39 
09/22 09:10:04 Trace: [raatserver] [RaatServer SPIKE1-DESKTOP3 @ 127.0.0.1:9200] connecting (attempt 1)
09/22 09:10:04 Trace: [mobile] [remoteconnectivity] Port Verification started due to: load status changed, not testing port opening in router because the Roon Core is set to use a manually selected port that is in use by another program on the same machine
09/22 09:10:04 Trace: [raat] RAATServer discovered: RaatServer SM-N970W @ 192.168.11.138:9200
09/22 09:10:04 Info: [raatserver] GOT SERVER efbaf67d-c24b-a86a-e254-7784417fce2d::efbaf67dc24ba86ae2547784417fce2d @ 192.168.11.138:9200 SM-N970W PROTOVER=1 RAATVER=1.1.39 
09/22 09:10:04 Trace: [raatserver] [RaatServer SM-N970W @ 192.168.11.138:9200] connecting (attempt 1)
09/22 09:10:04 Trace: [raatserver] [RaatServer SPIKE1-DESKTOP3 @ 127.0.0.1:9200] connected
09/22 09:10:04 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
09/22 09:10:04 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"devices": [{"device_id": "default", "type": "wasapi", "name": "System Output", "is_system_output": true, "config": {"unique_id": "943b2cf5-77d6-8f7c-c10d-3fa90ad5a9b3", "external_config": {}, "volume": {"type": "wasapi", "device": "default"}, "output": {"name": "System Output", "type": "wasapi", "device": "default"}}}, {"device_id": "{0.0.0.00000000}.{686d3bf5-bcae-492d-b16d-6d39faf8dbc5}", "type": "wasapi", "discovery_data": {"tcp_port": 52985, "raat_version": "1.1.39", "unique_id": "cc1eaa25-d059-43da-a184-09bc928d7ac8", "version": "N/A", "protocol_version": "3", "model": "N/A", "vendor": "N/A"}, "usb_id": "21b4:0085", "name": "AudioQuest DragonFly Cobalt v1.0", "config": {"unique_id": "cc1eaa25-d059-43da-a184-09bc928d7ac8", "volume": {"type": "wasapi", "device": "{0.0.0.00000000}.{686d3bf5-bcae-492d-b16d-6d39faf8dbc5}"}, "output": {"exclusive_mode": true, "type": "wasapi", "device": "{0.0.0.00000000}.{686d3bf5-bcae-492d-b16d-6d39faf8dbc5}", "name": "AudioQuest DragonFly Cobalt v1.0", "event_driven_mode": true, "dsd_mode": "none"}, "external_config": {}}}, {"device_id": "{0.0.0.00000000}.{ee2d2b60-d7d3-4704-b775-5b97f998ae2b}", "type": "wasapi", "name": "Realtek(R) Audio", "config": {"unique_id": "2a6c42cd-0d0e-17ab-1897-fca36e396b80", "volume": {"exclusive_mode": true, "type": "wasapi", "device": "{0.0.0.00000000}.{ee2d2b60-d7d3-4704-b775-5b97f998ae2b}"}, "output": {"exclusive_mode": true, "type": "wasapi", "device": "{0.0.0.00000000}.{ee2d2b60-d7d3-4704-b775-5b97f998ae2b}", "name": "Realtek(R) Audio"}, "external_config": {}}}, {"device_id": "{A80362FF-CE76-4DD9-874A-704C57BF0D6A}", "type": "asio", "name": "Realtek ASIO", "config": {"unique_id": "860d09ef-2318-be16-9010-16edf1e329c3", "output": {"type": "asio", "name": "Realtek ASIO", "device": "{A80362FF-CE76-4DD9-874A-704C57BF0D6A}", "dsd_mode": "native"}, "external_config": {"is_private": false}}}], "status": "Success"}
09/22 09:10:04 Info: [raatserver] GOT DEVICE 0e20396c-cb34-4556-a3cd-855634d5f54f::default Type=wasapi Name=System Output

It looks like RAATServer wasn’t found or wasn’t active until you signed in. This is consistent with no audio devices being found. Then when you signed in two RAATServer possibilities were seen, and Roon connected to the RAATServer on your PC and began seeing audio devices.

I know earlier we asked you to whitelist RoonServer can you make sure RAATServer is also on that list?

27

Thanks Daniel. RAATServer is listed 4 times!:
C:\users<username obfuscated>\appdata\local\roonserver\application\raatserver.exe
C:\users<username obfuscated>\appdata\local\roonserver\application\raatserver.exe
C:\users<username obfuscated>\appdata\local\roon\application\raatserver.exe
C:\users<username obfuscated>\appdata\local\roon\application\raatserver.exe
-of the above 4 entries, they are in 2 identical pairs. Which is the correct one?

roon.exe is listed twice, identically:
C:\users<username obfuscated>\appdata\local\roon\application\roon.exe
C:\users<username obfuscated>\appdata\local\roon\application\roon.exe

roonappliance.exe is listed twice, identically:
C:\users<username obfuscated>\appdata\local\roonserver\application\roonappliance.exe
C:\users<username obfuscated>\appdata\local\roonserver\application\roonappliance.exe

RoonServer is listed once:
C:\Users<username obfuscated>\AppData\Local\RoonServer\Application\RoonServer.exe

RoonBridge.exe is not listed (although it is mentioned in the article you shared)

Should I remove the duplicates? Can I confirm that the only tick I need is in the box for “Private” network type (I don’t use Roon ARC)?

Thanks

28

Hey @Matthew_Jobling,

Yes, you can remove all of them and manually point to the proper files - check both boxes for Private and Public and see if you experience the same issues. You can use these instructions to add the exceptions and the executables themselves would be located in your Database Location/Application folder path.

Let me know if that helps! :+1:

29

Hiya @benjamin ,

I appreciate you are trying to help me and that you sent the link to the page explaining the process to locate the database

As per the file paths I shared, you can see I have 2 database locations - a “roon” folder and a “roonserver” folder. I’ve removed all the duplicates I mentioned above but have left one entry for each raatserver.exe instance. I’ve enabled both public and private network types for all

So far the issue hasn’t reoccurred so perhaps this has fixed it! I’ll monitor for a couple of weeks before I firmly decide that :slight_smile:

Please can you explain why I need the Public network type to be selected as well as the Private type? This Roon server is a Windows desktop PC and is locationally static - never moved off the home network. It is always physically connected to the same home network connection using the same NIC interface and IP address, which is always identified/set as a “Private” network within windows. The Squeezeboxes are IP addressed in the same subnet. I don’t use Roon ARC. Thanks

30

Hi @Matthew_Jobling,

That’s great we’re glad Roon is working for you again.

I think @benjamin was just trying to be thorough. From your description of your network only private would be needed. You can try unchecking Public if you want but there shouldn’t be any downsides to leaving it as it is now since it works and the computer is only ever on your home network.

31

I see. Got it. Thanks Both

1 Like
32

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.

33

What’s happening?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

Please re-open "Issue with Audio Devices Disappearing After Remote Wake from Sleep via WoL (ref#DTE75G)" as the issue remains even with all of the exceptions for the various Roon .exe files added as allowed/exceptions in Windows firewall. Thank you

Describe your network setup

Roon Server running on new Windows 11 Pro PC. Wired, flat network of squeezeboxes as audio devices and an Android wireless device to control it all. All devices are in same subnet. Additionally, on the server there is a DragonFly DAC

35

Hi team. Just a gentle reminder on this one as it is still an intermittent issue - when remotely woken, sometimes no audio devices are found (including the DragonFly DAC that is directly connected to the server via USB), other times all the audio devices are found. Do you have any advice or ideas for next steps to try to fix? Thanks

37

Hi @Matthew_Jobling ,

Thanks for the reminder on this. We’ve submitted a task for our QA team to try to reproduce this behavior, we’ll let you know when we hear back from them, or if you don’t hear anything please remind us in ~2 weeks and we’ll follow up directly with QA. Thanks!

38

Thanks @noris

1 Like
39

Hi @noris and team. I expect you are already aware of this but if I search the Roon Labs community for the terms “wake server” I am able to see several other people describing issues that look to be the same. Thanks

1 Like
40

Hi @Matthew_Jobling ,

Thanks for the info, yes I am aware there are a few related reports, I’ve included them in my request with QA. We’ll follow up when we have more info or free free to send a message Nov 8th onward and I’ll ask QA for a status update.

1 Like
41

Hi @noris and team. Any update? My family are frustrated because only I am able to play music at the moment (any of us can remotely wake the Roon Core/server via WoL, but whilst we have this issue, only I can actually play any music when I unlock the Windows desktop with my password or facial recognition for the audio devices to be found). As always, many thanks

43

Hi @Matthew_Jobling,

Thank you for your patience - we understand this is taking longer than expected, but we should have more detailed next steps and a more conclusive response shortly.

44

Hi @Matthew_Jobling,

Thank you for your ongoing patience. We’re close to identifying this long-standing failure point. Please reproduce one more time at your convenience and note the timestamp here. We’ll respond promptly with more detailed next steps.

45

Hi @Matthew_Jobling,

Following up here after further internal investigation.

In the long-term, a fix will require developer work that will be released via Early Access into a future Roon public build. We don’t have a timeline for when our investigation will mature into a developer ticket; as of now, we’re at the stage of reproducing internally to isolate the cause.

That said, development recognizes this as a long-standing issue and considers it a Roon bug. We’ll eventually release an improvement for this problem.

In the meantime, restarting either RoonServer or Windows itself remains the workaround. WoL will intermittently continue to reproduce the issue.

Thank you again for your patience.

47

Hi @connor
Thanks. Sorry for the delay - I have been away. I’m pleased to be involved (of course in a miniscule way) in improving the product and hope to be notified of the fix once it gets incorporated into an update

49

Hi @Matthew_Jobling,

The team is working to reproduce the issue - we’ll reach out with any questions, but the ticket should progress through the pipeline without any user assistance. Thank you for your help so far.