mirror of
https://github.com/lox-audioserver/lox-audioserver.git
synced 2026-04-26 06:45:47 +03:00
[GH-ISSUE #57] Media provider setup #18
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#18
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 @mr-manuel on GitHub (Nov 1, 2025).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/57
Just deleted the whole config, installed v3.0.0 but I'm unable to configure a Media Provider.
After selectiong Music Assistant and entering the IP there is no way it saves the new IP. After a few seconds it reverts to Dummy Provider.
@mr-manuel commented on GitHub (Nov 1, 2025):
If the Media Provider is configured the first time over a zone config, then it fills out the fields and the button changes, but it's still not possible to connect the provider.
@rudyberends commented on GitHub (Nov 1, 2025):
The web interface needs some attention. There are major changes in the code.
Just configure a zone. it will set it. It looks like it is not saved, but it is
@bogi9999 commented on GitHub (Nov 2, 2025):
Same problem here.
In the Zone setup a can choose a Sonos Player, but in Loxone the Player is shown as offline.
@rudyberends commented on GitHub (Nov 2, 2025):
There is not really a problem. If you configure your first zone, it asks if you want to use it as a media provider. This will be saved if you choose yes. It's just a quirk in the web interface
@bogi9999 commented on GitHub (Nov 2, 2025):
But exactly the same steps in 2.5.1 will work.
The Player is Online and works.
If i use 3.0 i can start the player in MA. In Loxone only - Offline -
@rudyberends commented on GitHub (Nov 2, 2025):
how does you config.json look like? You did start with a clean file?
@bogi9999 commented on GitHub (Nov 2, 2025):
I started with an complete new Installation on a new volume on my nas.
Also removed the devices in Loxone Before.
@rudyberends commented on GitHub (Nov 2, 2025):
Do you have access to the json file? What do you see in the debug logs? Does the player respond to volume up/down?
@bogi9999 commented on GitHub (Nov 2, 2025):
Actually i have no Access.
If the Player is offline it reponds to nothing.
In MA everything work.
@rudyberends commented on GitHub (Nov 2, 2025):
its a little difficult to troubleshoot for me when I dont have some clues on the configuration. You are able to access the web ports 7091 and 7095 in a browser? What do you see in the logs when set to debug? Maybe you can share it here?
@bogi9999 commented on GitHub (Nov 2, 2025):
i'am able to connect throug port 7090, 7091 and 7095.
On 7090 is the WebIf, 7091/7095 shows up
`{
"admin_result": [],
"command": "admin"
}
I've made a clean reinstall of the audioserver.
Added it in Loxone, paired it,
After that i added a extension, in the WebIf and in Loxone.
Provided the Serial, made an Audioplayer, saved it and waited for the ability to config it in the WebIf.
Did that and suddenly there is an other extension waiting to be configured in the WebIf with the same Serial.
Here is the complete Log for that.
@mr-manuel commented on GitHub (Nov 2, 2025):
For multi line code/log please add
~~~in the line before and after the code/log. That way it's nicely displayed.@rudyberends commented on GitHub (Nov 2, 2025):
I see there is a parsing issue. Not sure if it prevents it from running though. You have one player configured? I see an extension, so I assume more zones, but there is probably only one output place in your loxone config. For them to show up, you need to drag them to a room and attach a player block. Maybe you are only testing one zone for now?
@bogi9999 commented on GitHub (Nov 2, 2025):
I have only one player configured with the extension.
The Outputs of the Audioserver are not in Use.
@bogi9999 commented on GitHub (Nov 2, 2025):
Made a clean new setup.
Now i use the First Sereo Out of the AS.
But still the Same
@bogi9999 commented on GitHub (Nov 2, 2025):
thx
@bogi9999 commented on GitHub (Nov 2, 2025):
Also no.
@rudyberends commented on GitHub (Nov 2, 2025):
hard to say. from the logs everything looks fine. It receives state updates from musicassistant and you see the actual metadata in loxone. I think the loxone server is telling the client it is offline. Does it show online in loxone config?
@bogi9999 commented on GitHub (Nov 2, 2025):
After the third reboot of the miniserver, that litle bitch works.
But...
The first Icon is correct, the list isn't.
@rudyberends commented on GitHub (Nov 2, 2025):
no, you are right. its already fixed on the testing branch. I will push it to main soon
@rudyberends commented on GitHub (Nov 3, 2025):
should now be fixed in 3.0.1.
Your current favorites are broken. Even with the new version they will still show wrong information. Newly created favorites in 3.0.1 should be the correct type.
@bogi9999 commented on GitHub (Nov 3, 2025):
Problem with the MediaProvider still persists.
New Problem, TuniIn Radio Favorites disapeard and i'am not be able to search for RadioStations anymore.
@rudyberends commented on GitHub (Nov 3, 2025):
Yes, I did not fix that yet, I was referring to the favorites issue where they are all the same type.
Just to keep things clear, let's keep this one for the provider issue. Please report other issue separately.
@Lorrentop commented on GitHub (Nov 17, 2025):
I have the same problem with the MediaProvider. I cannot make changes to Music Assistant. It does not save to the JSON and the button stays on “fill in required fields.” When I open my zone adapter and select MA it stays stuck on “scanning player.” I can access MA and everything works manually through MA.
Edit:
After multiple attempts, restarts, and deleting the config, it finally accepted the music provider for MA. Selecting the adapter and scanning players still does nothing.
@rudyberends commented on GitHub (Nov 17, 2025):
it should work, but the web interface needs some attention.
If you clear the config, and start with a zone by selecting musicassistant and setting it up, it will ask you if you also want to use it for mediaprovider. Using it this wat should allow you to set it up.
I will fix the web interface so this will work as it was intended.
@behesse commented on GitHub (Dec 25, 2025):
I can connect to Music Assistant. But when trying to assign a player to a zone "Scanning" seems to not work at all.
@rudyberends commented on GitHub (Dec 26, 2025):
That release has some issues with its web interface. I will release a new one very soon. for now, try it like this;
If you clear the config, and start with a zone by selecting musicassistant and setting it up, it will ask you if you also want to use it for mediaprovider. Using it this wat should allow you to set it up.
@rudyberends commented on GitHub (Dec 29, 2025):
fixed in 4.x release