· Other
· How do I ...?
· Other
My SOTM 200 NEO that was recognized as a ROON endpoint when I was on Windows is no longer recoginized as a roon end point, but only as a Sharepoint via Airplay on Roon software. I have latest MAC OS Sequoia and need your help in resolving this.
SOTM 200 NEO connected via Ethernet and MAC OS connected also via Ethernet on the same network.
I recently move to Mac Mini and running my Roon server on this one. The OS is Mac Sequoia
The SOTM NEO 200 that was recognized as a roon end point is only shown as a sharepoint via airplay on Roon Audio options. I tried multiple restarts of SOTM and I feel this is something do with ROON’s software. Need help in resolving this.
Regards,
Deepak
@Deepak_Manoharan I merged your second post on this to here.
Visit http://eunhasu.local and make sure it is set to Roon Ready mode…
Only one setting at a time on the SOtM sMS-200…-
I understand. When I set it to Roon ready mode, SOTM is not recognized as Roon endpoint. Only visible in sharepoint. This is the issue
It will only be available/visible in Roon when it has got a compatible DAC connected (and recognized in eunhasu.local) to it’s USB port as well.
Post screen shots of the Roon Ready settings in Eunhasu as well as Audio devices in Roon, please.
Just in case you want to re-burn a new image: en:eunhasu:burn_sdcard_image [SOtM docs]
Hello @Deepak_Manoharan,
Thank you for reaching Roon support and welcome to our coumunity!
As the first troubleshooting step lets make sure that you Roon server on the Mac OS have the access to the LAN devices.
Can you please navigate to macOS System Settings > Privacy & Security > Local Network , and make sure Roon is allowed. If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists.
Additionally please attache the Screnshot of the Settings → Audio
Thank you for your reply! I did try what you told me and still do not see the SOTM as roon endpoint. You can see ROON Active, but not showing on the right.
I will now turn on sharepoint and you can SOTM listed as an Airplay device
is the DAC connected seen by the SoTM?
btw: the SoTM should be displayed in the Roon ready section…your picture shows Roon tested…
An other check: did you connected the DAC to the USB-Audio port?
In the first setting, please show a screenshot of the Settings under Roon Ready in Eunhasu.
Like this:
Since one of the last firmware updates my Neo will also sometimes not shown as Roon Ready device.
Obviously in the setup Roon is marked as active, I’ve then to reload (or disable + enable) the Roon setting an then it appears as Roon Ready device in Roon again.
Also setting for the device a fixed IP doesn’t resolve this problem.
I’ve not done more research for issue, because I’m using the Neo very rarely, but it can be that it can’t survive a Roon server restart or a (longer) disconnected USB DAC.
With older firmwares, this problem had never occured.
Hi @Deepak_Manoharan ,
Please share a screenshot of the Roon Ready configuration as @Mikael_Ollars noted and we can proceed from there, thanks!
Yes, this is the problem Stefan. SOTM does not show up as Roon Ready anymore even after it is set to Active on the SOTM Portal
Burkhardt, so did you resolve this issue or still have the same problem?
As described in my posting…
@Deepak_Manoharan your firmware seems to be on V 1.1.38. @Mikael_Ollars firmware is V 1.1.43. Have you, or can you, update your firmware and see if this helps resolve your issue?
This is the issue, Roon only recognize the SOtM while it identifies an attached DAC.
What is the exact DAC you have connected?
Could you actually play something while using Shairport, or does it simply show in Roon?
If your USB attached DAC is stable and can be used directly attached to a computer (without drivers) i would recommend a reinstall of the Eunhasu operating system on the SOtM, as described above.
You could also engage in an upgrade through the System/Settings section of Eunhasu.
Unlike @Burkhardt_Petermann my two SOtMs are 100% stable and sounding the best they ever have with the latest firmwares and some tweaking.
Hi @Deepak_Manoharan ,
@Mikael_Ollars provided some excellent suggestions here, please let us know if this helps!
