include
Answered

Help blocking songs / artists from playing through Sonos/Alexa

  • 22 January 2024
  • 5 replies
  • 52 views

Please help!

I have a Sonos Roam with in built Alexa. I’ve linked Sonos to my Deezer account. I’ve blocked explicit content via Deezer app, but there are songs which are inappropriate which my 5 year old takes great joy in requesting. Please can you show me how I can block certain artists/songs from being played through Sonos when asked by Alexa.

example: Willy Willy by Lola Lee. (You can see where this is going…) I have gone to the artist page and in top right clicked the three dots and clicked ‘Don’t recommend this artist’. It still plays when requested through Sonos via Alexa. 

please help!

Sincerely,

A desperate dad

 

icon

Best answer by awesomemac 22 January 2024, 21:46

View original

This topic has been closed for comments - the content may no longer be relevant or up-to-date, so please search for keywords so that you can find a newer post or look below for a direct link

5 replies

Userlevel 7
Badge +12

 

Hi @chocobear !

 

Here is link How to filter explicit content on Deezer

iOS

 

Go to Settings Settings.png

  1. Select Explicit content
  2. If you want to disable explicit content, select Hide explicit content Slider.png. Any explicit content will be made grey and unplayable

    Note: This filter prevents content from appearing in searches, Flow or recommendations. All cover art tagged as explicit will also be hidden.

    If you still want to search and play explicit content, select Do not recommend explicit content Slider.png, which will stop explicit content from being recommended in your Flow and mixes.

    Warning: You must first select Do not recommend explicit content before you can select Hide explicit content, which prevents explicit content from being recommended, playable or searchable

here is link

https://support.deezer.com/hc/en-gb/articles/360000590898-Explicit-Content

 

Hi @chocobear !

 

Here is link How to filter explicit content on Deezer

iOS

 

Go to Settings Settings.png

  1. Select Explicit content
  2. If you want to disable explicit content, select Hide explicit content Slider.png. Any explicit content will be made grey and unplayable

    Note: This filter prevents content from appearing in searches, Flow or recommendations. All cover art tagged as explicit will also be hidden.

    If you still want to search and play explicit content, select Do not recommend explicit content Slider.png, which will stop explicit content from being recommended in your Flow and mixes.

    Warning: You must first select Do not recommend explicit content before you can select Hide explicit content, which prevents explicit content from being recommended, playable or searchable

here is link

https://support.deezer.com/hc/en-gb/articles/360000590898-Explicit-Content

Thanks, but I’ve already done that. There are songs & artists that aren’t classified as “explicit” but aren’t appropriate. There is hopefully a way I can block those?

Userlevel 7
Badge +5

Hi,

I took a look at the Sonos app, but I’m afraid that it isn’t possible to block explicit songs.

According to the website of Sonos, this is only available with Apple Music, YouTube Music and Amazon Music:

https://support.sonos.com/en-gb/article/filter-explicit-content-on-sonos

(My screenshot is in Dutch)

 

Userlevel 7
Badge +12

 

 Oh , I see @chocobear 

There is one more way ...

You can disable artist which are not appropriate to you if  you go to artist page and then click on 3 dots to open window and choose  Don’t recommend this artist 

 

but like you said that does not work ...I don’t know why 

 

 

Thanks all.  Doesn’t look like this can be solved which is a real shame and I can’t believe I’m the first to report this.

So is this a Deezer issue, a Sonos issue or an Alexa issue?

I’ve spoken to Sonos and like @awesomemac says, they can only block through Apple Music, Youtube Music & Amazon Music.

Next stop Alexa, but I feel like this is the least likely to provide a solution.

Can I log an improvement request here for this to be solved?