Answered

Yamaha R-N303-D does not connect to Deezer

  • 16 June 2019
  • 5 replies
  • 49 views

Hi,
I have allowed any traffic from my new R-N303-D to the internet.
I entered full deezer credentials (of web.de 3 month prbationary account) into Yamaha's "Music Cast" set-up screen for deezer, and I alway get "Zugriffsfehler
Es ist ein Verbindungsfehler aufgetreten" after about 30 to 40 seconds.
I have not set up any different way to access deezer (not on my PC, not on my smartphone), I only want my Yamaha device to work with it. There is no firmware update pending, so it should work!
Many thanks in advance,
Mark S. Fischer
icon

Best answer by Alessandra.Deezer 30 June 2019, 18:38

Hey @msf2 ! Thanks a lot for the further info. I am afraid this is a bug we are aware of 😕 Please follow this thread and all troubleshooting suggested 😉
View original

5 replies

Userlevel 6
Badge +4
Hey @msf2 ! Can you make sure you have the latest firmware? Please let us know! 🙂
I checked that this is a brand-new model and Yamaha does not provide firmware updates yet (see https://de.yamaha.com/de/products/audio_visual/hifi_components/r-n303d/downloads.html).
Userlevel 6
Badge +4
Hey @msf2 ! Thanks a lot for the further info. I am afraid this is a bug we are aware of 😕 Please follow this thread and all troubleshooting suggested 😉
Many thanks, Alessandra,
but if this is a known bug I would rather expect an explicit solution, not a redirection to a 45 post long story of suggestions and new questions. Moreover, the thread you are pointing to is about intermittent drop-outs during listening (after successful connection and start of listening), which is not my case. I am experiencing a different error: my device can not connect, not even a first time. There has never been a sound from my device from Deezer.
Userlevel 6
Badge +4
Hey @msf2 ! According to what you wrote in your very first post (I alway get "Zugriffsfehler Es ist ein Verbindungsfehler aufgetreten" after about 30 to 40 seconds) I interpreted the issue as the same as the one I mention, this is the reason why I suggested you to check that thread.

If you actually mean that during those 30-40 minutes nothing happens, this was not really clear I'm afraid. However, according to our protocol we always need to suggest basic troubleshooting and see if it helps - and sometimes it does :)

We haven't heard anything new from our developers yet, but as soon as we do, we'll update everyone on the topic I suggested. In the meantime please make sure you check and follow all suggestions you find there. I apologise for the inconvenience and I hope the issue will be resolved soon 🙂

Reply