Meridian 218 disappears after being switched off

Support
1

Roon Core Machine

QNAP TS251 with 8Gb RAM

Networking Gear & Setup Details

Billion 7800 router, Netgear unmanaged switch

Connected Audio Devices

Meridian 218 Zone Controller hard wired to the router and Meridian 7200/2 speakers

Library Size

28000 tracks

Description of Issue

My system is working normally except for when I switch off at the end of a night’s listening. For the last few months my Meridian 218 is not found when I open Roon the next day. The interface says “no audio devices found”. The 218 is not set to go into standby but the only way I can get it to reappear in Roon is to unplug it from the mains and plug it back in again. It then works normally for as long as I want it to.
This seems to be an issue since the last but not most recent Roon update.

2

Hey @Alan_McMillan,

Thanks so much for sharing this! I’ve checked with our team and based on what you’re describing, this behavior might be related to the way networking works on QNAP.

It’d be great if you could temporarily switch to a Mac or a PC Roon Core, connect your Meridian 218 and see if this happens again.

3

Hi Rebeka
I’m afraid I don’t have the facilities to do either. It can’t be a networking issue. My system has been working flawlessly for four years. Why would it change now?

4

Hi again Rebeka
It occured to me that a firmware update had taken place on the QNAP a few weeks ago. They happen really frequently for some reason and are never an issue but this time I thought it might be since that is the only change that has taken place on my system. I have therefore downgraded the QNAP firmware by one version and it seems to have cured the problem. I’ll let you know if this is a real solution after a few days of using it.

Alan

1 Like
5

Hey @Alan_McMillan,

How wonderful that you’ve thought of that! Thank you so much for trying it out. I hope the victory is as permanent as it can be :partying_face:

Please, keep us posted :pray:

6

Hi @beka
I’m afraid it was a false dawn. It worked for me several times during yesterday, but after being switched off overnight, Roon couldn’t find the 218 again this morning and I had to unplug it from the mains and plug it back in again to get it to reappear as an audio device in Roon. So whatever the problem is, I don’t think it’s the QNAP server as it’s now in the state it was, firmware-wise, that it was in long before this issue arose and aside from Roon updates, nothing else has been changed.
I have looked at the logfiles and have discovered a lot of errors in connection with the 218. Here is a selection of what I found and this section seems to repeat often: it appears to be going round in circles trying to start the 218.

07/10 07:32:50 Warn: [meridian] failed to connect to endpoint (management) Connection timed out
07/10 07:32:50 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
07/10 07:32:50 Info: [meridian] connection failed to 192.168.1.100 management=58392 control=58391 clock=49154
07/10 07:32:50 Trace: [push] retrying connection in 89915ms
07/10 07:32:50 Trace: [meridian] Meridian zone discovered: ‘5f27f7e3-aa8d-4031-8f9f-e8f229ff7936’ @ 192.168.1.100:58392,58391,49154
07/10 07:32:54 Info: [stats] 1767mb Virtual, 660mb Physical, 263mb Managed, 0 Handles, 67 Threads
07/10 07:33:00 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
07/10 07:33:00 Trace: [push] connecting to 34.138.211.184:9204
07/10 07:33:00 Trace: [push] connected
07/10 07:33:09 Info: [stats] 1767mb Virtual, 661mb Physical, 263mb Managed, 0 Handles, 71 Threads
07/10 07:33:24 Info: [stats] 1767mb Virtual, 661mb Physical, 263mb Managed, 0 Handles, 68 Threads
07/10 07:33:39 Info: [stats] 1767mb Virtual, 661mb Physical, 263mb Managed, 0 Handles, 67 Threads
07/10 07:33:54 Info: [stats] 1767mb Virtual, 661mb Physical, 263mb Managed, 0 Handles, 67 Threads
07/10 07:34:09 Info: [stats] 1767mb Virtual, 661mb Physical, 263mb Managed, 0 Handles, 67 Threads
07/10 07:34:24 Info: [stats] 1767mb Virtual, 661mb Physical, 263mb Managed, 0 Handles, 68 Threads
07/10 07:34:39 Info: [stats] 1767mb Virtual, 661mb Physical, 263mb Managed, 0 Handles, 67 Threads
07/10 07:34:54 Info: [stats] 1767mb Virtual, 661mb Physical, 263mb Managed, 0 Handles, 67 Threads
07/10 07:35:01 Warn: [meridian] failed to connect to endpoint (management) Connection timed out
07/10 07:35:01 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
07/10 07:35:01 Info: [meridian] connection failed to 192.168.1.100 management=58392 control=58391 clock=49154
07/10 07:35:01 Trace: [push] retrying connection in 77407ms

