I run a mini pc with (nuc) linux installed - as my preferred option. Even if the pc isn’t up to functioning as a ROON server it will be adequate for RHEOS and most other extensions.
Easy to use a docker container directly …
Peter
not sure which thread you are replying to but you were unable to find the config file?
when i would run rheos as a docker without mapping the config file to the host, rheos would use the embedded one peter ships with the docker image… from there, you could ‘bash’ into the image and see the config file… the settings would save this way but would be lost when you updated the image…
when mapping the config.json file in docker, you have to create your own empty config file on the host and map it into the image, rheos will see the empty file and do its thing…
Sorry, I must have hit the generic reply button. It was a reply to CrystalGipsy’s suggestion.
I crashed out last night so haven’t tried the YAML yet. I’m sure I’ll be fine, I’m quite techie 
Not sure what json file has to do with dietpi? You dont need to run anything separatley in docker as Roon extension manager manages it all, you just install docker then extension manager, install RHEOS from Extension Manager, bobs your Uncle it works. No messing around.
2 Likes
@patrick_mccarthy
Love Yello… Band built for good hifi!
@Kent_Frese and I only recently saw for the first time the silly video for Kiss in Blue because of some video feed on tidal on roku and it got me scrolling thru their albums again. then looking for work from Heidi Happy
Every whichway I run Rheos has the same issue, Rheos crashes because it can’t find any players. The only way I’ve found to avoid this is to edit the default settings JSON config file giving it the IP address of my amp.
You have something unusual on your network setup.
Not able to download latest, it’s still pulling RHEOS 0.8.6-0
I did stop RHEOS, prune the images (once container stopped) and re-installed.
I did uninstall RHEOS
I did remove the app, containers and images and reinstall
all end up with 0.8.6-0 (I did also try a to update RHEOS via roon extension manager)
Any thoughts?
my docker composer command (with adding to group 0 not ideal)
version: ‘2.4’
services:
rem:
image: theappgineer/roon-extension-manager:v1.x-standalone
container_name: roon-extension-manager
group_add:
- ‘0’
restart: unless-stopped
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- rem_data:/home/node/.rem/
environment:
- TZ=America/Vancouver
network_mode: bridge
volumes:
rem_data:
Extension manager 8.6.0 is the only one available. Other versions are for testing and only available via docker directly.
1 Like
If you are pulling direct from docker pull the image tagged with test.
I should be updating this over the weekend and would appreciate feedback.
If you use extension manager 0.8.6-0 is the current version.
Peter, it’s too bad Extension Manager won’t let you publish RHEOS and RHEOS-BETA as two extension options for everyone that uses EM (or maybe they will?). I actually like having each of my Roon extensions on their own docker image so I can control every aspect of the deployment and not rely on the ‘middleware’… but I can see the alure of a single place to install extensions.
@Sean_Fowler
so even using the yaml in synology container manager, mapping to an empty config.json file in the folder and granting everyone read/write to the folder fails? IF you do this via synology docker, you will capture all the logging peter does - can you paste here?
1 Like
Agreed. The only slightly unusual thing I can think of is that my IP range is 192.168.2.nnn rather than 192.168.1.nnn.
I have an Orbi mesh system but that’s pretty mainstream. I’ve gone through the settings and disabled anything that looked like it might have an impact (although they were WAN settings so shouldn’t matter) but it made no difference.
Anyway I’ll try Patrick;s suggestion and see how that goes.
Unfortunately the last three nights I’ve fallen asleep whilst settling the lads. The good news is I should now have more mental energy (well it’s a nice theory ).
1 Like
Hi Patrick, well I learned some stuff and got some different results than previously so I’m calling that progress
It still bombs out even with the config.json and/or default_settings files replaced. It does show up in Roon extensions (until it crashes) and if I open the settings I can see the IP addresses from the config/default settings files so they’re being picked up.
Interestingly in the logs it mentions my amp but via Airplay and also my ifi DAC. That’s new.
Here’s the log:
| 2024/03/16 13:40:16 | stderr | Node.js v19.9.0 |
|---|---|---|
| 2024/03/16 13:40:16 | stderr | |
| 2024/03/16 13:40:16 | stderr | } |
| 2024/03/16 13:40:16 | stderr | code: ‘ERR_UNHANDLED_REJECTION’ |
| 2024/03/16 13:40:16 | stderr | [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.] { |
| 2024/03/16 13:40:16 | stderr | |
| 2024/03/16 13:40:16 | stderr | ^ |
| 2024/03/16 13:40:16 | stderr | triggerUncaughtException(err, true /* fromPromise */); |
| 2024/03/16 13:40:16 | stderr | node:internal/process/promises:289 |
| 2024/03/16 13:40:08 | stdout | SUBSCRIBING Marantz Air 1701f47c722a81071f0dade09b673cc04f7d |
| 2024/03/16 13:40:08 | stdout | SUBSCRIBING iFi 1701b9b9a2c2e9dbac2608ff660488afa2c3 |
| 2024/03/16 13:40:08 | stdout | 3/16/2024, 1:40:08 PM ROON PAIRED com.RHEOS.latest |
| 2024/03/16 13:40:06 | stdout | STARTING HEOS |
| 2024/03/16 13:40:06 | stdout | STARTING HEOS CONNECTIONS |
| 2024/03/16 13:40:06 | stdout | 192.168.2.248,Linux,DiskStation,linux,x64 Version : 0.8.6-0 |
| 2024/03/16 13:40:06 | stdout | INITIATING SERVICES |
| 2024/03/16 13:40:06 | stderr | 3/16/2024, 1:40:06 PM STARTING ROON |
| 2024/03/16 13:40:06 | stdout | STARTING ROON CONNECTIONS |
Are you using a docker image or have you installed via another route?
This is the docker image on the DiskStation, using Patrick’s YAML to replace the config.json and/or default_settings.json. All combinations of replaced file give the same result.
The unhandled promise rejection is the same error I normally get when I don’t provide the player’s IP address, but those JSON files are being picked up as mentioned previously.
I’ll let Patrick see if he has any ideas.
so you modify the default settings file inside the image OR are you mapping that file - i am not sure how you can map that file without having a copy of the data for that file, since mapping it means the host has to have the content before you start the image…
can you post your copy of your yaml or pm me directly? also, can you pm me screen shots of the file path and the permissions on the subfolder under the docker folder? lastly, do you mind PM’ing the contents of the config.json file too – it should have started empty but then get data even though it crashed…
- so the docker image gets the error and then restarts… how long does it stay running before crashing?
Lets use Peter’s new test image - he is fixing it but it has some detailed logging the stable versions does not:
- change my yaml from :latest to :test in the image section
- let is start up with an empty config.json file (delete the file and put an empty file or delete all content in the files – do not modify the default file)… wait until it crashes then STOP the image (it will restart due to the yaml setting)
- then we can go into the config.json file on the host and lets do two things:
a. see WHAT was written
b. change the custom logging attribute peter has from info to debug
c. start the image… let it crash and stop it after it trys to restart…
d. capture the debugging detail and let us have a look
I still believe you have a file permission or network issue outside of rheos – @peter_richardson - your code should not crash because it cannot find devices or roon, right?
1 Like