starred/lox-audioserver

Fork 0

mirror of https://github.com/lox-audioserver/lox-audioserver.git synced 2026-04-26 06:45:47 +03:00

[GH-ISSUE #59] Music assistant: Filesystem media #20

New issue

Closed

opened 2026-02-27 19:27:57 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 19:27:57 +03:00

Owner

Originally created by @mr-manuel on GitHub (Nov 1, 2025).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/59

When using Music Assistant as backend then the media of the file providers Filesystem (local disk) and Filesystem (remove share) are not shown in the Loxone app. Would be nice, if we could also add them under the library in the app.

Originally created by @mr-manuel on GitHub (Nov 1, 2025). Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/59 When using Music Assistant as backend then the media of the file providers `Filesystem (local disk)` and `Filesystem (remove share)` are not shown in the Loxone app. Would be nice, if we could also add them under the library in the app. <img width="1030" height="215" alt="Image" src="https://github.com/user-attachments/assets/6d3aeb38-015f-458b-80f1-976a8dce8e55" /> <img width="1256" height="787" alt="Image" src="https://github.com/user-attachments/assets/393c8681-2ff2-4901-a8c2-a0d4411e4710" />

kerem closed this issue

2026-02-27 19:27:57 +03:00

kerem commented

2026-02-27 19:27:58 +03:00

Author

Owner

@mr-manuel commented on GitHub (Nov 1, 2025):

Local files are also shown as Spotify media, but are not found searching them. At least at the moment they can be added to the favorites.

{
  "id": 9,
  "type": 4,
  "start": 0,
  "totalitems": 1,
  "items": [
    {
      "id": 7,
      "slot": 1,
      "plus": true,
      "name": "Custom Audio File",
      "title": "Custom Audio File",
      "album": "",
      "artist": "",
      "audiopath": "spotify@filesystem_local--Y4q4pnTy://track/custom-audio/Custom Audio File.mp3",
      "type": "spotify_track",
      "coverurl": ""
    }
  ]
}

@mr-manuel commented on GitHub (Nov 1, 2025): Local files are also shown as Spotify media, but are not found searching them. At least at the moment they can be added to the favorites. ```json { "id": 9, "type": 4, "start": 0, "totalitems": 1, "items": [ { "id": 7, "slot": 1, "plus": true, "name": "Custom Audio File", "title": "Custom Audio File", "album": "", "artist": "", "audiopath": "spotify@filesystem_local--Y4q4pnTy://track/custom-audio/Custom Audio File.mp3", "type": "spotify_track", "coverurl": "" } ] } ```

kerem commented

2026-02-27 19:27:58 +03:00

Author

Owner

@rudyberends commented on GitHub (Nov 2, 2025):

Yes, the entire musicassistant library is shown under the spotify section. We just fake a spotify service, because it has more features than the NAS drive. So if you have both deezer and Apple Music active, both will still show up under spotify.

This is by design and I dont think rerouting the MA local media/shared folders to the Loxone local media/shared folders has any advantages.

Every MA provider does have its own specific uri scheme, however, so it could be that are issues with some providers, but that can be fixed. I mainly tested Apple Music, tunein and spotify.

I might move to faking a SoundSuit library instead of spotify because of the confusion. Just because you mainly use spotify, it might look it is specifically mapping spotify, but it is not. It maps the entire MA library using a faked spotify service. Only for radio we make an exception and route it to radio.

As for the search; Does it show up when you search in musicassistant web interface?

@rudyberends commented on GitHub (Nov 2, 2025): Yes, the entire musicassistant library is shown under the spotify section. We just fake a spotify service, because it has more features than the NAS drive. So if you have both deezer and Apple Music active, both will still show up under spotify. This is by design and I dont think rerouting the MA local media/shared folders to the Loxone local media/shared folders has any advantages. Every MA provider does have its own specific uri scheme, however, so it could be that are issues with some providers, but that can be fixed. I mainly tested Apple Music, tunein and spotify. I might move to faking a SoundSuit library instead of spotify because of the confusion. Just because you mainly use spotify, it might look it is specifically mapping spotify, but it is not. It maps the entire MA library using a faked spotify service. Only for radio we make an exception and route it to radio. As for the search; Does it show up when you search in musicassistant web interface?

kerem commented

2026-02-27 19:27:58 +03:00

Author

Owner

@mr-manuel commented on GitHub (Nov 2, 2025):

Thanks for the explanation. Indeed my tests track was the only one not indexed and all others are working. So yes, others are showing up in Loxone and Music Assistant.

In that case I would leave it as it is.

@mr-manuel commented on GitHub (Nov 2, 2025): Thanks for the explanation. Indeed my tests track was the only one not indexed and all others are working. So yes, others are showing up in Loxone and Music Assistant. In that case I would leave it as it is.

kerem commented

2026-02-27 19:27:58 +03:00

Author

Owner

@mr-manuel commented on GitHub (Nov 2, 2025):

I saw now, that eight of the Spotify icon you write Music Assistant in that case. Did not saw it before. This way it should be already clear.

@mr-manuel commented on GitHub (Nov 2, 2025): I saw now, that eight of the Spotify icon you write Music Assistant in that case. Did not saw it before. This way it should be already clear.

kerem referenced this issue

2026-02-27 19:28:34 +03:00

[PR #20] [MERGED] Beta #135

kerem referenced this issue

2026-02-27 19:28:34 +03:00

[PR #21] [MERGED] main #136