MDC BluOS 2i seems to crash sometimes while playing with Roon

Hello,

My MDC BluOS 2i module seems to crash sometimes while playing Roon,

I’ve already contacted the Bluesound support. The last time, they said I have to contact Roon support.

Symptoms I expierence:

  • Playback is disrupted at a given moment.
  • MDC module dissapears from list of Roon audio devices. Network wise, the module isn’t also unreachable anymore (tested with infinite ping from my Windows 10 ethernet cable connected Roon core host, no working BluOS app, no Spotify or Tidal connect).
  • According my FritzBox 7490 router logs, the module kept it’s wifi connection - until just before the problem was restored by itself - without any intervention. The downtime took about 4 minutes.
  • No other network devices suffered connection loss or any other issues

As I have opend another ticket to Bluesound, a debug log is attached to the Bluesound support ticket automatically.

What I keep seeing in a large amount are lines like this in the module’s log.

first occurence:
Jun 15 19:42:38 (none) user.warn RAAT: dropout of 242 samples at 284930074 [2]
(there are about 3086 such lines with about 200 each second)
last occurence:
Jun 15 19:42:47 (none) user.warn RAAT: dropout of 242 samples at 285676644 [2]

Next lines

Jun 15 19:42:47 (none) user.info ./ms.pl: main::HttpRequest ./ms.pl (1098) [1] 127.0.0.1: /Services
Jun 15 19:42:47 (none) user.info ./ms.pl: main::HttpRequest ./ms.pl (1098) [1] 127.0.0.1: /RadioBrowse?service=Capture
Jun 15 19:42:52 (none) user.info sovi-spotify: onConnectionNotify: 3
Jun 15 19:43:12 (none) user.info sovi-spotify: onConnectionNotify: 2
Jun 15 19:43:30 (none) user.info sovi-spotify: onConnectionNotify: 2
Jun 15 19:43:43 (none) user.info sovi-spotify: onConnectionNotify: 2
Jun 15 19:43:55 (none) user.info sovi-spotify: onConnectionNotify: 2
Jun 15 19:44:11 (none) user.info sovi-spotify: onConnectionNotify: 2
Jun 15 19:44:49 (none) user.info sovi-spotify: onConnectionNotify: 2
Jun 15 19:45:35 (none) user.info sovi-spotify: onConnectionNotify: 2
Jun 15 19:46:02 (none) user.err ./cp.pl: AmazonIoT::_on_error Sources/AmazonIoT.pm (318) AWS IoT error! fatal: 0 message: "keep alive timeout"
Jun 15 19:46:26 (none) user.err ./cp.pl: AmazonIoT::_on_error Sources/AmazonIoT.pm (318) AWS IoT error! fatal: 1 message: "Error: No such device or address"

(logs above in UTC timezone)

My infinite ping check reported failed ping’s during 15-06-2021 21:43:03 and 15-06-2021 21:46:48 (UTC+2 is my actual timezone).

According the module’s logs, it plausible Roon is involved in this problem some way.

I just have another confirmation by Bluesound support the problem is related to Roon.

I can confirm I have exactly the same problem with my module ( in a Dali Sound Hub). This module looks exactly the same as yours - and probably is, but is not Roon Certified. Therefore I have not asked for support from either Roon or BlueOS yet.

Im my case the module dissapears when Roon is started on a device. Only a hard reset or waiting for about 15 min. resolves the problem. Let us hope Roon of Bluesound check this out.

By the way: I think it is a fault of the module and not Roon, as also Spotify connect and Tidal connect are out of service at the same moment