There are also similar errors referring to the RAAT server
I can send you this logfile if you need to see it.

SUPPLEMENTARY ENTRY!!!
I have been playing music for the last 26 minutes and without warning or user intervention from anywhere, it stopped. The Meridian 218 simply vanished from the system whilst it was in use. That’s new behaviour…I have never known it to do that. I looked at the core log and pulled out the section relevant to this event:

07/11 14:04:05 Trace: [The Snug] [Lossless, 16/44 FLAC => 16/44] [100% buf] [PLAYING @ 4:01/10:36] Symphony No. 3 in C major, “Singulière”: I. Allegro fuocoso - Neeme Järvi / Gothenburg Symphony Orchestra / Franz Berwald
07/11 14:04:10 Trace: [Sooloos.Broker.Transport.MeridianZonePlayerEndpointStreamingClient disposed]
07/11 14:04:12 Trace: [Sooloos.Audio.Meridian.EndpointManagementClient disposed]
07/11 14:04:12 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
07/11 14:04:12 Trace: [push] retrying connection in 67327ms
07/11 14:04:12 Info: [meridian] connection failed to 192.168.1.100 management=57346 control=57345 clock=49154
07/11 14:04:12 Info: [transport] destroyed zone The Snug was playing? True
07/11 14:04:12 Trace: [zone The Snug] Suspend
**07/11 14:04:12 Info: **
–[ SignalPath ]---------------------------------------------
SignalPath Quality = Lossless
Elements:
Source Format=Flac 44100/16/2 BitRate=1412 Quality=Lossless
Output OutputType=Meridian Quality=Lossless SubType= Model=218
------------------------------------------------------------
07/11 14:04:12 Info: [zone The Snug] OnPlayFeedback Stopped
07/11 14:04:12 Info: [library] recorded play for profile 7b157f28-2f3a-49b9-b8da-1706cf76ed99: mediaid=50:1:c1b1a88b-cf24-4188-981e-617d972e49b8 metadataid=97:0:137969015972948 contentid= libraryid=50:1:c1b1a88b-cf24-4188-981e-617d972e49b8 isfromswim=False
07/11 14:04:12 Trace: [library] finished with 14 dirty tracks 1 dirty albums 0 clumping tracks, 0 clumping auxfiles 0 compute tracks, 0 deleted tracks, 0 tracks to (re)load, 0 tracks to retain, 0 auxfiles to (re)load, 0 auxfiles to retain, and 2 changed objects
07/11 14:04:12 Info: [zone The Snug] Canceling Pending Sleep
07/11 14:04:12 Trace: [The Snug] [Lossless, 16/44 FLAC => 16/44] [100% buf] [PLAYING @ 4:06/10:36] Symphony No. 3 in C major, “Singulière”: I. Allegro fuocoso - Neeme Järvi / Gothenburg Symphony Orchestra / Franz Berwald
07/11 14:04:12 Trace: [meridian] [192.168.1.100:57345] SENT REQUEST f
07/11 14:04:12 Info: [audio/env] [zoneplayer → stream] All streams were disposed
07/11 14:04:12 Info: [zone The Snug] Canceling Pending Sleep
07/11 14:04:12 Debug: [music/profilestats] Computed stats in 28ms, got 9 top albums, 11 top performers, 1 genres
07/11 14:04:12 Trace: [library] endmutation in 105ms
07/11 14:04:13 Trace: [meridian] Meridian zone discovered: ‘5f27f7e3-aa8d-4031-8f9f-e8f229ff7936’ @ 192.168.1.100:57346,57345,49154
07/11 14:04:13 Warn: [meridian] failed to connect to endpoint (management) Connection refused
07/11 14:04:13 Info: [meridian] connection failed to 192.168.1.100 management=57346 control=57345 clock=49154
07/11 14:04:15 Trace: [meridian] Meridian zone discovered: ‘5f27f7e3-aa8d-4031-8f9f-e8f229ff7936’ @ 192.168.1.100:57346,57345,49154
07/11 14:04:15 Warn: [meridian] failed to connect to endpoint (management) Connection refused
07/11 14:04:15 Info: [meridian] connection failed to 192.168.1.100 management=57346 control=57345 clock=49154
07/11 14:04:18 Info: [stats] 2407mb Virtual, 1308mb Physical, 446mb Managed, 0 Handles, 65 Threads
07/11 14:04:22 Trace: Successful POST response from https://push.roonlabs.com/push/1/connect
07/11 14:04:22 Trace: [push] connecting to 35.196.244.84:9204
07/11 14:04:22 Trace: [push] connected
07/11 14:04:24 Trace: [meridian] Meridian zone discovered: ‘5f27f7e3-aa8d-4031-8f9f-e8f229ff7936’ @ 192.168.1.100:57521,57520,49154
07/11 14:04:24 Trace: [push] restarting connection (Unable to read data from the transport connection: interrupted.)
07/11 14:04:24 Trace: [push] retrying connection in 70076ms
07/11 14:04:24 Warn: [meridian] failed to connect to endpoint (management) Connection refused
07/11 14:04:24 Info: [meridian] connection failed to 192.168.1.100 management=57521 control=57520 clock=49154
07/11 14:04:26 Trace: [meridian] Meridian zone discovered: ‘5f27f7e3-aa8d-4031-8f9f-e8f229ff7936’ @ 192.168.1.100:57521,57520,49154
07/11 14:04:26 Warn: [meridian] failed to connect to endpoint (management) Connection refused
07/11 14:04:26 Info: [meridian] connection failed to 192.168.1.100 management=57521 control=57520 clock=49154
07/11 14:04:28 Trace: [meridian] Meridian zone discovered: ‘5f27f7e3-aa8d-4031-8f9f-e8f229ff7936’ @ 192.168.1.100:57521,57520,49154
07/11 14:04:28 Warn: [meridian] failed to connect to endpoint (management) Connection refused
07/11 14:04:28 Info: [meridian] connection failed to 192.168.1.100 management=57521 control=57520 clock=49154

