Samsung Multiroom App Feedback: login and other issues

Rudi will you find a solution or do I have to go to Spotify as well?

Hi there @Gazturner @Gaston @Raun 

Thanks for the feedback. Apologies if you misunderstood my intentions - of course we notify Samsung about this and other issues 

We're on the same side as you, to be entirely honest. We have pushed Samsung about this every single time someone here posts a bug on their apps. I personally created several bug reports about this for over 1 year. You can see this in the pages of this and other threads. It's always forwarded to them and it isn't about blame, but ownership. Perhaps my own frustration of a community manager that wants to help more but has his hands tied took over my previous reply 

But that's all we can do really. Gather all the feedback and info from you, create a report using our internal systems and contacting the devs responsible for this API integration. Then all of it is forwarded to Samsung, the developers of the app.

By the way, our API is available for any developer who wishes to integrate Deezer within their system. For more info, please see here 

Hi @GaynorJ I believe my colleague Esther was referring to Samsung.

Hey @Emma1975 we're unable to fix an app which isn't developed by us, only our API. But your feedback is surely appreciated and will be forwarded to the relevant teams here at Deezer.

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?

Hi  Emma, 

Not just using TV Soundbar, the group was centred on that. 

Whole group is still working at the moment.... 

Fingers crossed it will stay that way. 

That looks nothing like my multiroom app.

Same here

Thanks, @Ripperoo and all for your patience and feedback. We're working on getting this clarified with Samsung. Please accept our apologies for any inconvenience caused 

Did all that still not working?  The all devices thing is interesting.. how do you know. TVs etc.