If you stop RHEOS what happens?
Rebooted fine. Watchingā¦
You may find this of help 
Thanks for tip! Iāll try it out. Iāve been using another CLI tool called Glances to get realtime utilization stats, so I can see RoomAppliance is the process that is swallowing ram.
So I think I have the same configuration as you. Roon installed on Ubuntu server with Rheos in a docker container. If true, have you ever seen this?
No - but I donāt watch for it either. Many reports on forum in general of this occurring. May not be an issue unless it crashes or impact performance ā¦
e.g. Roon server on Linux consuming huge amount memory even when not in use
After reading the forum posts, it looks like two issues may be contributing. The first is IP6. I donāt use IP6 on my network so I turned it off on Ubuntu. The second issue called swappiness and I implemented this change too. see below. Weāll see how it goesā¦
Hopefully. I donāt think this is a RHEOS issue.
Are your AVRs behaving? Do the x=zones come on and off for each.
I am thinking its getting time to put 0.9.3-13 out as ālatestā - Iāll be around over the weekend and able to address issues promptly, but it seems we have rooted out the issues cased by two way control.
I am also thinking of adding a setting to allow 2-way control to be on or off as not everyone uses the HEOS app or a remote control with their devices. Input appreciated on whether having these types of options is of use or adds to confusion.
Agreedā¦not a RHEOS issue, but top of mind for me. On the new version, everything seems to be working for me. Some testing on zones shows it is working as expected. More as time permitsā¦
1 Like
So I do not know the details of why a user would want 2-way control to be offā¦but
I do know, at all times, I would like all devices to know the volume state or at minimum, only do a relative up/down.
the wifey and I have ādiscussionsā over Spotify use on ātheā AVR - [the audio quality sucking b*lls being the first vs her loving the UI], but it has no idea the volume of the AVRās - everā¦ I am forever coaching the fam-damily to do volume down first, then up on their Spotify app when connected to the AVRs because a direct up in volume could cause Spotify to bump the AVR vol to 100 (luckily it tripped the surge device)ā¦
1 Like
Still no luck getting ROON to play nice with HEOS. I will continue to try.
Describe your problem and we can usually help.
Stephen,
You are running on QNAP right?
-
rheos is not crashing?
-
you have stopped rheos, stopped roon, then restarted roon, wait, wait a bit more, then rheos
** i find this helps roon cache every once in a while - but is of limited use -
in the extension authorizations, you only see rheos 1 time?
** it doesnt hurt to remove rheos, then re-add it in the extension area btw -
in the top of rheos settings you do not have anything in the default-heos or roon ip addr field?
-
in the upnp settings at the bottom, rheos found the IP address to your roon server?
-
you see the players in the list (from your prev screen shot it looks so)
-
you Deleted the fixed groups listed there?
** delete and save, to close rheos settings then go back to settings -
you turned OFF avr zones
-
you turned OFF fixed groups
now on to roon
-
in audio, do you see the 3 devices you have?
-
go to roon Setup and turn off squeezebox
-
go back to audio - do you see any ghost devices?
-
go back to Setup and turn on squeezebox (or click the button that says enable sbox in audio)
-
see if you can now see the audio devicesā¦
lets pause hereā¦
and in rheos settings, players you still see the list of your devices?
can you change one to hi res and save and then restart rheosā¦
then go back and see if it stayed hi-res between restarts of the docker
Are you running the container with network:host
i think he is running qnap bridged - so it could be that multicast is now allowing roon to see your exposed sbox devicesā¦
ā¦going dark for a bitā¦
When I change it the Hi-res, it just shows it Saving. It doesnāt look like it actually does save. It just keeps going.