Meridian Unplugged - Powered by MrTechGuy.co.uk Forums Discussion Meridian - Streaming Sooloos v2.477 Build 406

Thanks VK

Further to update and point 6 in the list I had to reinsert Tidal Account in Sooloos.
It had been deleted.

Hector

Hopefully the TCP/IP stack improvements will help with zones going awol for both Sooloos and Roon users. Most welcome if so.

So much for better stability of end points. I am having continual drop outs since updating to this version. Rebooting all of my equipment hasn't made any difference. My ID41 zone drops out continually. It had been very stable prior to this update. I hope Meridian sort this out.

As the network stack appears to have had an overhaul you might want to post some details regarding your setup to see if anyone might be able to help troubleshoot.

T

Does anyone here know how to "force" a Firmware Update onto a Meridian MS200 Endpoint??... it's stuck on Device Version 137, even after upgrading to v2.477 B406

Disconnected all Endpoints from Roon... and Roon Server and Clients switched off completely.

Started Sooloos on pre-existing Version... and ensured that all Endpoints were "seen" by Sooloos and I played a track to each to make sure... also checked that they were visible in the Debug screen.

After the above, I ran the update... which ran successfully... and resulted in the Version changing in the Debug screen etc.

However, the MS200 did not change to the most recent version of the Firmware

Anyone know a method to "force" this Firmware update??

I asked the same question of Marc Koval last week. My recollection is that the core pings HQ a good number of times a day( if not an hour) to inquire if there is a new software update, and downloads, if there is one. Then, it immediately looks for endpoints on the network and pushes out any embedded update to them (if there is a change to be made to the endpoints). In other words if the devices are all on the network and core enabled, it should work automatically. You have power cycled the endpoints after the core was switched back on after using Roon.
Is it possible the changes were limited to core control and not the endpoints?

I had been away a few days so only yesterday loaded this update. Disappointing to find all my end points disappeared (MS200s and MS600) immediately.

I have followed the usual required rebooting sequence of all units to bring them back on line. As I have observed before, this is never straightforward and frequently requires several tries before things fall into place. My experience suggests that it's first necessary to reboot the end point and afterwards robot the C15. I have sometimes needed to reboot the end point with the C15 completely de-powered. It's all a it hit and miss.

Again my experience is that it's not always an update that loses end points - for me it happens randomly from time to time. Drives my other half crazy when it occurs when I am not around.

I would like to understand why it happens, and if there is a preventative measure to avoid it re-occurring.

Thanks
regards
Huw

Huw, see my previous post and let's hope that zone are more stable with the new firmware.

It is the updating of your zone firmware that takes them off line at software update time.

I've just done some experimenting and as far as I can see, Sooloos is still taking endpoints away from Roon while they are enabled in Roon.

Has anyone else tried to run them parallel with this new build/firmware?

(Ronnie, my MS200 was also sticky, but a few power cycles both there and of the MD600 got it updated. Did you have luck in the end?)

From a quick experiment this morning, I found that an endpoint enabled in Roon would become 'un-enabled' if selected in Sooloos and would remain paired with Sooloos until such time as re-enabled in Roon.

So it looks as though the pairing is working well, it is just that one needs to re-enable in Roon if the same endpoint has been subsequently used with Sooloos.

The above was just a quick test as I was updating the version of a MS200 and trying a few things at the same time.

John

If I enable a zone in Roon, it simply becomes immediately un-enabled again a second or two after.

The one zone which was playing when I turned the MD600 on has however remained selected in Roon. Which is odd.

Certainly not behaving as I would hope, although perhaps half-working in that one zone has remained with Roon.

I had the Sooloos Core debug page up whilst doing the tests. You need to refresh the page, however it does it does let one see what is going on. Then flip between Roon Audio Settings page and the Sooloos debug screen.

You may already be doing this, however it helped me see exactly what communication was taking place between systems.

John