Samsung Multiroom App Feedback: login and other issues

Hi there @Jonathan Roy @papasof @papasofetal 

Sorry that's happening and you still have problems. But after several attempts, we currently don't have the support of Samsung on this issue. Please note that the Samsung Multiroom app isn't developed by us and you may have more support from their side.

Hi there @Marco O 

Our developers attempted to work in conjunction with Samsung on this - but it wasn't possible. Deezer isn't responsible for developing this app, so we're unable to move things forward. Thank you for your support and understanding.

Hi there @Marco O 

Thanks for coming back. We haven't had updates from Samsung at the moment.

However, I've tried to have a brief look at your account and I couldn't find a Deezer account linked to the Gmail email you used here in the community. So I suggest you check your credentials, your account could be linked to another email address 

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?