Since you’re running macOS, the behavior you’re seeing is very often tied to the newer, stricter Local Network permission controls introduced in recent macOS releases. Roon needs explicit permission to scan your network for audio endpoints.
Step 1: macOS Local Network Permissions
Please try the following steps to refresh these permissions:
Open macOS System Settings → Privacy & Security → Local Network.
Make sure both Roon and Roon Server are enabled.
Even if they are already enabled, please toggle them off and back on to force a refresh.
Fully quit Roon Server from the macOS menu bar.
Reboot your Mac.
After the reboot, launch Roon again and check if the Meridian 818v3 is available.
Step 2: Network Connectivity Checks
If the Mac permissions are set correctly and the endpoint is still missing, we need to ensure there isn't a routing barrier on your local network preventing Roon from seeing the device.
Same Subnet: Double-check that both your Mac and the Meridian 818v3 are connected to the same Inteno EG300 router. If your Mac is on Wi-Fi, ensure it is not connected to a "Guest" network, as these isolate devices from each other.
The Power Cycle: Turn off the Meridian 818v3, your Mac, and the Inteno router. Unplug the router for 30 seconds, plug it back in, and let the network fully establish. Then, power on your Mac and the Meridian to establish a fresh connection.
Please give these steps a try and we will be standing by to hear your results!
Following up on our last exchange, I wanted to check whether you had a chance to refresh the macOS Local Network permissions for both Roon and Roon Server, then fully quit Roon Server and reboot the Mac. If the Meridian 818v3 is still not showing up, were you able to confirm that your Mac and the Meridian are on the same Inteno EG300 router and not separated by a guest network? Let us know what you’re seeing, thanks.
I have not succeeded in seeing the Meridian 818 from the Macbook. Configuration on Macbook seems ok.
I have installed Roon on an iMac now which is connected to wifi lan, not to ethernet, but still not able to see the Meridian.
I wanted to check the config on the 818, maybe something needs to be configured on the ID41 card, but need a serial cable that is on order now. I fear that trial license will expire before I can troubleshoot the issue.
I think I can see the ID41 card with arp command, but still Roon is not detecting it.
I attach a screenshot where you can see arp result with ID41 card not plugged in (first arp result) and with network connected after power cycle of both 818 and iMac (second arp).
Roon restarted too and list of audio device is refreshed.
Cheers
Not to worry here, if you’re unable to get things sorted out in time we’d be happy to extend your trial to ensure you get ample time to see if Roon is right for you.
Following up on what @ncpl has mentioned - are you able to access the ID41 homepage via the IP?
I’m also curious, how is your Meridian device connected to your router in comparison with your iMac hosting Roon Server? Can you simplfy this connection at all?
Are you able to use the ID41 outside of Roon via the same machine?
Following Nick suggestion, I actually had the chance to reach the Meridian 818 home page once.
Shame on me, I did the worst think I could do to check if it was possible fo change anything.
I changed the setting from DHCP to static IP. A classic mistake!
The device disappeared from the network and I have not been able yet to discover its new address… It might be living in a different subnet. The same address did not work.
With a script I have scanned both the subnet 192.168.0.x and 192.168.1.x without being able to find it.
Next attempt was to use serial connection and MConfig, but unfortunately at startup, tbe program tries to reach a web page at Meridian Audio, which does not exist.
It looks I am ending my ideas. I will try to load new firmware from USB key hoping not to brick the device.
It has been always tricky to mantain a Meridian system, but after many years that I have not updated anything, I have upgraded components and now I feel to be moving on a dead track.
If you have a laptop then just plug a network cable between the laptop and ID41. Disable your wifi and see if you can connect to the ID41 using the Meridian Device Manager. If you can, then revert to DHCP and be careful when you next play with IP addresses.
I have tried to use the direct ethernet connection without passing through a router, just to find out the IP address on the other side without success.
I think the two parties need to be on same subnet to talk though, which I am not sure they are anymore.
I am not sure either if I need a different ethernet cable (crossover cable).
I will continue my attempts next week. I am traveling now.
Do you know if other tools can work, apart mconfig, through serial cable and where to fetch in case?
Safe travels! Some additional thoughts on your issue here:
If you could try to manually assign your laptop a static IP in the same likely range as the ID41. For example, try setting your laptop’s ethernet adapter to:
IP: 192.168.1.100 / Subnet: 255.255.255.0 — then ping/scan 192.168.1.1–254
Then try: 192.168.0.100 / Subnet: 255.255.255.0 — scan 192.168.0.1–254
You can scan with nmap -sn 192.168.1.0/24 or use a tool like Angry IP Scanner.
Since MConfig tries to phone home to a defunct Meridian Audio web page and fails, here are alternatives for communicating with the ID41 via its serial port:
1. Any standard terminal emulator — The ID41’s serial port uses a straightforward RS-232 TTL connection. You can use:
Screen (built into macOS terminal) — screen /dev/tty.usbserial-XXXX 9600 — no download needed
minicom (Linux/macOS via Homebrew)
PuTTY (Windows, free) —
https://putty.org
Typical serial settings for Meridian gear: 9600 baud, 8 data bits, no parity, 1 stop bit (8N1), no flow control. This is the standard for most Meridian equipment.
2. What you can do via serial: Once connected, you should be able to access a command-line interface that lets you view and change the network configuration (including reverting the IP back to DHCP) — which is exactly what you need right now.
Another good news is that yesterday MConfig worked (meridian page found) and I managed to upgrade FW to latest ver. Still no config is possible on connectivity from MConfig.
the port scan I already tried, without success.
I will retry later this week after another clean reboot of all LAN devices and Router/Gw.
For the serial access, I appreciated a lod your detailed guidance, really useful info.
After some attempts, I managed to communicate to the 818, but what I got was nothing like a cli, though any basic command I tried, linux or windows, returned the string “error”.
It more seems to work as secondary display, showing same content as I see on the 818 display.
I see text appearing when selecting source or raising volume from remote.
Need to find out what I am doing wrong.
Btw, I used putty as terminal client from my windows laptop, connected to 818 serial port through USB-to-RS232 (on port COM3).
Cheers
I can finally report that I managed to solve all problems!
The only way to regain control of the 818 was go use direct ethernet connection and accessing the config of IP address through its web interface.
Once that was solved, still the connectivity on the home LAN remained an issue. Connectivity was very unstable over different tools (ping, arp, http, raat) and 818 was sort of out of control, until I used a switch connected to wall plug to connect the computer with roon server and the 818.
Now I am enjoyng the new streaming setup.
What a surprise to see the leap in musicality and transparency with that simple configuration with a quite old laptop with roon connected via ethernet to ID41 card in 818v3 versus the USB connection from a decent streamer/player!
This gives me hope that I might step up even more in quality using a dedicate roon server on a more hi-end network transport.
Thanks to community for the great tech. support!