Tablet cannot maintain ongoing connection to Roon Core

Core Machine (Operating system/System info/Roon build number)

Roon ROCK on NUC7i7BNB

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Ethernet for music play back, Netgear Orbi for wireless control

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Huawei Media Pad M5 tablet

Description Of Issue

The tablet cannot maintain a solid connection to the Roon core, it might connect fine one minute and the next I get the “Remote Connection, then waiting for Roon Core” screen. I have not observed the Roon app disconnect directly when using it, usually if I jump across to another app (firefox or youtube for example) and then back, it won’t connect, but this experience is also inconsistent. This has been happening for the last 10 days or so. My Galaxy s9 phone connects to Roon and does not exhibit the same behaviour, so it seems specific to the tablet.

I have used the tablet for the last few years with pretty much no problem. I can see that the tablet is connected if I look on the Orbi app, and I can see a good connection to the wifi when looking on the tablet its just the issue with Roon.

I can fix it sometimes by killing the app and trying again, sometimes it connects, sometimes not.

Any ideas?

Hi @tahsu,

Is there any change in behavior if you try to reinstall the Roon app on the tablet?

How is the tablet connected vs your other Roon Remotes? Are they all on the same access point or is the tablet on a different one?

Hi @noris,

I will uninstall the app and then report back when I know a bit more.

The phone and tablet are on same orbi satelite.

1 Like

I tried uninstalling and reinstalling the app, but the same behaviour is observed. The phone and tablet are on the same orbi satelite, its about 6 feet away, in the same room.

Hi @tahsu,

If you try clicking on the “Help” button that appears and typing in the IP of the Core or the address of 255.255.255.255 does that allow connection to the Core?

A post was split to a new topic: Issues connecting to Core

Why does the that approach fix it? What would cause the need to do that and what does entering 255.255.255.255 do to make it work?

Hi @Michael_Guy,

The IP of the Core is straight-forward, and the reason why 255.255.255.255 works is because it is the multicast broadcast address. Typically you wouldn’t have to input any IP if the multicast routing of the network and the remote work properly.