I'm using subsonic (5.0, going to update soon) on a dedicated server located in France, while living in Japan. I noticed that a few month ago, the scrobbling to lastfm stopped working.
My lastfm account uses the timezone of the place I'm living (UTC+9), while my dedicated server is on the timezone of the place it's located (UTC+1).
So looking at the log of subsonic on my dedicated server, I got this warning:
[2015-09-26 08:58:32,780] WARN AudioScrobblerService - Failed to scrobble song 'xxxxxxxx' at Last.fm. Bad timestamp, please check local clock.
I suppose, given my configuration, that this warning makes sense. I just wonder while it worked for years, and suddenly stopped working. Might be related to the changes they're doing at lastfm.
So now I'm looking for a way to fix this problem. I think (hence the title of this topic) that it would be good if each users of a subsonic server could be able to set its timezone, and then have this information used for lastfm scrobbling and everywhere else it makes sense.
Meanwhile, has anybody have a proper workaround for this problem, so I could make scrobbling work again? I can't really change my dedicated timezone, and I would like to keep my lastfm account in the Japanese timezone.
I also noticed that subsonic is using the old deprecated 1.2.1 API from lastfm, there's a version 2.0 and updating subsonic to this version might solve my problem as well.
Thanks
PS: not sure if this topic should be in the Feature Requests or in the Help board, feel free to move it