Okay, some update. Weird update.

I just got some scrobbles pushed to last.fm. About 12 songs I supposedly listened to within the last 4 hours. I did not listen to songs the last 4 hours. So not only is the scrobbler probably pushing with an extreme (!) delay, but it is also using the timestamp of the scrobble to last.fm and not the timestamp when the song was actually played.

I’m sorry, but this thing needs to be reimplemented. It is dysfunctional and even under best circumstances working wrong.

I sent an email to Deezer about this and (myself and it seems many others according to the last.fm support thread) received this mesage:

Thank you for your patience.
 
We have investigated the issue and found that the cause is not on our side. Please contact Last.fm directly to resolve the matter there.
 
Best regards

So it kind of seems they’ve wiped their hands clean of any fault, even though there are no technical details given and last.fm seemed to have a better understanding of what might be causing the block/delay?? Very frustrating!

This is also happening to me. Very frustrating. My first time using Deezer's internal scrobbling option (I was using Pano Scrobbler before). What's the point of having the option if it does not work as advertised?

This is utter bullsh*t. Sorry for my wording, but it is.

I just tested it with foobar2k and the scrobble plugin from 2010 (!) and it works flawlessly. I even get the “Scrobbling now” icon in last.fm when the song is just playing.

Could you respond to the Support guy and point him towards this thread? Or share how you contacted him in the first place?

Thanks for your efforts :)

Not a problem! I did respond asking them to re-investigate and got a reply this morning:

Thanks for the reply. 
 
We have started the investigation and will get back to you once there are updates. 
 
We are really sorry for the inconveniences. 
 
Regards

​

Yes, I feel you.

I would actually also like a common standard for scrobbles. I have seen some FOSS solutions covering last.fm like stats and scrobble mechanics, but at this point I don’t see any issues with last.fm, and I like their recommendation engine :D

I also just filed a support ticket and already took the wind out of their sails by stating that the issue is not on the side of last.fm and also the timestamps is wrong, showing that the problem is most likely a buggy implementation of the scrobbling in Deezer.

Let’s hope it will help.

​

Hey everyone!  

It’s a relief I’m not the only one with this issue. Waiting impatiently for the solving… 

Hello,

We are working with the Last.fm team to have this issue resolved.

It’s currently on its way and catching up on old scrobbles.

It should be all back to normal soon, I’ll keep you posted.

Deezer submitted my remaining old scrobbles about 20 hours ago, and currently they are showing the last scrobbled track when the next track starts. This is the normal behaviour for the internal Deezer scrobbling option, as “Scrobbling now” is not showing in the recent tracks list on the Last.fm user profile.

Mine seems to be working again this morning! :)

Same here! Thank you, developers! 🥳