-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can no longer login to Qobuz #247
Comments
Same here! |
I'm afraid we are no more allowed to use their API (our key seems revoked, the API has changed and the API documentation has been removed from their public repository). |
I sent them a complaint requesting them to refund my subscription. In one hand they state Qobuz is compatible with Kodi on their Web site, and on the other hand, they remove access to their API. Hope this make them react... |
Bonjour, j'ai évidement le même problème. Je pense que nous devons être beaucoup dans ce cas !!! Je pense que beaucoup d' abonnements grâce a votre addon, ont dus être engrangés. Ils ont fait la même pour l'api Qobuz de volumio, ou du jour au lendemain : - https://forum.volumio.org/qobuz-temporarily-not-working-from-t12936.html |
Same here. They are still listing Kodi on their hompage to be compatible software. Asked them for refund. Let's see what will happen... |
Short update, they (Qobuz) stated that there's presently a risk of hacker attacks and therefor they decided to ban the Kodi qobuz plugin for now. They also stated that they are in talks with Kodi to fix the issue. |
From Qobuz:
|
they deleted the kodi compatible app on their site ... |
On my side, answer from qobuz : "Nous vous invitons à utiliser des systèmes de streaming plus officiels." Translation : We invite you to use more "official" streaming systems. In other words, they are not able to provide a solid, protected API that would be consumed in any environment. Thinking about canceling my subscription. |
We should not cancel our subscription but force them to provide am API
secure enough for Kodi as they did state that they were compatible...
Le mer. 9 oct. 2019 à 12:16, Florent <[email protected]> a écrit :
… On my side, answer from qobuz : "Nous vous invitons à utiliser des
systèmes de streaming plus officiels." Translation : We invite you to use
more "official" streaming systems. In other words, they are not able to
provide a solid, protected API that would be consumed in any environment.
Thinking about canceling my subscription.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#247?email_source=notifications&email_token=AE6LTHT5GS2FIH6HZEZ5LRDQNWVQHA5CNFSM4I5FSWOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAXMTWQ#issuecomment-539937242>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AE6LTHVNKVP3XUT4NYL5E7TQNWVQHANCNFSM4I5FSWOA>
.
|
my answer from support :
I think they identified the bug where we could stream directly (ie. mplayer.) on urls 's like : Now I can download a data file but it doesn't look valid, it seems to be a partial file or something like that.
The communication of qobuz seems strange, they remove on the site the fact that qobuz works on kodi/osmc but they still seems to want to work to solve this incident. @tidalf Are you in contact with them as the volumio developers were? Do they really care about alternatives platforms usage ? |
I'm waiting for an answer :) And yes usually they care. |
Any news about this issue ? |
I have the same issue, contacted the Qobuz customer service and they just replied the same thing as mentioned above :
I was just inquiring if there were exchanges going on with qobuz/kodi addon team. No answer to that. |
Quobuz said to me it was up to the developers of the opensource integration to take care of the API keys and refrain from getting it stolen and not to them to provide some other API architecture. So for me it does mean a simple thing : deadlock. |
It means we have to find a way to use the Qobuz API keys, in an open source project, without exposing it to the public.
The only safe way I see could be to store the Qobuz API key online, and allow the Qobuz plugin to retrieve it (It has to remain secure in memory unitl plugin restart). We still need some magic to authenticate the Qobuz plugin to the online store but I'm sure it is doable.
That would also permits to:
|
Any news on this? I was wondering if we could switch to user provided API key but I cannot even find anymore Qobuz API documentation. |
Hi ! here is Qobuz's answer that I received last week : We must therefore forget the current add-on and hope that Qobuz develops its own add-on for Kodi |
Got the same response. That's too bad, off I go. |
Imho best is to disable your Qobuz account and tell them why: that you love to have a working Qobuz add-on and that you hope that Qobuz will provide one for Kodi in the near feature. |
As a workaround, I found that BubbleUPnP can still be used to stream Qobuz to an OpenHome renderer and to create said OpenHome renderer on top of a DNLA client. I’m running a Kodi DNLA music server and a BubbleUPnP server on my Mac, and its easy to use an OpenHome control point like Linn Kazoo to switch between playing a Qobuz stream and playing my own music from Kodi on any of my renderers (Volumio, MoOde, Denon HEOS). I realize this work around gives no satisfaction to all of the hardworking folks who developed the Qobuz add-on for Kodi. But it’s an option for anyone who wants to stream Qobuz to a DNLA renderer, as once was possible using only Kodi, without resorting to a paid proprietary device or service (e.g. Roon). Details for configuring BubbleUPnP to stream Qobuz are available from https://www.hifizine.com/2019/07/stream-qobuz-to-anything/ |
Hi,
Since yesterday the plug-in is no longer accepting my credentials to login.
I even set up a new temporary account with Qobuz and tried those credentials.
Still doesn’t work.
I wonder if this is happening for all users of this Qobuz plug-in
Thanks
Geofstro
The text was updated successfully, but these errors were encountered: