Meridian MS200 not detected by Roon when connected via Orbi mesh (ref#35VWPI)

Support
1

What best describes your playback issue?

· My DAC, streamer, or speaker doesn't appear as a Zone in Roon

What type of Zone is affected by this problem?

· *Network Zones* are affected.

Is the affected network Zone connected with Ethernet or WiFi?

· WiFi

Which network audio protocol is the Zone using with Roon?

· Meridian

Does the device show up at all in Roon Settings -> Audio?

· No, it does not show up there

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

Since you are using a network connection to the device, please ensure that your RoonServer is on the same subnet as the device

· My devices are on a single subnet but is not visible to Roon

Do you have a complex network setup?

· I have a *mesh network* with devices connected to multiples points

Your local network might need some re-arranging to support Roon.

· None of the suggestions have helped me. I'd like to submit a support request.

Do you have an approximate timestamp of when the issue last occurred?

· Zone not showing now at time of report

What are the make and model of the affected audio device(s) and the connection type?

· Meridian MS200

Describe the issue

Meridian MS200 endpoint is hardwired to Orbi satellite which is linked to Orbit router via WiFi (mesh). The MS200 can be seen on the network by eg IP Scanner Pro and shows up as an attached device in the router admin page. However it doesn't show up as a zone for Roon.

I have tried power cycling Orbi and rebooting Roon. If I move the MS200 and connect it to the network by ethernet then it does show as a zone. I have unchecked "disable IGMP proxying" as suggested.

Describe your network setup

Meridian MS200 is hardwired to Orbi satellite which is linked to Orbit router via WiFi (mesh). The MS200 can be seen on the network by eg IP Scanner Pro and shows up as an attached device in the router admin page. However it doesn't show up as a zone for Roon. I have tried power cycling Orbi and rebooting Roon. If I move the MS200 and connect it to the network by ethernet then it does show as a zone. I have unchecked "disable IGMP proxying" as suggested.

2

Hi @Ian_Tollett,

Thank you for your post.

The Meridian MS200 is registering on our diagnostic servers on a different subnetwork than the other endpoints in your ecosystem - the access point is likely creating a dedicated subnetwork for WiFi while functioning as an access point for ethernet.

I’d verify that your Orbi mesh nodes are all on the same subnetwork, for due diligence.

Where is the RoonServer machine plugged in, relative to both the main router and the mesh node serving the MS200?

4

It looks like they are all on the same subnetwork - I’ll send a screenshot in a moment.

My Nucleus is plugged directly into the Orbi router by ethernet.

The Orbi is in router mode (ETA - so that it is the Orbi that is assigning addresses rather than the internet modem)

5

Screenshot 2025-01-08 at 20.48.03
Screenshot 2025-01-08 at 20.48.031878×1252 334 KB

6

Also, please could you look at my open topic ref#UGVOY9 as it seems to have been forgotten - thanks.

8

Hey @Ian_Tollett,

Thanks for the screenshot, odd that is showing different addresses in this situation.

Just for due diligence, can you temporarily set the MS200 to be hardwired directly to your primary router via ethernet and see if your issues persist? Using different cables and ports may help as well.

It may also be worth reviewing the current firmware on the MS200, and see if any updates are available.

We’ll be on standby for your results, thank you!

9

Thanks for the reply. I’ve tried moving the MS200 so that it’s connected by Ethernet and it does show as a zone, so it’s definitely a WiFi issue. Unfortunately it’s impossible to serve that location by Ethernet.

I’ve checked the firmware also and it’s the latest version.

10

Got it, thanks for the test @Ian_Tollett!

If that doesn’t help, do you have a different node you could test temporarily? It may be worth getting in touch with Netgear support directly as well.