Thanks - I took a complete guess when I selected buffer sizes. I could set even bigger and change the defaults if we confirm this improves things? I think most folks have memory to spare thes days - I come from a time of floppy disks and counting every byte…
1 Like
I’m on a pi so limited in that capacity. Will keep an eye on it and see how it goes. So far so good.
And of course - some code improvements may be helping😉
1 Like
It was the same version so not sure about that for this I am afraid. But the other improvements are welcome.
Ah - well.
Fresh installs work wonders!
For any lurkers, I should add that automatic power up of the multiple receivers is something that not even the HEOS app does. This is a wish list for me but generally a minor issue.
1 Like
My goal is to keep ahead of the official integration…. If it ever gets here.
Too many years waiting. …
1 Like
@peter_richardson I will try out the groups tomorrow… to date, never works well in my environment…
can you give me instrucations on the following:
A. what do you want me to do to ‘reset’ everything in my environment for you before I test
B. Confirm: no groups in Heos app, make a group in Roon, go to settings, make static, save. Go to audio, go to new virtual device and enable and rename. Save and enjoy?
C. any other steps?
To date, volume gets batty and controls get batty when I try. Also, I am back to HI RES for the devices as your documentation says its better when more are grouped - so pass-thru or hi-res?
thanks,
Patrick
@Evan_Kohn1 /@peter_richardson - I “may” have this working but need to confirm a few things and the real test is when 0.8.5-1 roles out 
I will give details once i see its actually working…
1 Like
I think you are correct in the steps. Pick your most used combination. Make the group. Go to fixed groups and you should see it and select cd or hi res group. For background play I honestly can’t hear a difference .
When you save a virtual squeezeplayer should be created named after the first device in the group and the number of additional players. Enable that and call it what you will. I add a Unicode character at the beginning so they appear at the top of my zone selections.
Once enabled they should stay in the configuration (I know you may find this not to work 
- I promise we’ll get there!)
Selecting play on the fixed group will automatically group the configured players and they will ungroup on pause.
The fixed zone will appear as an output at the bottom of the group (takes a few seconds and sometimes a couple of tries) this can then control the volume for all the players - as in a HEOS group with the new app.
I use all the time for listening on the ground floor at home (4 zones)
Let me know how it works for you. Not perfect but it is getting better and Id appreciate feedback and ideas.
Peter
1 Like
What a tease …
Sweat!
I think to test, just delete your container and image if you can’t wait.
Looking forward to playing with heos, just haven’t had time.
0.8.5-1 loaded.
Fixed not saving default HEOS device address and added ‘giant ’ buffer option.
Hello,
Thanks for the works done 
I’m trying to install without success (latest 0.8.5-1).
I’ve enabled Squezeserver support in Roon and I can see the extension during 5 seconds and then it crash.
I’ve tried multiple things from this thread but it always end up with:
2024-01-14 16:19:17.494005+01:00STARTING ROON CONNECTIONS
2024-01-14 16:19:17.499435+01:001/14/2024, 4:19:17 PM STARTING ROON
2024-01-14 16:19:17.504983+01:00INITIATING SERVICES
2024-01-14 16:19:17.505095+01:00172.16.1.13,Linux,roon-rheos-ix-chart-78cb6655f5-57n7w,linux,x64 Version : 0.8.5-1
2024-01-14 16:19:17.506085+01:00STARTING HEOS CONNECTIONS
2024-01-14 16:19:17.506227+01:00STARTING HEOS
2024-01-14 16:19:27.503596+01:00⚠ Please ensure RHEOS is enabled in Settings -> Extensions
2024-01-14 16:19:27.511360+01:00node:internal/process/promises:289
2024-01-14 16:19:27.511376+01:00triggerUncaughtException(err, true /* fromPromise */);
2024-01-14 16:19:27.511386+01:00^
2024-01-14 16:19:27.511395+01:002024-01-14T16:19:27.511395130+01:00
2024-01-14 16:19:27.511405+01:00[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-14 16:19:27.511422+01:00code: 'ERR_UNHANDLED_REJECTION'
2024-01-14 16:19:27.511439+01:00}
2024-01-14 16:19:27.511447+01:002024-01-14T16:19:27.511447623+01:00
2024-01-14 16:19:27.511456+01:00Node.js v19.9.0
Any idea ?
What are you running this on?
Looks like a non supported os.
It’s in truenas scale (amd64) and it run as a docker app (using your official repo)
My roon and extension are running on the same system using host networking with a dedicated IP.
No experience with this NAS. Others may be able to help but I wnt be much help I’m afraid.
Read the thread and see if any of the pointers made help.
Sorry.
Peter
If you look you’ll see a similar error reported when you don’t specify network:host in the command line. For docker…
I’ve finally found a workaround for this platform (removing default interface so RHEOS found the right IP)
Now I detect my AVR but in audio there is no Squeezebox found.
EDIT: Finnaly found it after some times
1 Like
Glad to hear.
Please share any feedback and workarounds.
Let me know how it works.
Thanks for testing.
1 Like