Roon Extension : RHEOS 2-way control & 192Hz/24bit Playback and Grouping on Denon/Marantz HEOS devices now in Extension Manager

Sean_dB · January 9, 2024, 10:59pm

Just installed RHEOS via Windows VM Box Dietpi. Worked great! HEOS Bar showed up right away but HEOS Amp HS2 is not showing up. Any ideas?

peter_richardson · January 9, 2024, 11:21pm

Not many ideas. I assume the Heos AMP is on the same network. Is it wifi or ethernet? I usually don’t hear of any issues with these players and the discovery is pretty reliable. Wifi can be a little more falkey (check the device is visible to the HEOS app).

It’s worth stopping the extension and restarting to see if it’s then discovered.

Not had reports of how this works in a VM setup - but if the HEOS Bar is discovered other devices on the same subnet should show up.

If you are able to share the logfile from extension manager I can see what’s being discovered.

Sean_dB · January 10, 2024, 3:21pm

Got it! Reinstalled on a rpi zero 2 w and it worked without a hitch!! Thanks!!!

Evan_Kohn1 · January 10, 2024, 3:27pm

@peter_richardson I really want this to work. I’ve just tried to install the container (no PIs but i have lots of containers running on a couple of NASes.

the container is crashing almost as soon as it starts with the following:
1/10/24 10:19 stdout code: e[32m’ERR_UNHANDLED_REJECTION’e[39m

1/10/24 10:19 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".] {
"
2024/01/10 10:19:54,stdout,

2024/01/10 10:19:54,stdout, ^

2024/01/10 10:19:54,stdout, triggerUncaughtException(err" true /* fromPromise */);
"
2024/01/10 10:19:54,stdout,node:internal/process/promises:289

2024/01/10 10:19:54,stdout, ‚ö† Please ensure RHEOS is enabled in Settings → Extensions

2024/01/10 10:19:44,stdout,STARTING HEOS

2024/01/10 10:19:44,stdout,STARTING HEOS CONNECTIONS

2024/01/10 10:19:44,stdout,172.17.0.5" Linux rheos-roon-extension-rheos-1 linux x64 Version : 0.8.4-8
"
2024/01/10 10:19:44,stdout,INITIATING SERVICES

2024/01/10 10:19:44,stdout,1/10/2024" 3:19:44 PM STARTING ROON
"
2024/01/10 10:19:44,stdout,STARTING ROON CONNECTIONS

2024/01/10 10:19:42,stdout,Node.js v19.9.0

2024/01/10 10:19:42,stdout,

2024/01/10 10:19:42,stdout,}

2024/01/10 10:19:42,stdout, code: e[32m’ERR_UNHANDLED_REJECTION’e[39m

2024/01/10 10:19:42,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".] {

Please let me know if anything stands out so i can correct.

thanks.

peter_richardson · January 10, 2024, 3:37pm

Thanks for sharing the log.
Allows me to see where the problem is likely to be - even if the messages are a little cryptic.

We’ve usually been able to get this running on a NAS. Would help to know more about your set up. What is the NAS and how is it networked?

What is the command line you are using to start this? Usually something like this works. You need to specifically define network host.

$ sudo docker run --name roon-extension-rheos --network host -v $(pwd)/.reg/etc/config.json:/home/node/config.json rheos/roon-extension-rheos:test

Is the NAS on the same sub net as the ROON server? How is your network set up.

Some folks have used a MACLAN address successfully.

Let us know how you get on. This is still in Beta, as I iron out some occasional niggles, so watch for updates and please let me have feedback.

Evan_Kohn1 · January 10, 2024, 4:20pm

@peter_richardson thanks for the quick followup.

the network setup is quite simple. Roon is up and running on a Mac mini M2.
I have a synology RS822 NAS, DSM 7.2, running docker on the same network.

Network is flat, no vlans, all the same subnet. i probably need to trouble-shoot some port conflicts (like 80) but that shouldn’t cause the rheos to shutdown.
thanks

peter_richardson · January 10, 2024, 4:23pm

Please try with the command line (edited for your local use) and let me know the outcome.

Thanks

Peter

patrick_mccarthy · January 10, 2024, 4:31pm

@Evan_Kohn1 are you using the Container UI to install and run the RHEOS image or are you using the projects “compose” yaml to run the image?

@peter_richardson references you use the ssh command line - I do not implement that way. Also, the mapping for the json file does not appear to work on synology’s implementation of docker - at least via either using the Container UI to create an image or using the projects compose yaml either. I will admit, I have never tried to create an RHEOS image using Peter’s ssh command line but given how synology works, I do not see how that fixes the json mapping issue.

for me, i do not map anything from host to container (no volume or file) and just have to reset my settings in the extension when i update his image - takes 30 seconds…

Try to not map the config file or anything else between host and image and see if it does not crash.

Evan_Kohn1 · January 10, 2024, 4:46pm

i went with the Synology container manager and tried to update any info there.

if there’s some install out there that uses portainer with the install files, i’d do have portainer running too.

patrick_mccarthy · January 10, 2024, 4:53pm

@Evan_Kohn1
below is a screenshot of my portainer STACK compose

i kinda lied about volume mapping – i do sometimes map a child folder in the container called rheos so i can use portainer to get into the running image can copy the config.json to my sub folder so i can get it “out” of the image - you will see that mapping below - you dont need it
i use a macvlan – so you will have to adjust the network to use host etc - since you use portainer, its easy and if not, i can create an example for you…
i am running the TEST image - i am almost always running the test image - i have the “latest” turned off as its my backup version back to 7.x of Peter’s app

peter_richardson · January 10, 2024, 5:38pm

Thanks Patrick. Your help here is invaluable.

Evan_Kohn1 · January 10, 2024, 5:54pm

Patrick, I really appreciate the assist.

I updated to the test version, and checked my paths and other info as best i can.
Unfortuantely it still stops with the same error.
I am not using portainer for this, just the native synology docker interface.

patrick_mccarthy · January 10, 2024, 8:01pm

so you are just following the GUI to find and download the image and then create it… can you share some screen shots? I ‘think’ way back in this thread I posted some example screen shots…

patrick_mccarthy · January 10, 2024, 8:17pm

so i just ran thru it with the GUI - then started it, got your same errors - steps below (will follow up if i find anything to change during the config in the GUI):

Test image used and I did not change anything during the creation (just clicked NEXT)

Noticing PORT 80 so you will see later on, it defaults to BRIDGE network…

summary:

note - bridge was created:

patrick_mccarthy · January 10, 2024, 8:51pm

@Evan_Kohn1

I built it via the project compose UI like so (image below):

i put this on the HOST network and it runs
it has errors in the log but stays running - this is because my ROON is on my macvlan network so the two apps never find each other…

here is the text - doesnt always format correctly here in this forum (still beats typing it all):

version: ‘3.3’
services:
rheos:
container_name: zroonhrc_rheos_test
image: rheos/roon-extension-rheos:test
network_mode: “host”
ports:
- ‘1255:1255’
- ‘1256:1256’
volumes:
- /volume1/docker/roon_rheos_extension_label_test/rheos:/home/node/rheos:rw

- /volume1/docker/roon_rheos_extension_label_test/node:/home/node/:rw

- ${pwd}/volume1/docker/roon_rheos_extension_label_test/config.json:/home/node/config.json:rw

  restart: 'unless-stopped'
  pull_policy: always
  environment:
    - TZ=America/Phoenix
    - PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

- NODE_VERSION=19.2.0

- YARN_VERSION=1.22.19

  mem_limit: 4096m

Evan_Kohn1 · January 10, 2024, 10:19pm

I do have a few differnces. Im not using a project is one.

FWIW, I eneded up taking an old pi and got it working via Roon Extensions, but eventually will like to have it live in a docker.

here’s some picts of the existing config.
I am also curious of the file structure, i assume i have my shared folders wrong.

peter_richardson · January 10, 2024, 10:33pm

Glad its working from the pi. Let me know how you get on. I leave it to you and Patrick to workout whats needed on the NAS. Please share so we can learn!

Evan_Kohn1 · January 10, 2024, 11:51pm

Hi Peter

I may have spoken to soon. When selecting my Marantz receiver in Roon audio, it gives me an error that manufacturer has not yet completed the verification.

Also which device is the Roon extension host up address?

peter_richardson · January 11, 2024, 12:01am

You are looking in the wrong place. Denon/Marantz HS2 enable players have started being shown as “ROON READY”. Unfortunately they are not - we are hoping they will be certified (and RHEOS will no longer be needed )

RHEOS makes any HEOS enabled device appear as a “SQUEEZEBOX”.

Assuming you have turned on “Enable Squeezebox support” in Settings setup you should see your HEOS devices appear in the Settings → Audio → Squeezebox section.

Here you can enable them and name them as you wish.

All of this is explained in the readme accompanying the Docker repository.

If you haven’t enable squeezebox support that would be why no devices were found and the app crashed.

Let me know if this helps - the ROON READY players appearing is very misleading but its down to Denon/Marantz or ROON to fix this.

Evan_Kohn1 · January 11, 2024, 12:04am

You beat me to it. I enabled squeezebox and now it works via the extension

Going back to try the docker version.