I had nothing but problems connecting using a Linux based Sonictransporter and iOS or Android devices .
I went to Windows and Mac core and zero problems z
I am reading the this thread for long time, since I have same problem: no connection on various Android devices⌠but so far it seems no solution in sight :-((
My setup:
-Roon device is: ELAC Discovery
-Roon essential on:
Samsung Tab-S, S4, S5, S8, Huawei P8 lite (ALL with connection problems!!)
Apple iPad, iPhone 6 (never any problem)
-Router is Fritzbox 7580
I tried everything (reboot, power on/off, change network connection, firmware/software updates, sequence of switch on/offâŚ) - but no clear rootcause: sometimes it works, most times not :-(((((
I tried adding a wifi adapter to my QNAP/Core, pointed the client at the IP address of the wifi adapter and the problem still happens.
I think the following log entries were generated on my Pixel when I opened the Roon app and failed to connect and then connected. It only tool about 20 seconds this time; sometimes it is shorter and sometimes much longer.
01/17 10:51:40 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
01/17 10:51:40 Trace: [push] retrying connection in 4716ms
01/17 10:51:40 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:42326] lost client connection. Retrying
01/17 10:51:40 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:42326] connecting (attempt 1)
01/17 10:51:40 Info: [transport] destroyed zone My Name Pixel 2 was playing? False
01/17 10:51:40 Trace: [zone My Name Pixel 2] Suspend
01/17 10:51:40 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
01/17 10:51:40 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:42326] client connection failed. Retrying in 500ms
01/17 10:51:40 Info: [brokerserver] Client disconnected: 192.168.0.82:38660
01/17 10:51:41 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:42326] connecting (attempt 2)
01/17 10:51:41 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
01/17 10:51:41 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:42326] client connection failed. Retrying in 750ms
01/17 10:51:42 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:42326] connecting (attempt 3)
01/17 10:51:42 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
01/17 10:51:42 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:42326] client connection failed. Retrying in 1125ms
01/17 10:51:43 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:42326] connecting (attempt 4)
01/17 10:51:43 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
01/17 10:51:43 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:42326] client connection failed. Retrying in 1687ms
01/17 10:51:45 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:42326] connecting (attempt 5)
01/17 10:51:45 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
01/17 10:51:45 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:42326] client connection failed. Giving up
01/17 10:51:45 Trace: [raat] [sood] Refreshing device list
01/17 10:51:51 Info: [stats] 2713mb Virtual, 448mb Physical, 232mb Managed, 0 Handles, 71 Threads
01/17 10:51:51 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
01/17 10:51:51 Trace: [push] connecting to x.x.x.x:9200
01/17 10:51:51 Trace: [push] connected
01/17 10:52:03 Trace: [raat] RAATServer discovered: RaatServer My Name Pixel 2 @ 192.168.0.82:38363
01/17 10:52:03 Info: [raatserver] GOT SERVER ########################### @ 192.168.0.82:38363 My Name Pixel 2 PROTOVER=1 RAATVER=1.1.23
01/17 10:52:03 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
01/17 10:52:03 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:38363] connecting (attempt 1)
01/17 10:52:03 Trace: [push] retrying connection in 71598ms
01/17 10:52:03 Trace: [raatserver] [RaatServer My Name Pixel 2 @ 192.168.0.82:38363] connected
01/17 10:52:03 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"}
01/17 10:52:03 Trace: [rnet/RnetJsonClient] GOT NONFINAL {"status": "Success", "devices": [{"config": {"unique_id": "##################################", "output": {"max_bits_per_sample": 16, "name": "Default Output", "type": "android", "device": "default"}, "volume": {"type": "android", "device": "default", "exclusive_mode": null}, "external_config": {"is_private": true, "max_bits_per_sample": 16, "max_sample_rate_multiplier": 1}}, "name": "Default Output", "type": "android", "device_id": "defAndroid devices to be very slow or not connecting to the Core running on a QNAP NAS. I disabled IGMP Snooping on my NetGear switch. I also went ahead and disabled âFlow Controlâ but donât think that was the issue. I hope this helps others that have been having issue connecting to Roon Core.
1 Like
Interesting! My home network configuration also has a NetGear switch between my Linux NUC running the core and both main router (Ubiquiti EdgeRouter PoE-5) and wifi AP (UniFi), to which my remotes connect. I thought I had tried to disable IGMP snooping on the NetGear switch before, but it was on. Turned it off. Stopped and cleared data on the Roon app on my Pixel 2, which had never been able to connect to the core. Restarted the Roon app on the Pixel 2, agreed to the license dialog, the app showed the core immediately and connected to it.
Now the real test is whether my Pixel 2 will reconnect to the core when I get home from work tomorrow without any further intervention.
3 Likes
Fernando- Is it still working after turning IGMP off? Do you have any Sonos in your environment? If so, do you ever get âLost control of audio devicesâ error in the client applications? I frequently get locked out of using the Roon clients if I click âNextâ or click in the song graph to move forward or backward in the song that is playing. Are you running the latest Core version and client versions?
Thanks,
Scott
Still working! No Sonos devices, no âLost controlâ ever. Latest Core and clients.
Thatâs good news!
I know I have gone in and changed a setting and then forgot to Save. Caused lots of hassle and wasted time. So now, I always go back and double check changes I make to gear to verify the change was actually made.
Another day, my Pixel 2 still connects to my Core, which had not happened ever before. Pretty surprised that just turning off IGMP snooping did the trick (thanks @Scott_Muckleroy!) because Iâm almost sure that I and others had tried this way back unsuccessfully. Maybe something else changed too in core or client network stacks along the way that led to this happy convergence. Iâm sure @mike will be interested in this thread if he is not currently following it.
Unfortunately Iâve got one of those ISP supplied routers that has very little in the way of config options so I canât try it, but hopefully this knowledge pushes us closer to a general fix.
Mark- If your AP is not in your ISP router/firewall you could try moving everything to a cheapo switch to see if the issue goes away. If you donât have one laying around, before buying one you might want to verify that the new one doesnât have IGMP snooping enabled by default or can be disabled. If you do this you would wanât one cable coming out of your ISP router and everything connected to the switch.
My Nokia 8 with Android Oreo 8.1 (beta) is now connecting (almost) immediately, every time.
This was definitely not the case with Android 7, or Android 6 on my old HTC One.
I say âalmostâ - because the âRoonâ and the âRemote Connectionâ screens both flash up briefly, before the ânow playingâ screen is displayed.
Iâve changed nothing whatsoever (else) in my home system - and I appreciate that there may be significant differences between Android 7 & 8 - but perhaps thereâs a clue somewhere in there?
I am getting constant connections all the time now. I have noticed though that the app seems to behave differently though as it completely restarting if its been sent to the background. What ever its been pretty consistent for a while now, even my Samsung is working better to.
Possibly but itâs completely the other way around for me. Worked perfectly with Android 7, stopped when I moved to 8.0/8.1 
Yes, that happens for me too. But the big/surprising positive difference is that even with my Pixel 2 totally up to date, I would never get a connection until I turned off IGMP snooping on the NetGear switch that sits between my core and my wifi AP.
@mike Just to update this thread: since I turned off IGMP snooping on the NetGear switch between my Ubuntu NUC with Roon Core and the rest of my network, my Pixel 2 consistently connects to the core. Software versions:
Pixel 2: Android 8.1.0, Feb 5, 2018 security patch
Roon Android app: build 298
NUC: Ubuntu 16.04.1, Linux 4.4.0-112-generic kernel
Core: build 298
Switch: GS108Ev3, firmware 2.00.08
Just as a counterpoint, Iâm running exactly the same switch with ROCK and Android devices - Iâve had no issues since disabling power management for the Roon app on those devices. I have IGMP snooping enabled, running firmware 2.00.12. Maybe a firmware bug??
Actually, I just remembered that I have one of these Netgear Prosafe switches (GS108Ev3) lurking behind my TV connecting a number of devices (firmware 2.00.05).
I disabled IGMP snooping which is on by default, and my Pixel remote connected immediately!
IGMP snooping is one of the settings that is recommended by Roon to be OFF, as is Jumbo Frames (it too should be OFF).