My setup is NUC7i7BNH with 8GB RAM, 256GB Internal SSD and 2TB SATA SSD (250GB used). The NUC is connected directly to my modem connected google Wifi router. I have 3 other Google Wifi points in the house and my BlueSound and Sonos devices are cable connected to them.
I’ve been using Fiio M11 Pro almost exclusively since I got it (dec 27th)
Before that I used mostly my Sonos Port.
The Sonos error was a rarity, the system seem to work pretty flawlessly with Sonos actually.
Less so with my BlueSound Node 2i which I use occasionally, but the errors there are not the same as M11 (they are mostly hiccups in the starting of songs), please see you own forums, people have been discussing BlueSound issues at length. I consider these problem fairly minor at this point
In short the M11 has more issues.
I’m an experienced software developer and I can “smell” problems pretty good when I see them. This looks to me very much like a robustness issue within the communication protocol used between components. So yes it is probably a network problem and it is happening on a network that I would qualify as excellent. I don’t expect quick fix for this, but I hope the system will be updated to be more robust in the future.
Also can you tell me why it is that Fiio can’t supply the correct Roon version from their app store? Is there anything you guys could to about this?
It seems that the Sonos issue was more of a one-off issue, so I’ll pass this back over to the team for continued investigation and we will focus specifically on the M11.
Have you discussed this with Fiio at all? I discussed this with the team once more who have been investigating further. In the logs, when these errors are occurring, they’re seeing traces like this:
01/14 20:14:01 Debug: GMS: done saving nav stack
01/14 20:14:05 Warn: [ui/slowness] widget queuelist(2409) took 242ms to _Update
01/14 22:37:46 Trace: [push] retrying connection in 0ms
01/14 22:37:46 Trace: [client/roonbridges] network reachability changed, sending discovery query
01/14 22:37:46 Trace: [roonbridge] [sood] Refreshing device list
01/14 22:37:46 Warn: Error in web request https://push.roonlabs.com/push/1/connect: NetworkError (Error: NameResolutionFailure)
01/14 22:37:46 Trace: [push] request to manager failed
01/14 22:37:46 Trace: [push] retrying connection in 13079ms
01/14 22:37:55 Warn: [remoting] connection received no data for 13610ms. Assuming dead.
01/14 22:37:55 Info: [brokerclient] Connection dropped: Roon Optimized Core Kit (6c1e4e19-f2be-42f6-9070-0dc50dd068cc) @ [IP ADDRESS]
01/14 22:37:55 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
01/14 22:37:55 Trace: [push] retrying connection in 172566ms
01/14 22:37:55 Info: [brokerclient] connecting to Roon Optimized Core Kit (6c1e4e19-f2be-42f6-9070-0dc50dd068cc) @ [IP ADDRESS] (attempt 1/6)
01/14 22:37:55 Info: [client/root] Broker changed Roon Optimized Core Kit (Remote Broker 6c1e4e19-f2be-42f6-9070-0dc50dd068cc) => null
01/14 22:37:55 Info: [client/root] Client is acting as a remote
01/14 22:37:55 Info: [client/root] Broker ready changed True => False
01/14 22:38:00 Info: [distributedbroker] LOST BROKER Roon Optimized Core Kit (6c1e4e19-f2be-42f6-9070-0dc50dd068cc)
01/14 22:38:05 Warn: Error in web request https://push.roonlabs.com/push/1/connect: NetworkError (Error: NameResolutionFailure)
01/14 22:38:05 Trace: [push] request to manager failed
01/14 22:38:05 Trace: [push] retrying connection in 253107ms
01/14 22:57:51 Trace: [push] retrying connection in 0ms
01/14 22:57:51 Trace: [client/roonbridges] network reachability changed, sending discovery query
01/14 22:57:51 Trace: [roonbridge] [sood] Refreshing device list
01/14 22:57:51 Info: [brokerclient] connecting to Roon Optimized Core Kit (6c1e4e19-f2be-42f6-9070-0dc50dd068cc) @ [IP ADDRESS] (attempt 1/6)
01/14 22:57:51 Info: [distributedbroker] FOUND BROKER Roon Optimized Core Kit (6c1e4e19-f2be-42f6-9070-0dc50dd068cc)
01/14 22:57:51 Debug: [brokerclient] auth with Roon Optimized Core Kit (6c1e4e19-f2be-42f6-9070-0dc50dd068cc): Attempting to authenticate with no PIN
01/14 22:57:51 Trace: SENT REQUEST DistributedBroker.ConnectRequest={ ClientBrokerId=bb9886eb-c85f-4f16-9466-2ead951e191c ClientBrokerName='FiiO M11 Pro' ProtocolVersion='26' ProtocolHash='4ed7b54472efd44c52dce34644e8c79fcb3abdaf' }
01/14 22:57:51 Trace: GOT NONFINAL DistributedBroker.ConnectResponse={ BrokerId=6c1e4e19-f2be-42f6-9070-0dc50dd068cc BrokerName='Roon Optimized Core Kit' }
01/14 22:57:51 Trace: [brokerclient] connected to Roon Optimized Core Kit (6c1e4e19-f2be-42f6-9070-0dc50dd068cc)
01/14 22:57:51 Trace: GOT NONFINAL DistributedBroker.UpdatesChangedResponse={ IsSupported=True WasJustUpdated=False Status='UpToDate' HasChangeLog=False CurrentVersion={ MachineValue=100700511 DisplayValue='1.7 (build 511) stable' Branch='stable' } }
01/14 22:57:51 Info: [client/root] Broker changed null => Roon Optimized Core Kit (Remote Broker 6c1e4e19-f2be-42f6-9070-0dc50dd068cc)
01/14 22:57:51 Info: [client/root] Client is acting as a remote
01/14 22:57:51 Info: [client/root] Broker ready changed False => True
01/14 22:57:51 Debug: [easyhttp] POST to https://bits.roonlabs.net/1/q/roon.childprocess.,roon.debug.,roon.sood.,roon.client.?roon_auth_token=94951b82-864b-459e-996c-6b51edefc7ec
01/14 22:57:51 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
01/14 22:57:51 Trace: [push] connecting to [IP ADDRESS]
01/14 22:57:51 Trace: [push] connected
01/14 22:57:51 Debug: [easyhttp] POST to https://bits.roonlabs.net/1/q/roon.childprocess.,roon.debug.,roon.sood.,roon.client.?roon_auth_token=94951b82-864b-459e-996c-6b51edefc7ec returned after 347 ms, status code: 200
01/14 22:57:51 Trace: [bits] updated bits, in 351ms
01/14 23:29:36 Warn: [remoting] connection received no data for 13737ms. Assuming dead.
01/14 23:29:36 Info: [brokerclient] Connection dropped: Roon Optimized Core Kit (6c1e4e19-f2be-42f6-9070-0dc50dd068cc) @ [IP ADDRESS]
01/14 23:29:37 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
01/14 23:29:37 Info: [brokerclient] connecting to Roon Optimized Core Kit (6c1e4e19-f2be-42f6-9070-0dc50dd068cc) @ [IP ADDRESS] (attempt 1/6)
01/14 23:29:37 Trace: [push] retrying connection in 27020ms
Essentially, what the above shows is that the Core machine is losing connection to the remote device entirely. It’s a brief disconnect, but that is what is causing playback to stop.
It’s hard to say exactly what is causing the disconnect, it could be the device’s network connection being interrupted briefly, or the way that the OS is interacting with Roon, but ultimately this device just becomes unavailable to Roon for some time.
“Have you checked to see you are on the latest FiiO M11 Pro firmware?”
I have, according to the device I’m up to date.
That being said I’m looking forward and hoping to see an update that would fix this connectivity issue.
Hopefully Fiio will figure out if there is a problem on their side.
As for Roonlabs since this is by definition a distributed system I suppose it is always a good idea to always work on making your application layer communication more robust and more able to deal with lower layer protocols issue (to a point obviously…)
I can try to ask Fiio but I suspect they will tell me to try another Wifi, as they have told others, which of course I can’t easily do with Roon.
That being said on the M11 I have not had any other networking issues except with Roon.
So again I hope your team is working on making communication ever more robust.
BTW this happened today, what is “System.Exception: serverside buffer overrun”:
Fiio released a firmware update recently, been using it for a few days and things seem to be much better now.
Still the occasional interruption but usually can resume playing the same song after Core reconnects. Seem to help to restart the Roon Server Software prior to use…