Hi, firstly Im a photographer, not an IT expert and I have had Roon for nearly 3 years and love it.
I moved into an old house with thick walls 2 years ago and so I bought some Google nests ( network 2)to help with my work and they really help alot
I have ROCK on a server connected to the router ( network 1 )
I have various Sonos and a Wiim Ultra
Ive been having a lot of troubles recently with firmware upgrades where i upgrade and then i get into a loop where Roon doesnt work and so I restart and it defaults back to the older version and so on and so forth, many support calls and all a great help.
My question is one that I really am not sure is stupid or valid
I play Roon via the app using Network 2 ( the Google nests) as its much quicker.
When I do firmware upgardes from my phone should I be connected to the same network as the Rock server is connected to , i.e Network 1 and should all the Sonos’s and Wiim Ultra also be connected to Network 1
I’m wondering if when I update my firmware and my phone is on Network 2 that it may be causing the issues I am seeing
The next time you have issues, check the IP assigned to the Rock and the other Roon devices and see if they are on different subnets.
Rock/Roon and your remotes/endpoints all need to be on the same subnet IP (first three sets of numbers in the IP address, ex. 192.168.1.xxx). If your two networks have different subnets then it may be that your devices are switching subnets after the updates? Which you then have to change or “fix” (might be a random connection that your devices are doing?). Not knowing exactly how your network is configured it’s hard to tell what exactly is going on.
My recommendation is to either remove one of the networks and have all devices on one network\IP subnet. Or move all the devices that will use roon onto the same network and assign them IP reservations from that network in the router for that network so they are not being assigned a random IP by the DHCP servers.
I am not an expert on this and so have added screenshots below of what my server is on and my end points
They look the same apart from the last digits
So this morning Roon cut out again , I had to reboot my router and the server and it defaulted back to the old firmware. I get this every time there is an update, days of firefighting and constant defaults back to the old firmware
They are definitely on the same network. The last number being different is because your router assigns a different address to each endpoint. It is like a row of mailboxes in a street. Each house has a different number, so each mailbox has a different number as well.
I have no idea what causes your Roon defaulting to its original firmware. My Rock doesn’t do that.
The devices all look like they are on the same subnet so that “should” not be an issue.
Take a look in settings/about and make sure all the devices are on the same version and build of Roon. Can you post a screenshot of settings about and the webUI for ROCK?
An issue I see is that you appear to be on an old version of ROCK (version 1.0 build 259).
The latest ROCK is at least Version 2.1 (271) as far as I can tell from the software release section of the forum (I am on early access so a different version of ROCK) look here:
Also, Roon OS is version 2.49 build 1525
You may need to re-install ROCK to get to the latest version, I would also suggest making sure you are using UEFI in the BIOS in your NUC in order to get the latest features (tailscale and other features).
The above items “might” be what is causing some of the problems you are seeing.
Let us know if you need help/guidance with this.
Thank you for your time
Yes you are correct I am on an old version as per attachment
How do I upgrade it? I dont have a spare screen to plug the server into so have to do it remotely, I guess I can just press the reinstall right?
This is the current version of ROCk on my little NUC. I’ve bought the machine just over a month ago and I installed from fresh. With an USB stick with a ROCK image from here.
I’ve connected the NUC to my TV in the living room (HDMI) and used a spare USB keyboard during the installation. After setting it all up I’ve disconnected all the cables (apart from power, network and the external HD which holds my music). And since then I have only accessed the server through my web browser.
I take it that when you click the “click here to install” you are seeing on the about page is when you are getting the loop and issues? correct?
It would not hurt anything to try the “reinstall” option on the webui. It “might” fix your issue?
If your issue continues I woul ssubmit a support request from the support section and let the Roon techs review your logs.
On another note: when weird things like this start happening it may be best to start from scratch after the final option above is tried. You just need a TV or monitor and a keyboard for the install process.
And yes, it is not entirely necessary to update to 2.1, but if you are going to need to re-install anyway… there are more features than Tailscale that you will not get if you stay on an older revision.
When I go to about and click here to install it does install and reboot Roon
The problem then is that there are so many issues, music not playing, crashing when I click search, screen flashing etc . Its so bad that I have to reboot the server. Turn it off and turn it on and then when I do that it defaults back to the previous iteration of the firmware.
I have submitted a tech request ticket, I’m just waiting for them to update me
Connect to Network 1 for Administrative Tasks: When you need to update firmware or perform setup changes to your ROCK server or other audio devices, connect your phone or management device to Network 1. This ensures that all devices are on the same network and can communicate without hindrances.
Consolidate Your Audio Devices on One Network: Ideally, all your audio devices, including Sonos and Wiim Ultra, should be on the same network as your ROCK server. This can reduce the chances of issues with device visibility and control.
Check Network Settings: Make sure that your router does not have any settings that are isolating devices across the two networks more than necessary. Features like AP (Access Point) isolation or client separation can sometimes cause these issues.
