Scrobbling on Roon to Last.fm when playing from Qobuz does not work, as the scrobbles are +1h. I.e. all in the future. Not sure what to do about it, but I'm on a trail now and don't think I'll continue with this issue.
The issue might be with Qobuz on that part, so my other issue is that when I activate last.fm in Roon scrobbles will be double.
Cannot turn roon scrobbling off, because then I cannot play my local files
Welcome to the forum and thanks for reaching out. Can you please share a few examples of scrobbles that have this behavior? Where are you located physically, is it in a UTC +1 country? I wonder if the playtime could have been accedentally sent in UTC time? As for the double scrobbles, did you start/stop playback for these tracks at any point or did they play through from start to finish? Let us know, thanks!
Streaming from Qobuz, without Last.fm Audioscrobbler in Roon.
Since Qobuz manages to scrobble ok from Sonos, on phone, etc, my guess would be that there’s something going on with how Roon plays music from Qobuz.
This is the output from Timedatectl on my Roon VM:
Local time: Sun 2025-09-28 18:25:22 CEST
Universal time: Sun 2025-09-28 16:25:22 UTC
RTC time: Sun 2025-09-28 16:25:22
Time zone: Europe/Oslo (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
This is correct. and it’s the same as on the host machine running the Roon VM. The host is running Proxmox.
Here’s the host output:
Local time: Sun 2025-09-28 18:26:21 CEST
Universal time: Sun 2025-09-28 16:26:21 UTC
RTC time: Sun 2025-09-28 16:26:21
Time zone: Europe/Oslo (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
If I activate the audioscrobbler in Roon, this is the result:
Please note that virtualized systems (VMs) are not officially supported by Roon. To help us investigate, could you try reproducing the issue on a bare metal setup (a physical machine) and see if the same scrobbling behavior occurs?
If the problem persists on a supported setup, please get back to us with the details and we’ll continue troubleshooting from there.
I can’t do that, as I no longer have a subscription or free trial period. Unless I know this will work fine, I don’t think I’ll continue with Roon now.
Nevertheless this worked initially, and the issue showed up during the trial period.
I also find the lack of VM or dockkerized support weird in 2025, but that’s not relevant for the case, just some general feedback.
We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.
You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.
We wish we had a more fruitful update, but this issue remains under investigation. We are making progress with the ticket and will comment with more information as soon as possible.
Thanks for performing that test, we have added this info to the investigation ticket. The ticket has been submitted for developer review, meaning that this may take some time to be reviewed.
There aren’t any additional details needed at this time, so we will go ahead and close the thread for the time being, and if any other questions arise after the developers have reviewed the case, we will re-open the thread and reach out once more.
Thanks again for your report, and thank you in advance for your patience as the ticket progresses through the development queue for review.