Issue with Endpoint Defaulting to 100% Volume on Server Restart (ref#PITP3I)

Affected Product

Roon

Roon Issue Category

Playback

Description of Issue

I have an issue with my install.

I have 3 endpoints : all are roopiee running on raspberry pi’s (one rpi3’s and one rpi4 I believe). After them comes always a dac then an amp then speakers.

Now, I have the habit of restarting my server quite often. It runs on a Linux (Ubuntu) laptop.

The issue: on server restart one (and only one) of the endpoints defaults to 100% volume. This is very annoying as I usually play music on the three endpoints simultaneously. The other two endpoints go back to the last volume value upon server restart.

Where could I start looking to solve this issue?

See attached picture. The troublesome endpoint is in red, which is also… odd. The only thing making it special is that it was added last and it is connected to outdoor speakers (with a dac+amp in between). I believe this is also the one on a rpi4 and not 3. Other than that and the fact that the dac is the only one from hifiberry (it’s a hat for the rpi) I see nothing setting him apart.

Thank you so much,

Roon Core Platform

Linux (NAS/SonicTransporter/Antipodes/Ubuntu/etc.)

Linux Core Type

Ubuntu

Roon Core Specifications

Ubuntu

Connected Audio Devices

See issue description

Home Network Details

Roon core connected via Ethernet.

Hi @Gustavo_Lucena_Gomez ,

Thanks for reaching out.

It doesn’t look like your picture came through properly, can you please re-upload the screenshot directly on your forum post? Here is a guide on how to upload screenshots to the forum:

What kind of volume control do you use in the Device Setup for that device? Is it on Fixed Volume, DSP Volume or Device Volume? Is it using the latest firmware?

Also note that you can set volume limits for the device, to ensure that it does not get too loud as you troubleshoot the issue.

1 Like

Just a thought, within RoPieee settings are they set to 100% by default. This inturn will set Roon’s volume to 100% upon a reboot. Might not, but I recall having a similar issue with RoPieee

Thanks to everyone for the help.

Dumb me: did an update on the faulty RPi and that did the trick.

The culprit I believe is that this particular RPi, unlike the other two, was running Roopiee XL and not just Roopiee.

Thanks again,

2 Likes

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.