Connecting third-party apps
Jellyfin-compatible apps
Section titled “Jellyfin-compatible apps”Use this server address, with /j and no trailing slash:
https://your-lumastra-instance.example.com/jNo separate Jellyfin server is required. Generate a dedicated client password rather than using your browser login password:
- Sign in to Lumastra in your browser.
- Open Settings → Connections and select the Jellyfin card to open Connect a Jellyfin app.
- Select Generate password and save it; it is shown only once.
- Enter your Lumastra username and that password in the Jellyfin app.
Reset the password from the same page. Clients with Quick Connect can instead pair by code: approve the client’s code in Connect a Jellyfin app under Settings → Connections, or through a Quick Connect footer link if your admin added one.
Library browsing, search, playback, progress sync, ratings, favorites, and configured Live TV are supported. Watch Together and server administration are unavailable through Jellyfin-compatible apps.
A Jellyfin app’s remote control can control the Lumastra devices on your own account. The Lumastra remote can in turn control Jellyfin clients that announce remote control, with basic transport, starting playback and messages. See Remote control.
Concurrent streams
Section titled “Concurrent streams”Two concurrent /j streams are included across the whole server. A third video
stream plays a limit notice; music clients show an error. Stale sessions release their
slots after a couple of minutes. Lumastra’s web, iPhone, iPad, and Apple TV apps don’t
count towards this limit.
Additional /j streams belong to the supporter module, free during early access; see
Editions & Licensing.
Token access
Section titled “Token access”For automations, use a PAT with jellyfin_compat or jellyfin_compat_read from
Users & Sessions → API tokens. These scopes work only with /j; ordinary
read/write/admin scopes don’t grant /j access. Seerr setup wizards using
/j/Auth/Keys receive a PAT automatically.
Subsonic music clients
Section titled “Subsonic music clients”Your administrator must enable OpenSubsonic compatibility first.
-
Sign in to Lumastra, open Settings → Connections, and select the Subsonic music apps card.
-
Select Generate token and save it; it is shown only once.
-
Enter these values in your music app:
Field Value Server URL https://your-lumastra-instance.example.comUsername Your Lumastra username Password The generated token; display spaces can be omitted.
Standard clients append /subsonic/rest/ themselves. Use token authentication when the
client offers it; password mode also accepts the generated token. Apps supporting the
OpenSubsonic apiKey extension can use that token as their API key.
Browsing, search, streaming, transcoding, playlists, bookmarks, queues, scrobbling, favorites, and ratings are supported. Internet radio, podcasts, jukebox, and sharing aren’t implemented.
Lumastra’s Sound Search, Music Map, Song Paths, Mixing Desk, personalised discovery rows, and smart queue stay in its own apps. Scrobbled plays from Subsonic apps still feed your listening history and recommendations.
TV apps and device-authorization login
Section titled “TV apps and device-authorization login”Native Lumastra apps and other clients supporting device login show a code or QR code. Open the displayed address in your browser, sign in, and approve the code. The app completes login automatically.
For client implementation, see OAuth device-flow clients and Building a player.
Connection problems
Section titled “Connection problems”Ask your administrator to check these if a client cannot connect:
| Symptom | Check |
|---|---|
/j returns 404 | Jellyfin compatibility is enabled (FEATURE_JELLYFIN_COMPAT). |
| Subsonic is unavailable | FEATURE_SUBSONIC_COMPAT=true; it is off by default. |
| Client receives a browser login page | The proxy must bypass forward auth for /j/ or /subsonic/; clients authenticate their own requests. |
| Device login fails | Device auth is enabled; /oauth/ and /api/v1/ bypass forward auth while /device remains protected. |
| Subsonic connects but shows an empty library | The proxy must preserve query strings, including empty searches used by some clients to index the library. |
Proxy configuration is covered in Authentication and Single sign-on with Authentik.