It then goes round and round in circles again, trying to start the 218.

Alan

7

Hey @Alan_McMillan,

Thanks so much for following up as soon as things changed. Needless to say, I’m sorry :sweat:

To help with the details you’ve sent (especially the logs), I’ve looped in our technical team so they can share their insight.

Please, sit tight :pray:

8

Thanks Rebeka. There’s one other thing to note. The 218 is also used for my TV’s sound as it handles the optical input from my LG OLED panel. That comes on as normal whenever it is needed, that is, the TV never fails to find the 218, it’s only Roon that loses it completely such that it needs to be unplugged from, and replugged to, the mains to get Roon to re-detect it.

Alan

9

Hi @beka
Any ideas on this problem yet?

Regards

Alan

10

Hello @Alan_McMillan,

Thanks yet again for the extra details about the 218 and the TV. Also, for following up so kindly and for your patience.

I’ve just gotten in touch with our technical team about your case. You should hear back soon :pray:

11

Hi @Alan_McMillan

Can you share a full set of logs with us using Dropbox or another file sharing service? Thanks!

12

Hi @dylan
I’ve uploaded the logs as requested to WeTransfer. Here’s the link:

Regards

Alan

13

Thanks, @Alan_McMillan.

I’m definitely seeing errors here showing that the Meridian is refusing the connection to Roon, but I’m not 100% sure why it’s doing that just yet. I’ve passed this along to our gear expert for further feedback. I’ll be in touch once I have their input

14

Hi @dylan
It is a weird one and I’ve never seen this problem before in the five years since I built this system. It may be unconnected but it has only been happening since Roon 1.8 came out.

15

Hi @Alan_McMillan, I’m sorry for the late response here. I heard back from our ecosystem expert — He’s tried reproducing this issue but has been unsuccessful. As mentioned before, it looks like the Meridian is actively refusing the connection to Roon, so we were hoping we could try something:

Does the same behavior occur if you use a different Core? If you use a PC or something as a temporary Core do you see the same issue appear?

16

Hi @dylan
The issue hasn’t occurred since we last communicated. I have no idea why as nothing has changed at all. It simply doesn’t misbehave anymore. I’m inclined to leave well alone, but if it recurrs, I’l get back in touch with you.

Regards

Alan

1 Like
17

Thanks, @Alan_McMillan. Definitely let us know if anything changes. I’ll close this for now but happy to re-open if needed.