Skip to content

v2026-06-09

Choose a tag to compare

View all tags
@SofusA SofusA released this 09 Jun 12:34
v2026-06-09
4ab737d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Disconnect

This release brings a self-hostable Connect feature called "Disconnect".

You can host the server yourself, or you can use my public at: https://qobine-disconnect.sofusconnect.addington.dk
Please don't abuse it 😄

Currently only the RFID and the web projects are supported. Support for the TUI and the GTK players are coming.

How to use:

When running the web or rfid project provide the following flags:

      --disconnect-device-name <DISCONNECT_DEVICE_NAME>
          Disconnect device name
      --disconnect-password <DISCONNECT_PASSWORD>
          Disconnect password
      --disconnect-server-url <DISCONNECT_SERVER_URL>
          Disconnect server url

eg: qobuz-player-web --disconnect-device-name livingroom --disconnect-password very-secret --disconnect-server-url https://qobine-disconnect.sofusconnect.addington.dk

Now when you open the web ui, you will be able to see a music note icon, where you can select all running clients (web or rfid) with the same password.

Why not Qobuz connect?

Good question.

I am still interested in using the official Qobuz Connect, but the protocol is undocumented, and generally not fun.
But most of the improvements done here is required for Qobuz Connect to control, activate and deactivate a player (client).

Qobuz Connect would also allow us to use the official smartphone app for controlling.
I personally don't use the official app, so this is not compelling for me.

Feedback

Please please give this a try and give me feedback.
I found building this quite fun and learning.

And as always feel free to provide feature requests or contributions.
I always prefer issues before pull requests.

Assets 33
Loading