Will do and advise. Did that previously for 30 seconds. Will wait longer
OK, that is a potential problem as the nodes will switch momentarily to the node with the strongest signal. When it switches the connection to the Nucleus is lost and then reconnection takes place. If this happens frequently you can lose access or get severely interrupted playback as Roon won’t have a stable connection.
You really need to connect directly to the router for a stable connection as I’m pretty sure that is the source of your playback problems. You can get a long ethernet cable and plug the Nucleus directly to the router prove the problem one way or another.
1 Like
I’m afraid I disagree, everything including your log files and physical connections point to a connectivity issue which is almost certainly a mesh issue. As in my last post, you can prove it with a long ethernet cable to provide a temporary direct connection.
1 Like
You are correct as network connectivity switching issues between nodes. I get that and concur.
However that does not explain either the inability to connect to the Nucleus + or why my Roon arc app can see the Nucleus+ and its playlists.
No success after powering down. And restarting.
It’s looking for the core but recognizes the core and its serial number
I am sorry but again, the physical connections explain exactly why you have intermittent connectivity and I have explained how you can prove it.
Domestic events are demanding my attention, good luck.
1 Like
Appreciate the help. Just checked with my Roon Arc app. It says it sees my Nucleus+.
Now Roin Arc says ‘ make sure your Roon Core is configured for remote access’. How does one do this?
You need to have a connected Roon Remote and then use Settings > Roon Arc to check the configuration.
Room Core, Roon App and Arc are routinely updated as updates are made available.
My issues today started with updating the Roon Remote Aop on my I pad. Therafyervtge music shut off and and have been trying to restart for nearly 2 hours.
Please don’t open duplicate Support requests. I’ve merged the duplicate into your already open Support request thread. Thanks you for your understanding.
Hi Sunder,
I’m avidly following your discussion as I had similar complaints. Is your core (or wherever you have Roon installed) connected to your network via cable? Made a significant difference for me.
Regards, Terry
Hi Terry,
My Nucleus+ is connected via Ethernet cable to a mesh router.
I now understand and agree that a mesh router is not the optimal solution for Roon Nucleus+. Hard wired to the Ethernet is optimal.
That being said, the main issue at hand is not Roon freezing due to internet connectivity, but that once it freezes one cannot reboot / wake it back up reliably and quickly.
I spent 2 hours last night trying. Gave up at 4 am. This is after rebooting, deleting and reinstalling the Roon Remote app. No success.
This morning, 7 hours later. Same process. Reboot, reinstall app. No success. An hour later, by magic, Roon app recognized my Nucleus+ and all good.
However, this will happen again.
All the while our 4 tv’s happily stream Netflix, Amazon Prime without any issues and the TV’s are not connected via an Ethernet cable to a mesh router. Just WiFi to mesh network.
Same applies to me streaming Tidal to my Devialet speakers. Tidal does not go on the fritz. Again, the Devialet speakers are not connected via Ethernet cable to the mesh router. Just WiFi to mesh network.
I am not in disagreement with the optimal setup. However, there should be a simpler and faster approach to relaunching Roon. Roon app should not freeze up post an update as it did last night while Roon Arc can still see my Roon account.
Spotify, Pandora etc also suffer connectivity issues but do not freeze up for hours on end.
I would think that after you delete your Roon app and reinstall, you would have to log in once again. Not so.
While the support community may not want to hear this, to me the least technical person on these chats, Roon should wake up quickly and not hours and lots of rebooting, deleting and reinstalling apps and the like. Roon is getting hung up somewhere due to its architecture.
Maybe this hasn’t been explained before.
Roon is very demanding of network resource. Yes - Netflix, Amazon Prime etc. may all stream perfectly, but they’re streaming heavily compressed streams without additional baggage.
Besides streaming the audio that you’re listening to, Roon is buffering a fair amount of data. It is also constantly updating the database with info/album art/discography for all of your library. Oh, BTW, it’s also communicating with your remotes/displays, displaying artwork/lyrics etc. etc.
For this reason, your core should not be connected over WiFi.
ARC may work perfectly, especially when streaming from Qobuz/Tidal. The data in this instance is being streamed from the service, not from your core. You’re only streaming from the core when playing local library versions.
As has been suggested numerous times, try hardwiring your core, even temporarily, with a long ethernet cable.
If it all works seamlessly hard-wired, you have your answer. Hard-wire your core. It may be difficult or awkward, but it’s never impossible.
I’m going to be unapologetically blunt here:
There’s no point complaining about Roon if you’re not prepared to meet the minimum recommended networking standards.
Endpoints may work fine over mesh networks etc. Your core needs a hard-wired connection.
I have an enterprise wireless network at home and every access point has a full-duplex Gbit wired backhaul, yet I still choose to hardwire every device where possible. Why? Because it minimises load on the WiFi to give the best possible experience to the devices that really need it and ensures the best possible connectivity to the devices that don’t need WiFi.
If you run a mesh network with wireless backhaul and Gbit cable to the primary node, you have 1 Gbit duplex available on your Mesh. Say you have 3 access points, then your looking at 333 Mbps duplex on each AP. If your core happens to connect to an AP which has a number of other devices connected to it - A TV streaming netflix, a couple of phones, a tablet, any other smart devices, then your core’s actual available bandwidth may be very low indeed.
With a cable back to the router, your core has a dedicated duplex Gbit connection.
If Roon crashes due to network strangulation, it isn’t going to recover quickly or easily.
This isn’t rocket science.
4 Likes
Graeme
Appreciate the reply.
While my next point does not change your recommendation, my wife and I hardly ever watch Netflix etc irrespective of 4 tv’s. The main use of our one gig service is our 2 I phones and Roon Nucleus+.
Get your point regarding Arc. However, for a different day and different discussion Roon Arc can be rather fussy when traveling. Not for this discussion.
1 Like
A further point around Roon’s network requirement is that Roon is bit perfect data transmission. Any errored or missing packets have to be retransmitted in real-time and if your network isn’t up to the job, this process will be unable to keep up and playback will stop. Video streaming from Netflix etc is not error free. There is no time to retransmit nor any real feedback path to indicate errors as such. Errors are therefore masked or will result in a small or not so small visible glitches in transmission.
Nobody is making excuses for Roon’s programming choices but it is what it is and you either fix your network or choose another audio product which is not so fussy.
Graeme
A note of thanks now that I have gone and done some reading / educating myself. Appreciate the long email. By way of background I am very much a neophyte when it comes to the technical matters you raised, such as backhaul etc which I now better understand.
Will work on getting a hardwired connection as recommended.
Again, thanks
Sunder
PS - not to takeaway anything from your explanation and recommendation, there is a section on using mesh networks on Roon Support. May need to be updated to the standards your fellow community members and you recommend.
1 Like
Hi Sunder,
Many thanks, and, please accept my apologies - the rocket science comment was harsh.
It’s great that you’ve done some reading and can approach this with more understanding. Where it comes to critical networking applications, you really can’t beat physical connections.
I echo your sentiments on the mesh network article in the Roon support pages. To me, it glosses over the disadvantages of WiFi backhaul. Yes, it’s better than a wi-fi extender, and the separate WiFi backhaul networks help to manage bandwidth sharing, but you are still sharing the single wired connection of the primary node. It does say that wired backhaul is best, but it also infers that wireless backhaul is probably OK, which in your setup, you have found not to be the case.
Good luck with the cabling and I hope you get your Roon setup working the way it should.
Graeme
2 Likes