……now it changed to: upgrade required deezer: 3115072.

????

I have the same problem with an m10v2 but different error code "Upgrade required Deezer: xxx xxx 418". but only with different artists and titles.

I have the same issue. Happening on about 20% of tracks when using Bluos. Never had an issue before. It needs sorting ASAP

same issue on nad m66 with deezer only.. all bills are payed but deezer service lacks. do anyone from support read here or is it 127.0.0.1

btw,.. on random tracks an on several deezer radio station too

​@Jaime.Deezer Could you please take a look at this and/or pass this to the developers? 

Same issue here...i have reported this as well in the bluesound community : https://support1.bluesound.com/hc/en-us/community/posts/28168609313431-Upgrade-required-Deezer

J'ai le même souci. Obligé de connecter mes diffuseurs Bluesound Flex 2i via Bluetooth pour contourner le problème de l'application Bluos en passant directement par l'application Deezer. Pas normal. Faut-il arrêter l'abonnement Deezer pour aller sur un service de streaming plus fiable ?

Hab auch das Problem. Streame zzt über Bluetooth. Der Fehler tritt, wie bei anderen nur bei bestimmten Alben auf. 

...and you are not using bluesound?

I use node 130n. When i connect with Bluetooth, all is ok. When I use Bluos the error occurs

Seems to be a problem with Bluos update 

I hope, in future Deezer Connect will work with Bluos. Would be more comfortable 

It's freakin' annoying - it did well for a while yesterday night and now it stops after every few tracks again. Deezer support must have picked it up by now - c'mon guys!

yes I am suffering this too!

really annoying.

I suspect the problem was introduced in BluOS 4.8.7 

If I had known I would not have updated to the latest/greatest(?) version

If it's a BluOs update bug the bluesound support team needs to be addressed. This could take a while to be fixed.

https://support1.bluesound.com/hc/en-us/community/topics/200546948-General-Discussions

I have the same in the Netherlands with two different Bluos players (Node and N2.

Could be relay on both, deezer and bluOs!  Neither qobuz or tidal is affected on my m66. The message reads as a security feature of deezer, priviledge level issues on streaming client accounts. Should be easy to reproduce on any responsible dev account... if someone like to take care on this bug

Just to add also to this thread. 
 

Same issue here with Deezer on Bluesound B100S.
 

The error number corresponds to the Deezer <track id>, so thats why you may keep seeing a different one. Unless you try playing the same track over and over.

I’ve also logged a support ticket with Bluesound.

Hopefully here at Deezer ​@Jaime.Deezer can find a developer. Let me know if a developer wants to see a log file. 
 

Happy squashing bugs!

From what I’ve been reading, it looks more like an issue that happend after an update from Bluesound. So let’s see who is giving their answer and update first.

I have the same problem

Player Notification

Error: Upgrade Required

Deezer:132988618

Player Notification

Error: Upgrade Required

Deezer:132988.24

bluesound says the premium content is no longer available via th Deezer API and to contact Deezer 

Bluesound seems te be working on it, in collaboraration with Deezer. See the reports later on in this thread:

https://support1.bluesound.com/hc/en-us/community/posts/28168609313431-Upgrade-required-Deezer

To be clear in this (https://support1.bluesound.com/hc/en-us/community/posts/28168609313431/comments/28205009141271),

“Deezer has made some recent changes on their back end. In making those changes it is creating an issue with their existing supplied API to BluOS. The issue is not BluOS Version related as it occurs in our testing using older versions and is a change implemented at the Deezer end.”

The fix? Also mentioned in the Bluesound comment: “can <this> be resolved at the server end by Deezer alone or if they will require our intervention by making changes to BluOS.”

Deezer! Talk to Bluesound please.

Maybe I am looking in the wrong place, but I cannot find the Deezer API changelog. So the changes are secret?

Ik heb dit nu ook een aantal dagen. Vooral met nieuwe albums of artiesten. Ik heb een blousound node 130i.

Heb ook al contact gehad met het blousound team. Zij wisten ook niet precies waar het probleem lag, maar moet dit probleem ook melden bij Deezer. 

Yes the more we can highlight the issue with BluOS devices to Deezer, the more Deezer may be willing to work on fixing it with the Bluesound team. :)

Always good to remind Deezer that most of us are quite ‘locked in’ with Bluesound or BluOS.

While I am one of the biggest fans of Deezer and don’t want to jump, if this isn’t fixed soon my wife will forget that we even have Deezer in BluOS… as there are other options :)

Appears fixed for me this morning :)