Using both ipad or iphone with roon endpoint on my Hegel H390 both volume buttons only increase volume, that is the physical buttons on my ipad/iPhone both only increase the volume in roon/hegel amplifier. Been like this for 3 ios releases and for all roon releases this year
Describe your network setup
Wifi for ios devices and lan for Hegel and for my roon rock nuc
Strange. I also have a Hegel H390 and I use an iPad, but both volume buttons behave like they should.
I can’t think of any setting that causes the behaviour you’re experiencing.
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
Hi sure, I will try also including a video/screen recording of the issue occuring on my iphone.
In the video you can see on the ledt side what buttons are being pressed, and that they both
increase volume, untill I specifically open the graphical volume control in Roons bottom right, then it starts working correctly.
The date time stamps for your logs is
CET (Stockholm time) 2025-09-01 12:35
Could you please let us know whether you can normally control the volume from the slide bar in Roon mobile remote ?
Also, does the issue persist if you on your iPhone set the media control with buttons instead of Ringtone control ?
And the last questions would be: if you play the music to your iPhone and not to your DAC can you normally control the volume or the issue still persists ?
We wanted to reach out to ask if you were still encountering this issue. Our QA team is eager to investigate, but we’ll still require the logging requested in the previous post from 26 days ago. Please let us know if we can clarify any of the steps above.
We’re pinging this thread again before it closes due to inactivity. Our team will has not been able to access the diagnostic logging we require to take action on this thread, so we’ll require you to upload manual logs and share an approximate timestamp of when you last encountered the issue.
You can find specific instructions for how to do so in @alex_h’s post above.
Without a response from you, this thread will close shortly, requiring you to initiate a new support request to reactivate the conversation. Thanks!