· Since about a fortnight ago, ROON has stopped recognising any of the audio devices that it had previously identified/recognized, including my Apple devices (Apple TV and HomePods and MiniPods), my SONOS systems, my Blusound Vault 2i and Onkyo TK850 receiver, etc. Other than the outputs on the CORE and the Apple MacMini that I am currently on, none of the other devices are seen.
Hi, Carl and Vadim,
Thanks, guys, for your quick and helpful responses.
Regretfully, the suggested actions don’t appear to have sorted out the problem. The NUC that I use as the ROCK is still unable to identify/select available audio devices. In fact, it recognises nothing, except its own audio outputs and my MacMini!
However, if I switch the Roon Server to my MacMini, we are back in business again!. The MacMini (as Roon Server) identifies all the available devices, which probably means there isn’t an issue with Roon.
So, the problem seems isolated to the NUC which was specifically installed to house my music library and act as the Roon Core.
Funnily, both the ROCK and MacMini Roon Servers were working fine till a few weeks ago. The only change I have made in the interim is to rename the NUC Roon Server! Could that be a reason for the “blackout”. If so, how do I go back to how things were. Would it mean going back to scratch and reinstalling the software in the NUC? While the MacMini as Roon Server’s working, because of the Wifi connection, there are occasional audio dropouts, which did not happen with the NUC, which was connected by Ethernet (locationwise, not possible for the MacMini, without extensive wiring).
Regards,
Pratik
Hi, Geoff,
Attaching 2 sets of screenshots - 1. With dedicated NUC as Roon Server 2. With MacMini as Roon Server. Both on same network, except that NUC is connected via Ethernet whereas MacMini is via Wifi.
It looks like you have two subnets on your home network:
ROCK NUC : 192.168.29.xx
Mac Mini and the networked endpoints 192.168.1.xx
You need to have all devices on the same 192.168.1.xx subnet.
A couple of things to explore…
Make sure the ROCK NUC is configured to use DHCP (and not static).
Reboot your network router, wait for it restart completely (say 3 mins), reboot the ROCK NUC, and then check what IP it is now using.
If that does not help, can you describe how you network is arranged eg what router(s) are you using, how are that connected and how the NUC, Mac, and endpoints are connected.
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
11
Post moderated to remove personal email address from view on this public forum.
Thanks very much, Carl. Followed your advice and shifted both ROCK NUC and networked endpoints to the same router 192.168.1.XX. Post- rebooting the ROCK and the router, things are back to “normal” with all previously identified audio devices back on line! Haven’t had a long music session but one (relatively minor, though irritating) issue cropped up - after running seamlessly for nearly an hour, the music stopped though both the ROCK and the endpoint in use at the time (Sonos Play 5s) are connected to the same router by Ethernet (the rest of the devices, barring Bluesound Vault 2i) are connected via WiFi. Hopefully, the stoppage in playback that occurred was a one-ff though it was preceded by an ominous alert - “Oops, something seems to be wrong. Searching for your ROCK” , which, fortunately, was “rediscovered” after a break of a couple of seconds without my having to do anything.
Glad to heear that there has been an improvement in the behavior. Please not that while the reboot may have gotten the devices on the correct IP for the time being, it is not a permenant solution, and the best way forward would be to “bridge” your two network, so that only one router is managing the IP address assignments. If you have an ISP router, you can often call the ISP and they can put their router into Bridge mode remotely.
To follow up on @noris’s post, you can find our networking best practices and general recommendations here:
In the broadest sense, Roon relies on two types of network traffic:
broadcast/multicast traffic, which carries device announcements for Roon to discover endpoints.
sustained TCP connections, which RAAT (Roon’s audio transport protocol) uses to carry the actual audio data.
Both announcement and playback require networked Zones to have a single, unchanging IP address. If an endpoint announces itself from one IP address but then receives another IP address later in the day, Roon cannot recognize it as the same endpoint.
Please let us know if we can clarify anything further.
> About page?
