Hi
After the HEOS Update all my devices are listet as Roon Ready (but Not Certified). I think there is a nativ Support for Roon on the way.
At the moment i can not activate them.
Regards
Hi
After the HEOS Update all my devices are listet as Roon Ready (but Not Certified). I think there is a nativ Support for Roon on the way.
At the moment i can not activate them.
Regards
Lets hope!
This would make life a lot better for those of us with HEOS devices.
On mine HS2 type devices are shown as ROON ready - but not certified.
Maybe this is why they have had such a delay in all certifications as having the whole to certify would be an undertaking . But my scepticism thinks it’s a Roon error and these should be Roon Tested. I hope I am wrong but with all the cock ups with Roon of late who knows.
I hate to agree with you but I think you are probably correct. I remember when the initial Denon/Marantz ROON certification was accidentally leaked by Denon in an advertisement, which gave me the initial hope - many years ago. We were let down by the eventual Roon tested/ airplay solution. As you know, I’ve tried to fix this best I can, but would love a ROON ready solution.
But some of the Heos speakers that are already Roon Tested are showing up as Roon Ready so maybe it’s the real deal your Heos 250 is already Roon Tested I believe.
So - perhaps this may be my last release of RHEOS? I’m hoping that a ROON ready version will fulfill all I need. Lets see. The latest ROON sortware update didnt make the HS2 players now showung as ROON Ready as Certified.
Today’s release 0.8.4-4 corrects a small bug where if a group is fully ungrouped in the HEOS app , this would not be mirrored in the ROON group .
This release also adds more choices of time delay (0- 20 sec) in the new AUTO-START capability.
Interesting… let’s hope! I definitely like what they have done with the HEOS app. Not perfect but much better. It also shows their commitment.
I just checked out tthe app, massive improvement.
I am not understanding this extension, excuse my ignorance. My core is installed on a Synolgy NAS. I use Roon Remote on my iMac. I looked at the instructions but not following on a Friday, been a long week.
It allows you to play to heos enabled devices from Roon and not being limited to using Airplay. It bridges the UPnP protocol of Heos to Roon. Means you can play Hires up to 192/24 and can play to the group if you have multiple Heos devices.
So, all my devices are showing Ready but not certified now either…
in looking at this article:
Uncertified Roon Ready devices announcement - Roon Software Discussion - Roon Labs Community
it seems the database or configuration files of our roon server holds the key to allowing existing uncertified devices since it worked for those after September IF they did not reset their core… hmmmm
Yes - to me it seems some investment is being made again in the HEIS system. Thank goodness. After the disastrous loss of the dispute with The Sonos people I was afraid they would pull. But perhaps googles recent win is allowing them to risk developing again! The close integration into a wide variety of products set the system apart IMHO.
I didn’t know Sonos had ago at them too. Who’s next Amazon? Apple?
not sure if anyone else sees this - when I update my portainer (pull new image) i have to now update the UPnP settings for roon upnp server (and i increase the log file size) - its setting this field to 192 address…
Only Roon can unlock it when a device passes certification its locked from their side nothing you can do. They grandfathered a few devices when they brought in the more stringent process to ones that were near certification but after the September cut off no exceptions to any new devices or users who didn’t apply.
As no press release of this at all it’s either been pushed early as a mistake by Marantz, Roons behind schedule for updating their side or Roons made a cock up and these are just Roon Tested like every other Marantz Denon product. But it’s so many products popping up it feels to good to be the first or even 2nd but let’s hope so.
Mine is set to my Roon core IP address which it’s supposed to. Peter added that as if you also run another instance of LMS the player will lock to that if Roon core is offline. With this it will just wait until the core is back online and ignore any other instance.
Whoops - that’s not right! That’s the address of my server. I’ll look and see what I’ve done. This was intended to reflect your local device up so that it didn’t look for a Logitech media server elsewhere on the network.
Nothing looks wrong in the code(I must be missing something).
This should show the ip address of your roon server. This should be aut-detected but what happens if you edit to that and save?
Thanks
Peter