Thanks @Kent_Frese - you use the Extension manager, correct? so when you uninstall and re-install it creates a new signature for ‘enabling’ the extension and it starts with a fresh config file?
I will have to see about mapping a blank config.json file and restarting the image…
@Kent_Frese , @peter_richardson
That did it: told portainer to repull the image, stopped rheos, made a backup of the config.json file, then emptied all the data out of the config.json file (empty text file), saved and restarted rheos…
changed the following items:
started playing some Boston 
life is grand…
My money is its not the re-pulling the image, rather something in the config.json file between these version fixes Peter that is causing an issue?
I have a copy of the “offending” json file if you want it Peter…
spoke too soon… its hit or miss on advancing to the next song in the queue - got by Boston but did not get by Dire Straits…its on Toto right now… will let you know…ha
I have what the issue is.
Have been working on an off all day to fix but not quite there (it wont be an issue if you don’t enable the same devices in Airplay and RHEOS). Its do do with the 2 way control and that interferes with the airplay device (I never had them enabled in my system).
However - I have uploaded the old 8.6 trusted version and will pit out a test again when I have this fixed.
Apologies to all. Should make progress tonight but may take longer.
Peter
Thanks Peter, and no apologies… you are working way more on this than any of us expected.
And I’ll make an archive version of 8.6 available on docker.
Hi Peter, I had a go with Appgineer via VirtualBox. Appgineer appears as an extension and I can add Rheos via that.
Holwever Rheos doesn’t seem to find my amp, although it’s hard to tell. I need to give it my amp’s IP but when I try to enter it in the Rheos settings (from the extension page) it doesn’t save. The Rheos extension keeps briefly disappearing and reappearing on that screen, which is odd (I wonder if it’s constantly crashing and restarting). Perhaps if I could find the Rheos config file in the image I could enter the IP address there but I haven’t been able to find it (perhaps it’s stored within Appgineer?)
I’ve also tried the Docker image. When I give it the amp’s IP it finds the amp. However Roon doesn’t see the Rheos extension so that’s as far as I get. Disabling the WIndows firewall has no effect.
Forgot to mention, I also tried updating the WIndows installation as you said but unfortunately the behaviour remained the same.
The crashing and cycling typically means it cannot find a config file, empty, or otherwise.
i’m not sure where you would give Peter’s application the IP address of the amp other than the default device, which is not needed as long as you were on the same subnet and don’t have any firewall issues on the windows box network card.
something about the security and the config file, and or the network interface seem to be the issue.
let’s try something different, completely separate from this to see if it’s an issue with Peter‘s app or with your configuration…can you look for macroon as a docker image… this little app does not require much for configuration, I think it needs a volume mapping to save your settings, but it’s just a simple extension to roon… if I get a chance here soon, I will add or edit this post and get you the link to it. this cool little app just allows you to hit a webpage or URL to adjust Roon but it’s a perfect little docker image to test your environment from Peters app. if it runs and can find roon then we know it’s something with Peter’s app or file permissions, if it does not then we know it’s your network or firewall, etc.
its actually macro.on…
Roon Extension: macro.on - Tinkering / Roon API - Roon Labs Community
Thanks for your patience and understanding.
A lot of updating today to address the issue uncovered with Airplay interference and bi-directional control.
To address this, I have changed the ways that players are identified and you will see that auto-magically they are named as your chosen HEOS player name + (RHEOS) + model. This will not affect the names you have previously configured which remain independent. They will change if you alter them in the HEOS app. This allows me to identify RHEOS enabled players from those that are AIrplay - or indeed when ROON READY certified as I would have problems mixing there.
I have tested this, but am only loading to the test docker “image” so others can check before going to extension manager and “latest” image.
I will move 0.8.6-0 to an archived tag in Docker and post the code in case needed.
A couple of other things have been added to help me with some issues. In settings, I have added an option to select various log levels. and the ability too vary how frequently AVRs are polled for their status. This will be helpful as I try to understand what is happening with the AVR zone issue Kent is having and I want much more detail in the logs - but want you to be able to control what is spewed out. At present set to “Monitor” to give me more information. AVR polling defaults to every 3 seconds - set to zero to turn off. I will be adding to this over the next sessions to help when I am tracking down issues.
I certainly hope this addresses the issues of today and you can get back to enjoying some music.
I’ll be thinking about the windows question - and whether its really worth supporting this going forwards. Do let me know if the changes made today help here as well.
Thanks Patrick, I’ll give Macro On a go later
Every different way I’ve tried Rheos I’ve had to give the IP of the amp. I only have one HEOS device though so that’s been fine.
I was able to find where to put the IP on the docker image, which did then find my amp, but not in the Virtual Box.
Another thing I can try is running Rheos on my Synology NAS but still having the Room server on my Windows mini PC. Just to make things really complicated 
That’s a very typical set up.
RHEOS needs relatively little power and others have it running nicely on their NAS.
@Sean_Fowler any reason to not run both on your Synology NAS – there is a direct package you can run, or like myself and others, run both roon and rheos as docker images. Happy to help. We can cobble together a project compose script for the Synology Container Manager OR go thru the UI too… Personally, I use portainer instead…
I suspect your windows firewall is creating the issues both with it’s allow/deny settings AND its treatment of the network stack (whether it is properly identifying it as private or public both on the NIC and on any virtual NIC).
Let me know your interest in moving to all NAS…
PS - what model synology are you running?
running 0.9.2-03 now… set to debug and 10 second monitoring… up’d the log to 2048… is there something particular you would like to see from the logs as i test?
edit: was getting the ‘won’t advance to next track issue and it would show 2 seconds longer than the track length’
So I went to settings and: REFRESH HEOS PLAYERS…started playing track, dragged location bar to 15 seconds before end of track… it appears to advance to next track now… will update again if it stops…
UPDATE: set buffer to small, picked a ‘trashy’ playlist and started it… running perfectly now… will test back and forth between buffer sizes and classic vs shameless playlists to see which is the issue… 
2024-03-12T18:12:23.585711596Z 3/12/2024, 11:12:23 AM 
Office 
One of These Nights (2013 Remaster) - Eagles
2024-03-12T18:12:45.259138385Z 3/12/2024, 11:12:45 AM Office Hide In Your Shell - Supertramp
2024-03-12T18:17:35.052475478Z HEOS SOURCES CHANGED {
2024-03-12T18:17:35.052962998Z heos: {
2024-03-12T18:17:35.053009307Z command: { commandGroup: ‘event’, command: ‘sources_changed’ },
2024-03-12T18:17:35.053050347Z message: {}
2024-03-12T18:17:35.053078077Z }
2024-03-12T18:17:35.053101347Z }
2024-03-12T18:17:35.135460154Z HEOS SOURCES CHANGED {
2024-03-12T18:17:35.135574354Z heos: {
2024-03-12T18:17:35.135604384Z command: { commandGroup: ‘event’, command: ‘sources_changed’ },
2024-03-12T18:17:35.135635674Z message: {}
2024-03-12T18:17:35.135660224Z }
2024-03-12T18:17:35.135682794Z }
2024-03-12T18:20:25.163134131Z HEOS SOURCES CHANGED {
2024-03-12T18:20:25.163631591Z heos: {
2024-03-12T18:20:25.163680981Z command: { commandGroup: ‘event’, command: ‘sources_changed’ },
2024-03-12T18:20:25.163724071Z message: {}
2024-03-12T18:20:25.163753261Z }
2024-03-12T18:20:25.163778081Z }
2024-03-12T18:20:25.228699198Z HEOS SOURCES CHANGED {
2024-03-12T18:20:25.228812438Z heos: {
2024-03-12T18:20:25.228839698Z command: { commandGroup: ‘event’, command: ‘sources_changed’ },
2024-03-12T18:20:25.228875388Z message: {}
2024-03-12T18:20:25.228898748Z }
2024-03-12T18:20:25.228919988Z }
Hi Patrick, I gave macro.on a try. Running directly on Windows it was fine and Roon saw the extension.
However when running the Docker image Roon couldn’t find it. I think this is expected, from the macro.on Docker page: " --net=host uses the host’s network stack inside the container. This is needed to make the discovery of your Roon core work. Please note: The host networking driver only works on Linux hosts, and is not supported on Docker Desktop for Mac, Docker Desktop for Windows, or Docker EE for Windows Server. (Host network driver | Docker Docs)".
I guess this may mean that the Docker image isn’t viable on non-LInux hosts, if Rheos has the same dependency as macro.on.
It’s odd. I left it running overnight and never skipped a beat.
Let’s compare UPnP settings!
you need network = host.
I had both Roon and Rheos on my Synology way back (DS1019+) but it’s not that fast and Roon recommend an SSD (which my mini PC has). When I looked at adding an SSD to the DiskStation the way it’d be used wouldn’t have been suitable for Roon.
I’ll try just having Rheos on the DS and see how that goes. I bought the mini PC primarily for Roon (and to plug a DAC into) so I’m keen to at least keep Roon on there.
