mirror of
https://github.com/lox-audioserver/lox-audioserver.git
synced 2026-04-26 06:45:47 +03:00
[GH-ISSUE #95] Filesystem media not displaying in AudioServerLibrary #44
Labels
No labels
bug
enhancement
pull-request
released
released on @beta
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lox-audioserver#44
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @betadriver1995 on GitHub (Dec 28, 2025).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/95
When I add a shared or local folder wihtin MA (v2.6.3) it does not show up as a library within the Audio Server Zone.
@rudyberends commented on GitHub (Dec 29, 2025):
Music Assistant aggregates many services into one library. That full library is exposed in Loxone under a single "Music Assistant" Spotify account.
New release will support local library on its own. the ma library will be unified with all other services (except radio) under the music assistant spotify account
@betadriver1995 commented on GitHub (Dec 29, 2025):
Ok. So you extend your project to add a media library instead of adding it in MA and therefore it shows emulates a library in loxone audio zone?
@rudyberends commented on GitHub (Dec 29, 2025):
Yes, I’m extending the project to include a local media library in the next release. However, also in the current release, Music Assistant (MA) is not mapped to the Loxone local media library.
Music Assistant maintains its own concatenated library. You can add an Apple Music provider, a Spotify provider, and a local filesystem library, and all of these are merged into a single MA library. That is simply how MA works. This entire combined library is then exposed by lox-audioserver as one Spotify account, meaning all MA-enabled providers appear together there.
With the new release (and enabled by MA 2.7), there are options to split services, allowing you to separate them logically. Even then, they are still presented to Loxone as fake Spotify accounts.
If there is demand, we could map the local library to the Loxone local media library, but I don’t think that adds much value. You can just as easily point Loxone to the same network share, and the media will already be available there.