Fresh install of Windows 11 pro (up to date) NUC 10i7FNK, RAM: 32 GB Ram, Samsung EVO Plus NVMe
Networking Gear & Setup Details
Router ASUS RT-AC68U
Core and endpoints wired over LAN with static IPs.
Connected Audio Devices
Bluesound Node 130, Bluesound Flex (gen 1)
Number of Tracks in Library
Description of Issue
I had this problem 2 weeks ago with no audio devices showing up after my core resumes from sleep when waking from LAN. Now it’s back.
I thought it was related to a Geekom computer I had recently purchased as my core. I then got a NUC 10i7FNK instead but I have the same problem now: The Roon remotes on both android, iPad and Windows shows a completely blank audio screen. The audio devices appear instantly if I hit any key on the keyboard connected to the core. The screen connected to the core does not come on when waking from LAN (I have tried the various HDMI CEC settings in the bios).
What I have tried since last time is a factory reset of my ASUS RT-AC68U. Then only setting up manual IP addresses for the core and the endpoints and a port forward rule for ARC. DNS is Cloudflare.
I have left all other settings on default. Then I tried resuming from sleep over LAN with only the core and the Bluesound Node wired to the router. It was the same problem with no audio devices showing. I have a feeling this is not a network problem but somehow relates to power/standby settings on the NUC.
I can access and play from ARC over the LAN while the Roon remotes still shows no audio devices. It happens whether I wake the computer over LAN or WAN and whether it is Roon remote, ARC or a third party WOL app that wakes the core.
Could this be related to modern standby vs legacy S3? Which sleep mode is recommended for Roon?
Thanks for getting back to me. This have been driving me crazy I have been reinstalling Windows several times in both Modern Standby mode and Legacy S3 mode (NUC bios setting).
Right now I’m in Legacy S3 mode. If I connect via Teamviewer to the core computer after waking from LAN the endpoints return in Roon along with the signal to the screen.
Turning the screen on or off does not affect the behavior.
After reading about modern standby it seems that wake on LAN is not supposed to wake the display so this seems like expected behavior. But it also happens in Legacy S3 mode.
I tried waking from LAN without the HDMI cable plugged into the NUC. It still starts Roon without any audio endpoints.
One more thing that happens when waking from LAN. The NUC returns to sleep after about 2 minutes if I haven’t pressed any key on the attached keyboard (or connected via Teamviewer). The core will also return to sleep while playing from ARC if its woken from LAN. This is with Windows set to never go to sleep in power settings.