I have been using Roon for a few weeks now and, so far, I am really enjoying it. One issue I’ve noticed is that under “Recent Listening” it shows 0m and all my last four weeks of history are all at 0 minutes.
It shows 0 minutes on my iPad, the Windows app, and on the Android app.
Recent Listening was populated but at some point in the last few days all history (Last 4 weeks) reset to 0 and is not incrementing. My listening history seems to be fine and shows all the tracks I’ve listened to back to April 28 (which is when my Rock was built).
The only thing I’ve done to my system is backup my Rock and then setup a backup schedule.
I’ve had the same issue since the latest update arrived this week. A full reboot of my Linux laptop running my Core solved the problem here. Now it’s showing the correct listening time.
This is a daily occurrence now.
Rebooting the core ‘fixes’ it
My core now takes over a minute to find every morning and I don’t own an android device that I can use for a remote without restarting it between every song. I’m unsure how only I have this issue. Android 10 and 13.
I’m feeling like a lot of regression is occurring as new features are added. That is a tough balance.
Thank you all. I rebooted my CORE and all the listening data returned. Thank you. I will let you all know if it “stays” or if it goes away again and I have to reboot later to “fix” it.
My setup or situation my differ from others but I’ve been noticing the zero minutes for a long while going back numerous updates. On my windows laptop remote it will happen daily, seemingly when the new day occurs. Simply restarting the remote software gets it back to normal, no booting laptop or NUC core.
It appears to happen at midnight. The log file this is reading resets. I’m not sure how they are populating that table but it doesn’t appear to know to reread the log until the client/core is restarted.
It use to be. Leave the client up overnight. this occurs.
A quick close of the client would repopulate the data.
today, if you leave the client open after midnight, you have to reboot the core to repopulate the data.
I have no idea what caused that slight change for me.
It does appear related to scheduled backups. Forcing a manual backup doesn’t break it; switching views doesn’t break it, and it is tied to a Profile. When it shows “0” for the Profile last used, changing to another Profile shows the correct calculation for that Profile. Switching back to the last used Profile returns to “0”.
Definitely related to Core (I’m using a NUC), and all Remotes display the same error until restarting Core/Server. Fortunately a cosmetic issue that’s a minor inconvenience.
