Some additional information about what I’m seeing here:
I have 6 remotes - 2 Macs, 2 iPads, an iPhone and an Android phone. All connect to the Roon server except the Android phone (Pixel 8).
My Roon Server is a Nucleus One.
When I first set up the Nucleus and downloaded and installed Roon software for remotes (a few days ago), I saw ‘Uh oh … can’t find server’ messages on a couple of other remotes, but that has stopped. Now, the only remote having issues is the Pixel.
With the Pixel phone:
If the Nucleus has been running for a while - not sure how long ‘a while’ is - the Roon app on the phone will not connect.
If I reboot the Nucleus and attempt to connect from the Pixel immediately after seeing that the server is up, it WILL connect.
If I leave the Remote app running on the Pixel, at some point, I’ll get the ‘Uh oh …’ message again as it has lost the connection with the Roon server.
With respect to disabling the firewall on the Nucleus - I did not do that because 5 of the 6 remotes we have are connecting just fine.
After reinstalling the Remote app, it did connect to the server when I provided the IP address for it, then hit SCAN. After verifying that I could play music using the Android remote, I closed the app and waited about 5 minutes. At this point, the app won’t connect to the server.
Can you please reproduce this behavior and let us know the exact local time + date when you are able to connect, vs when the connection breaks? We can enable diagnostics for your account and compare a before/after to see if there’s any clues in the logging.
Do you happen to have any other Android device? Do other Android devices present similar behavior? What operating system is the Android device using? Have you checked for the issue on multiple OS versions or just the one?
Yes, please do enable diagnostics for my account.
Once thats done I can run tests here.
I only have the one Android device.
I’ve attached a screenshot showing Android version and Build info.
I am new to Roon so have only seen the connection problems on Android 16.
I see you’re running version 1554 on the pixel - are you able to update to the latest Roon versionProduction 1576
If that doesn’t help, can you test out installing the APK version of Roon? You can download it directly here:
https://download.roonlabs.net/builds/RoonMobile.apk
Do you have any issues using Roon Arc on this device?
The diagnostic mode is enabled, but your NUC is currently not reaching our servers for some reason. Please reproduce the issue once more, note the exact timestamp when it occurs, and then follow the directions found here to collect the logs.
Once collected, please upload the logs to our File Uploader. After you’ve uploaded them, let us know so we can check our server for your files.
Over the last 2 days, I’ve noticed that the Android app will occasionally connect, but usually not. To be clear, this is distinct from the case where I open the app immediately after restarting the Nucleus One, in which case it reliably connects - the first time.
I installed and tested the APK version of the Roon app for Android.
the APK version exhibits essentially the same (not) connecting behavior as the Play Store version of the app.
I’ve switched back to the Play Store version of the app for now.
Nucleus One restart test
Run:
Thursday October 30, 11:26AM, Toronto time.
After rebooting the Nucleus One, the Android app connects.
Testing to see how much time passes between initial connection and when the connection starts to fail …
after 2 minutes, 5 minutes … connecting OK.
after 8, 27 minutes … slower connection (slow connection screen displayed), then connect with no intervention from me.
at 42 minutes from the initial (successful) connection, the Android app no longer connects to the Roon server.
But wait - I left the app running on the phone,
came back to it about 5-10 minutes later and it did eventually connect to the server.
Roon ARC
I have set up ARC and tested it on the Pixel. It seems to be working fine while in the house.
I have uploaded the zipped Log files using the Logs-Upload-Server. My name is in the file name.
We’ve activated diagnostics on another Roon remote associated with your account to see if it also experiences background disconnection events to the Nucleus One at those approximate timestamps.
We do see network reachability events occurring quite frequently on the other device in logs - the device stops receiving traffic from the Nucleus One, which then fails to send or respond to any device announcements over multicast.
The Bell Home Hub series handles multicast internally and these features aren’t configurable - we don’t often see problems with that particular modem/router combo unless you have so many devices that it saturates the network bandwidth.
You can try disabling the 2.4GHz band temporarily in the Bell Home Hub settings - I believe this setting is in the router admin page/app under “manage my WiFi".”
If you open Roon ARC alongside Roon on the Pixel on your home network, do you see ARC disconnect as well when the Roon app loses sight of the server?
Do you have any additional network gear in this setup - like switches, access points, etc - beyond the Home Hub?
Not sure if this is connected but I’m also experiencing problems connecting to Roon from my Pixel 6a. I’m on Android 16. Roon 2.56 (build 1577) on the phone and Roon 2.56 (build 1583) on a NUC.
I can only connect to Roon on my phone when in close proximity to the NUC server. I was given the info to allow multicast routing but it hasn’t fixed the problem.
Hello again:
Here are responses to your latest questions:
… try disabling the 2.4GHz band temporarily in the Bell Home Hub settings - I believe this setting is in the router admin page/app under “manage my WiFi".”
Unfortunately, we need to keep 2.4GHz running because we've got Hunter Douglas (powered blinds) devices that only operate in that band.
If you open Roon ARC alongside Roon on the Pixel on your home network, do you see ARC disconnect as well when the Roon app loses sight of the server ?
I did this test as before:
- restart the Nucleus One
- immediately launch the Roon app on the Pixel - it connects
- then, I launched ARC - its working too.
We're inside my place so the phone is talking to the local network on Wifi to the router, then to the N-1.
- I went away to fix a bike for about 40 minutes ...
- I then relaunched the Roon app and the ARC app
- ARC connects to the server and I can play anything from my local collection
- the Roon app does not connect.
Do you have any additional network gear in this setup - like switches, access points, etc - beyond the Home Hub?
Yes. The Hunter Douglas equipment has two parts.
- something they call the PowerView Hub, and
- the other thing they call a Repeater.
Thank you very much for the detailed follow-up and for running all those tests — this information is extremely useful.
From what you’ve described, we can confirm that:
The Roon ARC app maintains a stable connection (both locally and remotely)
The Android Roon app loses visibility of the Nucleus One after some time, while other remotes remain connected
The issue can be temporarily resolved by restarting the Nucleus One
This pattern suggests a multicast discovery issue specific to the Pixel’s connection rather than a general network or server failure.
The Bell Home Hub’s multicast handling is usually automatic, but certain IoT devices (like the Hunter Douglas PowerView Hub and Repeater) can sometimes introduce multicast interference on mixed 2.4 GHz/5 GHz setups.
Let’s try the following steps to narrow this down:
Static IP for Nucleus One
In your Bell Home Hub settings, assign a fixed IP to your Nucleus One (based on its MAC address).
This prevents any possible discovery issues when the IP lease changes.
Disable “Private DNS” on the Pixel 8
Go to Settings → Network & Internet → Private DNS, and set it to Off.
Some users have reported this resolves intermittent discovery problems.
Force Multicast Refresh
When the Pixel loses connection, try toggling Airplane Mode on/off or Wi-Fi off/on — if it reconnects immediately, that confirms a multicast discovery timeout issue.
Wi-Fi Band Lock
If possible, create a temporary 5 GHz-only SSID on your router and connect the Pixel to it.
Leave 2.4 GHz available for your IoT devices. This test will show if cross-band multicast bridging is the culprit.
If the connection becomes stable on 5 GHz only, we’ll know that the issue lies in the Home Hub’s band-steering or multicast bridging behavior.
Please try these steps and note the exact local time when you perform them — if the problem persists, we’ll review the logs again with those timestamps.
Thank you again for your patience and thorough testing!
I wanted to touch base with some good news, which is that our technical team has been able to reproduce this behavior and we’ve opened up a bug report with our developers.
While I can’t say for certain when this bug will be fixed, getting things reproduced in-house is a critical first step, and I will keep this thread up to date as the team passes along feedback and work begins to get this resolved. Thanks again for the report!
My overall satisfaction with the Pixel 8 has been lacking. Googles constant intrusions, ads and over-reach on user data policies didn’t sit right.
The device not working as expected with Roon was the last straw.
My solution: I’m now using an iPhone.
I’ll watch this space with curiosity, but I’m going to turn my attention to other things.
