mirror of
https://github.com/lox-audioserver/lox-audioserver.git
synced 2026-04-26 06:45:47 +03:00
[GH-ISSUE #94] 3.1.0 not working anymore - after the new MA 2.7.0 release today. #42
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#42
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 @simon2207 on GitHub (Dec 18, 2025).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/94
Unable to run 3.1.0 anymore.
Last night Music Assistant got its new release 2.7.0 and now I m unable to run/open Lox-Audioserver Webinterface. Audioserer is down in Loxone as well.
Even after new install - the issue persists.
Kind Regards
Simon
@mr-manuel commented on GitHub (Dec 18, 2025):
See also https://github.com/rudyberends/lox-audioserver/issues/88
@simon2207 commented on GitHub (Dec 18, 2025):
@mr-manuel thanks - but it seems that there is no solution for that...
@rudyberends commented on GitHub (Dec 18, 2025):
The new Music Assistant version introduces a completely different state API and adds authentication to the API.
The upcoming lox-audioserver release will address this, but it is not ready for release yet. I moved too quickly with earlier releases, and each time I ran into architectural issues that required significant revisions. This time, I want to take the time to get the architecture right before publishing a new release.
In the meantime, to keep everything functional, you can stay on the older Music Assistant version.
I will try to have a test version ready this weekend.
@simon2207 commented on GitHub (Dec 19, 2025):
@rudyberends Thx rudy - went back to MA 2.6.3 and will wait over the weekend to get on the testing branch and MA 2.7.x. THANK YOU VERY MUCH!!!
@tobsch commented on GitHub (Dec 22, 2025):
you're the best, @rudyberends! hopping on the rolling train with this fix finally.!
@DiskoDisko404 commented on GitHub (Dec 22, 2025):
Thanks for this
One of the best plugin so far!
I hope the next fix, fix this problem
@DiskoDisko404 commented on GitHub (Dec 27, 2025):
Is the release ready ? :)
@wiking-at commented on GitHub (Dec 28, 2025):
i suppose this is why I couldn't find any MA devices to connect the zones to. I'm looking forward to trying out this project when the connection is fixed. thanks for your work rudyberends .
@simon2207 commented on GitHub (Dec 29, 2025):
hey @rudyberends would love to get some infos on the testing branch, as I would like to use some of those new features in my household during new years eve... any chance? Kind regards Simon
@rudyberends commented on GitHub (Dec 30, 2025):
I’m still a bit hesitant to post this version here, because in its current state it may introduce more new issues than it actually resolves. As long as it’s clearly understood for what it is — a test version — I’ll go ahead and share it anyway. Testing does help to surface the remaining issues.
This new version is fully capable of emulating the Loxone Audio Server on its own. If you require additional services, Musicassistant is available as a bridge provider. The new release only support MA 2.7 or newer.
@DiskoDisko404 commented on GitHub (Dec 31, 2025):
Greatful News!!! Thanks for that
How can I install the new version? Or is it not yet online?
@rudyberends commented on GitHub (Dec 31, 2025):
There is a separate testing branch that contains the upcoming 4.x version. If you run it standalone, you need to checkout the testing branch.
This branch also automatically builds a new Docker image on every commit, published with the :testing tag.
If you are using Docker, you can simply run the testing image:
This will always pull and run the latest testing build.