Today, when I played from iPad or iPhone on Apple HomePods the volume goes suddenly to 100%.
I did the same test with my Mac, and playing on Homepod = the same issue. When playing on Mac speakers, or just on the iPad the volume stays the same.
Every device has the latest firmware: iOS is 26.5, Homepods are version 26.5 (23L471). setting for volume in Roon is ‘volume device’. Roon version 2.67 build 1661
Also, unplugging the HomePod and Nucleus One did not help.
Is there a known problem when playing on Homepods? Last week everything worked like it should.
Thank you for reaching out. We are not aware of a known issue with HomePods jumping to 100% volume. To investigate further, could you please note the exact time and date of the next occurrence and share it here?
Additionally, please send us your logs using the directions found here and upload them to our File Uploader. Once uploaded, please let us know so we can locate your files.
We’re eager to investigate this issue and we have verbose logging we’d like to enable for your account in order to pinpoint what’s wrong more precisely.
However, we haven’t seen a response to this thread, and we’ll require the following from you in order to take effective action from here:
a set of logs from your RoonServer (see post above).
An approximate timestamp of when the event last occurred (the name of the track that was playing).
thanks for your message. I uploaded the logs today. Strangely, the issue of the volume disappeared… I did nothing special, no updates (on either device) or something like that. I only had this issue on 7th June.
Glad to hear the volume issue seems to have resolved itself! That said, we’d still like to take a look at the logs to understand what happened on June 7th.
One quick note — it looks like the logs you uploaded are from the Roon Remote rather than the Roon Server. To get the server logs, please follow the guide shared before and upload the logs from your Roon server.
If the issue doesn’t come back we likely won’t need to dig further, but having the server logs from around June 7th would help us confirm the root cause.