Samsung Multiroom App Feedback: login and other issues

Hi there @Kierran 

Thanks for the feedback, apologies for the experience. Please see above 

Really sorry to hear that @heille1221 @Bosmaneelco 

But we completely agreed with you on this. If it serves of consolation, our big focus for 2021 is to address issues with connectivity, including this one. We want to focus less on new features and actually make the apps more robust and reliable. Please check back in the new year, we hope to give you a better streaming service 

Situation is really unacceptable !

“Press:  July 2018 – Samsung Electronics Co. announced the addition of Deezer High Fidelity Lossless Audio on select Samsung soundbars and wireless speakers. As of today, music fans and audiophiles can stream music and listen to tracks the way it was originally intended.”

Two years later and the system is completely broken. I have not been able to listen to any music for months.  You would expect close relationship within this partnership between on R&D and Customer Support and that happy customers are valued by both companies.

Very, very disappointing from both !

​Any news on that?

What have you done in the meantime?

Months/years ago someone posted this (sounds valid):

So, I’ve just recently encountered the ID login error, now coming up without fail, making it impossible to use on my Samsung K950 soundbar. This is a bummer of note, as I used to use it to play FLAC’s from Deezer. I can still use bluetooth, but the quality is absolutely abysmal.

I’ve gone through all the loops of uninstalling, re-installing, rebooting & resetting all devices involved, as well as the password itself to no avail.

I did some more digging, and it turns out the Multiroom app doesn’t connect to Deezer (or any of the other integrations) itself. Instead, it simply sends instructions to the soundbar, which is meant to connect to Deezer. Thus, all the connection logic sits on the soundbar (which actually runs an Express HTTP server), and not in the app.

I used some packet capturing to inspect the flow of request/responses between the app and soundbar while trying to login to Deezer, and noticed that the error message that we get (incorrect ID/password) is probably not correct.

The response that the soundbar sends back to the app when I get the error is the following:

<?xml version="1.0" encoding="UTF-8"?><CPM><method>SignInStatus</method><version>0.1</version><speakerip>192.168.0.104</speakerip><user_identifier>public</user_identifier><response result="ng">
 <cpname>Deezer</cpname>
 <timestamp>2020-05-07T22:33:43Z</timestamp>
 <errmessage>No connection to Internet, please check it.</errmessage>
 <errcode>71</errcode>
 <category isroot="1"></category>
 <category_localized></category_localized>
 <root>Playlist Picks</root>
 <root_index>2</root_index>
 <root_localized>Playlist Picks</root_localized>
</response>

As you can see, the actual error message is “No connection to Internet, please check it.”, so it doesn’t seem like it even got as far as submitting the login credentials to Deezer.

What is odd, is that the soundbar definitely does have internet connectivity, as it can stream from TuneIn perfectly. Maybe that error message is also bugged.

I was going to say that this could hint towards a Deezer problem (maybe the authentication hostname was changed, or something to do with SSL certs).

But then I tried Tidal and also got the same error on the surface. The underlying response was a bit different though:

<?xml version="1.0" encoding="UTF-8"?><CPM><method>SignInStatus</method><version>0.1</version><speakerip>192.168.0.104</speakerip><user_identifier>public</user_identifier><response result="ng">
 <errmessage></errmessage>
 <errcode>50</errcode>
 <cpname>Tidal HiFi</cpname>
 <category isroot="1"></category>
 <root>New</root>
</response>

Since both Tidal and Deezer attempts result in the same surface level error, I think we can at least assume that the “ID or password is incorrect” message is some kind of generic catch all error message, and not necessarily a reflection of the validity of the provided login credentials.

All in all, this doesn’t solve the problem, but it does indicate that if the issue is on Samsung’s side, it isn’t in the Multiroom app, but rather in the speaker firmware itself.

If it is really a connectivity issue, that could explain why the error is sporadic for some people. It could potentially be some service that doesn’t always start up properly which is needed to facilitate communication Deezer.

For Deezer people, can you provide the authentication endpoint that the Samsung firmware is meant to hit?

​

So keep us updated, please.

And who of you still believes after several months of no progress, that this issue is ever getting fixed?

This is not too good reviews on deezer. I have already signed up with Spotify but still holding onto my deezer account, hooing you will find a solution soonest

doesn't work on my systems as well. 

So I still think, this will never get fixed. Anyways, my Premium subscription is cancelled and I am happy with Spotify. Deezer, you lost me as paying customer because of this. 

Thank you for the feedback @t1no @Ripperoo I'll report it on.

One step at a time and we'll get these issues sorted. You deserve much more from us 

Well, believe it or not it is now working again!!!!!

My Samsung R3 has now connected again to Deezer. Finally!!!!!

Not sure whether Samsung or Deezer sorted it out ... but thanks.

Another 20 days on a topic that’s a problem for such a long time - and still not a single solution or pro-active feedback.