I am having a similar problem with a SoTM SMS-200. After the latest software upgrade to my Roon Core running on a SonicTransporter i5, the sMS-200 has disappeared from Roon. I can log into the SoTM, manage the config via the GUI, etc. I have rebooted and power cycled both the SonicTransporter and the SoTM. I have multiple other RoonReady devices on my network including 2 microRendu, an exaSound PlayPoint, and a dCS Upsampler and they all work fine. It is just the SoTM that has completely lost visibility to Roon.
After looked through some other posts and finding that the SoTM can disappear from Roon if it isn’t connected via USB to a DAC and the DAC is on, I double-checked my set-up and discovered that was the case with mine. I was playing around with a new LPS for my Uptone regen and apparently while it has the right V it doesn’t produce enough A, so the Regen wasn’t powered up. The Regen power light is hidden on my installation, so I didn’t notice until I checked. All is fine now.
Hi @Kurt_Lantz ---- Thank you for the follow up and my apologies for the slow response.
Confirming that I have received your logs and and that they are in our queue to be evaluated. In the meantime, I would like to see how another network based endpoint behaves. Is it possible for you to load either Roon (as a remote) on another device OR Roon bridge? For this scenario to work either of these option must be loaded on to a laptop/desktop computer. The idea is to see if those devices remain stable.
@support
I had been enjoying a 2 month trial - working perfectly with the sms-200. Trial period ran out so I registered yesterday. In the process I received a message that an update was available so I updated. Since the update Roon will not work with the sms-200. A song will play for a few seconds then stop and skip on to the next song in the queue or stay on the same song and skip constantly.
Taking the sms-200 out and swapping in a Squeezebox Touch cures the problem, Also, the sms-200 works perfectly when running LMS instead of Roon.
I have the same problem with my MicroRendu. I did a clean install of Roon and it works fine again but only with the older build. After updating to 234 the problems occur again. Are you using Win10 (and maybe in “bridged mode”)?
We’ve heard of a few issues with this device since Build 234 went live, so I’ve most all the posts into one thread so we can gather info in one place. There were some RAAT streaming optimizations in our most recent release that were rigorously tested and have been widely stable, but we’ll be investigating this and following up with SOtM to see if we can get a handle on what’s going on here.
If you haven’t already, can you all please let us know the full details of your setup, as described here. In particular, it would be helpful to know the details of your network, and the networking settings of all the devices involved. The more details we have, the more likely it is that we can reproduce this issue in house and make some progress here.
I noticed that two people have mentioned “bridged mode” so that may be a clue – any relevant details about exactly how you have that set up would be helpful as well.
Thanks in advance for your help, and your patience guys.
Thanks for the follow-up. My problem turned out to be an anomaly with the SOtM where even if it is connected and powered up, it will not respond if the USB connection to the DAC is not working for any reason (unplugged, not selected input). Nothing to do with Roon, just my learning curve.
Sir I have tried to establish connections with my Sotm SMS200 the unit has been in the system for several months now and suddenly I have lost the connection and it does not showup on my list of Zones.
I have also lost the remote connection t my tablet, I have a screen shot showing the Sotm sms200 is connectd to the system as it is identified on the Eunhasu music player but this will not give it to Roon and also cannot use the system as it is controoled by my tablet in the other room from the server.
Hi @David_LAw ---- Thank you for the PM. I went ahead and moved your support question out to this thread were we are addressing this behavior you’re reporting.
Moving forward, may I kindly ask you to review @mike’s post from above and supply the requested information.
I’m away until next weekend. When I get back; I don’t have another device available but could I use my core (Mac Powerbook described above) as the endpoint as well? Let me know if that would be helpful.
I’ll keep my eyes on this thread to see if another solution is discovered in the meantime.
Hi @Kurt_Lantz ---- Thank you for the follow up and proposing an alternative test. Very appreciated!
Unfortunately, this test will not work for what I am looking for in terms of testing a network endpoint. Your logs are still with my tech team so hopefully they would be able to provide some insight once their analysis has been completed.
How can this all be ok and then Build 234 comes along and no Sms200 Connectivity this is crazy we are paying for a service and not being able to play my music because of your build is madness.
Please sort this out do not try to blame other manufacturers or connections if people have not changed their connections and the only difference is in the latest build then please revert to a build where I can listen to my music.
You see that’s what I pay for.
@David_LAw ---- I understand that these types of situations can be frustrating and just like you, we too wish that there was a quick, “turn this off and restart” type of explanation to this behavior, but unfortunately this is not the case.
As @mike has already mentioned, we are doing our best to understand the nature of this behavior and address it accordingly, as we have always done. When a situation like this appears we rely on the feedback provided by our users because without that, we are flying blind.
Moving forward, David, if you could please provide the information being requested in the post above it would be very helpful and appreciated!
Hi, I have the same problem as well. Just received my SMS-200 and decided to give Roon a try for 14 days. The SMS-200 is connected to my router and the output goes to my Yggdrasil (which is on). My laptop is on Windows 10 and I activated Roon through Eunhasu. I tried to look for SMS-200 under Roon > Audio to no avail. The only device detected was the HQ Player (I’m guessing it’s a default setting, since I don’t use it). I also tried searching for devices and Roon just kept loading without any success. And yes I restarted my equipments a couple of times before I gave up, frustrated.
It’s a pity as I actually wanted to give Roon a try and to decide whether I wanted to continue my membership. I hope this issue can be resolved before my trial period ends. Will try again when I have the time today.
Hi @Paul_Tan ---- Thank you for chiming in here and sharing your observations with us, both are appreciated.
Moving forward, piggy backing on Mike’s post from above, can you please provide me with the following information:
Can you provide make, model, and specs of the Win10 device hosting your Roon core.
If you know the IP address being assigned to the SMS200 from your router, can you successfully ping the device from your laptop?
My assumption (based on your description) to this question is going to be “No, I am not”, but please verify if you are using the SMS200 in "bridge"mode.
Can you please provide the make and model of the router you are implementing.
FWIW, I have not had any problems with Roon playing to my SMS200.
Roon Core is running on Linux Mint.
Roon Core and SMS200 is connected to the same switch.
A few days ago I was on SMS200 FW 3.5 and am now on the latest 3.8. Both work fine.
I know you probably have done this, but just in case - The first time you use SMS200, you have to login to the SMS from a browser and configure Roon Ready Info (i.e. the DAC options such as DOP or Native DSD) then click the play button to start it up. Once is starts, it will auto start on any reboot.
Another thing you guys can try to isolate whether is a RAAT problem or not is to stop Roon on the SMS and enable Squeezelite. Then from the Roon Client Settings->Setup, “Enable Squeezebox support”. This is for testing only, obviously you want to get it working with RAAT.
Also, make sure you are on the latest SMS FW because you see it contains Roonready 1.1.19.
You upgrade from the browser connection under System Setup.
If you are on say 3.5, the upgrade will go to 3.6 then you have to repeat until you get to 3.7 then 3.8. The upgrade does not jump straight to the latest version.