Oh yes this was a big win for Sonos and scuppered the original plans to basically copy their concepts by sound unlimited. Well worth googling if you are interested in the ip real estate SONOS got approved. Most of which I always thought were first thought out by the old slim server open source code …
So I pushed a small update that addresses the grouping of AVRs with multiple zones turned on - which seems to work better.
The individual zones will join a group and can be turned on and off using their respective power controls just like any device.
Let me know if you find problems.
Peter
After the latest update Rheos keeps crashing on my Synology (DS220+) - any suggestions? Thanks!!
rheos-roon-extension-rheos-1
date | stream | content |
---|---|---|
2023/12/17 22:40:17 | stdout | Node.js v19.9.0 |
2023/12/17 22:40:17 | stdout | |
2023/12/17 22:40:17 | stdout | } |
2023/12/17 22:40:17 | stdout | code: e[32m’ERR_UNHANDLED_REJECTION’e[39m |
2023/12/17 22:40:17 | stdout | [UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason “No devices found”.] { |
2023/12/17 22:40:17 | stdout | |
2023/12/17 22:40:17 | stdout | ^ |
2023/12/17 22:40:17 | stdout | triggerUncaughtException(err, true /* fromPromise */); |
2023/12/17 22:40:17 | stdout | node:internal/process/promises:289 |
2023/12/17 22:40:17 | stdout | ![]() |
2023/12/17 22:40:07 | stdout | STARTING HEOS |
2023/12/17 22:40:07 | stdout | 172.17.0.2,Linux,rheos-roon-extension-rheos-1,linux,x64 Version : 0.8.4-5 |
2023/12/17 22:40:07 | stdout | INITIATING SERVICES |
2023/12/17 22:40:07 | stdout | 12/17/2023, 9:40:07 PM STARTING ROON |
Try powering down and reinstalling if this persists. For some reason the start up is failing. Are you able to share a copy of the log fike?
how are you creating the rheos docker image - can you share the details (are you using the container UI, container projects or ssh compose or…?)
Thought I had it working again, but unfortunately it keeps crashing again. I am installing the container in line with the instructions in this thread. I have this issue since the last update.
Try changing the file path to read/write and execute permissions. You may want to try running as sudo.
Update - apologies the last version I uploaded had a copy of my local config file. This may cause issues for some of you. Please download and reinstall the latest images I have just posted.
Thanks
Peter
I got it to work again - thanks! Only thing I do not dare to touch now is the player resolution. When I tried to change this from CD quality to high resolution everything started to crash last time.
Shouldn’t be an issue.
With high res players some folks like pass thru mode.
Happy to help if you get stuck again!
@peter_richardson , @Bas_Verlee
Peter, is the node version 9.9.0 ?
-
in my ‘latest’ docker pull, i still had 9.2.0
-
but in my ‘test’ docker, i commented it out completely
-
also, there is no need to map any folder to the image - its not used in this setup – you would do it only if you manually install his program into an image… - I would take it out for now…
-
now, i DO map an rheos folder into peter’s container as a sub folder to the home / node directory of the user running his app… I do this so i can bash into it and copy his config file to my subfolder and then fetch it from my synology NAS… no need to do any of this of course… here is my mapping
/volume1/docker/roon_rheos_extension_label_test/rheos:/home/node/rheos
Lastly, Peter, Bas has his docker in BRIDGE mode - any issues - its been so long since I didn’t use macvlan’s for this I have forgotten if he should use HOST or BRIDGE is ok…
patrick
future feature request for rheos volume control:
I know you cannot use the slider control due to feedback delay… could we have the volume number shown as text next to the + / - buttons so we know WHERE we are in the volume
Sorry - not under my control wrt numbers.
I actually use the slider ….
Or use fixed and disable this apart from The individual zones which reflect the actual settings on the receiver …
I have the docker in host mode, bridge indeed did not work
Thanks. I always use host.
Peter
Update to 0.8.4-6 loaded to docker and available via extension manager:
- Improved creation and deletion of fixed groups.
- Fixed bug where fixed group volume changes could flood the system
- Changed default log file size from 1 to 100Mb
Enjoy.
Hello,
@peter_richardson
Thank you so much for developing RHEOS! It’s exactly what I need – using an Marantz amp while still able to enjoy Hi-res music from Roon.
I’m new to this app and have tried to install it yesterday on my Synology DS923+ (which is my Roon server).
I installed the image in the Container Manager, and I can see RHEOS and enable it on my Roon > Setting> Roon Extension. And it correctly showed 1HEOS Player on rheos-roon-…
However when I go to my Roon > setting > Audio, nothing seemsed to have changed.
I can only see my Marantz SR6015 (via Airplay) and everything was the same as before I install RHEOS. When I tried to play the music, it’s still via Airplay ( 16bit/44.1 kHz)
May I know if I have missed something or have done any steps wrong?
Thank you so much in advance.
Did you enable squezeplayer support in roon? Settings → Setup → Enale Squuezebox Support
If you do this the HEOS device will show in Settings → Audio → Squeezebox
If not we need to see if theres anything unusual with your system
Best
Peter
It turns out the problem was that I didn’t enable “squeezebox support” in Roon setting.
After doing so it works!
Thank you again for this fabulous app.
@peter_richardson I am noticing every now and then the extension stops being gapless for playback. Just had an instance and it had a long pause at the track boundary. Played it again and it transitioned gapless. Not sure if this is a Roon issue or the extension. I have had it happen a few times and a restart of the extension often sorts it if it continues. This is my own music not from streaming.